OA approval connections need to correspond to clear enterprise rules. Application modifications, returns and resubmissions, and changes in the handler may all affect whether the existing opinions are applicable. The process design first explains the business conditions, and then arranges the pages and nodes.

Business Scope

Select real and high-frequency approval matters, and clarify the application objects, necessary information and the purpose of the results. Flow charts cannot draw lines based only on organizational levels, because different matters may require the participation of different positions.

Node Actions

Write clearly what will be changed by passing, returning, supplementing and withdrawing. Whether to re-approval after modifying the application content needs to be confirmed according to the event rules to avoid inconsistency between the process status and the actual version of the application.

Record query

Applicants need to know the progress, handlers need to process to-dos, and administrators need to maintain rules. The three views collaborate around the same business record and should not each copy an independent copy of data.

Scenario verification

For example, if the amount or project content is modified after the application is submitted, whether it needs to be reviewed and approved again should be determined by business rules. It must be clear which version the original opinion corresponds to, and agreement with the previous version cannot automatically represent new content.

Specific verification method

Modify the amount during approval and check whether it is re-confirmed according to the rules; old opinions can be found in the original application version; return and resubmission retain the original process; continuous submission will not repeatedly generate processing tasks, and the new person in charge should also have the authority to read the information required for the application.

The rules explain which changes trigger re-processing, and the opinions clearly correspond to which version. In this way, after the application content changes, the old consent will not be misused as confirmation of the new content, and it will also facilitate subsequent tracing.