Joget DX 8 Beta Released
The beta release for Joget DX 8 is now available, with a focus on UX and Governance.
The ID Generator Field is used to produce a running number based on an App Variable. To learn more about its usage, refer to Generate Reference ID.
You will only need to do this if you are using MySQL, as other databases already default to "READ-COMMITTED".
Run the following queries in MySQL.
SET GLOBAL tx_isolation='READ-COMMITTED'; SET SESSION tx_isolation='READ-COMMITTED';
You will also need to set the following in your
transaction-isolation = READ-COMMITTED
The easiest way to see how the ID Generator Field works are to use the existing built-in App Expenses Claims. Here are the steps:
Element ID (By declaring as "ref", a corresponding database table column "c_ref" will be created)
Note when using this element when the form is part of a workflow process
Do not set the id as "id" when the form is used as part of a workflow process. The value generated by this element will not be associated with the process instance's ID.
|Label||Element Label to be displayed to the end-user.|
|App Variable Name|
Name of the app variable to be used to keep the running number.
Determines the pattern of the generated value (e.g., "REF-?????" will yield "REF-00001")
Determines if the element should be made visible in the form.
If the form is part of a workflow process, upon saving of the form (by clicking on "Save as Draft" or "Complete" button). The value in this input field will be saved into the corresponding workflow variable named here.
Using a non-existent Workflow Variable name
You will get the following warning with the name printed out (e.g. status) in the server log if you attempt to map to a non-existent Workflow Variable.
context attribute status does not exist in process context - adding new attributes to the process context is not allowed