In most cases, the User who handled the first Step in a Swimlane is also responsible for the downstream Steps. For example, the person in charge of answering a certain inquiry is responsible until completion of the issue. On the other hand, in the operations such as a new graduates selection process that may receive a large number of applications, it is not necessary that the downstream handler is the same person as the person handling upstream Step.
1. Usage Example of Cancelling Continuous Handling
- a. Background knowledge in the upstream process is not required 1
- Preparing a schedule of job interviews in accordance with internal rules
- b. Background knowledge in the upstream process is not required 2
- Confirming that an invoice amount is credited after billing
- c. Large Volume of Issues Being Created
- In a situation where 10 people are responding to 1,000 inquiries in a day, a different person can make the secondary response
- The cancellation of the principle of continuous handling is effective if the handling of the downstream Step does not depend on prior knowledge of the upstream
2. Operations Where Continuous Handling is Desirable
- a. Draft Proposal and Report
- Drafter to carry out "Re-applying for a Rejected Request" and "Implementation Report after Approval" by themselves
- b. Responding to Inquiries
- The person in charge of answering will continue to be responsible for correspondence, doing internal investigation and confirmation with the technical department, etc.
- Continuous Handling should not be canceled in cases where the downstream Steps are hard to handle for people who are not familiar with the circumstances of individual issue
3. Switching Off Continuous Handling
- 1. Modify the Swimlane Setting
- Use the radio buttons found in the editing screen of the [Operator] to toggle the setting. Selecting "The operator of each task can be made a different user" will cause the Issue to go to [Offered] each time it arrives at a new Step
