...
- To provide a more flexible Approval Process to customers using the PCR-360 CustomerCenter.
- Provide more options when designating which approvers Approvers should receive notificationsNotifications.
- 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 processApproval Process.
- Line-item approvalsApprovals
- Approvals by Department
- Approvals by GLA
- Tiered Approvals
- Account for approval required flag on the service catalog
- Customers should be able to designate which approvers receive notifications when a Request is created and requires approval. It has been stated that not all approvers should receive notificationsApprovals to be based on Service Catalog or Equipment Catalog.
- Approval check will be part of the validation process.
- If a Request requires approvalApproval, return the value so UI can inform the customer on the cart pageCart Page.
Requirements
| # | Title | User Story | Importance | Notes |
|---|
| 1 | Approval Process Changes | Users have requested more flexibility in the |
approval process | 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
|
each - the approved item after Approval.
- Needs Work Option
- A new "Needs Work" option will be added to the
|
approval process remark - Remark field will be available to list items that need to be updated or changed in the
|
request request approved- Approved.
- Modified Requests can be resubmitted
- Requiring
|
approval - Approval for Stand-Alone Equipment will be available.
- Ability to
|
import approval criteria - 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 is | Approval are to be expanded and more powerful. | Must Have | |
Department GLA- GLA Approval permissions by Contact Type
- Reassign GLA Approvals: Users will be able to take a CustomerCenter request that is assigned and waiting for approval and reassign it to another approver.
Approvals By Service Type, Equipment, Flag on Catalog - Service Catalog or Equipment Catalog
- Approvals By Request Amount Thresholds
- Approvals By Owner
- Current (legacy) GLA
|
approver - Approver settings will be migrated to the new
|
system |
| 3 | Approval Notifications | A revamped |
notification approvals | 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 Requests - Requests.
- Approval Notifications will include a clickable link (or button) to
|
approve request |
| 4 | Tiered Approvals | A tiered |
approval | Approval approach will allow organizations to require |
approval | Approval from multiple individuals. | Must Have | |
Ability - Add the ability to add multiple levels of
|
Approvers |
| 5 | Line Item Approvals | A more granular approach to |
approvals | Approvals will provide more control over new Requests. | Must Have | |
Ability approve deny - Deny individual items within a
|
Request User interaction and design
...
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|
What should be done with current (legacy) Requests awaiting |
approval Approval when the new system is released? |
1 | One organization has so far expressed that it will be easier to delete these Requests and the |
users | Users will have to resubmit them under the new system. |
