Information about the case
From RuLa, you can access certain information about the case itself. For this, within applicable rules, you have access to the constant CASE
like to any other instance. On this instance, the following information is available:
Property | Description |
| The case number in the user readable format, e.g. |
| The key of the process the case is based on, e.g. |
| The translated name of the process the case is based on, e.g. |
| The outcome instance this case operates on. For a case creating a new contract this is often |
| The key of the current state the case is in, e.g. |
| All possible states the case could be in according to the workflow of the process. |
| Returns a dictionary with some statistical information about each state. This includes:
|
| The key of the last transition (if any) that was done to arrive at the current state, e.g. |
| The time when the last transition (if any) happened, e.g. |
| The username of the user that performed the last transition |
| The name of the user that performed the last transition |
| How many information still should be provided (the sum of all the grey bubbles on information tabs). |
| Current number of tasks within the case. |
| Current number of issues within the case. |
| The time when the case was created, e.g. |
| The last time the case was updates, e.g. |
| The owner of the case (the email in rules and the full name and email when printed) |
| The full name of the case owner |
| A list of the names of the groups the current case owner has. |
| A list of the names of the roles the current case owner has. |
| The initiator of the case (the email in rules and the full name and email when printed) |
| The full name of the case initiator |
| The assignee to the case (the email in rules and the full name and email when printed) |
| The full name of the case owner |
| The user (if any) who approved the case (the email in rules and the full name and email when printed) |
| The full name of the case approver |
| A list with the names of all documents that are used in a case. This can be used to e.g. create a customised table of contents. |
| A list with the names of all proofs that are used in a case. This can be used to e.g. create a customised table of contents. |
Example: CASE.number_of_issues
This rule will only be fulfilled when there are no issues or tasks within a case.
Example: CASE.state
This rule would only be fulfilled while the case is in the state with the key '"draft".
Please note that if you are using this to create an issue or comment, it would be, as any other issue, comment or warning, removed when the case leaves that state (unless a user replied to it or was assigned to it).
Last updated