| | 4.3 Fulfilment
07. Person Switch Request | | |
|---|
| 4.3.07. Person Switch Request: | | 1. People change roles from time-to-time and scheduled tasks need to be bulk switched from one person to the next. The existing persons name is selected and the replacement persons name is selected - the rest is automated. | | 2. Person switch information is read-only, shared and retained for seven years. Many thousands of tasks can be switched from one person to another by Eliza in less than a tenth of a second. |
| 2. Procedure: | | 1. From the branch dashboard, click "Self-Service Support..." to popup page 2201. From the Self-Service dashboard, click "Person Switch Request..." to popup page 2245. | | 2. In the top menu bar, click "guide..." to popup this how to do it guide. | | 3. In the top menu bar, click "new..." to popup the Person Switch Request Pahe 2244. The key points of the procedure are replicated at the bottom of the page. | | 4. Select the existing persons name from the approved list. | | 5. Select the replacement persons name from the approved list. | | 6. Select that you approve and are responsible for the person name switch. | | 7. Click the validation button below to check that the names are correct and the replacement person has the right access rights. | | 8. When the data is complete and correct, click the approved button to cause the persons names to be switched in all applicable places. The person Switch procedure instantly switches names so the replacement person will be able to see the new work assigned to them - refresh the task list. |
| 3. Upgrade: Dec 2017 | | 1. An improvement has been applied to enable the last switched from persons identity to be saved with the date and time when the last switch was made. The first objective is to be able to identify those tasks that have been switched to a new person. A second objective is to be able to identify who the task has been switched from. A future procedure should be able to reverse the person switch procedure for one or all switched tasks. | | 2. In the light of learned experience, when a person imagines that a set of tasks is to be reassigned from a person who has left to a new person, in fact, something else may be the unsaid objective and business requirement. A future procedure is needed to assign tasks back to a person who has left where the set of tasks is identified by the switched date and time with the name of the person who they were switched from. This may be easy for Eliza, but hard to provide a user interface that can be used by people who will not use the procedure very much. | | 3. New data is being processed as ETA39 as switched from user id, ETA40 as switched date and ETA41 as switched time. This data is only known to and processed by Eliza so its integrity should be 100% and trusted. | | 4. Only one level of switched person reversal is provided by this design - only the last switched user, date and time are stored as evidence. When a set of tasks are switched from user-1 to user-2 and then switched from user-2 to user-3, then it is no longer practical to reverse the switch from user-2 back to user-1. It is practical to switch tasks form user-3 to user-1 as a normal switch person procedure, rather than as a reversal of a prior switch of certain tasks. |
| Document Control: | | 1. Document Title: Person Switch Request. | | 2. Reference: 164307. | | 3. Keywords: Person Switch Request. | | 4. Description: Person Switch Request. | | 5. Privacy: ITIL public shared with all approved people. | | 6. Issued: 20 Dec 2017. | | 7. Edition: 1.3. |
|
|