Changes

The recipient of workflows (selected in the Acknowledgement, Request for Comment and Request for Approval task types) can be defined using variable syntax, rather than being limited to the list by role.

The benefits to using this approach is, you can send to multiple roles at the same time, rather than having to configure different tasks for each role.

Workflow Tasks can be exported and imported into other Workflows using the Import/Export function on the Edit Workflow page. This feature is particularly useful if you have created workflows for testing on your backup instance and wish to implement the finalized reports in your live system.

The steps to export a workflow task or set of workflow tasks are as follows:

• The Edit Workflow page will refresh to show the newly-added workflow tasks.

A logical statement can be added to workflow connectors in the Condition field, enabling you to specify which workflow task will be triggered.

Example Branching Logic can be implemented to send an approval message to Senior Management when the request is over $100,000, while requests under $100,000 will take a different path when the workflow is triggered.

It is recommended that workflows with a loop include an empty task with 2 connectors with 2 separate conditions, one which goes back to the looped task and another which proceeds on to the next task, thus preventing an endless loop.

Note: Other than values that are always numeric, all variables should be enclosed in double quotes.

iCalendar is a file format that allows Internet users to send meeting requests, contacts and tasks through email and other digital methods.

SmartSimple workflows support 3 email attachments types (ievent, itodo and icard).

@@

Workflows can be triggered based on a value in a custom field on the object using a browser script.

_triggerwf(objectid,workflowid,Entity ID);

To access the workflows list, click the menu icon in the action bar, followed by the Workflows link in the System Process section.

The following tabs are also displayed:

Clicking on the Diagram button in the action bar of the Edit Workflow page will bring up a graphical representation of the Workflow Tasks that have been configured on that workflow.

System Administrators use this feature to document and troubleshoot complicated workflow configurations.

On the Edit Workflow page, the Pending Queue tab shows all instances where the workflow in question has been triggered, and the task has been scheduled for future completion. The last column shows the "Objectid" of the entity against which the workflow was fired.

In the Edit Workflow page, the history of an individual Workflow can also be accessed by the History tab. This page shows all instances of the workflow being triggered. The last column shows the "Objectid" of the entity against which the workflow was fired.

The Workflow History tab is made visible for a given Universal Tracking Application™ by enabling the relevant Manager Permission. Go to UTA – Settings – Security, click on Feature and Function Permissions. The Enable Workflow History setting is found on the Feature tab.

The user creating the workflow must have permission to set company workflow trigger.

Go to Global settings – Security – System Feature Permissions , go to the Action Permission tab and scroll down to the Workflows - Attach Workflow to Company setting. There should be a Lookup button to select the roles that should be allow them to do attach the workflow.

Once the role is selected, the options will display in the edit company view.