This section describes the default Direct Approval Process workflow for managing limits in
Atoti Limits.
What does the direct approval process look like?
Key features of this workflow include:
Simplest possible workflow for managing limits where no approvals are required for limits to be created, updated or
deleted.
What initializing variables are included in the limit-process-direct.bpmn workflow?
The following initializing variables are included in the workflow:
Comment — A text field for adding comments related to the limit.
Attachments — A file upload field for adding attachments related to the limit.
What user tasks are included in the limit-process-direct.bpmn workflow?
The workflow includes no user tasks.
What service tasks are included in the limit-process-direct.bpmn workflow?
The workflow includes one service task that is executed in the workflow:
Post limit approval service task
“Post limit approval” service task implementation
note
This example serves as a skeleton implementation not the default implementation. You may customize
this service task to meet your specific requirements. For more information see the section
on customizing service tasks.
@Bean@ConditionalOnMissingBean(name ="postDirectLimitApproval")public Connector postDirectLimitApproval(){return integrationContext ->{
log.info("Processing direct limit action (no approval required).");// code executed after limit is published
return integrationContext;};}
When is this service task executed?
After the limit is published to the datastore.
What does this service task do?
sets the workflow status to indicate that the limit creation, update, or deletion has been approved
notifies the connected server of changes when a limit is updated or deleted.
