Difference between revisions of "Structure/Status flow"
Jump to navigation
Jump to search
old>Admin (Created page with 'Status flows represent legal pathways in the workflow. In regard to the user interface, only valid options will be displayed i the records status selector. This check is also ca…') |
m (2 revisions imported) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 2: | Line 2: | ||
In regard to the user interface, only valid options will be displayed i the records status selector. This check is also carried out by the data layer, so the same restrictions apply regardsless of data was entered by regular users, file imports og the webservice interface. | In regard to the user interface, only valid options will be displayed i the records status selector. This check is also carried out by the data layer, so the same restrictions apply regardsless of data was entered by regular users, file imports og the webservice interface. | ||
If a given status can be used from most other states, we recommend using the Status:IsMeta attribute: Meta states can be entered from all other states. | |||
Latest revision as of 11:55, 10 December 2021
Status flows represent legal pathways in the workflow.
In regard to the user interface, only valid options will be displayed i the records status selector. This check is also carried out by the data layer, so the same restrictions apply regardsless of data was entered by regular users, file imports og the webservice interface.
If a given status can be used from most other states, we recommend using the Status:IsMeta attribute: Meta states can be entered from all other states.