Screens¶
Use screens when you need a process-backed user interface that does not start a new workflow instance. Typical uses are reports, dashboards, lookup pages, and operational tools for existing process data.
Screens use a data model to define their structure. A server-side initialization script can prepare the data before rendering, and the screen can then display the result through a normal Emakin form.
Please see the forms section for information on creating forms within screens.
Dashboard Views¶
Screens can be configured as dashboard views, automatically appearing in the dashboard folder. Dashboard screens are also listed in the domain's dashboard designer.
Administrative Views¶
Check the "Is Administrative" option to restrict access to process administrators only. Only users with execute permissions on the process can view these screens.
Anonymous Access¶
Check the "Is Anonymously Accessible" option to allow access to non-logged-in users. Anonymous access is granted via the screen's URL.
Form Sections¶
Form sections control the default states of screen content. Formatting rules can further modify these states.
Screen URLs¶
Screens can be accessed via URLs constructed as follows:
1 | |
Query string parameters can pre-populate the data model before rendering:
1 | |
Here, myfield and myfield2 are set to 1 and 2 respectively in the root of the data model. Nested fields can be set using XPath (e.g., myelement/myfield3=3).