Mobile app bundle

The Mobile App Bundles page defines the top-level container for a Mesh mobile deployment. It groups pages, workflows, services, and step definitions into a versioned unit.

By default, you have a production bundle installed with Aptean-configured workflows and pages. Any changes must be made on a copy of the bundle.

To configure an app bundle, follow these steps:

1. Select the Search icon , enter Mobile App Bundles, and then choose the related link.

   The Mobile App Bundles page opens.

2. Enter the required information in the following fields:

   Field	Description
   Bundle Code	A human-readable label. For example: STANDARD for the Aptean bundle, or Custom V1, Custom V2, etc., for customer copies.
   Publisher	Indicates who owns the bundle. Aptean for system bundles and Custom for customer copies. Custom bundles are never overwritten during a Mesh upgrade.
   Version	An auto-incremented integer managed automatically by the system.
   Status	Indicates the lifecycle stage of the bundle. The available options are: Dev, Test, Production, Archive.
   Description	A short description of the bundle for identification purposes.
   Root Page ID	Specifies the Page ID of the screen that appears immediately after signing in. This value must match a Page ID available in the bundle's Mobile Pages. If this field is left blank, the app cannot load.
   Min Client Version	Specifies the minimum mobile client VERSION_CODE required to run this bundle.

Create default app

To create the default app bundle, follow these steps:

1. Select the Search icon , enter Mobile App Bundles, and then choose the related link.

   The Mobile App Bundles page opens.

2. On the action bar, select Create Default App.

This action creates or resets the default Aptean locked bundle with the latest mobile pages, workflows, and services. If a Production bundle already exists, the system returns an error. You must archive the existing Production bundle before creating a new default app.

Copy bundle

To copy a bundle for customization, follow these steps:

1. Select the Search icon , enter Mobile App Bundles, and then choose the related link.

   The Mobile App Bundles page opens.

2. On the action bar, select Copy Bundle.

This action creates a copy of the selected bundle for customization. The copied bundle is set to Dev status and is not locked, allowing you to modify pages, workflows, services, and steps. Use this action to create a custom bundle based on the Standard or any existing bundle.

Bundle status and lifecycle

In the Status field, select the appropriate lifecycle stage. The available options are:

• Dev – Use during active development when you configure pages, workflows, and services.
• Test – Use to validate the bundle on devices before go-live.
• Production – The live bundle available to mobile users. Only one bundle may be in Production status at a time.
• Archive – Inactive stage for bundles that are no longer in use.

To move a bundle through its lifecycle, update the Status field as follows:

• To promote a bundle from development to test, set the Status field value to Test, and then assign testers to the bundle in Mobile User Assignment.
• To promote a bundle from test to production, first change the current Production bundle to Archive, and then set the Test bundle to Production.
• To archive a bundle, set the Status field value to Archive. Archiving does not delete the bundle or its related records.
• To restore the bundle, change the status back to Dev or Test.

The Standard bundle is always locked and read-only, regardless of its status. All child records (pages, workflows, steps, services) in the Standard bundle are read-only. Any bundle in Production status is also locked.

Customizing the bundle

Custom bundles support two levels of customization:

• Page layout (UI) – The visual layout of each page is stored in the Page JSON FastTab on the Mobile page and can be edited directly in BC from the bundle's Pages subpage. No development tools are required.
• Workflow and service logic (VS Code) – To customize workflow behavior, the Resolver Codeunit must implement the IStepHandler220FDW interface (IsStepRequired, HandleStep, UndoStep). To add or customize service logic, the service codeunit must implement the IBCRPC220FDW interface. Develop, compile, and publish both codeunits in VS Code before the changes take effect in Business Central.

For detailed developer documentation on customizing workflows, services, Mobile Pages and codeunit interfaces, refer to the Aptean Mesh Developer Documentation.