Navigation:  My tasks > Execution >

Request issuance

Previous  Top  Next

Task:

Request issuance

Who is notified:

User who is issuing the request.

When:

The request is created; however, it is not sent to the next step.

Purpose:

Alert the user of the existence of a request that needs to be issued.

 

How to execute this task:

 

1.

In the list of pending records, select the desired request.

 

2.1_auxnmb

1_auxnmbMake sure that the request data is properly filled out. To do that, click on the edit button on the main screen toolbar and make the necessary adjustments on the data screen that will be displayed. Refer to the Issuing a request section for a detailed description on the fields of the request data screen.

 

3.1_auxnmb

1_auxnmbTo end the issuance of the request selected in the list of records, click on the default toolbar button. At this point, the system will ask if you wish to send the request to the next step. Choose the desired option:

OK: The request will continue to one of the following steps:

oApproval: If in the request type it is configured that it will go through approval, the system will generate the Request approval task for those responsible for it.

oApproved: If the request does not the approval step configured on its type, it will be sent for service and will be available for tracking through the Request tracking task. Refer to the task for the request that will be generated by the system in the Object types and their operations section.

Cancel: The request will remain pending with the "Issue" status. In this case, it is also possible to close your issuance using the Execution arrowrgray Request issuance menu.

 

The system will request the countersign when performing this operation if the "Request user countersign when performing critical operations in the components" option is checked in the SE Configuration component (CM008).