system
December 31, 2017, 11:00pm
1
The 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.
These rules allow you to specify access to each row and field. These rules can be defined on the
Entity level
Field level
Users need a way to access 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 …
This part describes different user interface controls that can be placed either on screens or on sections .
Menu binding is a model element that connects a lookup with a screen containing the source lookup data.
Menu Item . When the menu item is set, the d…
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 thi…
If you change some data in a transformation, the state workflow will run at the beginning of the StoreData task. At this point, the new data is already in the database, so if you perform a c…
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 WebServic…