| Page Properties | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
Resources & Remarks Modification History
|
...
| Column in yuuvis® client | Corresponding Counterpart in BPM Engine | Description |
|---|---|---|
Description (not available anymore as of version 2021) | Process variable whatAbout | The description that was entered while creating the follow-up. |
| as of 2021 Winter: Subject | Web-API Gateway parameter subject, represented as Flowable string variable subject | Set while creating the process. |
| Created on | Process parameter startTime | The time the follow-up (process) was created. |
| Follow-up date | Process variable expiryDateTime | The due date that was entered while creating the follow-up. |
| Status | Derived from process parameters endTime and suspended | Possible values for Status are running, completed and suspended. |
...
- If the
cardinalityof a field issingle, its type is mapped to the type of the Flowable variable with the samename. - If the
cardinalityof a field ismulti, the Flowable variable type is set toJSONand its values are listed in the specified JSON structure.
Custom Confirm Actions
As of 2022 Spring, it is possible to configure custom confirm actions for a BPM task including an optional form that is offered after activation of the corresponding confirmation action. The so-called outcomes can be configured in the BPM-form file as well as in the dynamic one (internal: BUD-789):
| Code Block | ||
|---|---|---|
| ||
{
"model":
{
...
},
"outcomes": [
{
"name": "taskflow_finish",
"variable": "status",
"value": "close"
},
{
"name": "taskflow_forward",
"secondary": true,
"variable": "status",
"value": "open",
"model": "taskflow-form-forward"
}
]
} |
The outcomes list contains the custom task confirm actions visualized as buttons instead of the standard confirm button. The order of the buttons is from the right to the left. The buttons are shown in the accent color per default. The outcomes section can be used in the dynamic action forms as well.
| Parameter | Description |
|---|---|
name | Technical name of the custom confirm action that is used as label for the confirm button to be displayed in the client if not localized. |
variable | Name of the Flowable variable for which value should be set by the custom confirm action. This variable can be used to control the process flow. |
value | Value for the Flowable variable specified by variable. |
secondary | If If |
model | This model is offered by clicking the action button the model is part of. Specify the technical name of a defined BPM form or a complete valid form model. |