Changes

** '''Custom Date Field''' - The date in a selected custom field that stores date values.

* '''Delay(s)''' - user can specify any delays based on the trigger date:

** If the value 1 is entered, and use selects the time frame of Day with no Trigger Time selected, then the task will trigger 24 hours after the defined Trigger Date.

** If the value 1 is entered, and use selects the time frame of Hour, then the task will trigger 1 hour after the defined Trigger Date.

::* '''Activity Amount''': Level 2 field used to store the calculated amount for each record. If 'N/A' is selected, the Level 2s will be created without an amount.

::* '''Activity Index''': Level 2 field used to store the index number of each record. If 'N/A' is selected, the Level 2s will be created without an index number."

: If '''Schedule by Number of Activities''' option is selected then following settings are exposed.

::* '''Number of Activities''': Level 1 field used to set the number of activities to be created

::* '''Reminder Days''' - Sets delay for reminder message being sent.

===Task Type: Generate PDF File===

Auto generation of a PDF that can be:

The PDF generated must be based upon a Web Page View Custom Field. You must specify the Custom Field ID of the Web Page View to be converted in the Web Page Field ID field on the Workflow Task settings.

Multiple PDFs can be created and stored in a single Link - Multiple Files custom field using this workflow task type, by entering the Custom Field IDs of the Web Page View fields, separated by commas.

::*::* '''Message Template: Message Type''' - Type of message – e-mail, instant message, both, or none required with this task. E-mail and instant messages can be created using variables that will create custom messages specific to instances of the workflow. Options are No Message Required (default), Quick Message, Email Only and Quick Message and Email.

{{Template:WorkflowMessageTemplate}}

::* '''Routing: Use Variable for Recipients''' - Allows recipients of the message to be selected using variables. See this article for configuration details.

::* '''Routing: Use UTA Role''' - When using roles to select recipients, the UTA Role can be used to determine recipients.

::* '''Routing: Routing Options''' - Specifies the types of options available to process this workflow step. In many instances, the default options can be used, such as Approved, Rejected or Revise. But additional and alternate sets of options can be created to reflect more complex business processes.

===Task Type: PDF Merge===

Will convert [[Custom Field Type: Special – MS Word Merge|Word Merge]] document to a PDF which can then be:

:::::* Stored within a Multiple Files Custom Field

The PDF generated must be based upon a [[Custom Field Type: Special – MS Word Merge|Word Merge]] Custom Field. You must specify the Custom Field ID of the MS Word Merge document to be converted in the MSWord Merge Field ID field on the Workflow Task settings.

::*::* '''Message Template: Message Type''' - Type of message – e-mail, instant message, both, or none required with this task. E-mail and instant messages can be created using variables that will create custom messages specific to instances of the workflow. Options are No Message Required (default), Quick Message, Email Only and Quick Message and Email.

{{Template:WorkflowMessageTemplate}}

::* '''Routing: Use Variable for Recipients''' - Allows recipients of the message to be selected using variables. See this article for configuration details.

::* '''Routing: Use UTA Role''' - When using roles to select recipients, the UTA Role can be used to determine recipients.

::* '''Routing: Routing Options''' - Specifies the types of options available to process this workflow step. In many instances, the default options can be used, such as Approved, Rejected or Revise. But additional and alternate sets of options can be created to reflect more complex business processes.

===Task Type: People Association===

You can use the People Association Workflow Task Type to automatically add one or more contacts to a Level 1 record. They will be assigned to the record with the UTA role defined in the "Roles will be assigned" setting.

** Sensitivity={personal,private,company,confidential}

*: e.g. Priority=urgent;Importance=high

** '''Message Template: Endpoint''' - The URL or IP address of the destination server

** '''Message Template: Envelope Template''' - The content of the Web Service message to be sent to the external service. This can contain variables related to the object the workflow is triggered against.

''<u>Example of Incorrect Configuration</u>'':

Two connectors are set up on a workflow task with conditions of:

If the workflow is fired against a record associated with typeID 67890, the workflow will never progress to the next task.

''<u>Example of Correct Configuration</u>'':

Three connectors are set up on a workflow task with conditions of:

''<u>Example of Incorrect Configuration</u>'':

The system administrator wishes to send emails via workflow if the record is in one of the above statuses. One email should be sent out if the type is 12345 or 45678 and a different email should be sent out if a different type has been used.

Two connectors are set up on a workflow task with conditions of:

Two connectors should be set up on a workflow task with the following conditions:

This configuration satisfies Rule #2, in that the conditions are now mutually exclusive. However, a third connector must be included, with the following condition, which connects to the "Complete" task, in order to satisfy Rule #1 above:

===Password Variables===

{{WorkflowTaskTypeCCEmailSyntaxOptions}}