Versions Compared

Old Version 51

changes.mady.by.user Technische Redaktion

Saved on

compared with

New Version 52

changes.mady.by.user Technische Redaktion

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties
hiddentrue
idPROGRESS

Product Version
Report Note
Assignee

Resources & Remarks

Modification History

NameDateProduct VersionAction
Antje23 JUL 20212021 Autumncreated
Martin26 JUL 20212021 Autumn

draft

Bratislav29 JUL 20212021 Autumndraft
Antje29 JUL 20212021 Autumnformatting, published
Agnieszka25 AUG 20212021 AutumnrLANG
Martin24 SEP 20212021 WinterAdded the section for starting processes with a startform
Antje27 OCT 20212021 Winterclient-specific Flowable variables added
Christoph14 15 FEB 20222022 Springadded Custom Confirm Actions (DOKU-2347)

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:

Code Block
titleoutcomes configuration
{
  "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.

ParameterDescription
nameTechnical 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
&

value

 The name of the flowable

'variable' to be saved with the 'value'

variable for which the specified value is saved after the user has clicked

this

the button.

This

The variable can be used to control the process flow.

valueThe value for variable in Flowable.
secondary

If false (default), the button is shown in the accent color.

If true, the button is NOT shown in the accent color.

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.



Excerpt

Use the BPM Engine for process and task management within your client.

...

Column in yuuvis® clientCorresponding Counterpart in BPM EngineDescription

Description (not available anymore as of version 2021)

Process variable whatAboutThe description that was entered while creating the follow-up.
as of 2021 Winter: SubjectWeb-API Gateway parameter subject, represented as Flowable string variable subjectSet while creating the process.
Created onProcess parameter startTimeThe time the follow-up (process) was created.
Follow-up dateProcess variable expiryDateTimeThe due date that was entered while creating the follow-up.
StatusDerived from process parameters endTime and suspendedPossible values for Status are running, completed and suspended.

...