Step By Step
Process | |
•In the case that the customer request is created by a Sales Representative, the customer request is considered as approved at creation and goes directly to status Approved. Nevertheless, if the customer request is created by anyone else, the customer request needs to be approved through an approval flow.
•If additional information is needed before the Approval of the Customer Request, it can be recalled with a comment. Once the information has been delivered, the Request can be submitted for Approval again. •When the Customer Request is Approved, the Status will automatically be changed to Approved.
Approval for PePol No approval is needed for the GBU EP so the Customer Request will always be approved at creation. |
Recall the Approval Request | |
•If additional information is needed before the Approval of the Customer Request, it can be recalled with a comment.  •Once the information has been delivered, the Request can be submitted for Approval again and the Approver will receive a notification email.  |
Next process step | |
•As David submitted the Customer Request for Approval, the Status is changed to Pending Approval and the Approver is notified by email that he/she needs to take action.  •Let’s follow John, working as a Sales Representative and assigned as Approver, while he completes the Approval part of the Customer Request. |
Approver notification | |
•In order to get to the Customer Request page, John can either find the Customer Request on the Case object or simply click on the Customer Request link in the notification email.  |
Approving the Customer Request | |
 Once John opens the Customer Request, he can scroll down to the Approval History related list and click Approve or Reject it.  | |
|
Assignee Notification | |
•As defined previously, David assigned an Originator, Approver, Processor and Notified user to the Customer Request. These different assignees are the persons that are in charge of part of the Customer Request. •Once David has created the Customer Request and submitted it for Approval, the Status is updated to Pending Approval.   •The person in charge is notified by an email. A notification flow sends an email to the appropriate assignee to inform him/her that the status was changed and that further action is needed. The routing table is the following:  •These notifications are meant for users who need to take action on the Customer Request. Other users can always consult the Customer Request or the Reports if they need information on a Customer Request. •Well Done David ! The Customer Request is created and submitted for Approval and a notification has been sent to the Approver (John) to inform him that he needs to approve or reject the Customer Request. |
Need help?
Unable to render {include} The included page could not be found.
The best way to get IT support is to use the new
Service One Platform.