Copying Mobile Apps
A mobile application consists of X3 code (classes, representations, scripts, etc.), and administration data that describes the entities used to publish the services defined in X3 code. When copying a mobile application you need to:
- Create an X3 patch including all the dictionary elements.
- Extract the relevant administration data from the MongoDB repository.
This is performed using the export profile tool, with a relevant list of entities and properties to be exported.
Installing the mobile application requires:
- the installation of the patch on the corresponding X3 folder,
- the import in MongoDB of the JSON file generated by the export tool.
Export profile for mobile applications
Listed below are the entities to be exported to get a complete description of a mobile application:
| Entity (title) |
Use standard profile | Filter | Export all | Comments |
|---|---|---|---|---|
| representationProxies (Representation) |
No | No | Technical dependency mandatory in the description but it is never exported. Only the entity and representation properties can be found both in the Profile item key and Profile item attributes tabs. | |
| applications (List of applications) |
No | No | Technical dependency. Only the application and contract properties are listed in the Profile item key tab. | |
| roles (role) |
No | No | Technical dependency. Only the code property is listed in the Profile item key tab. | |
| mobileGadgetParams (mobileGadgetParam) |
No | No | Child entity of the mobileGadget entity. Therefore, no condition is needed, and the values are exported according to the exported mobile gadget list. The Profile item key tab only contains the name property. The Profile item attributes tab contains the name, title, and value properties. | |
| mobileGadgets (mobileGadget) |
No | This is the main entity to be exported for the gadgets definition. You must select the Export all check box, or provide a filter (or a list of key in the Exported object tab) to select the gadgets that are exported. For example, if you want to export the gadgets associated with factory code XXX, you can use the following condition: ($factory eq true and $factoryOwner eq 'XXX')The profile key is code, and most of the properties are listed in the Profile item attributes tab: action, code, description, entity, externalUrl, gadgetType, icon, keyParameter, mobileDashboard, parameters, representation, requestLevel, requestName, statName, title, ProcessLeg, processMenu, processName, application, representationRef |
||
| mobileDashboardVignettes (mobileDashboardVignette) |
No | No | Child entity of the mobileDashboard entity. Therefore, no condition is needed, the values will be exported according to the exported dashboard list. The Profile item key tab only contains the persistendId property. The Profile item attributes tab contains the displayStyle, gadget, and persistentId properties. | |
| mobileDashboards (mobileDashboard) |
No | This is the main entity to be exported for the mobile dashboards definition. You must define the right selection criteria. The same condition can be used to retrieve data for a given factory code: ($factory eq true and $factoryOwner eq 'XXX')The profile key is dashboardName, and the properties listed in the Profile item attributes tab are: description, title, dashboardName and vignettes |
||
| mobileApplications (mobileApplication) |
No | This is the main entity to be exported for the mobile applications definition. You must define the right selection criteria. The same condition can be used to retrieve data for a given factory code: ($factory eq true and $factoryOwner eq 'XXX')The profile key is applicationName, and the properties listed in the Profile item attributes tab are: applicationName, description, homeDashboard, iconName, roles, title, and versionNumber |