This page is a dashboard which covers all the change requests performed by the Logged in admin which requires peer review.
Submitted request:
Access the Submitted tab via Toku Admin Portal: Admin Portal> Logs > Request - Submitted. Page screenshot is available below:
Request Count: Displays the count of all the Requests in the dashboard as per default filters. All the requests can be accessed via pagination in the page footer.
Search Tab: Allows users to search within 'Submitted' request dashboard. Users can search with any keyword from the Username, Approver or Activity fields.
Filters: This dropdown option allows users to filter based on the factors below:
- Status: Used to filter the dashboard with certain status. User gets an option to select All status else can select one or more status(es) as per requirement to see the final results in the list table.
- Date & Time: Allows users to filter all requests from a specified duration. System only allows requests for the past 100 days.
- Username: Users can filter the 'Submitted' request list with a specific username to display activities performed by that specific user. Admins can enter part of the username to locate the user.
- Approver: There is an option available to filter review request results handled by an specific approver. Admins can enter part of the username to locate the user.
Clear All: This button allows users to clear all the selected filters. 'Clear All' is available only when custom filters are added by the users.
All Requests' Fields
Field Name | Definitions |
Date & Time | Timestamp of request creation. It is displayed in the format DD/MM/YYYY, HH:MM AM/PM. |
Username | The username of the logged-in admin who performed the activity to be reviewed. |
Request ID | System-generated ID for each review request created. |
Activity | Summary of the activity performed which is to be reviewed. |
Approver |
The username of the admin who will review the request and can take approval actions like Approve or Reject. For any request in 'Draft' and 'Pending' states, there will not be an approver assigned. |
Is Rollback |
Any rollback performed by the admin user; it comes to the peer review requests dashboard with the status as Pending. The values allowed are Yes and No. |
Status |
Shows the current state of the request. Applicable status in the dashboard are below:
In Review: Submitted change is accepted by the Approver for review. Approved: All the review requests which are approved. Once approved, changes will be applicable. Rejected: It is shown when the approver rejects the changes. The system will retain the old value. |
Action |
highlights the View Details option for the user. Further details are available in the View Details section below. |
Note: An admin user can not Approve or Reject their own review requests, they can only rollback the changes.
Also, if an admin has Approver role, they will receive a notification when a new review request is submitted by peers and admin user who submitted the request will also get the notification for changes in the state of the request like In Review, Approved or Rejected.
View Details: To view more details about the logged review request, logged-in admin can click icon under Action. This opens the pop-up for the user to check the details, a sample of which is available below:
Admin users can close this View Details pop-up screen by either pressing ESC button in their keyboard or by clicking on the close button available in the top right corner.
View Details' Fields
Field Name | Definitions |
Username | The username of the submitter of the request |
Date | Timestamp of review request creation. It is displayed in the format DD/MM/YYYY, HH:MM AM/PM. |
In Review Checkbox | The in-review checkbox is used by approver to assign the review request to him/herself. Once checked, status of will change from Pending to In Review and Approver's username will be assigned. For In Review requests, admin can click the check box again to move the request back to Pending state. |
Reject Button |
This gives approver to Reject the changes submitted for review.
This button will not be available for Approved or Rejected requests. F |
Approve Button |
This gives approver to Approve the changes submitted for review.
|
Approval Note |
Approver has been provided an option to add notes if any while rejecting or approving the request. This can help request submitter to make any amendments if needed and submit a new request. Max characters allowed is 1000 characters. |
App Category Tab(s) |
Changes are categorized per App where changes are made for review to easily track and review. System will show changes per App Name. Example of App Category is Queue, IVR, Announcements, Time Conditions etc. Scenario 2. Change in multiple App of same category Scenario 3. Changes in multiple App of different category
|
App ID |
This is unique ID assigned to every new App created under an App category. |
App Name |
This is user defined name for the App assigned during the App creation. |
Action |
It defines the action takes on the App. For e.g. Update, Rollback Update, Rollback Delete, Delete, Create etc. |
Details |
This column lists the field names in each row within the App which have been added, updated or deleted. |
Previous Data |
Display the old data against the specific field listed in the Details column. If there is no old data, field will show - as value, in scenarios like Create and Update actions. |
Updated Data | Display the new data against the specific field listed in the Details column. If there is no new data, field will show - as value, in scenarios like Delete and Update actions. |
Comments
0 comments
Please sign in to leave a comment.