send feedback

❮ Previous Next ❯

IFS Baseline Apps Installation Guide

Install the IFS baseline apps

This guide explains how to install the IFS baseline apps.

Prerequisites:

IFS is installed.
Mobile Enterprise Platform Version 9.0 SP10 or later is installed.
Mobile Enterprise Platform is configured to integrate with your IFS system.
All required IFS functions are installed. Refer to IFS functions for baseline apps.

To install the IFS baseline apps, complete the following steps.

Download and extract the contents of the zip file containing the app package files to a folder of your choice.
In Advanced Inventory Platform Manager, import the IFS_TextStrings_en.xml localization file. Refer to Import language text.
In Advanced Inventory Platform Manager, for each app that you want to install, upload the associated promotion package, such as _IFS_ADCFBASE_IN_COUNT.package. Refer to Upload a promotion package.
In Advanced Inventory Platform Manager, register the required IFS functions.
- For a list of the functions required for each IFS app, refer to IFS functions for baseline apps.
- For steps to register a function, refer to Register IFS functions.
In Advanced Inventory Platform Manager, publish the apps. Refer to Publish an app.

Import language text

Language text strings (including user-defined text) can be imported from language text files (for example, dsicfgLanguageText_en.xml) from one Mobile Enterprise Platform 7+ instance to another.

To import a language text file, complete the following steps in Platform Manager.

Go to Admin > Configuration > Localization.
Select Import Language File.
On the Language Text Import page, select the language text file to import.

Step Information

Note:For a Mobile Enterprise Platform English-only release, only English is available.
Select Upload.

Expected Result

Result: The Language Items Conflict dialog box displays to show any differences between the text strings and text IDs.
For each Element ID, evaluate the text strings and select one of the following options.
- To select all current elements, under Current, choose the first radio button.
- To select all new elements, under New, choose the first radio button.
Select Save.

Upload a promotion package

Uploading a promotion package retains the version numbers of the app and its related items. The promotion package has a manifest that contains referenced items and their versions.

Note:Starting with version 9.5 SP4, the app promotion process speed has improved up to 15% faster than previous versions. Please contact your Cloud Inventory® representative to discuss upgrade options.

Prerequisite: The promotion package you want to upload must exist as a file with the .package extension.

To upload a promotion package, complete the following steps in Platform Manager.

Go to Develop > Application Studio.
Select Upload > Promotion Package.
Optional. For Promo Package ID, enter an ID.
In the Upload Promotion Package dialog box, select Choose File.
Select the .package file that you want to upload and select Open.
Select OK.
If the Items Conflict dialog box displays, some of the promotion package items already exist in the target instance of Mobile Enterprise Platform. To specify how to handle each conflict, complete one of the following actions.

Step Information

Note:For a user with a non-development license and pristine items, only device database tables will display.

Important:We recommend that you verify each item before you select Replace. If an item is used in an app, and you replace the item with the wrong version, it may result in the app no longer functioning.
- For each item you want to keep, select Keep. The item maintains the current version number.
- To keep all items, in the header row, select Keep. The items maintain their current version numbers.
- For each item you want to replace, select Replace. Replacing a item will increase the version number of that item.
- To replace all conflicting item, in the header row, select Replace. Replacing items increases the version numbers of those items.
Expected Result

Result: If a device database table is part of the project upload, the system prompts you to provide additional information, such as the source and middle-tier connection strings, and to indicate whether to include the data replication schedules. If you specify to replace a device DB table, the system deletes the existing table and its data, and then recreates the table. This action cannot be undone.
When all selections are made, select OK.
If the Style Group Selection dialog box displays, the uploaded promotion package includes a form that does not reference a style group. This dialog allows you to select a style group for each form included in the promotion package.

Step Information

Note:This conflict happens only for packages created prior to 8.1 SP2 and if the target system contains more than one style group.
Select OK.

Register IFS functions

Registering functions provides access to the functions to be called in apps. A function can be registered any time, but it must be registered before creating an app that uses that function.

Prerequisites: Before registering an IFS function, the Procedure Connector for Oracle must be set up. For steps, refer to Configure the Procedure Connector for Oracle.

To register a function to the Procedure Connector for Oracle, complete the following steps in Advanced Inventory Platform Manager.

Go to Develop > Connectors.
Select Procedure Connector for Oracle.
If your system uses more than one environment, select your desired environment.
On the Registered Functions page, select Register New Function(s).
On the Find Package page, for Schema, select the appropriate schema.
For Package, enter a package to filter the list of functions to be registered.
Select Next.
On the Select Functions to Register page, select each function you want to register.

Step Information

Note:For a list of functions required by each app, refer to IFS functions for baseline apps.
Select Finish.
When all functions are registered, select Done.

Postrequisite: After a function is registered, it can be tested using the Test tool for that function on the Registered Functions page. Refer to Test functions.

