Auto-creation Conditions
If you are using a condition-based auto-creation process, ensure that you allow enough time (depending on the number of running background jobs) for routing of the workflow.
When designing business processes, especially when you are designing the relation between the business processes, note that there can be only one auto-creation job per record.
When the workflow advances, Unifier schedules an auto-creation job and executes it with high priority. If the workflow advances again, before the auto-creation job is executed, then the application will not schedule a new auto-creation job.
Notes:
- The manual auto-creation is transactional. The condition-based auto-creation is not transactional.
- If the option Do not evaluate condition based autocreation is selected for the workflow, the BP creator's conditions will not be evaluated irrespective of the conditions added in the auto-creation setup. This helps to reduce processing time when there are no BP creators on that step.
Because of the general way that processes are organized and relate to each other, when you create a job, several factors come to play to determine the job processing time.
Regardless of the job prioritization (high priority or low priority), Unifier will hold, or delay, processing the succeeding job when a record is being updated concurrently (for example, through web service, RAP, or manual updates), until the current job, or auto-creation, is complete. In other words, if a record is updated manually and the record auto-creation is in progress, the next request that is submitted by way of “UpdateRecord” will not trigger an auto-creation procedure because the previous job must finish first.
Example:
When a workflow advances from step 2 to step 3, the auto-creation initiates and is in progress. When the workflow advances from step 3 to step 4, if Unifier detects that the first job was not completed, then the application will prevent the second job from completing (auto-creation will not take place for the subsequent job).
Additional Information about Auto-creation Conditions
- Only manual auto-creation is form based.
- The auto-creation process does not depend on a business process form.
- Reverse Auto-population (RAP) process begins when the workflow advances. RAP uses the auto-creation process; therefore, RAP does not depend on a business process form.
- When a line item is auto-created (by using the line item auto-creation logic), the values in the fields on the line item that are based on a data picker in that line item will not be auto-populated.
Last Published Monday, August 28, 2023