Work flow as
3. Assign Flexi Task (commonly used group)
It seems to be the most commonly used work flow, which is intuitively understood to mean assigning elastic tasks. We can look at, probably the meaning of approval, have approval and reject branches. Here you can assign tasks to one or more individuals, in order to achieve a specific result, can be set to require full approval to obtain the results, that is, the function of the sign.
Check the configuration.
For a description of the configuration item:
Action Tab Section
Who the task is assigned to when the workflow runs (user or user group).
Users can directly enter the user name, mailbox or full name, can be resolved, and SharePoint similar, you can also click the Address Book icon to query users, but more functionally richer, said below. You can also enter a mailbox address outside of a SharePoint environment to assign to external users, but they do not have access to the SharePoint site, so they can only be done with lazy approval.
The dialog boxes for selecting users and groups are as follows
The first two parts are mentioned above, and the third part is shown as lookup, which is the concept of finding associations, which can be dynamically assigned to whom to assign tasks.
Create individual tasks for all group members
When assigning a task to a user group, check this box to indicate that everyone in the group receives a separate task and everyone in the group will be alerted, but anyone can handle it. (Only the first-level groups, groups in the group when the group is not open, a bit around the mouth, it is unclear why this explanation, SharePoint I should not be in the impression that there is a group in the case).
Whether the approval task can be delegated to other people for processing.
Whether to allow lazy person approval mode.
Some dynamic parameter values can be displayed to display additional information about the task.
Define the results, which are approved and rejected by default, and can be added and edited.
There are 5 options for behavior handling patterns for multiple task assignments.
First reaction takes effect: The result of the first response is the result of the task, and the other waiting tasks are set to not be required.
Most people must choose a specific result: most of the people assigned to the task must achieve the same result, if not the majority, the variable ' outcome achieved ' will be set to no, the result of the entire task is empty. When the Nintex system determines that most of the unreachable tasks will be reached, the other waiting task is set to not be required.
Everyone must agree to a result: all assigned to the task must choose a specified result, if any one chooses another result, the other waiting task will be set to not need, the variable ' outcome achieved ' will be set to No, The result of the entire task is empty.
Most people decide that the result variable will be set according to the most results. If the Nintex system is able to determine the most results before all tasks are completed, other pending items will be set to no need. If the number of result responses is the same after all tasks have been completed, the variable ' outcome achieved ' will be set to No, and the result of the entire task is empty.
All people must agree: all assigned to the task must agree to the same result if there is a different, other waiting item will be set to no need, the variable ' outcome achieved ' will be set to no, the result of the entire task is empty. That is, one-vote veto mode.
Outcome achieved meaning whether the result is complete, whether the type.
Store outcome in
To save the results in which workflow variable, click on the work rheology the Ribbon to create first.
Store outcome achieved in
If the results are saved in which workflow variable, the same is not created.
Task title, nothing to say, empty is the default title, you can also insert the reference into the dynamic generation.
Task Content Type
Set this to override the default content type, custom Task form, as long as there are other content types available that you do not have to create yourself.
The priority of the task.
Sets the expiration time for the task. (The phone is sorted by this date)
Select the type of form you want to use.
Store Task IDs in
The ID of the task generated by the workflow runtime is stored in which variable, the variable type can be integer, the list item ID, or the collection type.
Set user permission to: Sets the permissions for the workflow association item.
When the task is completed, set user permission to: Sets the permissions for the associated project after the task completes.
Setting permissions on a project is useful when a task is delegated, and it gives the delegated user the necessary permissions to view the project.
Space is limited, and the next chapter continues.
SharePoint Nintex Workflow Workflow Help (iii)