Service operations flow designer: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| Line 12: | Line 12: | ||
=== Supported actions === | === Supported actions === | ||
* TaskRequestWithRequestingPartner (parameter: task template, attacheddocuments, used task template) | * TaskRequestWithRequestingPartner (parameter: [[travel task template]], attacheddocuments, used task template) | ||
* InternalTask | * InternalTask | ||
* StartDiscussionWithRequestingPartner (parameter: initialtext, language) | * StartDiscussionWithRequestingPartner (parameter: initialtext, language) | ||
* TaskrequestWithServiceStation (parameter: task template, service stations to include (multi select: embarcation, disembarcation, transfer, mounting station, dismantling station ) | * TaskrequestWithServiceStation (parameter: task template, service stations to include (multi select: embarcation, disembarcation, transfer, mounting station, dismantling station ) | ||
Revision as of 17:40, 22 November 2024
This app allows to design process flows for service delivered. Essentially it allows servicespecific binding of actions to events
Supported events
- OnServiceRequestCreated
- OnServiceRequestDocumentMarkedMissing
- OnServiceRequestMedicalPreAppoval
- OnServiceRequestApproved
- OnServiceRequestRejected
- OnServiceDeliveryIsClosed (parameter: hours before)
Supported actions
- TaskRequestWithRequestingPartner (parameter: travel task template, attacheddocuments, used task template)
- InternalTask
- StartDiscussionWithRequestingPartner (parameter: initialtext, language)
- TaskrequestWithServiceStation (parameter: task template, service stations to include (multi select: embarcation, disembarcation, transfer, mounting station, dismantling station )