‍Legacy Workflow Template Filter

Traditionally we used the legacy "Workflow Template Filter" available within the Workflow Designer in the Teamcenter Rich Client to assign workflow templates to groups in Teamcenter based on different Item Types.  This method has been deprecated for several releases of Teamcenter and is no longer available in Teamcenter 14.
‍

Now Using CONDITIONS

In the current and new releases of Teamcenter we will create and use CONDITIONS to manage the filtering of workflow templates.  Conditions are powerful expressions which will qualify the use of workflow templates based on one or many different criteria we define.  This method of filtering workflow templates provides much more flexibility and capabilities than the traditional tools we used previously.
‍

The following process represents the steps required to Filter our Workflow Templates using CONDITIONS:

1) Using BMIDE, we create the CONDITIONS and define the criteria we will use to assign available templates to the end user.

2) Save and Deploy our new CONDITIONS to the database.

3) Use Workflow Designer to apply the newly created CONDITIONS to the different Workflow Templates we wish to be used by the end users.
‍

Once the above process is complete the user will now see only the available Workflow Templates from the New Process Dialog based on their Group/Role and Object Type that is selected.  Using CONDITIONS, should take the guesswork out of choosing the Workflow required to complete the process and will also ensure that the user selects the correct target object for submission.
‍

Using CONDITIONS to filter workflow template availability

You can create Business Modeler IDE conditions for use in filtering availability of workflow templates. Conditions can include versatile criteria for filtering, including:

• Session group, role, and user.
• Target object type
• Target project and target release status.
• Custom criteria, both session-specific and target-specific, that a Teamcenter administrator can create.

In the rich client Workflow Designer, the Attributes dialog box for a workflow task, the Filter Condition attribute lets you select a condition to evaluate template filtering.

Conditions will appear in the Filter Condition list if they meet the following requirements:

• The condition name meets the naming requirement as configured in the Fnd0FilterCondition dynamic LOV.
  As shipped, the naming requirement is that the condition name contains WF.

• The condition contains the following parameters:‍
• WorkspaceObject o
• ImanType t
• UserSession u

Workflow template filters affect:

• The Process Template choices displayed by the New Process Dialog dialog box.
• The Process Template List choices displayed by the New Item dialog box Define Workflow Information page.

When a workflow process is being created for a selected object, its WorkspaceObject parameter is used for condition evaluation to get a filtered list of workflow templates. While creating a new Item, as the object is not yet created, filter condition evaluation can use object ImanType parameter to get the list of filtered workflow templates. The UserSession parameter is used to evaluate user session values such as user, group, and role.

EXAMPLE CONDITIONS CREATED USING BMIDE:

You can start by creating some base level conditions that check for one thing and then combine them together to check for multiple criteria.

NOTE:

When naming the Conditions, we will use WF in the name so that they get added to the Filter Condition list when applying the Condition using Workflow Designer below.

So first we will create some base level conditions, for example "Check for Group" and "Check for Object Type", then when we have these created, we can combine them together to qualify the template to use.

The following Condition checks whether the user initiating the workflow belongs to the Engineering Group

Expression:

u.fnd0ConditionHelper.fnd0isSubGroupOf (u.group,"Engineering")

‍

Another base level condition to use, will check for the object type.

The following Condition checks whether the Object selected to submit is of the correct type:

Expression:

((o != null) AND u.fnd0ConditionHelper.fnd0isSubTypeOf (o, "DF4_DFItemRevision")) OR ((t != null) AND u.fnd0ConditionHelper.fnd0isSubTypeOf (t, "DF4_DFItemRevision"))
‍

The Second step would be to combine the above CONDITIONS together in a third to check both the User Group and the Object Type is correct for the Workflow Template.

Expression:

(Condition::DF4_EngWF (o, t, u) = true) AND (Condition::DF4_Eng_Type_WF (o, t, u) = true)

Now that we have the above conditions created, we can Save our BMIDE Project and Deploy these changes to complete out our steps in BMIDE.

Apply CONDITIONS using Workflow Designer:

Next, we can use Workflow Designer to apply the newly created Conditions to the Workflow Templates.

For this example, we will only apply the above CONDITION to the following Workflow Templates:

• 1 Check Attachments Based on Draft - PDF
• Quick Release1

1) Open Workflow Designer and Edit the Workflow Template that you want to Filter:

2) Select the Attributes panel and choose the combined Condition:

3) Apply the Combined Condition to check for both User Group and the Object Type:

4) Close the Attributes Panel, then save the Workflow Template by selecting the checkbox to Set Stage to Available:

‍

Here we simply repeat the above steps for the Quick Release1 Workflow Template:

1) Open Workflow Designer and Edit the Workflow Template that you want to Filter:

2) Select the Attributes panel and choose the combined Condition:

3) Apply the Combined Condition to check for both User Group and the Object Type:

4) Close the Attributes Panel, then save the Workflow Template by selecting the checkbox to Set Stage to Available:

Now we simply login to the client as a user with Engineering Group Role and Select the Object Type:

In this example:

• We will login as the user rob with the Engineering Group
• Select the Object Type of DF Item Revision
• Then Select the "New Workflow Process…"

‍

Now we will see the following Workflow Templates available based on our CONDITION:

‍

In Active Workspace,  

Select & open the object

Now with the object open, Select the Manage Icon on the Right Side of the display to Submit to Workflow Process:

Now we will see the following Workflow Templates available based on our CONDITION: