Request Details

View a Request's details.

Overview

Details of a request display the current status of the request, names of request participants, and the option to cancel or rollback a request. Follow these steps to view Request details:

1. Ensure that you are logged on to ProcessMaker Platform.

2. Click the Requests option from the top menu to see requests.

3. From the cards on top, click My Requests, In Progress, Completed, or All Requests card.

   
4. Click the Case # or Case Title column link to view tasks for the case.

5. Use the open menu icon to open the collapsible panel on the right. You can find the Request's details under the Details tab.

Details

The Details tab displays information depending on the status of the status.

In-Progress

In-Progress Request Detail

The following detail displays about an in-progress Request:

Request participant details for an in-progress Request

• Cancel Request: The Cancel Request field allows a Request participant or ProcessMaker Platform Administrator to cancel the Request if that Request participant's user account has the appropriate permission to cancel Requests for that Process. If your user account does not have the permission(s) to cancel Requests for that Process, the Cancel Request field does not display. See Cancel a Request.

• Participants: The Participants field displays each Request participant's avatar in the selected Request to that time. Hover your cursor over a user's avatar to view that person's full name.

• Child Requests: The Child Requests field displays any child Requests associated with this Request, referred to as the parent Request when a child Request exists. A child Request is one from which this Request automatically started as designed in its associated Process. All child Requests have their own statuses since each routes independently of their parent Request. Click the link for any child Request to view the Request details for that child Request. For example, a child Request represents a Sub Process. If there are no child Requests associated with this Request, the Child Requests field does not display. The status icon displays beside each child Request. See View Your Requests for descriptions of each status icon.

• Parent Request: The Parent Request field displays the parent Request associated with this Request, referred to as the child Request when a parent Request exists. The parent Request is one that automatically started this Request as designed in its associated Process. The parent Request has its own status since it routes independently of its child Request(s). Click the link for the parent Request to view the Request details for that Request. For example, a parent Request represents the main Process that started a Sub Process Request. If there is no parent Request associated with this Request, the Parent Request field does not display. The status icon displays beside the parent Request. See View Your Requests for descriptions of each status icon. Below is an example of a parent Request in a Request detail.
• Request creation date: The date and time the Request was created displays below the Participants field. The time zone setting to display the time is according to the ProcessMaker Platform instance unless your user profile's Time zone setting is specified.

• Requested By: The Requested By field displays the avatar and full name of the person who started the selected Request. Hover your cursor over a user's avatar to view that person's full name.

Completed

Completed Request Detail

The following detail displays a completed Request:

Request participant details for a completed Request

• Participants: The Participants field displays each Request participant's avatar in the selected Request. Hover your cursor over a user's avatar to view that person's full name.

• Child Requests: The Child Requests field displays any child Requests associated with this Request, referred to as the parent Request when a child Request exists. A child Request is one from which this Request automatically started as designed in its associated Process. All child Requests have their own statuses since each routes independently of their parent Request. Click the link for any child Request to view the Request details for that child Request. For example, a child Request represents a Sub Process. If there are no child Requests associated with this Request, the Child Requests field does not display. The status icon displays beside each child Request. See View Your Requests for descriptions of each status icon.

• Parent Request: The Parent Request field displays the parent Request associated with this Request, referred to as the child Request when a parent Request exists. The parent Request is one that automatically started this Request as designed in its associated Process. The parent Request has its own status since it routes independently of its child Request(s). Click the link for the parent Request to view the Request details for that Request. For example, a parent Request represents the main Process that started a Sub Process Request. If there is no parent Request associated with this Request, the Parent Request field does not display. The status icon displays beside the parent Request. See View Your Requests for descriptions of each status icon. Below is an example of a parent Request in a Request detail.
• Request completion date: The date and time the Request was completed displays below the Participants field. The time zone setting to display the time is according to the ProcessMaker Platform instance unless your user profile's Time zone setting is specified.

• Requested By: The Requested By field displays the avatar and full name of the person who started the selected Request. Hover your cursor over a user's avatar to view that person's full name.

Completed

Canceled Request Detail

The following detail displays about a canceled Request:

Request participant details for a canceled Request

• Participants: The Participants field displays each Request participant's avatar in the selected Request to the time the Request was canceled. Hover your cursor over a user's avatar to view that person's full name.

• Child Requests: The Child Requests field displays any child Requests associated with this Request, referred to as the parent Request when a child Request exists. A child Request is one from which this Request automatically started as designed in its associated Process. All child Requests have their own statuses since each routes independently of their parent Request. Click the link for any child Request to view the Request details for that child Request. For example, a child Request represents a Sub Process. If there are no child Requests associated with this Request, the Child Requests field does not display. The status icon displays beside each child Request. See View Your Requests for descriptions of each status icon.

