Request tab fields

This section describes the fields on the template Request tab.

Setup Project Request

The following table describes the fields in the Setup Project Request section.

Field	Description
Request description	The description displayed when a user adds a project request. You should briefly describe the purpose of the template. Length is limited to 300 characters.
Request re-approval rule	Radio buttons provide the following three options for the way project requests are handled if they are returned and then resubmitted. If project request returned and then resubmitted, request is processed by all recipients again (the default) If project request returned and then resubmitted, start process with the person who rejected If project request returned and then resubmitted, request owner selects the recipients it needs to go to In this case, on re-submitting the request the request owner can select only required recipients who have accepted the request.

Setup Recipients

The following table describes the fields in the Setup Recipients section.

Field	Description
Request owner can add and/or delete recipients	If you do not add recipients, you must leave this checkbox checked, or else you will receive an error message when you save the template. If this checkbox is checked, a project request that uses this template allows the requester to assign new recipients and change any non-mandatory pre-configured recipient assignments.
Add Recipient Step	A link that enables a set of fields you configure to add request recipients.
Remove selected Recipient Step(s)	A link that enables you to delete the recipients you have selected by checking the box at the beginning of the row.
Recipient Role	A drop-down list containing the recipient roles you configured on the Project Roles tab.
Recipient Assignment	A drop-down list that enables the following options. User/Team - Selecting this option enables a drop-down list of users from which you select to assign a user or team to the role you selected in the Recipient Role field. If you select a team, the recipient is the a team member or team manager (who assigns the request to a team member); this is determined by the option selected in the Request Routing Model section of the Team's summary tab. Requestor Assigned - Allows the requestor to assign a user to the role you selected in the Recipient Role field. Also, if you set the other fields (such as Default Duration, Sequence, and Project Owner), these values become the defaults for this request recipient, but the requestor can change them. Rule Driven - Selecting this option enables an icon that you click to open a Rule Builder window that allows you to define rules for assigning a user to the role you selected in the Recipient Role field. See Rule Builder for a description of the Rule Builder.
Default Duration	Time allowed for each review step. The way days are counted is set up when Unica Marketing Operations is installed and configured, in the UAPInitParamnumberOfHoursPerDay parameter. See the Unica Marketing Operations Installation Guide for a description of the options provided for this setting. If recipients do not respond within the time set as their default duration, they receive an alert. If the recipient is a team, alerts are sent according to the Request Routing Model configured for that team.
Sequence	A text field in which you enter a sequence number. You can specify the sequence number for each recipient to specify the order in which the recipient receives notification of the request and must approve the request. You can control whether recipients act in parallel with other recipients or before or after any other recipient. If you assign the same number to multiple recipients, they would all receive notifications when it is their turn to respond. This field must contain a number; the maximum is 99. By default, each time you add a recipient the value of this field is incremented.
Project Owner	The recipient designated as the project owner becomes the owner if the request is accepted by all required reviewers. The project owner is always a required recipient.
Required	A checkbox that determines whether a recipient is required. Check the box next to each recipient who must approve. If this box is not checked, the recipient is optional. Note the following behavior for required recipients. If a recipient is required, the next recipient in sequence will not be notified (and can not respond) until the current recipient has responded. If a recipient is required, and that recipient denies the request, then the next sequential recipient is not notified; rather, the request is placed on hold, and the owners are notified. If multiple recipients have the same sequence number (and therefore can act simultaneously), and one of the required recipients rejects the request, the request process continues until all the required recipients of the simultaneous process have responded. After all responses from that step are complete, the system sends a notification to the request owner and recipients who were previously notified of the request. At least one recipient must be set to Required. The system generates a warning message if someone tries to start a request that contains no required recipients.
Instructions	Opens a window where you can add instructions that this recipient sees on the Summary page of the project request. Length is limited to 1024 characters.