dspConduct
Manage Request Statuses Overview
Default statuses have settings configured for archiving a request, editing a request, and allowing role access to the request.
If the ARCHIVABLE check box on the Request Status page is enabled for a status, a request in the status can be archived. By default, a request is archived if it remains in the same status for 30 days. If the ARCHIVABLE check box is disabled, a request in this status is not archived, even after the default setting of 30 days has passed.
NOTE: This setting can be updated at the category level. Refer to Configure the Days Active for a Request Status for a Category for more information.
NOTE: Setting the request status to Cancelled, Deleted or Duplicate Request must be controlled on the Content WebApp's Request page. dspConduct™ does not set these statuses.
If the EDITABLE check box on the Request Status page is enabled for a request status, a Role Processor with access to the request can edit the request based on the role’s type when the request is in that status. If the EDITABLE check box is disabled, a request in this status is read only. No actions can be performed on the request until it moves to a request status with the EDITABLE check box enabled.
If the ROLE ACCESS check box on the Request Status page is enabled for a status, a request in the status can be processed by a role. The Finish and Validate buttons are active when the request is being processed by the Application role. The Reset, Validate, and Reviewer Workbench buttons are active when the request is being processed by the Review role. The Finish button is active for the Post role. If ROLE ACCESS is disabled, these buttons are disabled and a role cannot process the request until it moves to a status where the ROLE ACCESS check box is enabled.
Status |
Description |
Editable |
Archivable |
Role Access |
Draft |
The request has been created in the Content WebApp but has not been submitted. |
Yes |
No |
No |
Cancelled |
The request will not be posted because it has been marked for cancellation. |
Yes |
Yes |
Yes |
Deleted |
The request will never be posted because it has been marked for deletion. |
No |
Yes |
No |
Duplicate Request |
The request is a duplicate of another request already in the system. |
No |
Yes |
No |
Scheduled |
The request is scheduled to be posted at the date and time set on the Request Group Post page. |
No |
No |
Yes |
Posted |
The Request has been posted. All Integrate processes have completed posting, but the Post role has not been finished. |
Yes |
No |
Yes |
Posted with Errors |
At least one posting process has failed. All Integrate processes have completed posting, but the Post role has not been finished. |
Yes |
No |
Yes |
Posting Started |
A user clicked the Group Post or Post icons on the Request Group Post or Request Post Process page but the posting processes have not completed yet. . |
No |
No |
No |
Request in process |
This request is in process and has not been fully posted. |
Yes |
No |
Yes |
Finish Processing |
This request has been posted and is awaiting finished data download. |
No |
No |
No |
Finish Failed |
This request has been posted but the downloading of finished data failed. |
Yes |
Yes
|
Yes
|
Finished |
This request has been posted and the finished data has been downloaded. |
No |
Yes |
No |
A user can add a custom status, and set the archive, edit, and role access settings for that status.
To work with request statuses: