How OMX Apps adapt Workflow Actions
Essential knowledge
Changed on:
13 Feb 2024
Overview
The Fluent OMX App Framework is designed from the ground up to understand the way your business operates.Primarily, it does this by intelligently adapting to workflow changes. The user actions you've defined will show or hide depending on what's on a particular page and the state the primary entity being interacted with is in.Sometimes these actions will require additional information from the user, in which case a form will be auto-generated to capture what is needed to progress.The following document explains how this adaptation works from end-to-end, as well as where things can be further configured to meet your specific needs.Key points
- User Actions defined in the workflow can be interacted with on OMX apps.
- Users enter the event attributes expected by the ruleset via forms in the UI that open when a user action is clicked.
- The root object in the data query determines which workflow to search for any actions to display against on a given page.
- OMX apps utilise the
`action`prop on various components to identify which user actions should appear in specific parts of the app. - You can choose to confine user actions behind role-based action control or explicitly exclude them from a specific page.
The data query
The first object in the data query for a given route determines which workflow will be searched against to find all relevant user actions to display on a page.For example. In the reference Waves route. For example in the Customer Collections route`fc.mystique.manifest.store.fragment.customer.collections`The first object returned in the p