What is this? | A signoff flow specifies who signs off on feedback and which of those signatures are required.
Your organization will create Signoff Flows by designating certain people who will be approving or “signing off” on Feedback Reports. Reference: How to set up a Signoff Flow
There may be several levels of people who will be signing off on each Feedback Report. Some of these various levels will be required to sign off. Some will simply be Each signatory on a level can be marked as required (they must sign off before that sign-off engine will mark that level as complete). |
Why am I doing this? | Signoff Flows automate the documentation of the review and acknowledgement Feedback Reports, Training Observations, Task Lists, and Phase Enrollments. |
What will I learn? | By the end of this training, you will be able to…
|
| Definitions |
Feedback Report |
|
Author |
|
Evaluator |
|
Subject |
|
Signoff Flows |
|
TOR - Training Observation Report |
|
Signatory |
|
Returned |
|
Custom User |
|
Context User |
|
Sender | If someone other than the original author sends the shared draft, that person becomes the Author as well as "Sender". It is always the Sender who is signing off for the sign-off engine. |
Pending Request for Me | A quick filter button at the top of the Signature Requests tab list view, enabling one click access to records. |
Notification of signoff | Notification is sent where there is…
|
