Rules

The Administrator can configure multiple Page Flows for a single Model Level, and arrange for them to be used in different scenarios by specifying Rules. Rules are evaluated in the order they appear in the grid, from top to bottom. When it reaches a Rule that matches the current scenario, it uses that Page Flow. Platform provides support for automatically linking to Page Flows from Reports/Views if one of the set Rules applies. One can also define complex rules which consist of multiple expressions that are AND'ed at the time of evaluation. For example, show a PageFlow "X" if my user name is "PlatformTestSuiteUser" and if the RunReplenishment field is set to "true".

images/download/attachments/144835904/RulesEditor1-version-1-modificationdate-1656018187000-api-v2.png

Clicking on a Rule in the grid allows the Administrator to set the Page Flow that should be used, and one or more values for a variable, which can either be from the User Context or the current Model.

images/download/attachments/144835904/RulesEditor2-version-1-modificationdate-1656018157000-api-v2.png

Default Rule

The Administrator can also configure a "Default Rule" where if all other Rules fail for a scenario, a certain Page Flow is opened. You can see this in the screenshot with the Rules grid - the last row is where the Administrator can specify the Default Rule. If none is specified, then the default model detail page will be opened instead (the one, for example, that was registered using One.PageMgr.regDetail() ).