IFS functions for baseline apps

Most IFS baseline apps require that one or more associated IFS functions are installed and registered on your instance of Mobile Enterprise Platform.

Count Per Count

ESI_MEP_REV2_API.COUNT_REPORT_MEP

Posts the count to the specified Count Report.

Count Per Part

ESI_MEP_REV2_API.COUNT_PER_PART_MEP

Posts the count to IFS.

Customer Order Deliver

ESI_MEP_API.CO_DELIVER_ORDER_MEP

Posts the delivery to the specified Customer Order.

Customer Order Pick from Pick List

ESI_MEP_API.CO_PICK_PICKLIST_MEP

Posts the pick to the specified Customer Order Pick List.

Customer Order Pick

ESI_MEP_API.CO_PICK_MEP

Posts the pick to the specified Customer Order.

Move Inventory Part

ESI_MEP_API.INV_CHANGE_LOCATION_MEP

Posts the part movement.

ESI_MEP_API.GET_PART_FROM_SUPPLIER_PART

Retrieves the part number that is associated with the supplier part number.

Purchase Order Inspection

ESI_MEP_REV2_API.PO_INSPECT_MEP

Posts the approved quantity to the purchase order.

Purchase Order Move to Stock

ESI_MEP_API.PO_MOVE_TO_STOCK_MEP

Posts the purchase order to warehouse inventory.

Purchase Order Receive

ESI_MEP_API.PO_RECEIVE_MEP

Posts the purchase order arrival to the receiving location.

Report Shop Order Operation

ESI_MEP_API.SO_OPERATION_REPORT_MEP

Posts the operation report to the specified Shop Order.

Shipment Pick from Pick List

ESI_MEP_REV2_API.SHIP_PICK_PICKLIST_MEP

Posts the pick to the specified Shipment Pick List.

Shipment Pick

ESI_MEP_API.CO_SHIPMENT_PICK_MEP

Posts the pick to the specified Shipment.

Shop Order Issue from Pick List

ESI_MEP_API.SO_ISSUE_PICKLIST_MEP

Posts the part issue to the specified Shop Order Pick List.

Shop Order Issue

ESI_MEP_API.SO_ISSUE_MEP

Posts the part issue to the specified Shop Order.

Shop Order Receive

ESI_MEP_API.SO_RECEIVE_MEP

Posts the part receipt to the specified Shop Order.

ESI_MEP_API.GET_NEXT_SERIAL_NO

Retrieves the serial numbers currently used for the selected part.

Shop Order Reserve

ESI_MEP_API.SO_RESERVE_MEP

Posts the part reservation to the specified Shop Order.

Work Order Issue

ESI_MEP_REV2_API.WO_MAT_ISSUE_MEP

Posts the part issue to the specified Work Order.

Work Order Report Time

ESI_MEP_REV2_API.WO_REPORT_TIME_MEP

Posts the time report to the specified Work Order.

Publish an app

App publishing is the process of validating and generating a version of the app that devices can execute. The publishing process must validate all app references, formula usage, and environment-sensitive data. After the publishing succeeds, a device app file is produced. The app file can then be transferred to a device and executed. All validation occurs during the publishing process, not during the app creation process.

Note:As of 9.5 SP5, you can set app publishing to run in the background while you perform other tasks. Select Configuration > System Settings, scroll to the Publishing section, and select the Allow publishing/promote to run in the background option. In addition, use the Background publishing check interval option to set how often you want the system to run an automatic background update.

Check your list of published items by selecting the arrow icon to the right of the search field at the top of the screen. A red dot on the arrow icon indicates something new has been published.

To publish an app, complete the following steps in Platform Manager.Check your list of published items by selecting the arrow icon to the right of the search field at the top of the screen. A red dot on the arrow icon indicates something new has been published.

Go to Develop > Application Studio > Library.
Select Applications.
Hover over the app's version number in the highest promotion level and select Publish from the menu. If the app did not successfully publish, error messages display. Complete the following substeps to resolve errors.
1. Optional. In the Publish Results dialog box, select Copy to clipboard to copy the publishing results to your clipboard.
2. Select a link to the location from which the error originated or select a link to highlight the reference in the flowchart or form, and then correct the error.
3. Optional. To display the Publish Results box again, above the search box in the taskbar, select Last Published Results - [App name].
  
  Step Information
  
  Note:After a successful publish, the Last Published Results... label will include the app name and version published. If the most recent publish attempt failed, the label will only include the app name.
4. When all errors are corrected, publish the app.
Step Information

Note:Warnings may display when publishing, but do not prevent an app from publishing and may be corrected at your discretion. Errors must be corrected before you can publish the app.

Result: When the app successfully publishes, a confirmation message displays along with the version numbers and IDs of the app. The app is ready to run on the mobile device.

There was a problem loading this topic