• Parent Request: The Parent Request field displays the parent Request associated with this Request, referred to as the child Request when a parent Request exists. The parent Request is one that automatically started this Request as designed in its associated Process. The parent Request has its own status since it routes independently of its child Request(s). Click the link for the parent Request to view the Request details for that Request. For example, a parent Request represents the main Process that started a Sub Process request. If there is no parent Request associated with this Request, the Parent Request field does not display. The status icon displays beside the parent Request. See View Your Requests for descriptions of each status icon. Below is an example of a parent Request in a Request detail.
• Request cancellation date: The date and time the Request was canceled displays below the Participants field. The time zone setting to display the time is according to the ProcessMaker Platform instance unless your user profile's Time zone setting is specified.

• Requested By: The Requested By field displays the avatar and full name of the person who started the selected Request. Hover your cursor over a user's avatar to view that person's full name.

Error

Request Detail With Errors

The following detail displays about a Request in which an error occurred:

Request participant details for a Request with errors

• Participants: The Participants displays each Request participant's avatar in the selected Request to the time of the error. Hover your cursor over a user's avatar to view that person's full name.

• Child Requests: The Child Requests field displays any child Requests associated with this Request, referred to as the parent Request when a child Request exists. A child Request is one from which this Request automatically started as designed in its associated Process. All child Requests have their own statuses since each routes independently of their parent Request. Click the link for any child Request to view the Request details for that child Request. For example, a child Request represents a Sub Process. If there are no child Requests associated with this Request, the Child Requests field does not display. The status icon displays beside each child Request. See View Your Requests for descriptions of each status icon. Below is an example of a Child Request in a Request detail.
• Parent Request: The Parent Request field displays the parent Request associated with this Request, referred to as the child Request when a parent Request exists. The parent Request is one that automatically started this Request as designed in its associated Process. The parent Request has its own status since it routes independently of its child Request(s). Click the link for the parent Request to view the Request details for that Request. For example, a parent Request represents the main Process that started a Sub Process request. If there is no parent Request associated with this Request, the Parent Request field does not display. The status icon displays beside the parent Request. See View Your Requests for descriptions of each status icon. Below is an example of a parent Request in a Request detail.
• Request error date: The date and time in which the Request error occurred displays below the Participants field. The time zone setting to display the time is according to the ProcessMaker Platform instance unless your user profile's Time zone setting is specified.

• Requested By: The Requested By field displays the avatar and full name of the person who started the selected Request. Hover your cursor over a user's avatar to view that person's full name.

A Request detail with errors has the following actions:

• Manually complete a Request with an error

• Rollback a Request that has an error

• Retry a Request that has a Script or Data Connector error

Manually Complete a Request with an Error

Follow these steps to manually complete a Request with an error:

1. Locate the Complete field.
2. Click Complete. A message displays to confirm you want to complete the Request.
3. Click Confirm. The status for the selected Request changes from Error to Complete.

Rollback a Request that Has an Error

A user may rollback to return to a previously completed Task when an error has occurred in that Request. The Process Manager receives both an in-application and email notification that the Request is in-error. Rolling the Request back places its status as in-progress instead of in error so that the Process Manager may properly route that Request.

A Request may be rolled back in the following circumstances:

• That user attempting to rollback that Request is a Process Manager.

• The Script Task or Data Connector object that has an error is preceded by a Form Task element during that Request's workflow routing.

• The Script Task or Data Connector object that has an error has a subsequent Form Task element.

• That Request is in an ERROR state.

If a Request with an error does not meet these conditions, the button to rollback that Request is not available.

Follow these steps to rollback a Request that has an error:

1. Locate the Rollback Request field.
2. Click Rollback. The Caution screen displays to confirm rollbacking the Request that is in an ERROR state.
3. Click Confirm. ProcessMaker Platform rolls back to the previously completed Task.

4. Fix the error in the affecting Script Task or Data Connector object.

5. Continue that Request's workflow as normal.

Retry a Request That Has an Error

A user may attempt to resume a Request that has a Script Task failed in the following circumstances:

• That user attempting to retry that Request must have the Make this user a Super Admin option enabled on that user account.

• The Request that has an error is not a child Request to a parent Request.

• That Request is in an ERROR state.

• The error in the Request is caused by one or more Script Tasks which is in an ACTIVE, ERROR, or FAILING state.

• The Request does not have any other Tasks that are in ACTIVE, ERROR, or FAILING states.

If a Request with an error does not meet these conditions, the button to retry that Request is not available.

Retrying the Request only attempts to retry the affected Script Task(s) which are in an ACTIVE, ERROR, or FAILING state. If the error for a Request under these circumstances is resolved when retrying that Request, the Request resumes. Its status becomes in-progress. Workflow routes that were in progress prior to the error resume.

If the error for that Request is not resolved, the Request immediately errors again.

Follow these steps to retry a Request that has an error:

1. Locate the Retry Request field.
2. Click Retry. The Caution screen displays to confirm retrying the Request that is in an ERROR state.
3. Click Confirm. ProcessMaker Platform tries to resume that Request.