CustomerCenter Approvals Redesign - Requirements

Target release	2022.1
Released	2022.1
Document status	In Progress
Document owner	@David Engblom
Last Updated	May 19, 2022

Goals

To provide a more flexible Approval Process to customers using the PCR-360 CustomerCenter.
Provide more options when designating which Approvers should receive Notifications.
A phased approach will be taken to facilitate a speedy delivery of the most important features.

Background and strategic fit

Many of our customers that use CustomerCenter, as well as prospective customers, have asked for more flexibility and options with the Approval Process.

Line-item Approvals
Approvals by Department
Approvals by GLA
Tiered Approvals
Approvals to be based on Service Catalog or Equipment Catalog.
Approval check will be part of the validation process.
If a Request requires Approval, return the value so UI can inform the customer on the Cart Page.

Requirements

#	Title	User Story	Importance	Notes

#	Title	User Story	Importance	Notes
1	Approval Process Changes	Users have requested more flexibility in the Approval Process so they can more specifically tailor the requirements of a new Request for their organization.	Must Have	Phase 1 In CustomerCenter, the Approver(s) will be listed on the approved item after Approval. Needs Work Option A new "Needs Work" option will be added to the Approval Process. A Remark field will be available to list items that need to be updated or changed in the Request before the Request can be Approved. Modified Requests can be resubmitted Requiring Approval for Stand-Alone Equipment will be available. Ability to Import Approval Criteria Migrate legacy Contact/Worker GLA Approver records to the new system.
2	Approvals By Criteria	The available criteria for which a Request can require Approval are to be expanded and more powerful.	Must Have	Phase 1 Approvals By GLA Approvals By Service Catalog or Equipment Catalog Approvals By Request Amount Thresholds Approvals By Owner Current (legacy) GLA Approver settings will be migrated to the new system.
3	Approval Notifications	A revamped Notification system for Approvals and denials will aid in improving the speed of the whole process.	Must Have	Phase 1 Notifications will be able to be set up to inform Approvers of new Requests. Approval Notifications will include a clickable link (or button) to Approve the Request.
4	Tiered Approvals	A tiered Approval approach will allow organizations to require Approval from multiple individuals.	Must Have	Phase 2 Add the ability to add multiple levels of Approvers.
5	Line Item Approvals	A more granular approach to Approvals will provide more control over new Requests.	Must Have	Phase 2 Add the ability to Approve or Deny individual items within a Request.

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome

Question	Outcome
What should be done with current (legacy) Requests awaiting Approval when the new system is released?	One organization has so far expressed that it will be easier to delete these Requests and the Users will have to resubmit them under the new system.