The values for this property change with the type of process model you use:
Generic - Does this:
Specifies the name that shows in the participant's task list for this task.
If you create an ASP.NET project for this process in AgilePoint NX Developer, a new .aspx page is created for each human task with the same file name as the value of the work to perform property.
SPList and SPDoc - Specifies the name that shows in the participant's task list for this task
InfoPath - Does this:
Specifies the name that shows in the participant's task list for this task
Specifies the view from the InfoPath form for this process. These values are loaded from the InfoPath form.
You can add a new work performer name. But AgilePoint does not recommend this. A new name indicates a different type of form, such as an ASP.NET form. This functionality is technically supported, but you must write code to use it.
eForms - Specifies the name that shows in the participant's task list for this task
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..
Click the Ellipses button to open the General Configuration screen. Use this screen to complete theTime To Complete field.
Default Value:
1 Day
Accepts Variables:
No
User Defined Properties
Description:
Specifies ClientDataprocess 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.
Allowed Values:
Click the Ellipses button to open the User Defined Properties screen. Use this screen to complete the fields.
Default Value:
None
Accepts Variables:
No
Enable Mobile
Description:
Specifie show a human task activity on a mobile device with a special template for mobile view.
Allowed Values:
Selected - Features are enabled to support mobile devices.
Deselected - Features are not enabled to support mobile devices.
If you have set up a mobile view, and then deselect this option, your
options are saved.
An integer that specifies a number of participants
within a group required to complete a task.
Maximum Participants - Specifies that all members of a group are required to
participate.
Click the Ellipses button to open the Participants screen. Use this screen to complete the The maximun number of participant to complete this task or Unlimited Participants field.
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.
Reuse Participant
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:
True - 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.
False - If an activity is runs more than
one time, any participants can take assignment each time.
Default Value:
True
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.
Tracks the performance of an activity for the purpose of troubleshooting.
Allowed Values:
True - Shows that the activity logs the additional progress and debugging messages to the AgilePoint Server log file at runtime. Debugging information includes, for example, data being passed to or from the activity, or database connection information.
These messages help in verifying that the activity is functioning properly and/or with troubleshooting any problems or suspected problems with the activity's runtime behavior or configuration.
False - Shows that the activity does not log additional progress and debugging messages to the AgilePoint Server log file at runtime.
True - The first time a task is entered at runtime, it is automatically marked as Completed.
If the task is entered again at runtime, it is not automatically marked as Completed. This helps to avoid an infinite loop.
False - A task is not automatically marked as Completed.
Default Value:
False
Accepts Variables:
No
Wait Work Performed
Description:
Specifies whether data entry is required before a task can be completed in Manage Center.
Allowed Values:
True - Specifies that some data entry is required before a task can be Completed. If there is a form for a task, then data must be entered in the form.
False - Specifies that data entry is optional before a task can be completed in Manage Center.
Default Value:
True
Example:
This property might be set to False if a task requires some work that does not include data entry, such as delivering items to the post office.
False - Specifies that the activity starts as soon as any one of the activity's direct predecessors is Completed.
True (Static) - Specifies that the activity starts only after all of the activity's direct predecessors are Completed.All other activities process are ignored.
This setting is the logically the same as having an And activity with Dynamic set to False.
True (Dynamic) - Specifies that the activity starts only after all of the activity's direct predecessors are
Completed, along with all preceding activities
in the process branch. This setting ignores activities that are skipped or bypassed
because of the process logic or manual action in the
Manage Center.
If any of activities in the process branch is
delayed or does not start, this activity will not start, the process instance can be delayed indefinitely at this activity.
This setting is the logically the same as having an And activity with Dynamic set to True.
Example:
This topic gives details and examples for this property's configuration:
Specifies the amount of process related data that is stored to the AgilePoint NX workflow database. You can set this property at either the process template properties level or at the individual activity level.
Allowed Values:
High - Specifies that AgilePoint NX stores all data about the activity or process to the database.
Low - Specifies that AgilePoint NX will only store limited data to the database. This option enables you to selectively filter out unnecessary data.
At the process model level, the records for tasks with status of Removed and New are deleted from the database. After leaving the human task activity, the human task with the status of Removed are deleted first, then after the whole process completes, the tasks with status of New are deleted. Also the records for unreached
activity instances are deleted from the database.
Setting the Audit Level to Low has no effect on system activities at the process model level.
At the activity level for system activities, the records are deleted from database after the activity completes. No records are stored for the activity.
Default Value:
High
Example:
Setting the Audit Level to Low at the process model level is useful if you assign a group to a task. Tasks with status of Removed and New are not meaningful data after the process completes.
Setting the Audit Level to Low at the activity level is useful for an activity with a timer that goes through a large number of loops. Usually organizations are not interested in the information about the Timer activity, so setting the audit level for a Timer activity to Low deletes the records now, and the database size does not grow as fast.
Single - If the same activity runs more than one time in a process instance, any task that is not complete from a previous iteration are Cancelled, and a New task is created.
Multiple - If the same activity runs more than one time in a process instance, a new task is created, but any tasks that are not open from previous iterations are not cancelled.
The fully qualified Type name, including the namespace, of the .NET class (in the .NET assembly specified by the Assembly Name property) that represents the system activity component with which this activity instance is associated.
True - Microsoft Teams can send a notification.
This value must be set to True to send notifications configured
in Microsoft Teams Notifications screen.
