Parallel Tasks (External Forms) activity

An activity that specifies a set of human tasks that must be completed before the process can go forward. This activity is usually used to request approval for a task from a group of approvers that can change.


Parallel Tasks activity

Configure the Parallel Tasks (External Forms) activity

To configure the Parallel Tasks (External Forms) activity, do the procedure in this topic.

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, open the External Forms tab.

    Open External Forms tab
  3. On the External Forms tab, drag the Parallel Tasks activity onto your process.

    Drag Parallel Tasks activity

Procedure

  1. Complete the fields on the General Configuration screen.
  2. Click User Defined Properties User Defined Properties icon.
  3. Configure user defined properties on the User Defined Properties screen.
  4. Click Update Process Instance Variable Update Process Instance Variable icon.
  5. Set process data variables whose values you want to change a variable on the Update Process Instance Variable screen.
  6. Click Dynamic Parallel Configuration Dynamic Parallel Configuration icon
  7. Assigns participants and work to perform values on the Participants And Work To Performs screen.
  8. (Optional) ​When the task changes status, you can send notifications using e-mail, Viva Engage, Salesforce Chatter, or SMS:
  9. (Optional) If you want to configure your task to show on a mobile device, click Advanced Advanced icon > Mobile View Mobile View icon.

General Configuration

Specifies the basic settings for the Parallel Tasks activity.

Figure: General Configuration screen

General Configuration screen

Fields

Field NameDefinition

Display Name

Description:
Specifies the activity name that shows in your process.
Allowed Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Accepts Variables:
No
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Description:
Specifies an optional text description for your activity.
Allowed Values:
More than one line of text.
Default Value:
None
Accepts Variables:
No

Time To Complete

Description:
Specifies the maximum amount of time that should be allowed for the completion of the task associated with this activity before it is considered Overdue. This is a combination of a number of minutes, hours, days, or weeks.
Allowed Values:
A number of minutes, hours, days, or weeks.
Default Value:
1 Day
Accepts Variables:
Yes

User Defined Properties

Specifies ClientData process data variable values that are associated with a human task activity when a process runs. You can specify a set of variables as name/value pairs that are sent to your web forms. This is an alternative to sending data with URL parameters.

Figure: User Defined Properties screen

User Defined Properties screen

Fields

Field NameDefinition

Name

Description:
Specifies the name for the ClientData.

The ClientData property stores data related to the human task activity. This is like defining a process data variable to store specific values.

Allowed Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Accepts Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Value

Description:
The value for the ClientData variable.
Allowed Values:
A number or a text string that can contain spaces.

You can set the value for the process data variable by using an XML value.

Default Value:
None
Accepts Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Type

Description:
Determines the data type for the ClientData variable.
Allowed Values:
  • string
  • int
  • bool
  • decimal
Default Value:
string

Create Create icon

Function:
Creates a row where you can specify a ClientData property.

Delete Delete icon

Function:
Deletes the selected row from the user defined properties list.

Update Process Instance Variable

Updates a value for a process data variable based on a specified type of event.

Figure: Update Process Instance Variable screen

Update Process Instance Variable screen

Fields

Field NameDefinition

Process Instance Variable

Description:
Specifies the name of the process data variable you want to update on the basis of an event type.
Allowed Values:
  • The name of process data variable to be updated.
  • You can also use the XML variable associated with the process.
Default Value:
None
Accepts Variables:
Yes
Example:

Value

Description:
Specifies a value for the process data variable that is set when an event occurs.
Allowed Values:
Default Value:
None
Accepts Variables:
Yes

When To Update

Description:
Specifies the event that causes the process data variable to be set to your value.
Allowed Values:
  • Enter - The process goes into the activity.
  • Assign - A task is assigned to a participant.
  • Cancel - A task is cancelled.
  • Complete - A task is completed.
  • Leave - The process goes out of the activity.
Default Value:
None

Create Create icon

Function:
Creates a row to add a process data variable, value, and event.

Delete Delete icon

Function:
Deletes the selected row from the variable list.

Participants and Work to Performs

Connects a list of parallel tasks with their participants.

Figure: Participants and Work to Performs screen

Participants and Work to Performs screen

Fields

Field NameDefinition

Participant

Description:
Specifies the user to whom the task is assigned.
Allowed Values:
  • One line of text (a string) that can contain spaces.
  • A list of predetermined variables.

You can specify only one user name in the Participant field. You cannot specify multiple participants such as group of users, or a user role for the task at a time. However, you can add multiple instances of a Work to Perform, each with a different Participant assigned.

Default Value:
None
Accepts Variables:
Yes

Work To Perform

Description:
Specifies the name of the task that shows in a participant's task list.

In most cases, for processes that use ASP.NET forms, this value also determines the file names for the .aspx form pages.

For the Web Form activity, this property does not set the file names for the web form. Instead use the Web Form URL. For more information, refer to Web Form Task (External Forms) activity.

Allowed Values:
One line of text (a string) that represents the name of the task.
Default Value:
None
Accepts Variables:
No

Create Create icon

Function:
Adds a row for Participant and WorkToPerform where you can specify parallel tasks, and assign participants to complete them.

Delete Delete icon

Function:
Deletes the selected row.

Add Roles, Groups and Users

Description:
Specifies a category of participants to add to the task. The list of participants of the type you select shows.
Allowed Values:
  • Groups - Shows your AgilePoint groups.

    To create a group, refer to Groups.

  • Roles - Shows your AgilePoint roles.

    To create a role, refer to Roles.

  • Users - Shows your AgilePoint users.

    To add a new user, refer to Users.

When a group or role with more than 100 members is added to the participants list, a warning message indicates that performance may be negatively impacted.

Default Value:
Roles
Accepts Variables:
No
Example:
Refer to:
Limitations:

The warning message for maximum participants is available in these releases:

Search

Function:
Does a search based on the specified criteria.