Standard Task (eForms) activity

An activity that shows an eForm when the process runs.

Use a Standard Task activity only if you do not want the form to start the process. If you want your form to start the process, use the Start Task (eForms) activity or Start Task (External Forms) activity.

Configure the Standard Task (eForms) activity

To configure the Standard Task (eForms) activity, do the procedure in this topic.

Video: Add Standard Task Activities

Video: Process Designer Overview

Video: eForms with SharePoint - Part 3

Examples

(Example) Create an eForm (Set Available Leave Hours)
(Example) Create an eForm (Manager Approval)
(Example) Configure the Set Available Leave Hours Task in the Human Resources Example Subprocess
(Example) Use Anonymous Authentication in a Process-Based App
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.

Good to Know

In most text fields, you can use process data variables as an alternative to literal data values.
Use a Standard Task activity only if you do not want the form to start the process. If you want your form to start the process, use the Start Task (eForms) activity or Start Task (External Forms) activity.
In this activity these settings are configured by default:
- There is no default participant.
- The Auto Complete activity property is set to False. This means the first time a task is entered at runtime, it is not automatically marked as Completed.
- The Submit Step activity property is set to False. This means that the activity can not start the process.
If you assign a task to a new participant, and then that participant releases the task back to the pool, and the participant to whom the task was originally assigned is removed from the pool.
This applies only to the current process instance.
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to human task activities. For more information, refer to:
If you have questions about the security impacts or best practices for anonymous forms, contact AgilePoint Professional Services.

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the eForms tab.
On the eForms tab, drag the Standard Task activity onto your process.

Procedure

On the Standard Task Configuration screen, do one of these:
- Select the form that exists.
- Create a new task form.
  1. Click Add New Form.
  2. Complete the fields on the Form Details screen.
    For more information, refer to Form Details screen.
Click General Configuration .
Complete the fields on the General Configuration screen.
Click Participants
Add or change participants for your task on the Participants screen.
(Optional) If you want to let a runtime app user submit the form with anonymous authentication, click Advanced > Anonymous Access .
For more information, refer to (Example) Use Anonymous Authentication in a Process-Based App.
(Optional) When the task changes status, you can send notifications using e-mail, Viva Engage, Salesforce Chatter, or SMS:
- To send an email notification, click Advanced > Email Notifications .
  For more information, refer to Email Notifications screen (Process Activities).
- To send a notification with Yammer, click Advanced > Yammer Notifications .
  For more information, refer to Viva Engage Notifications screen.
- To send a notification with Salesforce Chatter, click Advanced > Chatter Notifications .
  For more information, refer to Chatter Notifications screen.
- To send a notification with SMS, click Advanced > SMS Notifications .
  For more information, refer to SMS Notifications screen.

Form Details screen

Creates a human task form for an app.

How to Start

App Builder

Click App Builder.
On the App Explorer screen, click [App Name] > Processes > [Process Name] > Forms > Task Forms.
Click New.

Process Builder

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, drag any human task activity onto your process.
On the eForm Configuration screen, click Add New Form.

Form Details screen

Configures a human task form.

Fields

Field Name	Definition
Form Name	Description: A name for your form. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Default Value: None Accepts Variables: No Example: Refer to: (Example) Create an eForm to Start the Process (Create Absence Request) (Example) Create an eForm (Set Available Leave Hours) (Example) Create an eForm (Manager Approval)
Form Description	Description: A description for your form. Allowed Values: More than one line of text. Default Value: None Accepts Variables: No
Next	Opens this Screen: Choose Form Layout screen Function of this Screen: Lets you choose the layout for your form.

Choose Form Layout screen

Lets you choose the layout for your form.

Fields

Field Name	Definition
Form Layouts	Description: Lets you choose a form layout to create a new form. Allowed Values: Blank Form - Lets you create a new form using blank form layout. Existing Form - Lets you create a new form using the form that is available in your app. Default Value: Blank Form

General Configuration

Specifies the general information for the Standard Task activity.

Examples

(Example) Offline Mobile eForms in a Process-Based App
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.

Fields

Field Name	Definition
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
Priority	Description: Specifies the importance of a task. Allowed Values: High - Specifies a high priority task. A high priority task shows High icon. Normal - Specifies a normal priority task. A normal priority task shows Normal icon. Low - Specifies a low priority task. A low priority task shows Low icon. Default Value: Normal Accepts Variables: Yes
Enable Offline Capability	Description: Specifies whether to make an eForm activity available in offline mode. Allowed Values: Deselected - Does not make an eForm activity available in offline mode. Selected - Makes an eForm activity available in offline mode. Default Value: Deselected Example: Refer to: (Example) Offline Mobile eForms in a Process-Based App

Participants

Specifies the people, groups, or roles assigned to a human task.

Fields

Field Name	Definition
Details	Description: Shows participants for the task. Allowed Values: Any user, group, or role - You can add users, groups, or roles as participants, as long as ProcessInitiator is also included in the list. A process data variable. ProcessInitiator - This is a process data variable for that represents a participant who completes a form to start a process instance. This value is required for start tasks. Default Value: ProcessInitiator - For start tasks. None - For other tasks. Accepts Variables: Yes Example: Refer to: The videos on this page
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. Default Value: Roles Accepts Variables: No Example: Refer to: The videos on this page
Search	Function: Does a search based on the specified criteria.
The maximum number of participants to complete this task	Description: Specifies the number of group members who need to be assigned as participants for a task. Allowed Values: An integer that specifies a number of participants within a group required to complete a task. Unlimited Participants - Specifies that all members of a group are required to participate. Default Value: 1 Example: If the participant is set to a group of users, and Max number of people to complete this task is 2, then 2 members of the group actually are required to participate in the task.
Assign task to the same participants each time activity runs	Description: Specifies if, when a activity runs more than one time during a process, the same participants must complete the task each time. Allowed Values: Selected - If an activity is runs more than one time, the same participants who took assignment the first time are also assigned the task each time after. Deselected - If an activity is runs more than one time, any participants can take assignment each time. Default Value: Selected Example: Ann is part of a group, and takes assignment for a task. She rejects the task. If this field is selected, the next time the process starts this task, the same user, Ann is assigned the task. If this field is deselected, the task goes back into the pool, and anyone in the group can take assignment. Also refer to: (Example) Configure Dynamic Task Pool Activity and Load Balancing Activity