Configure a User Activity

The name of the result, which will appear on all Forms, and as the completed result in the Timeline instance, if the result is selected by a user.

A brief text description of the result.

If the specified percentage of users select this result, the task will be considered complete, with this result recorded as the Activity result. For example, if you wish the task to be concluded when 75% of users select this result, then the value you'd place in the text box would be "75".

If the specified number of users select this result, the task will be considered complete, with this result recorded as the Activity result. For example, if you wish the task to be concluded when 3 users select this result, then the value you'd place in the text box would be "3".

If a user selects this result, the specified confirmation prompt will be displayed to the user, requiring the user confirm this selection before it is recorded.

This enables you to select a condition, or conditions, which, when met, will complete this task with the result recorded as the Activity result.

When setting an Activity result condition, you must set the Completed When dropdown to "When Any Result Condition Is Met" to complete the Activity on the Completed When tab of the Activity definition.

This enables you to select a condition, or conditions, which, when met, will display this result option to the user. If the condition(s) aren't met, the result button won't be displayed to users.

This is a check box that, when checked, designates the result as the default result for the Timeline Activity. When setting a Completed When condition, you must specify a default result, or the Activity will either not end as expected, or will go into an error state.

This is a numeric value that determines the order in which the Activity result button will appear on a Form. You may order the Activity results in any order you desire. If you don't order the buttons manually, they'll be displayed in the order in which the result was created. In older versions of Process Director, Process Timeline Activity results were specified using a comma-separated list. The display of the buttons on the form for each result followed the order in which they were listed. Now, when migrating from an older release to this one, the display order of the results will be automatically preserved. To modify the order, adjust the "Button Order on Form" property of each result in the Activity Results tab.

Clicking on the icon allows you to select a custom icon from a list. The selected icon will appear on the Activity result's button on the Form.

The setting enables you to select a background color for the result button that will appear on the form.

The setting enables you to select a text color for the result button that will appear on the form.

This text box will accept a comma-separated list of string values. For tasks that can be completed by email, a user can complete the task by replying to the task assignment email with one of the strings in the list you enter into this control. For example, the result displayed above is the "Reject" result. You might put the following list of responses into this control: "Reject, No, Disapprove, Rejected, Not Approved". If a user replies to the task assignment email with "No"—or any of the other possible responses in the list—as the body of the email message, the Reject result will be recorded as the Activity result.

If this option is selected, then, if the user selects this result, then the Results Comments control in the Form can't be empty.

If this option is selected, then users can complete this task from their Task List without opening the Form for the process.

This feature requires the use of a custom Task List that includes a column to display the results.

When the user completes a task from the Task List, Process Director will display a small popup that indicates the task completion is in progress. Additionally, if the result selected is configured to require completion comments, Process Director will prompt the user for the comments before completing that task.

The size of the prompt and confirmation dialogs won't usually need to be changed, however, if, for some reason the size does need to be changed, there are custom variables available to change the width and height of the dialogs: nTaskCompleteDialogWidth, nTaskCompleteDialogHeight, nTaskCompletePromptDialogWidth, and nTaskCompletePromptDialogHeight. Documentation for these four custom variables can be found in the Miscellaneous Custom Variables topic of the Developer's Guide.

Check this box to specify that a given Activity result will cause validation to be skipped. The feature is especially useful for steps/activities that include an option for the user to abandon or reject a form, which the user should be able to accomplish without, for example, filling in all required fields.

A dropdown that specifies the actions to take when the Due Date expires. The following options are available.

Checking this option won't allow a parent Activity to complete until this Activity is complete. This is the default option. This usually applies to an Activity that is organized under a Parent Activity Type. If this Activity doesn't complete, then the Parent Activity can't complete.

By default, the Result of a user Activity that is completed by multiple users will be the single result selected by most users. For instance, if two users pick Reject and one picks Accept, the Activity result is set to "Reject". In the case of a tie, e.g., if one user selects Accept and one Reject, the Result is set to "Accept, Reject". Selecting this option on a user Activity causes the Result to be set to the comma-separated union of all Results selected by users. So, in the first example above, the Result would be set to "Reject, Reject, Accept" or some similar result. The order of the results in the results list isn't guaranteed.

