Skip to content

Configurations for Mobile via Page Designer

All configurations are done via the use of IFS Cloud Web Page Designer. Configurations in the mobile app can only done by an Admin user on IFS Cloud.

Adding a Custom Attribute

  1. Follow the instructions to setup Custom Attribute for Entity

  2. Ensure that the Entity is Approved, Published and Synchronized and the Attribute also is Approved and Published.

  3. Go to Entity Details to publish the entity attributes for the mobile app by going to Solution Manager > Mobile Apps > Configuration > Entity Details.

  4. Filter by Mobile app name, and then by the Entity name.

  5. Under the Attributes table, use "Add Custom Attributes" button to select the newly created attribute.

  6. Now "Publish Custom Attributes".

  7. To configure the app to view this new custom attribute, use Page Designer to update the mobile app.

  8. Solution Manager > Mobile Apps > Configuration > Apps for Page Designer > [Select the app to update] and go to the detail view for that entity.

  9. Open up the view in page designer & update the view to include the new field.

  10. Save & Publish Page Designer changes.

  11. The mobile client needs to be reinitialized if already logged in, to see the new field changes.

Troubleshooting: If the custom field is not visible, Refresh MobileApplication Cache to force refresh the cache (Solution Manager > System Information and Utilities > Refresh Server Cache)

Setting Conditional Visibility, Editability and Requiredness

Users can set Conditional Visibility, Editability and Requiredness on fields on mobile screens by following the same process as with Conditional Fields. Refer Conditional Fields for more details.

As of 24R1, this functionality is supported for the most common field types such as Text, Number and BLOB/CLOB fields. Custom Fields of type Text, Number and Date are also supported. Other field types have limited support on 24R1, for example in setting the Required property on Boolean fields and setting Visibility on Lists. Further, conditional expressions must use the "record" prefix, and functions (see Condition Syntax) are not supported in Mobile.

In addition, care must be taken with conditional expressions with references. For example, remember to refer to the Entity Model to identify relationships to use in references. Note also that a referenced data record needs to be saved before the conditional expression reflects those changes.

Setting Conditional Commands

Users can set Commands to be conditionally enabled or disabled by following the same process as with Conditional Fields and setting the Enabled property on a Command. Refer the previous section for more details.

Filtering of LoV and Enumerations

Users can filter LoV and Enumeration fields on mobile screens by following the same process as with Conditional LoV and Enumeration Filtering. For LoV filtering, refer Filter LOV's conditionally for more details. For Enumeration filtering, refer Filter Enumeration Values Conditionally for more details. As of 24R1, LoV filtering supports the following OData expressions: startswith, endswith, contains. This functionality can also be used to logically connect multiple LoV's together to form hierarchical lists.

Adding a Custom Action

  1. Open Page Designer for the mobile app by going to Mobile Apps > Configuration > Apps for Page Designer > [App Name].

  2. Navigate to a page, and add a command by clicking (+) on the Command group section.

  3. Under Content for the page, find the Command Group section. Refer Adding Commands

  4. Select command type and add a label for the command.

  5. Save & Publish Page designer changes.

  6. Initialize the mobile client.

  7. Go to the page on the mobile app. User should be able to navigate to the new page via the command button.

Note: Custom Entities have limited support under the Batch Sync model. Custom Entities cannot be defined as Push types.

Adding a Page

Users can create a new page to an existing projection.

  1. Open Page Designer for the mobile app by going to Mobile Apps > Configuration > Apps for Page Designer > [App Name].

  2. Add a new page and update the layout.

  3. Save & Publish and close Page Designer.

  4. Now that the page is created, the app needs to be able to navigate to it.

Update Navigator entries on the Mobile app

Users can navigate to a page via a navigator entry or via a command

To navigate to the page via navigator entry:
1. Open Navigator Designer and navigate to Mobile Apps > Configuration > Apps for Page Designer > [App Name]

  1. Create a new navigator entry of type Page for an existing page or new page.

  2. Save & Publish navigator changes.

  3. Initialize the mobile client.

  4. User should be able to navigate to the added page.

To navigate to the page via a command:
1. Go to an existing page on Page Designer.

  1. Add a command to the command group section on the page.

  2. Add a new navigationLink command.

  3. Select the (new) page to navigate to.

  4. Save & Publish Page designer changes.

  5. Initialize the mobile client.

  6. Go to the existing page. User should be able to navigate to the added page via the command button.

Using the Navigator Designer, users can also remove a navigator entry or update navigator entries on the dashboard.

Working with Custom Entities

Custom Entities can be used in Mobile apps in different ways, and relationships can also be modelled between a baseline Entity and a Custom Entity. Here are some example scenarios.

To create a standalone read-only list view with a Custom Entity (for example to show some data that mobile users may need to refer to): 1. Go to Entity Configurations screen and create a new Custom Entity and also add the relevant attributes to it before saving and publishing it.

  1. Go to Projection Configuration screen and choose to Configure a Standard Projection, select the app (for example ServiceEngApp) to be configured, add the new Custom Entity and decide on the operations to be allowed as well as specify the Sync Policy and publish the Projection Configuration.

  2. Open Page Designer, open some page within the app to be configured and create a new List element using the newly created Custom Entity and add the needed attributes.

  3. Within Page Designer, create a new Page, set the Datasource Entity Set and add the newly created List element to the Page's content, and then save and publish the Page Designer changes.

  4. Open Navigator Designer and provide a way for users to reach the newly created page.

  5. Ensure that data can is added to the new Custom Entity.

  6. Initialize the mobile client and users should now be able to refer the newly created data records. It will be necessary to ensure that the Custom Entity has synced after the data was added.

See also the Tailoring Guide section for creating Master Detail Associations, especially the List of Details section.

To model a 1:1 relationship between a Custom Entity and a baseline Entity (for example to augment an existing Mobile screen with new information): 1. Similar to the previous scenario, use Entity Configuration screen to model a Custom Entity.

  1. As before, do the Projection Configuration and additionally model an Association from the base Entity to the new Custom Entity and do the key mapping from the parent Entity's keys to the child Entity's keys, and publish the Custom Entity.

  2. Open Page Designer, open some page within the app to be configured and create a new Singleton object for the new Custom Entity and also create a Crudactions object.

  3. Within Page Designer, also create a new Group connected to the new Custom Entity and add the Custom Entity fields.

  4. Within Page Designer, open the Page that should contain the new Custom Entity fields, and add the newly created Singleton and add to it a Binding with Bindname being an appropriate Selector, and Property being set to the Association created earlier.

  5. Within Page Designer, add the newly created Group to the page and add a Binding to it with Bindname having the newly created Singleton and Property being left empty.

  6. Open Navigator Designer and provide a way for users to reach the newly created page.

  7. If any data needs to be added to the Custom Entity, ensure that it can be done (for example by creating a page on the backend) and sync the Custom Entity.

  8. Initialize the mobile client and users should now be able to work with the Custom Entity.

See also the Tailoring Guide section for creating Master Detail Associations, especially the One-to-one detail view section.