NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm

Workflow Channels and tabbed dataforms

When configuring Workflow Channels, you can reference data from a tabbed dataform set:

  • On the Content step

  • On the Conditions step

On the Content step

On the Content step, you can set user fields to values that exist on dataforms across a tabbed set. Let's say that you have a parent dataform and it has a few child dataforms — we call this a tabbed relationship. And, you want to be able to reference user fields on both dataform types.

So, in the Content step of configuring the workflow channel, when you select Assigned To, the Assigned to Options dialog offers the User Source as Current User, Specific User, and From a Field on a Form. When you select From a Field on a Form, you have additional choices — from which Dataform and then when you select a dataform, which Field. The items in the Field list are driven by the Dataform you select.

The user type fields on workflow item tasks and dataforms include any child forms in a tabbed relationship with the available selected dataform when the user source option of From a Field on a Form is selected. The child form name has an asterisk, as in the following example: *Employee -- Project User (ProjectUser).

These tabbed form fields appear in the Field list below the primary form field in the tab relationship and are formatted as follows:
*<ChildFormName> — <UserFieldName>

Example

A form named Form Parent is in a tabbed relationship with Form Two and Form Three. Form Two and Form Three are child forms to Form Parent. Each form contains user fields.

Let's say you have the following scenario in the Assigned To Options dialog:

  • In Dataform, Form Parent is selected.

  • In Field, the fields for Form Parent are listed at the top of the Field selector, and fields from the child forms are available below the primary form in the following format:

*Form Two -- User By Role (fkUserByRoleID)
*Form Two -- Specialist User (fkSpecialistUserID)
*Form Three -- Other User (fkOtherUserID)

Keep in mind, all of these fields are user fields. You can select any user field from a child dataform. You can also select a user field from the parent form and any single dataforms.

Example

The following example shows a parent form named Tony Test Form in the Dataform list. Tony Test Form is a parent form to Form One. When Tony Test Form is selected, the Field field displays all user-related fields from the parent form and child form. For Fields, you can select a field from the parent form (in this case Tony Test Form) or you can select fields from any child dataforms. Child forms are denoted with an asterisk (*), as shown in the following example.

 

On the Conditions step

Workflow Channels include all active tabbed forms on the Conditions step of a workflow item when the triggering form is the home form of a tabbed set.

Source and Field lists

The Source list includes all active tabbed forms included in the tabbed set when the triggering form is the home form of a tabbed set. In the Source list, the primary tabbed dataform precedes the child tabbed forms. The child tab names are prepended with a dash ““. The Field list is filtered based on the selected Source.

This example shows that for the Source column, Tony Test Form is the parent, and Form One is the child.

The following example shows the Source column with a child dataform selected (-Form One) and in the Field column, a field named State Lookup 2 is selected.

Conditions

Condition Expressions operators (AND, OR, and NOT) work across multiple dataforms. You can configure conditions for task workflow channel items from the most recent parent dataform if your tasks are multiple levels deep. This enables you to refer back to the child dataform logically. (For example, a milestone triggers a Case, and the Case triggers multiple layers of Tasks, all Tasks can reference the Case).

  • Source includes the most recently referenced dataform that would trigger the initial task (single or multi).

  • Condition Expressions operators (AND, OR, and NOT) work across multiple dataforms.

  • IsDirty does not appear in the trigger operator list because the task can be separated from the dataform by several other tasks; the dataform may not be dirty.

  • The Add Untriggered functionality is available when adding fields from this source.

  • If the most recent dataform is the main triggering dataform for the workflow, the condition Source will be Channel Trigger: <NameOfTriggeringForm>.

  • If the most recent dataform is a cloned dataform workflow item, the condition Source will be Workflow #<ItemNumber>: <ItemName>.

NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm