Authorization subsystem allows the developer to assign access rights to multiple elements (e.g. menus, row-level-security filters etc.). The application’s administrator can then assign these access rights to users at runtime, allowing them access to the desired functionality.
The following model elements use authorization for controlling user access.
Row Level Security Filters
Users need a way to access the the different
screens and workflows from the client application. To allow this, you must define a menu. The menu is a list of functions and sub-menus that will be displayed in the client application.
Create one Menu per solution. To create menu items, add these under the Menu element.
The Name which will be displayed to the user.
Every entry displayed in a menu is called Menu Item. There are different types of menu i…
This part describes different user interface controls that can be placed either on screens or on sections.
Screen Section Widgets
Conditional Formatting Rules
Menu binding is a model element that connects a lookup with a screen containing the source lookup data.
Points to a Menu Item. When the menu item is set, the drop-down list control will display a three dotted button [8617993_84x46]. By clicking the button the specified menu item will be executed. This helps the user with a faster navigation e.g. to the address book while selecting a business partner.
Q: When the menu binding (…) doesn’t show?
The workflow is a sequence of steps, executed by the workflow engine. The sequence of the workflow is made of tasks or blocks. Tasks can use the data stored in context stores defined for this workflow.
Defines a rule which is evaluated before the task is performed. If the rule returns
True - The step is executed
False - The step is skipped
Context store upon which the start rule is evaluated.
Defines a rule which is…
After selecting the field, you can select a context store from the workflow that is of the same type as the field.
Select the field that will be mapped.
Possible values are Original, Current and ChangedFlag.
The behaviour depends on the event type.
StateEntry, RecordCreated, RecordUpdated, RecordDeleted – data saved first, event workflows run next. The workflow sees already saved data.
Web elements specify externally facing REST API or HTML pages. This way you can easily expose any data or functionality, or your ORIGAM applications in a simple way.
If you need a WebService (SOAP) interface you can find a description under
Web Services (SOAP) API
The typical use cases for Web API/Pages are:
HTML pages for extranet access.
JSON API for mobile applications.
XML API for integration with other enterprise systems.