The Pending tab displays alerts relating to the Project Refresh submission by divisions, and it provides the user with the ability to approve and deny changes. This is the default tab the user will land on when they enter the Actions interface.
Filter
The Pending tab can be filtered using the Quick Search fields at the top of the interface. When a value is selected in one of these fields, the table will automatically be populated with the relevant project list.
| Quick Search Field | Description |
|---|---|
| Division | This is a picklist of all values in the Division code list. It will be used to return all projects that are located within the selected Division. |
| Program | This is a picklist of all values in the Program code list. It will be used to return all projects with Programs that are within a selected Division. |
| Division Grouping | This is a picklist of all values in the Division Grouping code list. It will be used to return all projects that are located within the selected Division Grouping. |
The project list can be filtered further by selecting the checkboxes at the beginning of the project headers, then selecting the “Show Selected Only” toggle. This will remove any projects that were not selected from the table.
Table
Each project listed in the Actions interface will be composed of a Project Header and Project Change Table.
Project Header
The Project Header is displayed at the top of each project listing. It will be specified by these fields:
| Field | Description |
|---|---|
| Selection Checkbox | This is a checkbox for filtering the view of the Pending tab. Once selected, the user can choose the "Show Selected Only" toggle to remove any unchecked projects from view. The checkbox in the table header can be used to select all rows; this is used for Bulk Actions. |
| =/- | This is an icon used to expand all project rows to view their Project Change Tables. If the user wishes to expand the rows individually, they can use the caret icons on the desired row under this column. |
| Division ID | This is the unique identifier for the CIP project as shown on the Detail tab. This value will be a hyperlink that will allow the user to navigate back to the Detail tab for the project to review the Pending changes. |
| Division | This is the division in which the user who made the change is located. |
| Project | This is the name for the CIP project as shown on the Detail tab. This may be truncated due to space; however, the user can hover over the text to see the full value. |
| Action/Status | This is the pending action for the change, as chosen in the “Apply to Selected” picklist. |
Project Change Table
The Project Change Table is displayed after the Project Header row is expanded (caret), and it identifies all the pending changes associated with the project. Multiple pending changes can be listed under a project. This table will be specified by these columns:
| Column | Description |
|---|---|
| Funding Level 3 | The detailed revenue source for the project, to the program level. Represented as [Funding Level 1 |Funding Level 2 | Funding Level 3]. |
| Value Changed | This field identifies which project data element has changed. |
| Former Value | This field identifies the value of the data element prior to the change. |
| New Value | This field identifies the value of the data element after the change. |
| Updated By | This field identifies which user made the change. |
| Updated Date | This field identifies the date the change was made. |
| Notes | This field allows the user to enter comments to associate with the change. Comments entered when changes are submitted will be pre-populated in this field, but they can be edited if needed. |
Bulk Action
The Pending tab can be used to review Division imports and refreshes for field value changes prior to integration into the Project Universe. From this tab, System Administrators can process pending changes. This is done by using the "Apply to Selected" (Bulk Action) picklist. The user must select a row's checkbox to specify that the project is ready for an action, then this picklist can be set to one of these values:
| Field | Description |
|---|---|
| Queue as Approved | This option will allow System Administrators to approve the change. Once this action is executed, these changes will be considered approved and will be removed from the Pending tab and incorporated into the Project Universe. These changes will also be displayed in the Actions History tab when approved. |
| Queue as Rejected | This option will allow System Administrators to reject the change. Once this action is executed, these changes will be considered rejected and will be removed from the Pending tab and placed back in the Projects interface. |
| Remove from Queue | This state performs no action and leaves the change within the Change table. This is the default setting. |
The user can set an Action for multiple projects at once. To do this, the user can select the desired rows' checkboxes on the table, or they can select the checkbox in the table header to select all projects. Then, the user can select an option in the "Apply to Selected" picklist to update the Action/Status for all selected projects.
Additionally, varying action types can be processed at once. This means that the user can reject some projects and accept others at the same time if desired. To do this, the user must first select all projects for one action (checkboxes) and select the action in the "Apply to Selected" picklist (Queue as Approved or Queue as Rejected). Then, the user can deselect these rows, select all projects for the other action (checkboxes), and select the action in the "Apply to Selected" picklist (Queue as Approved or Queue as Rejected).
The "Execute Queued Actions" button processes all project changes with an action. Once selected on the Actions interface, a "Review and Execute" pop-up will appear for the user to review their selections before execution. Selecting this button again in the pop-up will officially execute the actions. For approved changes, a confirmation message will appear notifying the user that the Actions were added to the Project Universe successfully; all data changes are time-stamped.
Comments
0 comments
Please sign in to leave a comment.