Forces users to re-authenticate prior to completing a task. For example, when this option is selected, built-in users will be presented with a login screen, requiring them to log in prior to completing the task, even if they are currently logged in to Process Director. This is an extra security precaution.

Checking this option will cause a prompt to appear to users to enter signature comments when completing the task.

Checking this option will enable task sharing through the Shared Delegation feature. If this option isn't checked, this task won't be available for Shared Delegation.

Checking this option will enable users to complete the task by replying to an email without opening the Form associated with the Activity or Process Timeline. Process Director can monitor an email inbox, import and parse the emails, and search for specific text in the email to determine the result. If a possible result for an Activity is "Approved", a user can reply with the word "Approved" in the body text of the reply, and Process Director will complete the Activity with the result of "Approve".

Checking this option will enable users to invite others to perform the user task by forwarding the task assignment email to them. The task assignee can forward the email to a desired alternate, for example, and when that alternate clicks on a completion link in the email, the task will be completed with the appropriate result, and with an annotation that the task was completed by the users invited by the original task assignee.

If this option is checked, at least one user will be required to complete the task, or the task can't complete. Depending on how the task assignment is configured, it's possible that no users will be assigned to the task in certain scenarios. For instance, if a task restarts after all users have completed their assignment, and the assignment is set to "Start users that did not complete previously" there will be no available user to which the task can be re-assigned. Checking this option will assign the task to one of the previously completed users.

If an administrator cancels a user in an Activity where this option is set, the Activity will go into an error state. The administrator will have to cancel the Activity to cause it to move on.

Checking this option will, when the task is assigned to multiple users, allow the first user to accept the task to be assigned to complete the task. When the task begins, all of the configured users will receive a Task List item that requests them to accept the task. When opening the Form, an Accept Task button will be displayed at the bottom of the Form. When any of the configured users clicks the Accept Task button, Process Director will remove task acceptance request from the Task List of all the other configured users, and the task will be assigned solely to the user who accepted the task.

Checking this option will enable anonymous users to complete a task based on the user's email address. This is a required option when using the Email Anonymous Task List system variable. In the vast majority of use cases, however, the email address will be taken from a Form field identified on the Participants tab.

Access to Process Director for unauthenticated or anonymous users is enabled for Cloud and Subscription licenses. On-premise licenses using the legacy Tiered licensing model require an additional, optionally licensed component.

If this task is part of a Case Management application, checking the property will automatically display the Case Folder view when the user opens the task.

For Process Director v6.1.300 and higher, customers who use the Mobile Application component can, by checking this option, export user tasks to the Mobile Application for completion. Similarly, the most recent version of the Mobile Form Import Custom Task will automatically import user tasks and their status from the Mobile Application when invoked.

This option enables you to select how wish to assign a task when multiple users are associated with the same task. You have the following options:

This option determines how a user's tasks are displayed when a user is assigned two sequential tasks in a process. The default in Process Director is to automatically show the user's next task if it is in the current process.

For example, if a user completes a task in a Form, and is also assigned the next task in the sequence, once the user clicks the OK or other task completion button on the Form, the Form won't close, but will simply redisplay itself to allow the user to complete the next task in the sequence. For various reasons, you may wish to override this behavior, in which case the Form will close once the first task has been completed, and the user will have to re-open the Form to complete the next task in the sequence.

You have the following options for configuring the behavior of Process Director:

This option determines how participants are assigned to the Activity when it must be restarted, which is particularly relevant when an implementer changes the participants assigned to an Activity in the Process Timeline definition. An existing instance may have been created when different participants were configured to participate in the task. This option enables you to determine how to handle user assignments when the configured users have changed.

It is also important to note that the term "restart" is used for both:

• Cases in which a running task is restarted while the task is still running, and
• Cases in which a task has already been completed, but must be re-run, as in an iterative process, or as a result of a change to some condition.

In either case, the Restart Users options you select will be applied.

The following options are available:

This will allow you to specify a Form to use in this Activity. This controls the form displayed when a user opens their Task List.

This property enables you to specify a system variable that can return users who will be given shared task permission for this specific Activity. This enables dynamic task sharing per each Timeline Activity, as opposed to the normal task sharing, which is set universally.