Business Process Knowledge Template Version 5 Release 14 Page 1

Business Process Knowledge Template

Overview
Conventions
What's New?
Getting Started
Generating the User Workbench
Using the User Workbench
Basic Tasks
Setting up the working Environment
Reminder
Creating the Working Environment for the Expert User
Managing the Data Generated by the Expert User
Creating an Environment under Windows
Creating an Environment under Unix
Defining an Application Workbench
Working with technological Objects
Creating a Technological Object
Adding a Component to a Technological Object
Adding an Attribute to a Technological Object
To know more about the Add Attribute Dialog Box
Generating a Report
Working with Behaviors
Creating Behaviors
Combining Behaviors
Defining and Linking Behaviors
Working with Behaviors Patterns
To know more about patterns
Generating a User Workbench
Working with a User Workbench
Testing and Replaying the Process
To know more about the Operate Function...
Fixing a problem
Intervening when Instantiating Objects
Exploiting the Messages Displayed when Executing Behaviors
Managing Errors
Using the Error Check Tool
Working with a User Workbench
Getting Familiar with the End-User Workbench
Executing Behaviors
Editing Behaviors
Business Process Knowledge Template Version 5 Release 14 Page 2
Advanced Tasks
Knowledge Relations: Using the if...else Syntax
Using a Sequential Combination to instantiate a User Feature
Using the Insert Components behavior: Auto update mode
Using the Propagate Execution behavior
Using the Onxxx Behaviors
Using the Knowledge Certify Behavior
Using the Instantiate Template Behavior
Designing a Table using the Generate Component Behavior
Using the Loop Behavior
Use Cases
Creating a User Workbench: Indirect Vision
Before you start
Setting up the Working Environment
Creating technological Objects
Defining the "Define Vehicle Data" Combination for the IndirectVision object
Defining the "Define Driver" Combination on the IndirectVision Object
Defining a "Compute optimal Mirror" sequence for the Indirect Vision technological Type
Defining a "Generate Report" Behavior on the Indirect Vision technological Type
Defining a "Generate Indirect Field of View for a planar Mirror" Combination on the Driver
technological Type
Defining a "Check Driver Position" Behavior on the Driver technological Type
Generating the User Workbench
Designing the external Mirror
Computing the optimal Mirror
Optimal CATIA PLM Usability for Business Process Knowledge Template
Reference Information
Introducing the Structure Behaviors
Logical Combination
Sequential Combination
Loop Behavior: Data Sheet
Generate Components Behavior: Data Sheet
Introducing the Infrastructure Behaviors
Implementation Behaviors
VBScript Behavior
Command Behavior
URL Behavior
ActiveX URL Behavior
System Behavior
IO Based Behaviors
Link Input From Behavior
Synchronize Parameters Behavior
Bind Behaviors
Bind Object Behavior
Bind Reference Behavior
Bind Parameter Behavior
Bind Instance Behavior
Bind Type Behavior
To know more about the Bind Mechanism...
Business Process Knowledge Template Version 5 Release 14 Page 3
List Behaviors
Add item Behavior: Data Sheet Behaviors
Remove item Behavior: Data Sheet Behaviors
Get item Behavior: Data Sheet Behaviors
Propagate Execution Behavior
Information Behavior
Add Type Behavior
Introducing the Design Behaviors
Reuse Behaviors
Instantiate Template Behavior
Create External Reference Behavior
Copy/Paste Behavior
KWScript Behavior
Document Behaviors
Load Document Behavior
Create New From Behavior
FilterCatalog Behavior
Bind Behaviors
Bind PowerCopy Behavior
Bind UDF Behavior
Bind Part Behavior
Bind Publication Behavior
Bind Product Instance Behavior
Display in Window Behavior
Insert Components Behavior
Knowledge Relations Behavior
Knowledge Certify Behavior: Data Sheet
Introducing the Event-based Behaviors
On Done Behavior
On Create Behavior
On Remove Behavior
On Cancel Behavior
Workbench Description
Type Tools Toolbar
Knowledge Tools Toolbar
Design Tools Toolbar
Infrastructure Tools Toolbar
Technological Object Toolbar
User Application Toolbar
Specification Tree Description
Interface Description
Customizing
Glossary
Index
Business Process Knowledge Template Version 5 Release 14 Page 4

Overview
Welcome to the Business Process Knowledge Template User's Guide. This guide is intended for users who need

to become quickly familiar with the BKT workbench.

This overview provides the following information:

● Business Process Knowledge Template in a Nutshell

● Getting the Most out of this Guide

● Accessing Sample Documents

● Conventions Used in this Guide

Business Process Knowledge Template in a Nutshell

The CATIA - Business Process Knowledge Template solution allows companies to capture their business
processes, and to share and deploy them through dedicated workbenches. An expert can model any corporate
best practices and know-how. From complex conceptual studies in the automotive to airframe structure
generation, the expert captures, automates design and engineering tasks, and embeds core-knowledge rules
and checks within those tasks. As a result, he delivers the captured best practices through a specific pseudo-
application including all the required features and processes.

To reach that objective, the CATIA - Business Process Knowledge Template solution takes advantage of the
range of CATIA V5 products.

Finally, the end-user can access these pseudo-applications, as he can access any CATIA V5 products. He can
then create products while following a pre-defined methodology, resulting from the corporate best practices
definition and capture provided by the experts.

The Business Process Knowledge Template solution is divided into an authoring product, CATIA - Business
Process Knowledge Template 3 (BKT), and an end-user solution, CATIA - Business Process Knowledge Template
2 (BK2).

This product enables the expert user to:

● Capture business processes and best practices.

● Automate design and engineering tasks.
● Generate design assistants in a simple and intuitive way.
● Deploy best practices and know-how in an easy-to-reuse way.
● Accelerate and secure design process time.

Capturing business processes and best practices...

Business Process Knowledge Template Version 5 Release 14 Page 5

Creating a design assistant supposes that, beforehand, the corporate processes and best practices have been
identified. By using CATIA - Business Process Knowledge Template 3 (BKT), an expert can capture and capitalize
this knowledge, packing and combining the corporate processes and best practices inside a pseudo-application.
In order to ensure a global process coverage, these applications can be enriched by several experts, coming
from different disciplines.
This knowledge capture is made in the CATIA environment through its interface.

Automating design and engineering tasks...

From the identified processes and practices, the expert organizes the different design tasks and creates tasks
sequences. All the CATIA products functionalities can be inserted and reused in a design sequence as a result of
the V5 knowledge-based architecture.
The created tasks and the entire sequences can be automated. Complex or repetitive sequences, for example,
can then be run automatically. If needed, users can also perform these sequences manually, task by task.

Generating design environment in a simple and intuitive way...

The creation of a pseudo-application using CATIA - Business Process Knowledge Template 3 (BKT) benefits from
the CATIA V5 functionalities. An expert can use, without coding, the different building blocks provided by the V5
portfolio products and combine them altogether.
The result of this building process is a dedicated pseudo-application workbench generation integrated into the
V5 environment. The end-user benefits from the CATIA V5 products and generated pseudo-applications
synergy.

Deploying best practices and know-how in an easy-to-reuse way...

The pseudo-applications created using CATIA - Business Process Knowledge Template 3 (BKT) benefit from the
user friendly CATIA V5 interface. They embody the deployment of the corporate knowledge and know-how
within the V5 frame and consistency with the other V5 portfolio applications.

Accelerating and securing the design process time...

Finally, the end-user can access, in a V5 environment, one or several specific pseudo-environments, each
embodying specific best practices.

Getting the Most out of this Guide

This book describes how to use the Business Process Knowledge Template product. Before you read it, you
should be familiar with basic concepts such as document windows, standard tool bars, and view tool bars.

To get the most out of this guide, you should start with the tutorial in the Getting Started section.

The remaining sections of the book describe in detail the procedures for using all of the features of the Business
Process Knowledge Template product. The procedures are divided into basic, advanced, and customization
sections.

Accessing Sample Documents

Business Process Knowledge Template Version 5 Release 14 Page 6

To perform the scenarios, you will be using sample documents contained in the online/bktug/samples folder.

For more information about this, refer to Accessing Sample Documents in the Infrastructure User's Guide.

Conventions Used in this Guide

To learn more about the conventions used in this guide, refer to the Conventions section.
Business Process Knowledge Template Version 5 Release 14 Page 7

Conventions
Certain conventions are used in CATIA, ENOVIA & DELMIA documentation to help you recognize and understand
important concepts and specifications.

Graphic Conventions
The three categories of graphic conventions used are as follows:

● Graphic conventions structuring the tasks

● Graphic conventions indicating the configuration required

● Graphic conventions used in the table of contents

Graphic Conventions Structuring the Tasks

Graphic conventions structuring the tasks are denoted as follows:

This icon... Identifies...

estimated time to accomplish a task

a target of a task

the prerequisites

the start of the scenario

a tip

a warning

information

basic concepts

methodology

reference information

information regarding settings, customization, etc.

the end of a task

Business Process Knowledge Template Version 5 Release 14 Page 8

functionalities that are new or enhanced with this release

allows you to switch back to the full-window viewing mode

Graphic Conventions Indicating the Configuration Required

Graphic conventions indicating the configuration required are denoted as follows:

This icon... Indicates functions that are...

specific to the P1 configuration

specific to the P2 configuration

specific to the P3 configuration

Graphic Conventions Used in the Table of Contents

Graphic conventions used in the table of contents are denoted as follows:

This icon... Gives access to...

Site Map

Split View mode

What's New?

Overview

Getting Started

Basic Tasks

User Tasks or the Advanced Tasks

Workbench Description

Customizing

Reference

Methodology

Glossary
Business Process Knowledge Template Version 5 Release 14 Page 9

Index

Text Conventions
The following text conventions are used:

● The titles of CATIA, ENOVIA and DELMIA documents appear in this manner throughout the text.
● File -> New identifies the commands to be used.
● Enhancements are identified by a blue-colored background on the text.

How to Use the Mouse

The use of the mouse differs according to the type of action you need to perform.

Use this
mouse button... Whenever you read...

● Select (menus, commands, geometry in graphics area, ...)

● Click (icons, dialog box buttons, tabs, selection of a location in the document window,
...)
● Double-click
● Shift-click
● Ctrl-click
● Check (check boxes)
● Drag
● Drag and drop (icons onto objects, objects onto objects)

● Drag
● Move

● Right-click (to select contextual menu)

Business Process Knowledge Template Version 5 Release 14 Page 10

What's New?

Enhanced Functionalities
3D PLM Integration
Document Chooser integration and support of DLNames
You can now customize the document environment in order to select documents or paths using
various interfaces (folder, SmarTeam, and so on). The interface can be customized for a folder or DLName
path selection interface. Note that only catalogs can be accessed using this capability in Business Process
Knowledge Template. To know more, refer to the Document topic in the CATIA Infrastructure User's Guide.
Business Process Knowledge Template Version 5 Release 14 Page 11

Getting Started
The following short tutorials provide an introduction to the Business Process Knowledge Template product.
They are intended to give expert users (P3 scenario) and end-users (P2 scenario) a feel for the product's
capabilities in 2 step-by-step scenarios.

This scenario is taken from the interior packaging domain of vehicle design. Here the user instantiates
passengers into a vehicle.

Generating the User Workbench

Using the User Workbench

Business Process Knowledge Template Version 5 Release 14 Page 12

Generating the User Workbench

This topic provides the expert user with a short example. In this scenario, he will create an application
that will enable him to instantiate passengers into a vehicle. He will be able to select the government
legislation to be tested, the automotive standard as well as the number of passengers.

To carry out this scenario, you need the following files:

● BktDriver2D5Female.CATPart

● BktDriver2D50Male.CATPart

● BktDriver2D95Male.CATPart

● BktPassenger-2D-5-Female.CATPart

● BktPassenger-2D-50-Female.CATPart

● BktPassenger-2D-95-Male.CATPart

● BktManikins.catalog

These files are to be saved in specific directories. To know more, see Creating the Working
Environment for the Expert User.

The scenario is divided into the following steps:

● Creating a technological type, called Interior. This type will be instantiated into the user
workbench.

● Adding attributes to the technological type: These attribute will enable the user to filter the
catalog containing the manikins to insert.

● Adding behaviors to the technological type: The user creates a sequence that is made up of
the following behaviors:

❍ Filter Catalog Behavior: Enables the user to select a document

to be loaded.
❍ Load Behavior: Enables the user to load the document.
❍ Bind Object Behavior.
❍ Insert Component Behavior.
Testing the workbench
Business Process Knowledge Template Version 5 Release 14 Page 13

Creating a technological Type

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench.

2. Create the Interior technological type. To do so, proceed as follows:

❍ Click the Create Technological Type icon ( ) to create a type. The Create
technological type dialog box displays.

❍ Enter the name of the type: Interior.

❍ Click OK to validate.

To know more about the technological types, see Creating a Technological

Object.

Adding Attributes

3. Add a Legislation attribute to the technological type. To do so, proceed as follows:

● Click the Interior type in the specification tree and click the Add Attribute icon (

). The Add Attribute dialog box displays.

● In the Name field, enter the name of the attribute: Legislation.

● In the Type scrolling list, select String. The attribute is an input of the technological
type that will be changed by the end-user (if need be).

● In the Value field, enter EEC.

Business Process Knowledge Template Version 5 Release 14 Page 14

● Click OK to validate. Double-click the Interior type: Legislation now displays in the
Attributes tab.

4. Add a Standard attribute to the technological type. To do so, proceed as follows:

● Click the Interior type in the specification tree and click the Add Attribute icon (

). The Add Attribute dialog box displays.

● In the Name field, enter the name of the attribute: Standard.

● In the Type scrolling list, select String. It is an input of the technological type that
will be changed by the end-user (if need be).

● In the Value field, enter SAE.

● Click OK to validate. Standard now displays in the Attributes tab.

5. Add a NumberOfPassengers attribute to the technological type. To do so, proceed as follows:

● Click the Interior type in the specification tree and click the Add Attribute icon (

). The Add Attribute dialog box displays.

● In the Name field, enter the name of the attribute: NumberOfPassengers.

● In the Type scrolling list, select Integer. This is an input of the technological object
which enables the end-user to modify it.

● In the Value field, enter 2.

Business Process Knowledge Template Version 5 Release 14 Page 15

● Click OK to validate.

6. Save your file (name it T1 for example) in the directory specified by the environment variable

CATGraphicPath of your V5 environment. To know more, see Setting up the Working

Environment. Don't close your file.

7. Generate your workbench. To do so, proceed as follows:

❍
Click the Generate Applicative

Workbench icon ( ).
In the Workbench Name field of

the opening dialog box, enter the

name of the workbench, T1 in this

scenario.

For the Workbench type, select

Product

Click OK to validate.

❍ Click OK in the File Name dialog box. A new application opens corresponding to

the end-user workbench.

8. Instantiate the technological object and associate it with the product. To do so, proceed as

follows:

● Click the root product in the specification tree to activate your workbench
Business Process Knowledge Template Version 5 Release 14 Page 16

● Select the icon

associated with
the type (if any)
or click the
technological
type check box
in your
workbench
toolbar: You can
see the
technological
object and the
product.

Click the Product, then Technological specifications View icon ( )

to visualize your technological objects.

Using the Interior contextual menu, the user can edit the definition of
the Interior technological object : He can modify the attributes values,
and add local attributes.

The product is now extended by the data of the technological object. If you open the F(x) editor, you
will see the product parameters as well as the technological object parameters. The product is typed
Interior and inherits from the behaviors of the technological type Interior that are still to be defined.

9. Save your file.

Go back to BKT workbench to define the behaviors that you want to associate with the technological
type.

Adding behaviors to the technological type: Define Passengers. The expert user
wants the end-user to instantiate data from a catalog depending on the standard, the
legislation and the manikin type (driver or passenger). The system instantiates the
number of instances specified by the user.

10. Click the Interior type and click the Sequential Combination icon ( ) in the Structure toolbar.
SequentialCombination displays in the Behaviors View in the specification tree.

11. Double-click SequentialCombination in the Behaviors View, then double-click Interior in the

Behaviors tab: The SequentialCombination is now available.

12. Double-click the SequentialCombination in the Behaviors tab. The Sequential Combination

editor displays.

❍ In the Name field enter Define passengers.

❍ Click the Icons... button to associate an icon with the behavior (optional).
Business Process Knowledge Template Version 5 Release 14 Page 17

❍ Click OK to validate.

Using a filtered catalog to select a manikin

13. Click the Define passengers behavior in the Behaviors tab and click the Filter Catalog behavior

icon ( ) in the Doc based toolbar.

14. Double-click the Filter Catalog behavior in the Behaviors tab. The Filter Catalog editor displays.

❍ Click the button in the Catalog document field to select the BktManikins.catalog file.

This catalog contains manikins matching the US and the EEC legislations.

If the catalog is stored in the CATGraphicPath directory, indicate only the name of

the catalog, if not, enter the whole path of the file.

❍
Add attributes to specify the query that will filter the catalog contents. To do so,

proceed as follows:

1. In the Filtering Keywords field, click the Add button. The Attribute Panel

displays.

2. In the Name field, enter Name.

3. In the Type field scrolling list, select String.

4. In the Value field, enter SAE.

5. Click OK in the Attribute Panel.

Add the Legislation parameter. To do so, proceed as follows:

1. In the Filtering Keywords field, click the Add button. The Attribute Panel

displays.

2. In the Name field, enter Legislation.

3. In the Type field scrolling list, select String.

4. In the Value field, enter EEC.

Business Process Knowledge Template Version 5 Release 14 Page 18

5. Click OK in the Attribute Panel.

Add the DriverOrPassenger parameter. To do so, proceed as follows:

1. In the Filtering Keywords field, click the Add button. The Attribute Panel

displays.

2. In the Name field, enter DriverOrPassenger .

3. In the Type field scrolling list, select String.

4. Click OK in the Attribute Panel. Click OK to validate.

Note that the names of the variables added in this field are identical

to the catalog keywords (open the catalog to check the keywords).

For the catalog to reuse the same value as the one defined in the technological object attributes,
establish links between the parameters of the behavior and the attributes of the technological object.
To do so, proceed as follows.
Business Process Knowledge Template Version 5 Release 14 Page 19

15. Expand the Filter Catalog node and right-click the Name attribute, select the Name object-

>Link to command, expand the Interior variables node and click the Standard attribute.

16. Right-click Legislation, select the Legislation object->Link To command, expand the Interior

variables node and click the Legislation attribute.

Testing the filtered catalog

17. Save your file and retest it. To do so, go back to the user workbench.

18. Right-click Interior and select the Interior (Product) object-> Define passengers

command. The Catalog Browser displays.

Business Process Knowledge Template Version 5 Release 14 Page 20

As you can see, the catalog was filtered: only the passengers matching the EEC legislation display.
Business Process Knowledge Template Version 5 Release 14 Page 21

19. Double-click one of the manikins. The manikin is still not loaded.

20. Modify the Interior object attributes: To do so, proceed as follows:

❍ Expand the Interior variables node.

❍ Double-click the Legislation attribute and enter US in the Edit Parameter dialog

box.

❍ Double-click the Standard attribute and enter SAE in the Edit Parameter dialog

box.

21. Right-click Interior and select the Interior (Product) object-> Control_Define passengers

command.

22. Click OK when asked if you want to withdraw Define Passengers.

23. Right-click Interior and select the Interior (Product) object-> Define passengers
Business Process Knowledge Template Version 5 Release 14 Page 22

command.

The Catalog Browser displays. As you can see, the catalog was again filtered: only 2 manikins are
available.

24. Close your product file.

Now go back to BKT to enable the end-user to load a manikin.

Loading and Inserting the Manikin

To load the manikin document into the current session, you need the Load behavior.

25. Click the Define Passengers combination and click the Load icon ( ). LoadDocument
displays in the Behaviors tab.

26. Double-click the LoadDocument node in the Behaviors tab. The Load Document editor

displays.

27. Click the File path field, expand the FilterCatalog variables node and select Chosen Path. It

contains the path of the document selected by the user in the Catalog Browser. Click OK to

validate.

You have to define where the loaded part will be inserted. In

this example, we decide to insert the manikin under the
product on which the Define Passengers behavior is going to
run.
This product does not exist yet, you must use the bind
mechanism, which is a way to access the data using the
specification tree.
For example, in the user workbench, if you want to find
Interior (Product.2) using the specification tree, ".." will enable
you to find Define Passengers, ../.. will enable you to find
Interior, and ../../.. will enable you to find the extended
product.

28. Click the Define Passengers combination and click the BindObject icon. BindObject displays in

the Behaviors tab.

29. Double-click the BindObject node in the Behaviors tab. The Bind Object editor displays.

❍ In the Relative Name field, enter ../../..

Business Process Knowledge Template Version 5 Release 14 Page 23

❍ Click OK to validate.

Now you want to insert your product. To do so, you have to use the Insert component behavior.

30. Click the Define Passengers combination and click the Insert Components icon ( ).
InsertComponents displays in the Behaviors tab.

31. Double-click the InsertComponents node in the Behaviors tab. The Insert Components editor

displays.

❍ In the Definition scrolling list, select Existing

component.

❍ Click the Existing component field, expand the LoadDocument variables node and

select the Document output. =Document displays in the field.

❍ Click the Father Product field to specify the instantiation context, expand the

BindObject variables node and select the output Link. =Link displays in the field.

❍ Set Allow sub typing to false in the Typing management field.

❍ In the Properties tab, set the Update mode to Auto.

❍ Click OK to validate.

32. Expand the InsertComponents variables node, right-click the Number attribute, select the

Number object->Link to command, and select the NumberOfPassengers attribute in the

Interior variables node.

Business Process Knowledge Template Version 5 Release 14 Page 24

33. Save your file in the \CATGraphicPath directory and test it one last time. Click here to display

the final .CATfct file (if you want to use it, open it and change the Filter catalog file path).

Testing the Workbench

34. From the Start menu, select the T1 workbench.

35. Select the root product and click the Interior icon (if any) or check box. The Interior type is

now associated with the root product.

36. Right-click the Interior (Product1) object in the tree and select the Interior (Product1)

object->Define Passengers command. The Catalog Browser opens.

Business Process Knowledge Template Version 5 Release 14 Page 25

Note that the

catalog is filtered
according to your
settings:

● Legislation:
EEC
● Standard:
SAE

37. In the Catalog, double-click the BKTPassenger-2D-5-Female manikin. The manikins are

inserted. (Use the compass if the manikins overlap in order to separate them.)

38. Expand the Interior (Product1) variables node.

39. Double-click the NumberOfPassengers attribute, set it to 1, and click OK to validate. One
Business Process Knowledge Template Version 5 Release 14 Page 26

manikin is removed.
Business Process Knowledge Template Version 5 Release 14 Page 27

Using the User Workbench

This scenario enables the end-user to instantiate a manikin into a product using the workbench
generated by the expert user.

● We assume that the end user is provided with the P2 license and not the P3 one.

● If the T1 workbench is not available in the Start menu, contact your expert user for him to copy
the files that he generated in the Generating the User Workbench topic into the appropriate
directories and to generate the workbench to enable you to replay this scenario.

Starting the T1 Workbench

1. Open Catia and close the default empty product.

2. From the Start menu, select T1.

You are now in the user workbench. The items defined in the *.CATfct file display in the toolbar located
in the right part of the screen. Note that the icons might be replaced with empty check boxes if no
icons were associated with the created types when the expert user defined the *.CATfct file.

3. Select the root product in the specification tree and click the icon to activate your
workbench (if need be).

Defining the Type

4. Select the product and click the Interior icon. The Interior type is assigned to the root

product.
Business Process Knowledge Template Version 5 Release 14 Page 28

5. Right-click the Interior (Product1) object in the tree and select the Interior (Product1)

object->Define Passengers command. The Catalog Browser opens.

Note that the

catalog is filtered
according to the
Interior's
variables
(attributes):

● Legislation:
EEC

● Standard:
SAE

6. In the Catalog, double-click the BKTPassenger-2D-5-Female manikin. The manikins are

inserted. (Use the compass if the manikins overlap.)

Business Process Knowledge Template Version 5 Release 14 Page 29

7. Expand the Interior (Product2) variables node.

8. Double-click the NumberOfPassengers variable (attribute), set it to 1, and click OK to validate.

One manikin is removed.

Business Process Knowledge Template Version 5 Release 14 Page 30

9. Double-click the Legislation variable (attribute) and set it to US. Click OK to validate.

10. Right-click the Interior (Product1) object in the specification tree and select the Interior

(Product1) object->Control_Define Passengers command.

11. Click Yes in the dialog box when asked if you want to withdraw Define Passengers.

12. Right-click the Interior (Product1) object in the tree and select the Interior (Product1)

object->Define Passengers command.

13. Select the BktPassenger-2D-95-Male manikin and click OK. The manikin is inserted.
Business Process Knowledge Template Version 5 Release 14 Page 31
Business Process Knowledge Template Version 5 Release 14 Page 32

Basic Tasks
This section contains explanations and scenarios showing the expert user how to create workbenches by
creating technological objects and basic behaviors. It also shows end-users how to use a workbench
generated by the expert user.

Setting up the Working Environment

Defining a Workbench

Working with a User Workbench

Business Process Knowledge Template Version 5 Release 14 Page 33

Setting up the working Environment

The information provided in these topics are designed to help the administrator:

● Create a working environment,

● Collect the information from the experts,

● Manage the data,

● And deploy the end-user workbenches.

Business Process Knowledge Template Version 5 Release 14 Page 34
If you need more information about the administration, refer to the CATIA Administration and Installation User's
Guide.

Reminder
Creating the Working Environment for the Expert User
Managing the Data Generated by the Expert User
Creating an Environment Under Windows
Creating an Environment Under Unix
Business Process Knowledge Template Version 5 Release 14 Page 35

Reminder

What is an environment?

An environment is a set of runtime environment variables. Each variable points to a path searched by the
software when you start a session.

What are Global and User environments?

A global environment can only be created by a Windows administrator, or the root userid on UNIX. For example,
the default environment created at installation is a global environment: "global" means that it is visible to and
can be used by all users on the computer on which it has been set up.

Global environments can only be created, edited or deleted by a Windows administrator, or the root userid on
UNIX.

A user environment is visible to and can be used and manipulated (customized or deleted) only by the user who
created it.

What does customizing an environment mean?

Customizing your runtime environment means providing different values for the runtime variables in your
default environment, or setting up new environments.

When customizing runtime environments, you can:

● Create new environments

● Edit existing environments

● Copy existing environments (UNIX only)

● Delete environments

The runtime environment variables to be modified by the administrator are listed in the table below:

Variable Name Description

CATGraphicPath Graphic and icon search path

CATStartupPath Sample file search path

CATUserSettingPath Permanent user setting search path

Business Process Knowledge Template Version 5 Release 14 Page 36

CATReferenceStandardPath Default reference standard path for standards (for example, 3D graphics
standards). Directory used by the administrator to deploy the workbench
generated by the expert user

CATTemp Temporary user setting search path

To know more, see the CATIA Administration and Installation User's Guide.
Business Process Knowledge Template Version 5 Release 14 Page 37

Creating the Working Environment for the Expert User

This topic explains how to create a working environment for the expert user. It is highly recommended for the expert user to
create a set of directories before he starts creating the workbench. This way, once the he is finished with the workbench
creation, the administrator copies the required data generated by the expert user into the appropriate directories.

First method

1. Create a tree structure similar to the one below. (In this example the tree structure is located on the e: drive, the "1"

located at the end of BKT1 indicates that the expert user can attribute whatever name to this directory.)

2. From the Start menu, select the

Programs->CATIA->Tools->Environment Editor V5R13 command.

3. Select the Environment->New command.

4. In the opening dialog box, enter the name of the environment to be created, BKT1 in this example.

5. Enter the path of your installation folder. The default installation folder path is:

C:\Program Files\Dassault Systemes\B10

6. Click OK to create the new environment.

7. Edit the CATUserSettingPath variable. Enter your settings (see picture below).
Business Process Knowledge Template Version 5 Release 14 Page 38

8. Exit the Environment Editor and click Yes to save your changes. Your environment is ready now you can start

creating the workbench.

Second method

1. From the Start menu, select the

Programs->CATIA->Tools->Environment Editor V5R13 command.

2. Select the Environment->New command.

3. In the opening dialog box, enter the name of the environment to be created, BKT1 in this example.

4. Enter the path of your installation folder. The default installation folder path is:

C:\Program Files\Dassault Systemes\B10\OS_a\

where "os_a" is the operating system, for example intel_a on Windows.

5. Click OK to create the new environment.

6. Edit the variables. To do so, proceed as follows:

●
Right-click the CATGraphicPath variable, select the Edit variable command and concatenate your path
(e:\BKT1\intel_a\resources\graphic) into the existing one (insert your data at the end of the existing path). What
you get onscreen should be similar to the picture below.
Business Process Knowledge Template Version 5 Release 14 Page 39

●
Right-click the CATStartupPath variable, select the Edit variable command and concatenate your path
(e:\BKT1\intel_a\startup) into the existing one. What you get onscreen should be similar to the picture below.

●
Right-click the CATUserSettingPath variable, select the Edit variable command and enter the following path:
e:\BKT1\CatSettings1
What you get onscreen should be similar to the picture below.
Business Process Knowledge Template Version 5 Release 14 Page 40

7. Exit the Environment Editor and click Yes to save your changes. Your environment is ready now you can start

creating the workbench.

Remember to save the files you create (.CATfct for example) or the files you reuse (.CATPart, CATProduct, CATScript files...)
in the appropriate directories. If not, you will not be able to generate the end-user workbench.

Copy ● .CATfct files Into the \CATGraphicPath directory. If this directory does not
exist, create the folder E:\temp. Make sure that this
● .CATPart files folder is empty when beginning the scenario. The data
will be saved here by the VBScript automation.
● .CATProduct files

● .CATProcess files

● .CATDrawing files

● .catalog files

Copy ● .CATScript files Into the \CATStartupPath\automation directory.

● .CATvbs files

Copy .HTML files Into the \CATStartupPath\html directory.

Copy The icons that you associated Into the …\CATGraphicPath\icons\Normal directory.
with the behaviors you created (if
any).
Business Process Knowledge Template Version 5 Release 14 Page 41
Note ● The CATSettings files created when generating the user workbench are stored in the CATSettings directory.

● If the expert user wants to use the applications made available by the administrator, he can use the
Environment Administrator to concatenate his data.

● The expert user should copy the following data into the CATSettings path: Files starting with B_ and the
FrameConfig file. (see picture below.)

The files generated by the expert user when creating the end-user workbench will be copied by the administrator into the
appropriate directories and deployed by him.
Business Process Knowledge Template Version 5 Release 14 Page 42

Managing the Data Generated by the Expert User

This topic is designed to provide the administrator with the guidelines required to deploy the workbench
generated by the expert user.

To deploy the workbench(es) generated by the expert user the administrator should:

1. Create (or copy) the same tree structure as the expert user. To get an example, see Creating

the Working Environment for the Expert User, steps 1 to 7.

2. Copy the CATSettings files generated by the expert user into his CATSettings directory (note

that the CATSettings files generated by BKT start with B).

3. Concatenate the data generated by the expert user with his data.

When creating the user environment, make sure to select the Global mode in the
Environment editor for the application to be available to all users.
Business Process Knowledge Template Version 5 Release 14 Page 43

Creating an Environment Under Windows

This task is designed to help the administrator create a user environment under Windows using
the Environment Editor.

To know more, see the CATIA Administration and Installation User's Guide.

1. Select the

2. Start->Programs->CATIA->Tools->Environment Editor V5R13 command.

3. Select the Environment->New command.

4. In the opening dialog box, enter the name of the environment to be created.

5. Enter the path of your installation folder. The default installation folder path is:

C:\Program Files\Dassault Systemes\B13\OS_a\

where "os_a" is the operating system.

6. If you logged on as administrator, enter the environment mode.

The type can be user or global (global is available only for administrators only). If you are
logged on as a normal end user, the type is set automatically to "user".

7. Set the product line to CATIA.

8. Check the Add Desktop Icon option if you want to create a desktop shortcut and an

entry in the appropriate Version 5 location of the Start->Programs menu.

Business Process Knowledge Template Version 5 Release 14 Page 44

9. Click OK to create the environment. The environment is created.

Business Process Knowledge Template Version 5 Release 14 Page 45

Creating an Environment Under Unix

This task is designed to help the administrator create a user environment under UNIX.

To create or customize an environment using the catiaenv command

There is now an interactive tool available for customizing values for runtime environment
variables: the catiaenv command.

Run the command as follows:

/usr/DassaultSystemes/B13/$OS_a/code/command/catstart -run catiaenv

where "OS_a" is:

● aix_a

● hpux_a

● irix_a

● solaris_a.

The Environment Editor appears. The user interface and functions are the same as under
Windows. For more information, refer to Creating an Environment Under Windows.

To create or customize an environment using the setcatenv command

The setcatenv command is available for customizing environments.

Run the command as follows:

/usr/DassaultSystemes/B13/$OS_a/code/command/catstart -run setcatenv

where "OS_a" is:

● aix_a

● hpux_a

● irix_a
Business Process Knowledge Template Version 5 Release 14 Page 46
● solaris_a.

To get the full list of options for the command setcatenv, see the CATIA Administration
and Installation User's Guide.
 Business Process Knowledge Template Version 5 Release 14 Page 47

Defining an Application Workbench

The topics of this section are designed to help the expert user create a new application.

The purpose of defining an application is to deliver efficient user interfaces to dedicated users. The purpose of BKT is to rely on
the CATIA V5 interface for an expert user to quickly program such applications by using building blocks such as catalogs,
document templates, UDFs, and V5 commands. The expert user can organize and control the various building blocks by the
means of behaviors pertaining to an object called a technological object. This object will enable the end-user to put in action the
right building blocks combination at the right time.

The diagram below provides the expert user with an overview of an applicative workbench definition process.

1- Before he starts creating the end-

user workbench, the expert user must
have defined the process to be
captured and created the features that
he intends to reuse like UDFs,
PowerCopies, VBScripts, CAA
commands...

2- The expert user starts with the

definition of technological objects, that
is to say a hierarchy of types, and sub-
types associated with variables
(attributes).

3- The expert user defines for every

technological object the behaviors that
correspond to the tasks that the end-
user will perform. To define a new
behavior, the expert user will use
"building blocks" (see graphic below)
that he will link with each other.

4/5- The expert user can test the user

workbench throughout the definition
process by generating the workbench
that will be used by the end-user.
Note that the user workbench only
needs to be generated once. If the
expert user modifies the .CATfct file,
the changes will also apply to the user
workbench.

In case of errors, the expert user can

locally modify the access rights to the
behaviors to edit them and to test the
new solution before he makes the
same corrections in the .CATfct file in
BKT.

The "building blocks" used by the expert user are ordered depending on their families (see graphic below.) Refer to the Working
with Behavior Patterns topic to see examples of behavior combinations.
Business Process Knowledge Template Version 5 Release 14 Page 48

Working with Technological Objects

Working with Behaviors
Generating a User Workbench
Working with a User Workbench
Testing and Replaying the Process
Business Process Knowledge Template Version 5 Release 14 Page 49

Working with Technological Objects

What is a technological Object?

A technological object is an object used in the Business Process Knowledge Template workbench.
A technological object is made up of three sets of components:

● A type
● A set of attributes
(variables)
● A set of behaviors

A type

Expert users can create their own types in Business Process Knowledge Template.
An engine, a gearbox or a windshield can be potential types.

A set of attributes (variables)

Attributes are added to the technological object and are located in the types hierarchy.
There are three different types of attributes:

Input attributes will be valuated by the user. Inputs are requirements, target values, working
hypothesis. For an engine for example, the number of cylinders is considered as an input.

Output attributes cannot be modified by the user. Outputs are valuated by behaviors.
For an engine, the power and the swept volume are considered as outputs.

Internal attributes are never seen by the user. This attribute type is used by the behaviors and is
used for storing intermediate results.

A set of behaviors

Behaviors are designed to describe how:

Business Process Knowledge Template Version 5 Release 14 Page 50

● To test, compute and evaluate object performances.

● The object behaves in a real environment.

Technological objects can be associated with structured CAD elements such as Parts, Products, Part Bodies and
other Bodies (Geometrical Set). They can contain other technological objects.

Managing technological Objects

The Business Process Knowledge Template workbench provides the expert user with an interface that he can
use to define and drive object types and sub-types, and attributes.

Creating a Technological Object

Using the Error Check Tool
Adding an Attribute to a Technological Object
To know more about the Add Attribute dialog box...
Generating a Report
Business Process Knowledge Template Version 5 Release 14 Page 51

Creating a Technological Object

This task explains how to create a technological object using the Business Process Knowledge
Template workbench and how to add sub-types to this object.

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench. The FeatureDictionary window opens.

2. Click the Create Technological Type icon ( ). The Create technological type dialog
box opens.

3. Enter the name of the object, Manikin in this scenario and click OK.

Manikin displays under the Classes

View node in the Feature Dictionary
tree.

4. Click the Manikin object in the Feature Dictionary tree and click the Create technological

Type icon ( ). The Create technological type dialog box opens.

5. Enter the name of the sub-type, Driver in this scenario and click OK to validate.

Driver displays under the Manikin

object in the Feature Dictionary tree.
Business Process Knowledge Template Version 5 Release 14 Page 52

6. Save your file, keep the file open and proceed to the next task: Adding an Attribute to a

Technological Object.

Please note that types names should not contain spaces and non-alphanumeric
characters.
Business Process Knowledge Template Version 5 Release 14 Page 53

Adding a Component to a Technological Object

What is a component?
A user can define that a technological object is
made up of instances of other technological
objects.
An engine is made up of 4 pistons, and 6
connecting rods for example. In this case, the
pistons and the connecting rods are the
components of the engine.

The composition enables the user to formalize the relations existing between different technological types
(technological objects).

Note that:

● The composition is a persistent notion. A derived type inherits the components defined on the father.
● In the user workbench, the father object can provide users with the lists of its components.

Getting Familiar with the Add components Behavior Interface

Creating the Add Components Behavior

To create a component, select the type to which the component will belong and click the Add components

behavior icon ( ) in the Technological Object toolbar.

Owner Name: This field cannot be modified by the user. The

name indicated in this field is the name of the type to which
the component will be added.
Name: Enter the name of the component that will be added.

Component Type: This type is either typed in the editor field

or the result of a selection in the Knowledge browser panel.
Note that the technological types present in the .Catfct
loaded in session can be retrieved from the technological
object directory.
To know more about the types available when clicking this
button, see the Reference section of the Knowledge Advisor
User's Guide.
Number of components: Enter the number of components
expected. In the graphic opposite, the maximum number of
legs is 4.
Business Process Knowledge Template Version 5 Release 14 Page 54

Using the Behavior

The component displays directly below the technological type attributes.

● ListSize: Current size of the list.
● TargetSize: The size to be reached. It is equal to the number of components
entered when creating the component.

To get an example, see Designing a Table using the Generate Component Behavior.
Business Process Knowledge Template Version 5 Release 14 Page 55

Adding an Attribute to a Technological Object

This task explains how to add an attribute to a technological object. See also To know more about the Add
Attribute dialog box...

1. In the specification tree, select the type (here Manikin) to which you want to add an attribute and click the

Add Attribute icon ( ). The Add Attribute dialog box displays.

2. In the Name field, enter Percentile.

In the Type scrolling list, select String.

In the Value field, enter 95Male and click

OK.

To know more about the AddAttribute dialog

box, click here.

3. Double-click Manikin: The Percentile attribute displays in the Local attributes field.

4. Click the Driver sub-type in the FeatureDictionary tree and click the Add Attribute icon ( ). The Add
Attribute dialog box displays.
Business Process Knowledge Template Version 5 Release 14 Page 56

5. In the Name field, enter L40.

6. In the Type scrolling list, select

Angle.

7. In the Value field, enter 25deg

and click OK. This value is a

default value.

The L40 attribute is added to the Driver

type and displays in the Local attributes
field. (Click the graphic opposite to
enlarge it.)

Save your file and proceed to the next task: Generating a Report.

● Note that the number of attributes added to a technological object is not limited.

● Note that an attribute name cannot be modified once it is created. To modify it, delete it and
create a new attribute.

● Note that an attribute name can only be made up of alphanumerical characters.

Note that sub-types inherit the attributes from their super types. In the example above, Driver inherits the
attributes from Manikin.
Business Process Knowledge Template Version 5 Release 14 Page 57

To know more about the Add Attribute dialog box...

You can access the Add Attribute dialog box by clicking the Add Attribute icon ( ) in the toolbar.

The Add Attribute dialog box is made up of 5

fields:
● Class Name
● Name
● Type
● With
● Value
● Quality

Class Depends on the item selected in the Feature Dictionary tree to which you want to add attributes
Name: (variables).

Name: Enter the name that you want to assign to the attribute (variable).

Type: Enter the type of the attribute (variable). The types displayed in this scrolling list are the same
types available in the Knowledge Advisor product. 2 types were added:
● Object: Enables the user to point to a V5 feature located in the same document on in another
document.
When pointing to another object located in another document, the pointed object and the
object that points the other object will both be loaded when loading.
● ExternalObject: Enables the user to point to a document. The referencing occurs when the
value is needed.
Business Process Knowledge Template Version 5 Release 14 Page 58
The user can use the List type to
create lists of points, lines,
objects...

If the user selects the List type, the

Edit List button displays enabling
the user to access the List Edition
window available in the Knowledge
Advisor workbench. To know more
about the List Edition window, see
Creating a List in the Knowledge
Advisor User's Guide.

Note that List attributes can

be added to all behaviors.

Value: Enter the default value of the attribute (variable) if any.

The Unset button enables you to set the value of this field to Unset.

Quality: Defines if the attribute (variable) will be used as an input, as

an output or as an internal parameter.

Note that the attributes of a technological type can be accessed by double-clicking the type in the Classes
View or by expanding the variables node of a behavior.
Business Process Knowledge Template Version 5 Release 14 Page 59

Generating a Report

This task shows how to generate a report that displays the technological objects and their sub-types.

This function allows you to generate an external HTML file. The report will display all the objects located under the
Classes View and the Referenced Dictionary of the specification tree. It will also display all the variables (attributes)
associated with an object.

1. Click the Generate Report button . The Save User Dictionary Report dialog box will display.

2. Navigate to the directory where you want to save the file, give the file a name and save it. The report will be

saved in HTML format.

3. To view the report open it in your Web browser.

The information
provided in those
files are the
following:
● Types and
sub-types

● Variables
(attributes)
assigned to
the types

Note that the

information
provided in the
report are
identical to the
ones displayed in
the .CATfct file
(see graphics
opposite and
below).
Business Process Knowledge Template Version 5 Release 14 Page 60
Business Process Knowledge Template Version 5 Release 14 Page 61

Working With Behaviors

● Introducing the Behavior Concept

● Defining a New Behavior

● Introducing the Basic Behaviors

● Introducing the Behaviors Interface

● Creating Behaviors

● Combining Behaviors

● Linking Behaviors

● Working with Behaviors Patterns

● Typing Behaviors Attributes

Introducing the Behavior Concept

A behavior is a set of tasks performed on a technological object. It can be a V5 command, a CAA command, an
external application, a VBA Command, or a behavior defined in BKT. It enables expert users to capture
sequences of tasks that are manually performed in V5, and enables end-users to use the knowledge contained
in the behaviors to perform tasks and procedures related to the technological object.

A behavior is made up of the following components:

A name and an optional Name displayed in the end-user workbench. The comment associated with
comment this name can help the end-user understand the behavior function.

A set of variables Inputs: Data entered by the user

Outputs: Result produced by the behavior
Internals: Defined for internal use as storage of intermediate results

A set of properties Icons ...

Defining a New Behavior

To define a new behavior, the expert user:

● Creates behaviors
Business Process Knowledge Template Version 5 Release 14 Page 62
● Combines existing behaviors

● Links behaviors to define the dependencies.

Introducing the Basic Behaviors

Structure Behaviors Allow to define two different combinations of behaviors:

(Logical and Sequential ● Ordered (sequential combination)
Combinations)
● Not ordered (logical combination)

● Loop

● Generate Component

Infrastructure Behaviors Implementation Behaviors: Enable to reuse existing code samples.

Bind Behaviors: Enable to access resources not yet available at the definition
stage.

Event-based Behaviors Enable to define what element reacts and how it reacts when something happens.

Design Behaviors Enable to reuse CATIA V5 functions.

Reuse:

● Paste as specification, as external reference

● Template reuse (PowerCopy and User Defined Feature)

● Generative Script

Document:

● Load, New From

● Query in catalog

Insert Components: Enables to create a new component, or to insert an existing

one taking the multi-occurrence into account.

Knowledge Relations Enable to define rules, checks and formulas that need to be validated during the
process or add logical control to the model.
Business Process Knowledge Template Version 5 Release 14 Page 63

Introducing the Behaviors Interface

Note that it is now possible for the user to add attributes of List type to behaviors. To know more, see To know
more about the Add Attribute dialog box...

The Behaviors interface is made up of 2 or 3 tabs depending on the behaviors:

● The Definition tab

● The Properties tab

● The Attributes tab

The Definition tab contains the information that needs to be specified for the behavior to execute correctly. To
know more about this tab (specific to every behavior), see the documentation related to the various behaviors.

The Properties tab

This tab contains the information required for the behavior execution.

Behavior States

The scrolling list enables the expert user to define who can see the behavior.

● All Users: The behavior can be seen by all users.

Business Process Knowledge Template Version 5 Release 14 Page 64
● Expert&Administrator: Only the expert and the administrator can see the behavior.

● Expert: Only the expert user can see the behavior.

Activate: If not checked, the behavior will not be part of the execution process.

AutoDelete: If checked, the expert user does not want to keep track of the behavior execution and the
behavior is removed after it is executed.

Focus: If checked, no other behavior asking for the focus will be started till the current behavior is executed.

Update

Driven: The behavior is updated when one of its input is

modified. The update will be triggered by a user, or by
another behavior (Propagate for example).

Auto: This mode is an extension of the Driven mode. The

update will occur automatically if the behavior is eligible for
update.

Single: The behavior is run once no matter its input is

changed or not.

Icon Definition

This field enables the expert user to modify the icon identifying the Behavior in the behaviors tree and in the
user workbench. A set of icons is available from the Icons... button. If you click this button, the Icon Browser
opens showing all icons loaded in your CATIA session.

To associate an icon with a technological object, define a name: I_nametype. For example for the
technological object Interior, the icon name is: I_Interior. To save the created icons in the appropriate
directory, see Setting up the working Environment.

The Attributes tab

Business Process Knowledge Template Version 5 Release 14 Page 65

Filter Local/All

Local attributes are those

defined by the expert user.
The other attributes are
defined by default.

Input/Output

The parameters displayed

in this field are the ones
displayed in the behaviors
tree.

The BState parameter,

when available, indicates
the status of the behavior's
child.

● Done

● Suspended

● Canceled

Enables to add a local attribute (variable). To know more, see To

know more about the Add Attribute dialog box... In case of a logical or a
sequential combination, the
Enables to modify one of the local attributes (variables). name of the behavior that
was last run displays in this
Enables to delete the local attributes (variables) created by the field.
expert user.

Note that:

● The behavior is also provided with a property defining if it can execute or not. As long as the inputs are not
valuated, this behavior cannot operate ( ).
● Behaviors attributes can be accessed by clicking the Attributes tab in the behaviors interfaces or below the
behaviors in the Behaviors tree.

Typing Behaviors Attributes

Business Process Knowledge Template Version 5 Release 14 Page 66
ExternalObjects, Objects, and Lists can be typed
to specialize the pointed items. If the value
stored in the ExternalObject, the Object, and the
List does not match the selected type, an error
message displays when operating or editing the
behavior. Note that ExternalObject, Object, and
List attributes can be typed: Those created by
the user as well as those belonging to the
behaviors.

To type an ExternalObject, an Object, or a List

attribute, proceed as follows:

1. Click the button in the Attribute

Creation panel to access the types

browser.

2. Select the Package and the type.

3. Click OK to validate.

To know more about the packages and types of

this browser, see the Reference section of the
Knowledge Expert User's Guide.

Creating Behaviors
Linking Behaviors
Combining Behaviors
Working with Behaviors Patterns
Reference Information
Business Process Knowledge Template Version 5 Release 14 Page 67

Creating Behaviors

To create behaviors, proceed as follows:

1. Select the type with which you want to associate

a behavior in the Feature Dictionary tree.

2. Click one of the behaviors icon. The behavior

displays in the Behaviors View.

3. To add new behaviors, double-click the behavior

in the Behaviors View. The Behaviors tab is now
available.

4. Double-click the object name displayed in the

Behaviors tab and click one of the behaviors icon.
The behavior displays below the object name.
Business Process Knowledge Template Version 5 Release 14 Page 68

Combining Behaviors

By using already defined building blocks, the expert user can create a new behavior. He can use combination
behaviors (Logical and Sequential Combinations) that can contain the components of the new behavior.
Business Process Knowledge Template Version 5 Release 14 Page 69

Linking Behaviors

A user workbench is made up of different behavior models and types combined by the expert user. Links
created between behavior variables (attributes) enable the expert user to define the data flow.

Given A and B, the variables (attributes) of 2

behaviors. If a link is created between A and B, A and
B will share the same value.

What is the data flow?

In the example above, for B to be valuated, the user must execute A. The links existing between the behaviors
are known as "data flow". They enable the user to define the order in which the behaviors will be executed.

To link behaviors, the expert user can choose one of the three solutions described below:

1. Right-click the behavior variable (attribute)

that you want to link in the Behaviors tree.
2. Select the ...object->Link To command.
3. Click the target behavior attribute. A link ( )
displays next to the linked object.

- OR -

1. Click the technological object variable (attribute) that you want to link in the Behaviors tree.

2. Click the Link/Unlink icon ( ) in the Technological Object toolbar.

3. Click the target behavior variable (attribute). A link ( ) displays next to the linked object.
Business Process Knowledge Template Version 5 Release 14 Page 70

- OR -

To link behaviors, the expert user can also use the user interface of the following behaviors. To know more
about this capability, refer to the following topics:
● Bind behaviors

● Insert Components behavior

● Copy/Paste Behavior

● Display in Window Behavior

● Link and Synchronize Parameters behavior

● Propagate Execution behavior

Business Process Knowledge Template Version 5 Release 14 Page 71

Working with Behaviors Patterns

You want Reuse Create a Sequential Click here to get

to... models in a Combination containing: an example.
product ● A Load Document or
structure a Create New From
behavior

● A Bind Object
behavior

● An Insert
Components
behavior

You want Filter a Create a Sequential

to... catalog with Combination containing:
parameters ● A Bind Parameter
behavior

● A Filter Catalog
behavior

You want Navigate in Create a Sequential Click here to get

to... the product Combination containing: an example. To
structure ● A Bind Object know more about
and retrieve behavior this pattern, click
a Part here.
feature ● A Bind Reference
from a behavior
product
instance ● A Bind Part behavior
Business Process Knowledge Template Version 5 Release 14 Page 72

You want Navigate in Create a Sequential To know more

to... the product Combination containing: about this pattern,
structure ● A Bind Object / Bind click here.
and retrieve Part behavior
a product
instance ● A Bind Product
from a Instance behavior
PartBody

You want Create an Create a Sequential Click here to get

to... external Combination containing: an example.
reference ● A Sequential
Combination to
retrieve the Part
feature

● A Sequential
Combination to
retrieve the
publication
containing a Bind
Object on father, and
a Bind publication

● An Import behavior

You want Instantiate Create a Sequential

to... a Combination containing:
UserFeature ● A Load Document
behavior

● A Bind UserFeature
● A Bind Object to
retrieve the part

● An Instantiate
Template (with
UseIdenticalName,
Valuate inputs and
BestStrategy)

You want Manage Create a Sequential

to... Errors Combination containing:
● An On Cancel
behavior

● An Information
behavior

● A Behavior whose
failure needs to be
trapped
Business Process Knowledge Template Version 5 Release 14 Page 73

You want Use a Create a Sequential To get an

to... condition Combination containing: example, see
(if ... then ● A Knowledge Knowledge
...) relations Relations: Using
- OUT_Act1 the if...else
- OUT_Act2 Syntax
- Rule on Act1 & Act2

● A Sequential
Combination_1
whose activity is
linked to OUT_Act1

● A Sequential
Combination_2
whose activity is
linked to OUT_Act2

You want React to a Create a Sequential

to... given event Combination containing:
and ● An On Done behavior
perform an
action ● A Bind Object
behavior
Business Process Knowledge Template Version 5 Release 14 Page 74

To know more about patterns

● The blue arrows show how a Bind Object->Bind Reference->Bind Part combination operates.
● The green arrows show how a Bind Object->Bind Product Instance combination operates.
Business Process Knowledge Template Version 5 Release 14 Page 75

Generating a User Workbench

This topic provides the expert user with a workbench generation example. To complete this
task, the user may use the CATfct file he created in another topic or he may use the provided
file.

To generate a user workbench and to test it, data should be located in the appropriate
directories as shown below:
Copy ● .CATfct files Into the directory corresponding to the
CATGraphicPath environment variable.
● .CATPart files

● .CATProduct files

● .CATProcess files

● .CATDrawing files

● .catalog files

Copy ● .CATScript files Into the \CATStartupPath\automation

directory.
● .CATvbs files

Copy .HTML files Into the \CATStartupPath\html directory.

Copy The icons that you associated Into the \CATGraphicPath\icons\Normal

with the types you created (if directory.
any).

To know more, see the administrator's topic: Setting up the Working Environment
Business Process Knowledge Template Version 5 Release 14 Page 76

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench.

2. Open the IndirectVisionStep03.CATfct file (or save the .CATfct you are working on in

CATGraphicPath directory).

3. Click the Generate Applicative Workbench icon ( ): The Applicative Workbench

Generation window displays.

In the Workbench Name field,

enter the name of the workbench

you want to generate: Indirect

Vision.

The Functional Library field

displays the name of the current

.CATfct.

In the Workbench Type scrolling

list, select Product. Click OK to

validate. The new workbench is

created.

If the expert user wants the end-user to work in a Product

structure , he should select Product in the Workbench
Type scrolling list when generating the workbench. To
know more about Product Structure, see the Product
Structure User's Guide.

If the expert user wants the end-user to work in a Part

structure , he should select Part in the Workbench Type
scrolling list when generating the workbench. To know
more about Part Design, see the Part Design User's Guide.

If the expert user wants the end-user to work in a System

context , he should select System in the Workbench Type
scrolling list when generating the workbench. To know
more about Systems, see the Product Functional
Definition User's Guide.
Business Process Knowledge Template Version 5 Release 14 Page 77

4. Close the opening window.

5. From the Start Menu, select the Indirect Vision workbench. The workbench opens.

6. Proceed to Working with a User Workbench.

Business Process Knowledge Template Version 5 Release 14 Page 78

Working with a User Workbench

This topic provides the expert user with a workbench use example. To complete this task, the
user may use the CATfct file he created in Generating a User Workbench or he may use his own
file.

1. From the Start Menu, select the Indirect Vision workbench (or the workbench you

created). The workbench opens.

2. Click the icon to activate your workbench and click the root product. The
workbench is now activated.

3. Click the IndirectVision icon to type your workbench. The product is now typed and

displays along with the associated variables.

Business Process Knowledge Template Version 5 Release 14 Page 79

To know more about variables and parameters ...

The items displayed below the typed product are the type parameters as well as the those
defined in Catia. Note that the user can filter the parameters/variables displayed using the
Tools->Options menu. To know more see, Customizing the Business Process Knowledge
Template Settings.

● Parameters added to extended objects using the f(x) icon are considered as:
1.
Internal parameters (IN) if prefixed with IN_

2.
External parameters (OUT) if prefixed with OUT_

3.
Neutral if they are not prefixed

● Publications (Part and Product) are considered as external parameters (OUT).

● External references (Part) are considered as internal parameters (IN).

Business Process Knowledge Template Version 5 Release 14 Page 80

Testing and Replaying the Process

This topic provides the expert user with an example showing how to test a workbench.

Remember to save the BktKnowledgeRelations.CATfct and the BktDriver-2D-SAE.CATPart and

BktDriver-2D-EEC.CATPart files in CATGraphicPath variable prior to performing this scenario..

1. Open the BktKnowledgeRelations.CATfct file. Edit the file path of the LoadDocument

behaviors to find the Parts in CATGraphicPath.

Generating the Workbench

2. Click the Generate Applicative Workbench icon ( ) to generate a user workbench.

Enter the name of the workbench, Knowledge in this example, as well as the workbench

type, Product here.

If the expert user wants the end-user

to work in a Product structure , he
should select Product in the Workbench
Type scrolling list when generating the
workbench. To know more about
Product Structure, see the related
documentation.

If the expert user wants the end-user

to work in a Part structure , he should
select Part in the Workbench Type
scrolling list when generating the
workbench. To know more about Part
Design, see the related documentation.

If the expert user wants the end-user

to work in a System context , he should
select System in the Workbench Type
scrolling list when generating the
workbench. To know more about
Systems, see the Product Functional
Definition User's Guide.
Business Process Knowledge Template Version 5 Release 14 Page 81

Testing the Workbench

3. From the Tools->Options-

>Knowledgeware menu, select Expert

in the Access Rights scrolling list and

click OK to work in an Expert

environment.

The generated workbench displays.

4. Select the document's root product in the specification tree and click the driver check

box to type the root product.

The root product name is now driver (Product1).

5. Right-click driver (product1) and select the driver (Product1) object-

>SelectingManikin command.
Business Process Knowledge Template Version 5 Release 14 Page 82

To visualize the process, it is recommended to use the technological Specifications

view. To open it, select the root of the specification tree and click the Open the

Technological Specifications View window icon ( ).

The following box displays:

Click Yes until no Pursue dialog box displays.

The manikin matching the US standard is inserted.

Business Process Knowledge Template Version 5 Release 14 Page 83

6. Double-click the Legislation variable (attribute) located below the driver (Product1)

feature and enter EEC in the opening dialog box.

7. Right-click driver (product1) and select the driver (Product1) object-

>SelectingManikin command.

8. Click Yes in the opening dialog boxes.

The manikin matching the EEC standard is inserted.

Business Process Knowledge Template Version 5 Release 14 Page 84

Fixing a Problem
Exploiting the Messages Displayed When Executing Behaviors
Intervening When Instantiating Objects
To Know More About the Operate Function...
Managing Errors
Business Process Knowledge Template Version 5 Release 14 Page 85

To know more about the Operate Function...

To operate the behavior, that is to say, to update its inputs and execute it, right-click the behavior in the
specification tree and select Operate or Local Update. When operating a behavior in expert mode, the expert
user can select one of the 2 following operating modes:

Operate This operate operation is global: It is applied

to the whole sequence (combination).
If the sequence inputs are not updated, the
operate operation is applied to the children
behaviors.
If the sequence is already updated, a panel
will display asking if you really want to
execute the sequence.

Local This operate operation is local, that is to say,

Update it is applied to the selected behavior. The
behavior is operated whatever the status of
its inputs.
If the behavior is already updated, a panel
will display asking if you really want to
execute the behavior.
Business Process Knowledge Template Version 5 Release 14 Page 86

Fixing a Problem
When testing a user workbench, you may encounter some problems. To solve them, proceed as follows:

1. From the Tools->Options-

Knowledgeware-

>Business Knowledge

Template menu, change

the BKT Access Rights from

All Users to Expert.

2. Expand the sequential combination seen as failed in the specification tree (or in the specifications

view). Edit the failed behavior ( identified by the icon), modify its inputs to fix the problem.

3. Right-click the behavior and

select Operate to operate it.

In Expert mode, you can

follow up the execution of

the behavior thanks to

warning panels (see graphic

opposite).

4. If the problem is solved and the behavior operates well, open the .CATfct file corresponding to your

workbench, make the corresponding changes and save your file.

Behaviors seen in the user workbench are just instances of those defined in the .CATfct file. For the
corrections made in the user workbench in Expert mode to be saved, the correction should be made
in the original .CATfct file.
Business Process Knowledge Template Version 5 Release 14 Page 87

5. Go back to your user workbench.

6. From the Tools->Options-Knowledgeware->Business Knowledge Template menu, change the

BKT Access Rights from All Users to Expert.

7. Start from an empty document and replay your scenario.

 Business Process Knowledge Template Version 5 Release 14 Page 88

Intervening when Instantiating Objects

When instantiating objects i.e. adding a type to a V5 feature, the user can execute tasks (create data that will
be used during the process). To do so, the user should define a VB script whose name has the following format:

TypeName_Instanciate.CATScript

When instantiating the objects, the script is executed.

In Expert mode, before executing the VB Script, the following message displays:

If the user selects Yes, the VB script is executed. If the user selects No, it will not be executed.

Note that the VB definition is optional.

Business Process Knowledge Template Version 5 Release 14 Page 89

Exploiting the Messages Displayed when

Executing Behaviors

In Expert mode, the messages displayed enable the expert user to follow-up the behaviors execution. The
expert user is asked for confirmation.

For the combination behaviors, the expert user will be prompted to validate the execution of the combination
internals. The expert user can interrupt the execution whenever he wants. The execution of the behaviors will
start where it stopped when the expert user re-executes the behaviors.

There are three different types of messages:

This message is the first one to be

displayed. It displays when the first
behavior is about to be executed.

This message is the second one to

be displayed. It displays for every
behavior. If contained in a
combination, the behaviors execute
first, then the combination (logical
and sequential combinations)
executes.

If the user click no, the execution

is stopped. To restart the
execution, the Update icon should
be used.
Business Process Knowledge Template Version 5 Release 14 Page 90

This message is the last one to be

displayed. It displays only when
main behaviors are executed or
when behaviors, set to AutoDelete,
are executed. If the user click Yes,
the behavior will be deleted. If the
user click No, the behavior will not
be deleted and is still visible in the
graph.
 Business Process Knowledge Template Version 5 Release 14 Page 91

Managing Execution Errors

The management of execution errors aims at:

● Enabling expert and end users to better understand the errors that may occur when operating a behavior. There are 5
different errors:

❍ Input Errors made by the expert user when creating a behavior: One of the inputs of a behavior was
incorrectly defined.

❍ Errors made by the end user when using the behavior: The end-user runs a main behavior requiring an
object not yet created.

❍ Warnings: Errors made by the end user when using the behavior: The user cancels the execution of the
behavior. For instance by clicking the Cancel button of an Open file box for the Load behavior.

❍ Execution errors: The LoadDocument behavior enables the user to load a document. If this document does
not exist, a message is raised indicating that the document is missing.
● Enabling expert and end users to fix the problem.

❍ Expert user: Whatever the behavior (main or building blocks of a behavior), he can determine which
behavior is concerned and can edit or deactivate it.

❍ End user: He can only delete or deactivate the main behaviors (or the visible behaviors.)
● Enabling expert and end users to identify the behaviors in error in the specification tree.
● Keeping track of the information for the expert user to fix the problems.

Detecting Errors

The behaviors that are in error display with a in the specification tree. When an error occurs when executing the
application, the following panel displays:

● The Behavior column lists the behavior(s) that are in error.

● The Diagnosis column describes the reason why the behavior cannot be executed (An object variable cannot be
valuated).
● The Documentation field helps the user fix the problem. He can edit the behavior and modify its inputs before
launching its execution, or he can deactivate the behavior.
 Business Process Knowledge Template Version 5 Release 14 Page 92

The information about each error is saved at the level of each feature and can therefore be displayed by editing the
behavior. An information field is added to these behaviors (see graphic below) listing the information.

The information provided depends on the User type (expert user, administrator, or end user). In User mode, if an error
occurs on a main behavior or on an invisible behavior, the error is displayed and stored on this main behavior.

Using the Error Check Tool

 Business Process Knowledge Template Version 5 Release 14 Page 93

Using the Error Check Tool

This tool is designed to check that the physical name of the created type (technological object) does not already
exist in one of the .Catfct files located in the CATGraphic path.

● The Available Catalogs field lists the .CATfct files located in the CATGraphic path.

● The Selected catalogs field lists the .CATfct files that you selected using the arrow key.

●
The Generate report button enables you to generate a report listing the detected identical type names.
Clicking this icon opens a Save as dialog box. Two file formats are available:
● .xml (the default format) or
● .html

In case of error, the .xml or .html file indicates the types names that are identical and the files containing these
types (see graphic below.)
Business Process Knowledge Template Version 5 Release 14 Page 94
Business Process Knowledge Template Version 5 Release 14 Page 95

Working with a User Workbench

Getting Familiar with the End-User Workbench

Executing Behaviors
Editing Behaviors
 Business Process Knowledge Template Version 5 Release 14 Page 96

Getting Familiar with the End-User Workbench

● Accessing your Workbench

● Using the technological Specifications View

● Activating your Workbench

● Instantiating Objects

● Linking Behaviors to the Objects

● Operating Behaviors

Accessing your Workbench

You can access the workbench from the Start->Name_of_the_workbench menu. Workbenches generated using the BKT application are
located at the top of the Start menu.

Workbenches generated using the BKT application are similar to the other CATIA workbenches:

● The toolbar dedicated to the workbench is located in the right part of the window

● The standard toolbar is located in the bottom of the window

● The menu bar is similar to the standard CATIA menu bars (see graphic below).
 Business Process Knowledge Template Version 5 Release 14 Page 97

Note that the menu bar displayed at the top of the window depends on the Workbench type selected (Product, Part, or System)
by the Expert User when generating the workbench.

Using the technological Specifications View

To access the Technological Specifications View window, select one object in the specification tree and click the Open the Technological

Specifications View window icon ( ) in the Behavior Controls toolbar.

This window enables you to get a simplified

view of the specifications tree. Whereas in the
specification tree, you can visualize:
● The products

● The types and their sub-types,

● The variables (attributes)

● The behaviors

● The links between the objects.

 Business Process Knowledge Template Version 5 Release 14 Page 98

In the Technological Specifications View, you can visualize:

● The types

● The variables (attributes)

● The behaviors

Existing links between the objects are not displayed in this view, the objects are independent from each other.

It is recommended to use this view when working with big assemblies to get a simplified overview of the specification tree.

Activating your Workbench

When opening your application, the toolbar specific to your workbench is grayed out meaning that it is disabled (see the picture above). To

activate your toolbar, select the root product in the specification tree and click the icon to initialize the assembly context in the
selected product: The toolbar is enabled and you can start instantiating your objects.

Instantiating Objects
To initialize the process and to create your first object, click one of the icons in your workbench toolbar, then select the root product in the
specification tree to assign it the corresponding object type. The name of the root product changes accordingly. Each icon of your workbench
corresponds to one object type. To see how to use objects, see Executing Behaviors.

Linking Behaviors to the Objects

The objects are assigned behaviors. To access these behaviors, right-click the root product and select the command from the contextual
menu. To see how to execute behaviors, see Executing Behaviors.
 Business Process Knowledge Template Version 5 Release 14 Page 99
In the picture below, IndirectVision is provided with 4 behaviors:

● Define vehicle data

● Define driver

● Define external mirror

● Define target.

Note that:

The first 8 commands are standard CATIA

commands.

You access the behaviors by selecting the

Name_of_Object object command.

Available menus

Definition...: Enables you to access the

Attributes tab where you can add, modify, and
delete variables (attributes) values. To know
more, see Editing Behaviors.

Define vehicle data: Behavior defined by the

expert user, specific to this object enabling you
to select a vehicle and to insert it into the
Product.

Once a behavior is executed, its name is prefixed with "Control" in the contextual menu
(see picture opposite). If you want to re-execute the behavior:
● A Control Behavior Activity dialog box displays asking if you want to delete the
behavior if it executed correctly when first executing it.

● The Behavior re-executes if it failed when you first executed it. It restarts where it
failed.

Operating Behaviors
After editing a behavior, you may want to re-operate your behaviors. The Operate function enables you to update your features and re-
execute your behaviors. To do so, you can:

●
Click the Operate icon in the Behavior Controls toolbar.

- Or -
 Business Process Knowledge Template Version 5 Release 14 Page 100
●
Right-click the object in the specification tree and select the
Operate->Operate command.

To get an example, see Editing Behaviors.

To know how to use your workbench, contact the expert user who generated it.

Executing Behaviors
Editing Behaviors
Business Process Knowledge Template Version 5 Release 14 Page 101

Executing Behaviors

This task shows the end-user how to execute behaviors.

To execute a behavior,
proceed as follows:
● Right-click an object
in the specification
tree.

● Select the
Object_Name
object-
>Behavior_Name
command.

Starting the RearViewMirror Workbench

1. Open Catia and close the default empty product.

2. From the Start menu, select

RearViewMirror.
1.

If this workbench is not available, contact your expert user for him to copy the files provided
in the Before you start topic into the appropriate directories and to generate the workbench
enabling you to replay this scenario.

You are now in the user workbench. All the items defined in the .CATfct file now display in the toolbar
located in the right part of the screen. Note that the icons might be replaced with empty check boxes if
no icons were associated with the types.

3. Select the product in the specification tree and click the icon to initialize the assembly
context in the selected product.

Defining the Type and Loading the Vehicle

4. Select the product and click the IndirectVision icon. The IndirectVision type is assigned to the
Business Process Knowledge Template Version 5 Release 14 Page 102

root product.

5. Define the type and load the vehicle. To do so proceed as follows:

● Right-click the IndirectVision (Product1) object in the tree and select the IndirectVision
(Product1) object->Define vehicle data command. The file selection window displays.

● Select the BktVehicleData.CATPart and click OK to validate. The vehicle is loaded. Its type
is "Vehicle".

Instantiating the Driver

6. Instantiate the driver. To do so proceed as follows:

● Right-click the IndirectVision (Product1) object in the tree and select the IndirectVision
(Product1) object->Define driver command. The Catalog browser displays.
● In the catalog browser, select Driver-2D-95%-Male. The behavior instantiates the selected
driver. Click Yes in the Save As dialog box.

Note that if you do not have a e:\tmp file, you will need to edit the path in the
BktSaveLastPart.CATScript.
Business Process Knowledge Template Version 5 Release 14 Page 103

Instantiating the Target

7. Instantiate the target. To do so, proceed as follows:

❍ Right-click the IndirectVision (Product1) object in the tree and select the

IndirectVision (Product1) object->Define target command.

❍ In the Catalog browser, double-click Target and TargetTemplate. The target is

instantiated.

❍ Click Fit all in to see the target created (see picture below.)
Business Process Knowledge Template Version 5 Release 14 Page 104

Editing Behaviors

This task explains to the end-user how to edit behavior variable (attributes).

This scenario is extracted from the end-user use case Designing the External Mirror.

To edit a behavior variable (attribute), proceed as follows:

● Right-click the object and select the Object_Name object->Definition... command.

● Double-click the variable (attribute) to be modified. The Attribute dialog box displays.

● Edit the value of the variable (attribute). Click OK twice to validate and to exit the
Attribute dialog box.

● Update the behavior by clicking the icon or by right-clicking the object in the
specification tree and selecting the Operate->Operate command. (See steps 7 and 9.)

- Or -

● Select an object in the

specification tree and
expand its attributes
node.

● Double-click the
variable (attribute) to
be edited. The Edit
parameter dialog box
displays.

● Change the parameter

value and click OK to
validate.
Business Process Knowledge Template Version 5 Release 14 Page 105

Starting the RearViewMirror Workbench

1. Open Catia and close the default empty product.

2. From the Start menu, select

RearViewMirror.

If this workbench is not available, contact your expert user for him to copy the files
provided in the Before you start topic into the appropriate directories and to
generate the workbench enabling you to replay this scenario.

You are now in the user workbench. All the items defined in the .CATfct file now display in the
toolbar located right part of the screen. Note that the icons might be replace with empty check
boxes if you did not associate icons with the created behaviors when defining the .CATfct file.

3. Select the product in the specification tree and click the icon to initialize the
assembly context in the selected product.

Defining the Type and Loading the Vehicle

4. Select the product and click on IndirectVision icon. The IndirectVision type is assigned

to the root product.

5. Define the type and load the vehicle. To do so proceed as follows:

❍ Right-click the IndirectVision (Product1) object in the tree and select the

IndirectVision (Product1) object->Define vehicle data command. The

file selection window displays.

❍ Select the BktVehicleData.CATPart and click OK to validate. The vehicle is

loaded. Its type is "Vehicle".

Business Process Knowledge Template Version 5 Release 14 Page 106

Instantiating the Driver

6. Instantiate the driver. To do so proceed as follows:

● Right-click the IndirectVision (Product1) object in the tree and select the
IndirectVision (Product1) object->Define driver command. The Catalog browser
displays.

● In the catalog browser, select Driver-2D-95%-Male. The behavior instantiates the

selected driver. Click Yes in the Save As dialog box.

Note that if you do not have a e:\tmp file, you will need to edit the path in the
BktSaveLastPart.CATScript.
Business Process Knowledge Template Version 5 Release 14 Page 107

Instantiating the Mirror

7. Instantiate the mirror. To do so proceed as follows:

● Right-click the IndirectVision

(Product1) object in the tree
and select the IndirectVision
(Product1) object->Define
external Mirror command.
A new empty part typed
ExternalMirror is inserted into
the product. (See picture
opposite.)

● Right-click ExternalMirror (Mirror_Part.1)and select the Generate Geometry

command. The Mirror_Part has been created along with its publications.
Business Process Knowledge Template Version 5 Release 14 Page 108

Editing the Mirror Variables (Attributes)

8. Edit the mirror variables (attributes). To do so, proceed as follows:

❍ Right-click ExternalMirror (Mirror_Part.1) and select the ExternalMirror

(Driver_Part.1) object->Definition... command.

❍ Double-click the VerticalAngle variable (attribute). The Attribute dialog box

displays.

❍ Set the value of the VerticalAngle to 18deg. Click OK to validate.

❍ Double-click the HorizontalAngle variable (attribute). The Attribute dialog box

displays.

❍ Set the value of the HorizontalAngle to -4.5deg. Click OK to validate.

Business Process Knowledge Template Version 5 Release 14 Page 109

❍ Double-click the Width variable (attribute). The Attribute dialog box displays.

❍ Set the width value 40mm. Click OK twice to validate.

❍ Mirror_Part now needs to be updated. Right-click ExternalMirror

(Mirror_Part.1) and select the Operate command.

❍ Expand the Mirror variables node and double-click the modified attributes to

check their values. The values are updated.

Business Process Knowledge Template Version 5 Release 14 Page 110

Advanced Tasks

This Advanced Tasks section is intended to help expert users develop Business Process Knowledge Template
user workbenches using more advanced functions.

Expert User Knowledge Relations: Using the if...else Syntax

Using a Sequential Combination to instantiate a User Feature
Using the Insert Components behavior: Auto update mode
Using the Propagate Execution behavior
Using the Onxxx Behaviors
Using the Knowledge Certify Behavior
Using the Instantiate Template Behavior
Designing a Table using the Generate Component Behavior
Using the Loop Behavior
Use Cases

Use Cases Designing the External Mirror

Computing the Optimal Mirror

Creating a User Workbench: Indirect Vision

Business Process Knowledge Template Version 5 Release 14 Page 111

Knowledge Relations: Using the if...else Syntax

This scenario aims at providing the expert user with a use example of the Knowledge Relations
behavior. The expert user creates a combination containing a Knowledge Advisor rule that
drives 2 combinations:
● Insert_US, which enables the user to insert a manikin matching US standards.

● Insert_EEC, which enables the user to insert a manikin matching EEC standards.

The scenario is divided into the following steps:

● Creating a technological type, called Driver. This type will be instantiated into the user
workbench.

● Adding an attribute to the technological type: This attribute will drive the if...then...else
relation and therefore the 2 sequences (Insert_US and Insert_EEC).

● Adding behaviors to the technological type: The user creates a knowledge rule that will
drive 2 sequences of behaviors. These 2 sequences are identical except that the inserted
documents are different. They are based on one of the basic behavior patterns:

● Load Behavior

● Bind Object Behavior

● Insert Component Behavior

● Generating the workbench

● Testing the workbench

Remember to save the .CATfct, the BktDriver-2D-SAE.CATPart and BktDriver-2D-EEC.CATPart

files in the directory corresponding to the CATGraphicPath environment variable.
Business Process Knowledge Template Version 5 Release 14 Page 112

Creating a technological Type

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench.

2. Create the Driver technological type. To do so, proceed as follows:

❍ Click the Create Technological Type icon ( ) to create a type. The

Create technological type dialog box displays.

❍ Enter the name of the type: Driver.

❍ Click OK to validate.

Adding a Variable (Attribute)

3. Add an attribute to the technological type. To do so, proceed as follows:

❍ Click the Driver type in the specification tree and click the Add

Attribute icon ( ). The Add Attribute dialog box displays.

❍ In the Name field, enter the name of the attribute: Legislation.

❍ In the Type scrolling list, select String.

❍ In the Value field, enter SAE.

❍ Click OK to validate. Double-click the Driver type: Legislation now

displays in the Attributes tab.

Adding behaviors to the technological type

Business Process Knowledge Template Version 5 Release 14 Page 113

4. Click the Driver type and click the Sequential Combination icon ( ).
SequentialCombination displays in the Behaviors view. Double-click

SequentialCombination and double-click Driver in the Behaviors tab.

5. Double-click the SequentialCombination node. The Sequential Combination editor

displays. In the Name field, enter Selecting Manikin, and click OK to validate.

6. Click the Selecting Manikin node and click the Knowledge Relations behavior icon ( )
to create a rule.

7. Double-click the KnowledgeRelation node in the Behaviors tab. The Knowledge Relations

editor displays.

8. Click the Attributes tab and add the following attributes:

●
Name: Legislation, Type: String.

●
Name: Act_EEC, Type: Boolean, Value: false, Quality: Output

●
Name: Act_US, Type: Boolean, Value: false, Quality: Output

To know more about the Quality field, see To know more about the Add
Attribute dialog box...

9. Add a rule to the behavior. To do so, proceed as follows:

Click the Content tab then the Rule icon ( ) in the Knowledge Tools
toolbar to add the rule. The Rule Editor displays.

Enter the name of the rule and click OK to enter the Rule editor.
Business Process Knowledge Template Version 5 Release 14 Page 114

In the Rule Editor, enter the following script in the Rule editor. To do so,

select the objects in the behaviors tree and use the wizard. Click OK

twice to validate and to close the dialog box:

if Legislation == "SAE"
{
Act_EEC = FALSE
Act_US = TRUE
}
else
{
Act_EEC = TRUE
Act_US = FALSE
}

At this stage of the scenario, your

workbench should be similar to the

graphic opposite.

10. Link the Knowledge Relation behavior with the Selecting Manikin Combination for the

Knowledge Relation to react to the combination changes. To so proceed as follows:

● Expand the
KnowledgeRelations node
and right-click the
Legislation attribute, and
select the Legislation
object->Link To
command.
Business Process Knowledge Template Version 5 Release 14 Page 115

● Expand the Driver node and click the Legislation attribute. Both attributes are
now linked.

11. Click the Selecting Manikin node in the Behaviors tab and click the Sequential

Combination icon ( ) to add a new combination. This new combination will enable the
user to load a manikin matching the US standard.

12. Double-click the SequentialCombination node in the Behaviors tab. The

SequentialCombination editor displays.

● In the Name field, enter Insert_US.

● Click OK to validate.

13. Click the Insert_US combination in the Behaviors tab and click the Load behavior

icon. The LoadDocument behavior displays in the Behaviors tab.

14. Double-click the LoadDocument node. The Load Document editor displays.

● In the File path field, click the button and select the BktDriver-2D-
SAE.CATPart file.

● In the Properties tab, select Expert&Administrator in the scrolling list of the

Behavior States and check the Activate check box.

● Click OK to validate.

15. Click the Insert_US combination in the Behaviors tab and click the Bind Object behavior

icon. The BindObject behavior displays in the Behaviors tab.

16. Double-click the BindObject node. The Bind Object editor displays.

● In the Relative name field, enter: ../../../.. to access the root product. To know
more about the syntax to use in the Relative name field, see To know more
about the Bind mechanism...
Business Process Knowledge Template Version 5 Release 14 Page 116

● In the Properties tab, select Expert in the scrolling list of the Behavior States
and check the Activate check box.

● Click OK to validate.

17. Click the Insert_US combination in the Behaviors tab and click the Insert Components

behavior icon. The InsertComponents behavior displays in the Behaviors tab.

18. Double-click the InsertComponents node. The Insert Components editor opens.

●
In the Definition scrolling list, select Existing Component.

●
Click the Existing component field, expand the LoadDocument node and
select the output Document.

●
Click the Father product field, expand the BindObject node and select the
output Link.

●
Set the number of instances to 1.

●
In the Allow sub typing scrolling list, select false.

●
In the Properties tab check the Activate and Focus check boxes.

●
Click OK to validate.

At this stage of the scenario, your

workbench should be similar to the
graphic opposite.
Business Process Knowledge Template Version 5 Release 14 Page 117

19. Click the Selecting Manikin combination in the Behaviors tab and click the Sequential

Combination icon ( ) to add a new combination. This new combination will enable the
user to load a manikin matching the EEC standard.

20. Double-click the SequentialCombination node in the Behaviors tab. The

SequentialCombination editor displays.

● In the Name field, enter Insert_EEC.

● Click OK to validate.

21. Click the Insert_EEC node in the Behaviors tab and click the Load behavior icon. The

LoadDocument behavior displays in the Behaviors tab.

22. Double-click the LoadDocument node. The Load Document editor displays.

● In the File path field, click the button and select the BktDriver-2D-
EEC.CATPart file.

● In the Properties tab, select Expert&Administrator in the scrolling list of the

Behavior States and check the Activate check box.

● Click OK to validate.

23. Click the Insert_EEC node in the Behaviors tab and click the Bind Object behavior

icon. The BindObject behavior displays in the Behaviors tab.

24. Double-click the BindObject node. The Bind Object editor displays.

● In the Relative name field, enter: ../../../.. to access the root product.

● In the Properties tab, select Expert in the scrolling list of the Behavior States
and check the Activate check box.

● Click OK to validate.
Business Process Knowledge Template Version 5 Release 14 Page 118

25. Click the Insert_EEC node in the Behaviors tab and click the Insert Components

behavior icon.

26. Double-click the InsertComponents node. The Insert Components editor opens.

● In the Definition scrolling list, select Existing Component.

● Click the Existing component field, expand the LoadDocument node and select
the output Document.

● Click the Father product field, expand the BindObject node and select the output
Link.

● Set the number of instances to 1.

● In the Allow sub typing scrolling list, select false.

● In the Behavior States field and check the Activate and Focus check boxes.

● Click OK to validate.

27. Expand the Insert_EEC variables node, right-click the Activity variable, select the

Activity object->Link To command, expand the KnowledgeRelations variables node

and click the Act_EEC output.

Business Process Knowledge Template Version 5 Release 14 Page 119

28. Expand the Insert_US variables node, right-click the Activity variable, select the

Activity object->Link To command, expand the KnowledgeRelations variables node

and click the Act_US output.

29. Save your .CATfct file in the Graphics directory. Click here to open the created .CATfct.

Generating the Workbench

30. Click the Generate Applicative Workbench icon ( ) to generate a user workbench.
Enter the name of the workbench, Select Manikin in this example, as well as the

workbench type (Product here).

Testing the Workbench

31. From the Tools->Options->Knowledgeware->Business Knowledge Template

menu, select All Users in the Access Rights scrolling list and click OK to work in a

User environment.

32. Select Product1 in the specification tree and click the Driver check box to type the root

product. Its name is now Driver:Product1.

33. Right-click Driver (product1) and select the Selecting Manikin command.
Business Process Knowledge Template Version 5 Release 14 Page 120

The manikin matching the US standard is inserted.

34. Double-click the Legislation attribute located below the driver (Product1) feature and

enter EEC in the opening dialog box.

Business Process Knowledge Template Version 5 Release 14 Page 121

35. Select the KnowledgeRelations node below

SelectingManikin and click the update icon.

36. Right-click Driver (product1) and select the Driver command.

The manikin matching the EEC standard is inserted.

To know more about:

● The Knowledge Relations behavior, see Knowledge Relations behavior: Data Sheet.

● The technological objects, see Creating a technological Object.

● The technological objects attributes, see Adding an Attribute to a technological Object.

● The workbench generation, see Generating a User Workbench.

Business Process Knowledge Template Version 5 Release 14 Page 122

Using a Sequential Combination to Instantiate a

User Feature

This scenario aims at providing the expert user with an example of the sequential Combination
behavior associated with the Bind UDF behavior. The expert user creates a part containing a
UDF and a Product file into which the UDF will be instantiated. To do so, the expert user creates
a combination containing a BindUDF behavior.

This scenario is divided into the following steps:

● Creating a technological Object

● Adding behaviors to the technological type

● Generating the Workbench

● Testing the Workbench

Remember to save your .CATfct file as well as the Bkt_PartUDF.CATPart and the
BKT_InstantiateUDF.CATProduct, the BKT_PartResult.CATPart, BKT_PartSupport.CATPart files
in the directory corresponding to the CATGraphicPath environment variable.

Creating a technological Object

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench.

2. Create the TestUDF technological type. To do so, proceed as follows:

Click the Create Technological Type icon ( ) to create a type.

The Create technological type dialog box displays.

❍
Enter the name of the type: TestUDF .

❍
Click OK to validate.
Business Process Knowledge Template Version 5 Release 14 Page 123

At this stage of the scenario, the

Feature Dictionary tree should look

like the one opposite.

Adding behaviors to the technological type

3. Click the TestUDF type and the Sequential Combination behavior icon ( ) to
create a combination of behaviors.

4. Double-click SequentialCombination in the Behaviors View and double-click TestUDF in

the Behaviors tab. The Sequential Combination displays in the Behaviors tab.

5. Double-click the SequentialCombination combination in the Behaviors tab to edit it. The

Sequential Combination editor displays.

6. In the Name field of the opening dialog box, enter Instantiate UDF and click OK to

validate.

7. Select the Instantiate UDF combination in the Behaviors tree and click the Sequential

Combination icon ( ). Sequential Combination displays in the Behaviors tab.

8. In the Name field of the opening dialog box, enter Retrieve Part and click OK to

validate.

At this stage of the scenario, the Behaviors

tree should look like the one opposite.

9. Click the Retrieve Part combination and click the Bind Object behavior icon ( ).

10. Double-click the Bind Object node. The Bind Object editor displays.

❍
In the Relative Name field, enter ../../../../BKT_PartResult.1
Business Process Knowledge Template Version 5 Release 14 Page 124

".." indicates that the bind must be performed on the upper level. In

the current context, you go up 4 levels to reach the root product

and go down one level to access the PartResult.

❍
Click OK to validate

11. Click the Retrieve Part combination and click the Bind Reference behavior icon ( ).
BindReference displays in the Behaviors tab.

12. Double-click the BindReference node. The Bind Reference editor displays.

❍
Click the Reference of field.

Expand the BindObject node and click the output

link. =BindObject\Link displays in the Reference field.

❍
Click OK to validate.

13. Click the Retrieve Part combination and click the Bind Part behavior icon ( ).
BindPart displays in the Behaviors tab.

14. Double-click the BindPart node. The BindPart editor displays.

❍
Click the From object field, expand the BindReference variables

node and click the output link. BindReference\Link displays in the

Reference field.

❍
Click OK to validate.
Business Process Knowledge Template Version 5 Release 14 Page 125

At this stage of the scenario,

the behaviors tree should look

like the one opposite.

15. Select the Instantiate UDF combination in the Behaviors tab and click the Sequential

Combination icon ( ). SequentialCombination displays in the Behaviors tab.

16. Double-click SequentialCombination. The Sequential Combination editor displays.

17. In the Name field of the opening dialog box, enter Retrieve Publications and click OK

to validate.

18. Click the Retrieve Publications combination and click the Bind Object behavior icon

( ).

19. Double-click the Bind Object node. The Bind Object editor displays.

❍
In the Relative Name field, enter ../../../../BKT_PartSupport.1

❍
Click OK to validate

20. Click the Retrieve Publications combination and click the Bind Publication Behavior

icon ( ). BindPublication displays in the Behaviors tab.

21. Double-click the BindPublication node. The Bind Publication editor displays.

❍
In the Name field, enter BindPublication_Surface.
Business Process Knowledge Template Version 5 Release 14 Page 126

❍
Click the Starting from field, expand the BindObject node and click

the output link.

❍
In the Relative Name field, enter Surface.

❍
Click OK to validate.

22. Click the Retrieve Publications combination and click the External Reference

Behavior icon ( ). CreateExternalReference displays in the Behaviors tab.

23. Double-click the CreateExternalReference node. The Create External Reference editor

displays.

❍
Click the Feature to import field, expand the

BindPublication_Surface variables node and select the output link.

BindPublicationSurface\Link displays in the Feature to import field.

❍
Click the Destination field, expand the Retrieve Part node, and the

BindPart variables node and select the output part. BindPart\Part

displays in the Destination field.

❍
Set the Show Mode to true.

❍
Click OK to validate.

At this stage of the

scenario, the behaviors

tree should look like the

one opposite.
Business Process Knowledge Template Version 5 Release 14 Page 127

24. Click the Retrieve Publications combination and click the Bind Publication Behavior

icon ( ). BindPublication displays in the Behaviors tab.

25. Double-click the BindPublication node. The Bind Publication editor displays.

❍
In the Name field, enter BindPublication_Point.

❍
Click the Reference field, expand the BindObject node and click the

output link. =BindObject\Link displays in the Reference field.

❍
In the Relative Name field, enter Point.

❍
Click OK to validate.

26. Click the Retrieve Publications combination and click the External Reference

Behavior icon ( ). CreateExternalReference displays in the Behaviors tab.

27. Double-click the CreateExternalReference node. The Create External Reference editor

displays.
Business Process Knowledge Template Version 5 Release 14 Page 128

❍
In the Name field, enter CreateExternalReference_Point.

❍
Click the Feature to import field, expand the BindPublication_Point

node and select the output link. BindPublication_Point\Link displays

in the Feature to import field.

❍
Click the Destination field, expand the Retrieve Part node, and the

BindPart node and select the output part. BindPart\Part displays in

the Destination field.

❍
Click OK to validate.

At this stage of the

scenario, the

behaviors tree should

look like the one

opposite.

28. Select the Instantiate UDF combination in the Behaviors tab and click the Sequential

Combination icon ( ). Sequential Combination displays in the Behaviors tab.

29. Double-click the SequentialCombination. The Sequential Combination editor displays.

30. In the Name field of the opening dialog box, enter Retrieve UDF and click OK to

validate.

31. Click the Retrieve UDF combination and click the Load Document Behavior icon

( ). LoadDocument displays in the Behaviors tab.

32. Double-click the LoadDocument node. The Load Document editor displays.
Business Process Knowledge Template Version 5 Release 14 Page 129

❍ Click the button and open the Bkt_PartUDF.CATPart file

❍ Click OK to validate.

33. Click the Retrieve UDF combination and click the Bind User Feature Behavior icon

( ). BindUserFeature displays in the Behaviors tab.

34. Double-click the BindUserFeature node. The Bind User Feature editor displays.

Click the From object field, expand the LoadDocument variables

node and select the output document. LoadDocument\Document

displays in the From object field.

In the User Feature Name field, enter UserFeature1.

Click OK to validate.

At this stage of the scenario, the

behaviors tree should look like the

one opposite.

35. Click the InstantiateUDF combination and click the Instantiate Template Behavior
Business Process Knowledge Template Version 5 Release 14 Page 130

icon ( ). InstantiateTemplate displays in the Behaviors tab.

36. Double-click the InstantiateTemplate node. The Instantiate Template editor displays.

Click the Template feature field, expand the Retrieve UDF node

and the BindUserFeature variables node and select the UserFeature

output. BindUserFeature/UserFeature displays in the Template

feature field.

Click the Destination field, expand the Retrieve Part combination

node and the BindPart node and select the output part.

BindPart\Part displays in the Destination field.

In the Valuation Mode scrolling list, select UseIdenticalName.

Click OK to validate.

At this stage of the scenario, your

workbench should be similar to the

graphic opposite.

Generating the Workbench

Business Process Knowledge Template Version 5 Release 14 Page 131

37. Save the .CATFct file.

38. Click the Generate Applicative Workbench icon ( ) to generate a user workbench.
Enter the name of the workbench, Instantiate UDF in this example and click OK to

validate. The generated workbench opens.

Testing the Workbench

39. From the Tools->Options->Knowledgeware->Business Knowledge Template

menu, select All Users in the Access Rights scrolling list and click OK to work in a

User environment.

40. Open the BKT_InstantiateUDF.CATProduct : The following picture displays (click it to

enlarge it):

41. Click the root product of the specification tree and select the TestUDF icon to type the

root product. The root product name is now TestUDF2:Product2.

42. Right-click TestUDF (Product2) and select the TestUDF object-

>Instantiate UDF command:

The UDF is inserted into the product.

Business Process Knowledge Template Version 5 Release 14 Page 132
Business Process Knowledge Template Version 5 Release 14 Page 133

Using the Insert Components Behavior: Auto

Update Mode

This scenario aims at providing the expert user with a use example of the Insert Components
behavior in automatic update mode. The expert user wants to insert 2 manikins in a product,
then he changes the instances number to 1 using the Insert Components interface to display
only one manikin.

Remember to save the .CATfct, the BktDriver-2D-SAE.CATPart and BktDriver-2D-EEC.CATPart

files in the directory corresponding to the CATGraphicPath environment variable.

1. Open the BktInsertComponents.CATfct file.

2. In the Behaviors tab, expand the Insert_US combination node and double-click the

InsertComponents node. The Insert Components editor displays.

3. In the Instantiation context field, set the number of instances to 2 and check that the

update mode is set to Auto in the Properties tab. Click OK to validate.

4. Double-click the LoadDocument behavior and click the button to set the path.
Repeat the same step with the LoadDocument behavior located below the Insert_EEC

combination node.

5. Save your file in the Graphics directory. Click here to open the created .CATfct.

6. Click the Generate Applicative Workbench icon ( ) to generate a user workbench.

Enter the name of the workbench, Insert Manikins in this example, as well as the

workbench type.

7. From the Tools->Options->Knowledgeware->Business Knowledge Template

menu, select All Users in the Access Rights scrolling list and click OK to work in a

User environment.
Business Process Knowledge Template Version 5 Release 14 Page 134

8. Select Product1 in the specification tree and click the driver check box to type the root

product. Its name is now driver:Product1.

9. Right-click driver (product1) and select the driver (Product1) object-

>SequentialCombination command: 2 manikins matching the US standard are

inserted (use the compass to move the manikins that overlap).

10. Expand the driver node, then the SequentialCombination node, then the Insert_US.1

node and double-click the InsertComponents.1 behavior and change the number of

instances to 1. To do so, proceed as follows:

● Click the Attributes tab and double-click the 2nd line (Number) in the List of

Attributes.
Business Process Knowledge Template Version 5 Release 14 Page 135

● Set the value to 1 in the Value field of the Attribute dialog box.

● Click OK twice to validate.

The behavior is automatically updated and only one manikin displays.

Business Process Knowledge Template Version 5 Release 14 Page 136

Using the Propagate Execution Behavior

In the scenario detailed below, the expert user subscribes to the update of a part: If the part is
updated, a hole is created, if not, no hole is created.
To do so, the expert user uses the Propagate execution behavior that triggers the update of the
part if the Action Delayed option is not selected.

The scenario is divided into the following steps:

● Creating a technological type called Propagate

● Adding behaviors to the technological type: The user adds a sequence that is made up of 4
different behaviors:

● A VBScript behavior that will load the BktCreatePad.CATScript script.

This script creates a pad.

● A Bind Object behavior that will retrieve the pad.

● A Propagate Execution behavior.

● A VBScript behavior that will load the BktCreateHole.CATScript script.

This script creates a hole in the pad.

Generating the workbench

Testing the workbench

Remember to save your .CATFct file in the directory corresponding to the CATGraphicPath
environment variable and the VBScript files in the \CATStartupPath\automation directory.
Business Process Knowledge Template Version 5 Release 14 Page 137

Creating a technological Type

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench.

2. Create the PropagateUseCase technological type. To do so, proceed as follows:

Click the Create Technological Type icon ( ) to create a type.

The Create technological type dialog box displays.

❍
Enter the name of the type: Propagate.

❍
Click OK to validate.

At this stage of the scenario,

your feature dictionary should be

similar to the graphic opposite.

Adding Behaviors to the Type

3. Click The Propagate type and click the Sequential Combination behavior ( ) to
create a combination of behaviors.

At this stage of the scenario, your

feature dictionary should be similar to
the graphic opposite.

4. Double-click SequentialCombination in the Behaviors View and Propagate in the

Business Process Knowledge Template Version 5 Release 14 Page 138

Behaviors tab to access the sequential combination.

5. Double-click the SequentialCombination node that displays in the Behaviors tab.

(Expand the Propagate node if need be.)

6. Enter the name of the combination, Generate pad with a hole in this scenario, in

Name field of the opening dialog box and click OK to validate.

7. Select the Generate pad with a hole combination in the Behaviors tree and click the VB

Script Behavior icon ( ).

8. Double-click VBScript and enter Create a Pad in the Name field and select

BktCreatePad.CATScript in the VB Name field.

9. Select the Generate pad with a hole combination in the Behaviors tree and click the

Bind Object Behavior icon ( ).

10. Double-click the BindObject behavior. The Bind Object window displays. In the Name

field, enter Retrieve the part and enter ../../.. in the Relative Name field. Click OK to

validate.

11. Click the Generate pad with a hole combination and click the Propagate Execution

icon ( ). A PropagateExecution behavior displays in the Behaviors tab.

12. Double-click this behavior and enter Update the part in the Name field of the opening

dialog box.

13. Select the Target field, expand the BindObject variables node and select the output

link. =BindObject\Link displays in the Target field.

14. Select the Generate pad with a hole combination in the Behaviors tree and click the VB

Script Behavior icon ( ).

15. Double-click VBScript and enter Create a Pad in the Name field and select

BktCreateHole.CATScript in the VB Name field.

Business Process Knowledge Template Version 5 Release 14 Page 139

At this stage of the scenario, the

Behaviors tab should be similar to the
graphic opposite.

The definition of the behaviors is now over. Save your file and generate your workbench. (Click
here to display the generated .CATfct file).

Generating the Workbench

16. Click the Applicative Workbench Generation icon ( ) to generate a user

workbench. Enter the name of the workbench, Propagate Update in this example, as

well as the workbench type (Part Structure here).

Testing the Workbench

17. From the Tools->Options->Knowledgeware->Business Knowledge Template

menu, select All Users in the Access Rights scrolling list and click OK to work in a

User environment.

18. Open the BktPart_with_Sketch.CATPart part and access the Propagate Update

workbench from the Start menu.

19. Select Part1 in the specification tree and click the Propagate check box to type the root

part. Its name is now Propagate(Part1).

20. Right-click Propagate(part1) and select the Propagate(Part1) object->Generate pad

with a hole command.

Business Process Knowledge Template Version 5 Release 14 Page 140

The combination is executed and the following message displays.

Business Process Knowledge Template Version 5 Release 14 Page 141

21. Click OK. The hole is created (see picture below.)

22. Close your file and go back to your CATFct file.

23. In the Behaviors tab, double-click the Propagate Execution behavior (Update the part)

and check the Action Delayed check box. This way, the update of the part will not be

launched. Save your file.

24. Open the BktPart_with_Sketch.CATPart part and access the Propagate Update

workbench from the Start menu.

25. Select Part1 in the specification tree and click the Propagate check box to type the root

part. Its name is now Propagate(Part1).

Business Process Knowledge Template Version 5 Release 14 Page 142

26. Right-click Propagate(part1) and select the Propagate(Part1) object->Generate pad

with a hole command. The following message displays.

27. Click OK. The hole is created (see picture below.)

To know more about:

● The Propagate Execution behavior, see Propagate Execution Behavior: Data Sheet.

● The technological objects, see Creating a Technological Object.

● The workbench generation, see Generating a User Workbench.

Business Process Knowledge Template Version 5 Release 14 Page 143

Using the Onxxx Behaviors

This scenario aims at providing the expert user with a use example of the Onxxx behaviors.
In this scenario, the expert user tracks the insertion of a vehicle. When the vehicle is inserted,
the Heel_pt_Line publication is checked. If Heel_pt_Line is published, a message is fired
indicating that the publication is ok, if not, a message is fired indicating that the publication is
missing.

Remember to save your .CATScript files in the startup\automation directory and your .CATFct
file in the directory corresponding to the CATGraphicPath environment variable.

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench.

2. Open the onxxx.CATfct file.

3. In the Behaviors View, double-click the IndirectVision's Behaviors then IndirectVision in

the Behaviors tab.

4. Expand the Define vehicle data combination.

5. Click the Define vehicle data combination and click the On Done Behavior icon

( ).

6. Right-click the On Done behavior, select the OnDone object->Reorder command and

click the Define vehicle data combination.

Business Process Knowledge Template Version 5 Release 14 Page 144

At this stage of the scenario, your

workbench should be similar to the
graphic opposite.

7. Click the On Done behavior in the Behaviors tab and click the Information Behavior

icon ( ) to create the Information behavior that will display a message.

8. Double-click the Information node and enter the following string in the Message field of

the opening dialog box: Heel_Pt_Line published. Click OK to validate.

9. Click the Define vehicle data and click the On Cancel Behavior icon ( ).

10. Right-click the On Cancel behavior, select the OnCancel object->Reorder command

and click the On Done behavior.

11. Click the On Cancel behavior in the Behaviors tab and click the Information Behavior

icon ( ) to create the Information behavior that will display a message.

12. Double-click the Information node and enter the following string in the Message field of

the opening dialog box: Heel_Pt_Line publication missing . Click OK to validate.

13. Click the Define vehicle data and click the On Done Behavior icon ( ).

14. Double-click the On Done behavior. The On Done window displays.

15. Enter When vehicle data is inserted... in the Name field and click OK to validate.

16. Right-click the When vehicle data is inserted... behavior, select the When vehicle

data is inserted...object->Reorder command, and click the OnCancel behavior. The

When vehicle data is inserted... behavior is now located below the On Cancel

behavior. (See picture below.)

Business Process Knowledge Template Version 5 Release 14 Page 145

17. Click the When vehicle data is inserted... behavior and click the Bind Object behavior

icon. BindObject displays in the Behaviors tab.

18. Double-click the BindObject node. The BindObject editor displays.

❍ In the Relative Name field, enter

../../../.. to bind the root

product. To know more about

the relative name syntax, see To

know more about the Bind

Mechanism...

❍ Click OK to validate

19. Click the When vehicle data is inserted... behavior and click the Bind Publication

behavior icon ( ). BindPublication displays in the Behaviors tab.

20. Double-click the BindPublication behavior. The Bind Publication window displays.

21. Click the Starting from: field, expand the BindObject node and click the output link.

=BindObject\Link displays in the Starting from field.

22. In the Relative Name field, enter Concept_Surfaces.1/Heel_Pt_Line.

23. Double-click the OnDone behavior, click the Object to Survey field and click the When

vehicle data is inserted behavior in the behaviors tree.

Business Process Knowledge Template Version 5 Release 14 Page 146

24. In the Children Objects list, select BindPublication and click the right arrow. Update

now displays in the Child Object to Survey list. Click OK to validate.

25. Double-click the OnCancel behavior, click the Object to Survey field and click the

When vehicle data is inserted behavior in the behaviors tree.

26. In the Children Objects list, select BindPublication and click the right arrow. Update

now displays in the Child Object to Survey list. Click OK to validate.

27. Double-click the When vehicle data is inserted sequence, click the Object to Survey

field and click the ComponentCreation behavior in the behaviors tree.

28. In the Children Objects list, select Update and click the right arrow. Update now

displays in the Child Object to Survey list. Click OK to validate.

At this stage of the scenario, your

workbench should be similar to
the graphic opposite.

29. Save your .CATfct file in the Graphics directory. (Click here to open the created

.CATFct.)

Generating the Workbench

Business Process Knowledge Template Version 5 Release 14 Page 147

30. Click the Generate Applicative Workbench icon ( ) to generate a user workbench.
Enter the name of the workbench, Insert Vehicle in this example, as well as the

workbench type (Product here).

Testing the Workbench

31. From the Tools->Options->Knowledgeware->Business Knowledge Template

menu, select All Users in the Access Rights scrolling list and click OK to work in a

User environment.

32. In the User Workbench, select Product1 in the specification tree and click the

IndirectVision check box to type the root product. Its name is now

IndirectVision:Product1.

33. Right-click IndirectVision:Product1(Product1) and select the IndirectVision

(Product1) object->Define vehicle data command.

34. Select the Vehicle_Data_with_Publication.CATPart file and click Open (Note that this

vehicle contains a Heel_Pt_Line publication). The vehicle is inserted and a message is

fired indicating that Heel_Pt_Line is published.

35. Right-click IndirectVision:Product1 (Product1) and select the IndirectVision

(Product1) object->Control_Define vehicle data command.

36. Click Yes when asked if you want to withdraw the Define vehicle data combination.

37. Right-click IndirectVision:Product1 (Product1) and select the IndirectVision

(Product1) object->Define vehicle data command.

38. Select the Vehicle_Data_without_Publication.CATPart file and click Open (Note that the

Heel_Pt_Line publication is missing in this part). The vehicle is inserted and a message
Business Process Knowledge Template Version 5 Release 14 Page 148

is fired indicating that the Heel_Pt_Line publication is missing.

Business Process Knowledge Template Version 5 Release 14 Page 149

Using the Knowledge Certify Behavior

This scenario aims at providing the expert user with an example of the Certify behavior. The expert user wants to
check the design of a part containing holes. The diameter of the holes should be as defined in the expert checks
(see below).

The expert checks are located in a rule base saved in a catalog.

This scenario is divided into the following steps:

● Creating a technological Object

● Adding behaviors to the technological type

● Generating the Workbench

● Testing the Workbench

Remember to save your .CATfct file as well as the PartRulebaseOnHole.CATPart, the bktrulebasecatalog.catalog,
and the bktCatalogImport.CATPart files in the directory corresponding to the CATGraphicPath environment variable.

Creating a technological Object

1. From the Start->Knowledgeware menu, access the Business Process Knowledge Template

workbench.

2. Create the Design technological type. To do so, proceed as follows:

Click the Create Technological Type icon ( ) to create a type. The Create
technological type dialog box displays.

❍
Enter the name of the type: Design.

❍
Click OK to validate.
Business Process Knowledge Template Version 5 Release 14 Page 150

At this stage of the scenario, the BKT tree

should look like the one opposite.

Adding behaviors to the technological type

3. Click the Design type and the Sequence Combination behavior icon ( ) to create a combination of
behaviors.

4. Double-click SequentialCombination in the Behaviors View and double-click Design in the Behaviors tab. The

Sequential Combination displays in the Behaviors tab.

5. Double-click the Sequential Combination. The Sequential Combination dialog box displays. In the name

field, enter CertifyDesign. Click OK when done.

6. Click the SequentialCombination combination and click the FilterCatalog icon ( ). The FilterCatalog
behavior displays

7. Double-click the FilterCatalog node. The Filter Catalog editor displays.

❍
In the Name field of the opening dialog box, enter RuleBases_Catalog.

Click the ... button and select the bktrulebasecatalog.catalog. in the File Selection dialog
❍

box.

❍
Click OK to validate.

8. Click the Certify Design combination and click the Bind Object behavior icon ( ).

9. Double-click the Bind Object node. The Bind Object editor displays.

❍
In the Relative Name field, enter ../../..

".." indicates that the bind must be performed on the upper level. In the current

context, you go up 3 levels to reach the root product.

❍
Click OK to validate

10. Click the Certify Design combination and click the Knowledge Certify behavior icon ( ). KWCertify
displays in the Behaviors tab.
Business Process Knowledge Template Version 5 Release 14 Page 151

11. Double-click the KWCertify node. The KWCertify editor displays.

❍ Click the Rule base field, expand the RuleBases_Catalog node and click the output

feature. RuleBases_Catalog\Feature displays in the Rule base field.

❍ Click the Object field, expand the BindObject node and click the output

link. BindObject\Link displays in the Object field.

❍ Click OK to validate.

At this stage of the scenario, the behaviors tree

should look like the one opposite.

Generating the Workbench

12. Save the .CATFct file. Click here to access the created .CATFct file.

13. Click the Generate Applicative Workbench icon ( ) to generate a user workbench. Enter the name of
the workbench, Applying_rulebase in this example, select Part in the scrolling list, and click OK to validate.

The generated workbench opens.

Testing the Workbench

14. From the Tools->Options...->Knowledgeware->Business Process Knowledge Template menu,

select All Users in the Access Rights scrolling list and click OK to work in a User environment.

15. Open the bktCatalogImport.CATPart file in the user workbench. The following picture displays.
Business Process Knowledge Template Version 5 Release 14 Page 152

16. Click the root of the specification tree, the icon, the root of the specification tree, and click the Design
icon to type the part.

17. Right-click Design (MyPart) and select the Design(MyPart) object->CertifyDesign command. The

Catalog browser displays.

18. Double-click ComponentFamily.2 and RuleonHole. The check contained in the rulebase is launched and

performs a check of the holes. A report is launched displaying the result of the check.

19. Update the Part.

● Note that the Status of the check is indicated in the specification tree in the
form of a green/red light. If the check runs correctly, the light is green, if not
it is red.
● Note that the report can be accessed by double-clicking the Report node in the
specification tree.

To know more about the Certify behavior, see Knowledge Certify Behavior: Data Sheet.
Business Process Knowledge Template Version 5 Release 14 Page 153

Using the Instantiate Template Behavior

This scenario provides the expert user with an example of the Instantiate Template behavior. In this
scenario the user uses the Instantiate Template behavior to instantiate a tow hook.

This scenario is divided into the following steps:

● Creating a technological object

● Adding behaviors to the technological type

● Generating the workbench

● Testing the workbench

Remember to save your .CATfct file (step 11) as well as the following files in the directory corresponding
to the CATGraphicPath environment variable:
● AssTempSupport1.CATPart

● AssTempSupport2.CATPart

● AssemblyTemplate_1.CATPart

● AssemblyTemplate_2.CATPart

● AssemblyTemplate_3.CATPart

● AssemblyTemplate_4.CATPart

● BktAssemblyTemplate.CATProduct

● BktDocumentTemplateCatalog.catalog

● BktReceivingProduct.CATProduct
Business Process Knowledge Template Version 5 Release 14 Page 154

Creating a technological Object

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench.

2. Create the TowHook technological type. To do so, proceed as follows:

Click the Create Technological Type icon ( ) to create a type. The

Create technological type dialog box displays.

❍
Enter the name of the type: TowHook.

❍
Click OK to validate.

At this stage of the scenario, the BKT

tree should look like the one opposite.

Adding behaviors to the technological type

3. Click the TowHook type and the Sequence Combination behavior icon ( ) to create a
combination of behaviors.

4. Double-click SequentialCombination in the Behaviors View and double-click TowHook in the

Behaviors tab. The Sequential Combination displays in the Behaviors tab.

5. Double-click the Sequential Combination. The Sequential Combination dialog box displays. In the

name field, enter Instantiate Tow Hook. Click OK when done.

6. Click the Instantiate Tow Hook combination and click the FilterCatalog icon ( ). The
FilterCatalog behavior displays

7. Double-click the FilterCatalog node. The Filter Catalog editor displays.

❍
In the Name field of the opening dialog box, enter DocumentTemplate_catalog.
Business Process Knowledge Template Version 5 Release 14 Page 155

Click the ... button and select the BktDocumentTemplateCatalog.catalog in the

❍

File Selection dialog box and click Open when done.

❍
Click OK to validate.

8. Click the Instantiate Tow Hook combination and click the Bind Object behavior icon ( ).

9. Double-click the Bind Object node. The Bind Object editor displays.

❍
In the Relative Name field, enter ../../..

".." indicates that the bind must be performed on the upper level. In the

current context, you go up 3 levels to reach the root product.

❍
Click OK to validate

10. Click the Instantiate Tow Hook combination and click the Instantiate Template behavior

icon ( ). InstantiateTemplate displays in the Behaviors tab.

11. Double-click the InstantiateTemplate node. The InstantiateTemplate editor displays.

❍ Click the Template feature field, expand the DocumentTemplate_catalog node

and click the output feature. DocumentTemplate_Catalog\Feature displays in the

Template feature field.

❍ Click the Destination field, expand the BindObject node and click the output

link. BindObject\Link displays in the Destination field.

❍ In the Valuation mode scrolling list, select the UseIdenticalName option.

❍ Click OK to validate.
Business Process Knowledge Template Version 5 Release 14 Page 156

At this stage of the scenario, the

behaviors tree should look like the

one opposite.

Generating the Workbench

12. Save the .CATFct file.

13. Click the Generate Applicative Workbench icon ( ) to generate the user workbench. Enter
the name of the workbench, Instantiating_DocumentTemplate in this example, select Product in

the scrolling list, and click OK to validate. The generated workbench opens.

Testing the Workbench

14. From the Tools->Options...->Knowledgeware->Business Process Knowledge

Template menu, select All Users in the Access Rights scrolling list and click OK to work in a

User environment.

15. Open the BktReceivingProduct.CATProduct file in the user workbench. The following picture

displays.
Business Process Knowledge Template Version 5 Release 14 Page 157

16. Click the root of the specification tree, the icon, the root of the specification tree, and click
the TowHook icon to type the product.

17. Right-click TowHook (Destination_Product) and select the TowHook(Destination_Product)

object->Instantiate Tow Hook command. The Catalog browser displays.

18. Double-click ComponentFamily.2 and AssemblyTemplate. The Insert Object dialog box displays.

Click the Use identical name button and OK when done. The document template is instantiated.
Business Process Knowledge Template Version 5 Release 14 Page 158

To know more about the Certify behavior, see Instantiate Template Behavior: Data Sheet.

Click here to open the created .CATfct file.

Business Process Knowledge Template Version 5 Release 14 Page 159

Designing a Table Using the Generate

Components Behavior

In the scenario detailed below, the expert designs a table using the Generate Component
behavior. The scenario is divided into the following steps:
● Creating technological types and their sub-components

● Adding the "Creating the slab" sequence to the Table Technological Type

● Adding the "Creating the legs" sequence to the Table Technological Type

● Generating the Workbench

● Testing the Workbench

Remember to save your .CATFct file in the directory corresponding to the CATGraphicPath
environment variable. To carry out this scenario, you will need the following files:
● BktLegsCatalog.catalog (that references the Bktslabtemplate.CATPart and the
Bktlegtemplate.CATPart files.)

● BktSlab.CATPart

Creating technological types and their sub-components

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench.

2. Create the Table technological type. To do so, proceed as follows:

❍ Click the Create Technological Type icon ( ) to create the technological

type. The Create technological type dialog box displays. Enter Table and click
OK.

❍ Click the Create Technological Type icon ( ) to create the technological

type. The Create technological type dialog box displays. Enter Leg and click OK.
Business Process Knowledge Template Version 5 Release 14 Page 160

❍ Click the Add

Components icon

( ) to create the
component. The

Component Creation

dialog box displays.

❍ Enter the name of the

component: Legs_list.

❍ Enter the Component

Type: Leg.

❍ Enter the number of

components: 4.

❍ Click OK to validate.

At this
stage of
the
scenario,
your
feature
dictionary
should be
similar to
the
graphic
opposite.

Adding the "Creating the slab" sequence to the Table Technological Type

3. Click the Table type and click the Sequential Combination behavior ( ) to create a
combination of behaviors.
Business Process Knowledge Template Version 5 Release 14 Page 161

At this stage of the scenario, your

feature dictionary should be
similar to the graphic opposite.

4. Double-click the SequentialCombination in the Behaviors View and Table in the

Behaviors tab to access the sequential combination.

5. Double-click the SequentialCombination node that displays in the Behaviors tab.

(Expand the Table node if need be.)

6. Enter the name of the combination, Creating the slab in this scenario, in the Name

field of the opening dialog box and click OK to validate.

7. Select the Creating the slab combination in the Behaviors tree and click the Load

Behavior icon ( ).

8. Select the Creating the slab combination in the Behaviors tree and click the Bind

Object Behavior icon ( ).

9. Double-click the BindObject behavior. The Bind Object window displays. Enter ../../.. in

the Relative Name field. Click OK to validate.

10. Click the Creating the slab combination and click the Insert Components Behavior

icon ( ). An InsertComponents behavior displays in the Behaviors tab.

❍ In the Definition scrolling list, select Existing Component.

❍ Click the Existing component field, expand the LoadDocument variables

node and select the output Document. =LoadDocument\Document
displays in the Existing component field.

❍ Click the Father product field, expand the BindObject variables node and
select the output link. =BindObject\Link displays in the Father product
field.
Business Process Knowledge Template Version 5 Release 14 Page 162

❍ Click OK to validate.

Adding the "Creating the legs" sequence to the Table Technological Type

11. Click the Table type and click the Sequential Combination behavior ( ) to create a
combination of behaviors.

12. Double-click the SequentialCombination node that displays in the Behaviors tab.

(Expand the Table node if need be.)

13. Enter the name of the combination, Creating the legs in this scenario, in the Name

field of the opening dialog box and click OK to validate.

14. Select the Creating the legs combination in the Behaviors tree and click the Filter

Catalog Behavior icon ( ).

15. Double-click the FilterCatalog node. The Filter Catalog editor displays.

❍ Click the ... button and select the BktLegsCatalog.catalog in the File
Selection dialog box and click Open when done.

❍ Click OK to validate.

16. Click the Creating the legs combination and click the Generate Components Behavior

icon ( ).

17. Double-click the Generate Components behavior. The GenerateComponents dialog box

displays.

❍ In the Name field, enter Generate legs.

❍ Click the Component list name, expand the Table variables node and
select the Legs_list attribute: The other fields are automatically filled.

❍ Click OK to validate.

18. Click the Generate legs combination and click the Bind Object Behavior icon ( ).

19. Double-click the BindObject behavior. The Bind Object window displays. Enter ../../.. in
Business Process Knowledge Template Version 5 Release 14 Page 163

the Relative Name field. Click OK to validate.

20. Click the Generate legs combination and click the Instantiate Template behavior

icon ( ). InstantiateTemplate displays in the Behaviors tab.

21. Double-click the InstantiateTemplate node. The InstantiateTemplate editor displays.

❍ Click the Template feature field, expand the FilterCatalog node and
click the output feature. FilterCatalog\Feature displays in the Template
feature field.

❍ Click the Destination field, expand the BindObject node and click the
output link. BindObject\Link displays in the Destination field.

❍ Click OK to validate.

22. Click the Generate legs combination and click the Add item behavior icon ( ).

23. Double-click the AddToList behavior. The AddToList dialog box displays.

❍ Click the List field, expand the Generate legs combination variables node
and click the List. =Generate legs\List displays in the List field.

❍ Click the Object field, expand the InstantiateTemplate node, and select
the UserFeature output. =InstantiateTemplate\UserFeature displays in
the Object field.

❍ Link the index and the iteration feature of the Generate component
behavior.

❍ Click OK to validate.
Business Process Knowledge Template Version 5 Release 14 Page 164

At this stage of the scenario, the

Behaviors tab should be similar to the
graphic opposite.

The definition of the behaviors is now over. Save your file and generate your workbench. (Click
here to display the generated .CATfct file).

Generating the Workbench

24. Click the Applicative Workbench Generation icon ( ) to generate a user

workbench. Enter the name of the workbench, Designing a Table in this example, as

well as the workbench type, Product in this scenario.

Testing the Workbench

25. From the Tools->Options->Knowledgeware->Business Knowledge Template

menu, select All Users in the Access Rights scrolling list and click OK to work in a

User environment.
Business Process Knowledge Template Version 5 Release 14 Page 165

26. Click the root of the specification tree, then the icon, then the root of the
specification tree, and click the Table icon to type the product.

27. Right-click Table (Product1) and select the Table(Product1) object->Creating the

slab command. The File selection window displays. Select the BktSlab.CATPart file. The

following image displays.

28. Right-click Table (Product1) and select the Table(Product1) object->Creating the

legs command. The Catalog Browser displays. Double-Click ComponentFamily.2, and

Document Template.1. The Insert Object dialog box displays.

29. In the geometry, select one point and click OK. The first leg is instantiated.

30. Repeat the same operation with the other legs. The instantiation panel i.e. the Insert

object dialog box displays 4 times, enabling you to instantiate the 4 legs.

31. Click Close. The 4 legs

are instantiated as

defined when creating

the Table type.

Note that:

● The document templates

are instantiated and that
the parts are typed
according to the type
defined in the .CATFct file.
● If you edit the component
list located below the table
product, 4 instances are
present.
Business Process Knowledge Template Version 5 Release 14 Page 166

To know more about:

● The Generate Component behavior, see Generate Component Behavior: Data Sheet.

● The Add Item To List behavior, see Add item Behavior: Data Sheet Behavior.

● The workbench generation, see Generating a User Workbench.

● Components, see Adding a component to a technological object.

Business Process Knowledge Template Version 5 Release 14 Page 167

Using the Loop Behavior

The aim of this scenario is to show the user how to use the loop behavior as a "while" object.
The expert user defines rules and checks to set the instantiation context of dominoes and the
loop is automatically stopped during its execution. The expert user defines a number of
iterations which is too large and he wants to send a panel to inform the user when and why the
loop stops.

The scenario is divided into the following steps:

● Creating the technological type

● Adding the "Instantiation in Context" sequence to the DominoesSet Technological Type

● Creating the Loop of behaviors

● Generating the Workbench

● Testing the Workbench

Remember to:
● Save your .CATScript files in the startup\automation directory and your .CATFct file in the
directory corresponding to the CATGraphicPath environment variable.
● Modify the path of the LoadDocument behavior if you use the provided .CATFct file.
● To carry out this scenario, you will need the following files:

❍ BktUDFDomino.CATPart

❍ BktInfo.CATScript

❍ BktDominoSystem.CATPart
Business Process Knowledge Template Version 5 Release 14 Page 168

Creating the technological type

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench.

2. Create the DominoesSet technological type. To do so, proceed as follows:

❍ Click the Create Technological Type icon ( ) to create the

technological type. The Create technological type dialog box displays.
Enter DominoesSet.

❍ Click OK to validate.

Adding the "Instantiation in Context" sequence to the DominoesSet Technological

Type

3. Click the DominoesSet type and click the Sequential Combination behavior ( ) to
create a combination of behaviors.

4. Double-click the SequentialCombination in the Behaviors View and DominoesSet in the

Behaviors tab to access the sequential combination.

5. Double-click the SequentialCombination node that displays in the Behaviors tab.

(Expand the DominoesSet node if need be.)

6. Enter the name of the combination, Instantiation in context in this scenario, in the

Name field of the opening dialog box and click OK to validate.

7. Select the Instantiation in context combination in the Behaviors tree and click the

Bind Object Behavior icon ( ).

8. Double-click the BindObject behavior. The Bind Object window displays.

❍ Enter Bind Part in the Name field.

❍ Enter ../../.. in the Relative Name field. Click OK to validate.

9. Select the Instantiation in context combination in the Behaviors tree and click the

Bind Object Behavior icon ( ).

Business Process Knowledge Template Version 5 Release 14 Page 169

❍ Enter Bind PartBody in the Name field.

❍ Click the Starting from field, expand the BindPart variables node
and select the Link. =BindPart\Link displays in the Starting from
field.

❍ Enter PartBody in the Relative Name field. Click OK to validate.

10. Select the Instantiation in context combination in the Behaviors tree and click the

Bind Object Behavior icon ( ).

11. Double-click the BindObject behavior. The Bind Object window displays.

❍ Enter Bind Sketch Support in the Name field.

❍ Click the Starting from field, expand the Bind PartBody variables
node and select the Link. =Bind PartBody\Link displays in the
Starting from field. Click OK to validate.

12. Select the Instantiation in context combination in the Behaviors tree and click the

Load Behavior icon ( ).

13. Double-click the LoadDocument node. The Load Document editor displays.

❍ Click the ... button and select the BktUDFDomino.CATPart in the File
Selection dialog box and click Open when done.

❍ Click OK to validate.

14. Select the Instantiation in context combination in the Behaviors tree and click the

Bind User Feature icon ( ).

15. Double-click the BindUserFeature in the Behaviors tree. The Bind User Feature editor

displays.

❍ Select the From object: field, expand the LoadDocument

variables node and select the Document output.
=LoadDocument\Document displays in the From object: field.

❍ Click OK to validate.
Business Process Knowledge Template Version 5 Release 14 Page 170

Creating the Loop of behaviors

16. Select the Instantiation in context combination in the Behaviors tree and click the

Loop icon ( ).

17. Double-click the Loop in the Behaviors tab. The Loop editor displays.

❍ Enter the number of iterations: 15.

❍ Click the Attributes tab and add the following attribute:

NameInst_RatioType Real QualityInput Value 0.1

❍ Click OK to validate.

18. Select the Loop combination in the Behaviors tree and click the Knowledge Relations

Behavior icon ( ).

19. Double-click the KnowledgeRelations behavior. The Knowledge Relations editor displays.

20. Click the Attributes tab and add the following attributes:

Name TempRatio Type Real Quality Internal

Name RatioforUDF Type Real Quality Output

Name ratio Type Real Quality Input

Name UDF_Act Type Boolean Quality Output Value False

Name Info_Act Type Boolean Quality Output Value False

21. In the Content tab, right-click the TempRatio attribute and select the Edit Formula

command. The Formula editor displays.

22. Enter the following formula: TempRatio=ratio + `DominoesSetMDL\Instantiation in

context\Loop\Iteration` / 2 * 0.1. Click OK when done to close the editor.

23. Click the Content tab and click the Rule icon ( ). Enter the following rule body into
the rule editor, click OK when done and OK to exit the Knowledge Relations editor.
Business Process Knowledge Template Version 5 Release 14 Page 171
if TempRatio <= 1
{
RatioforUDF = TempRatio
UDF_Act = TRUE
Info_Act = FALSE
}
else
{
RatioforUDF = TempRatio
`DominoesSetMDL\Instantiation in context\Loop\NumberOfIterations`
= `DominoesSetMDL\Instantiation in context\Loop\Iteration`
UDF_Act = FALSE
Info_Act = TRUE
}

24. Expand the Knowledge Relations variables node as well as the Loop variables node.

25. Right-click the ratio variable located below the Knowledge Relations node, select the

ratio object->Link To command, and click the Inst_Ratio variable located below the

Loop node. Both variables are now linked.

26. Select the Loop combination in the Behaviors tree and click the Instantiate Template

Behavior icon ( ).

❍ Click the Template feature field, expand the BindUserFeature

node and select the UserFeature. =BindUserFeature\UserFeature
displays in the Template feature field.

❍ Click the Destination field, expand the Bind Part node and select
the Link. =Bind Part\Link displays in the Destination field.

❍ Click the Add button in the Defined inputs and parameters field
and add the following attributes:

Name: ratio, Type: Real, Quality: Input, Value:

0.1

Name: Sketch.1, Type: ExternalObject, Quality:

Input

❍ Click OK when done.

27. Expand the Instantiate Template variables node, right-click the ratio variable located

below the Knowledge Relations node, select the ratio object->Link To command, and

click the RatioforUDF variable located below the Knowledge Relations node.

28. Right-click the Sketch.1 variable, select the Sketch.1 object->Link To command,

expand the Bind Sketch Support variables node and select the Link.
Business Process Knowledge Template Version 5 Release 14 Page 172

29. Right-click the Activity variable, select the Activity object->Link To command, and

click the UDF_Act variable located below the Knowledge Relations node.

30. Select the Loop combination in the Behaviors tree and click the Synchronize

Parameters Behavior icon ( ).

31. Double-click the SynchronizeParameters behavior in the Behaviors tree. The

Synchronize Parameters editor opens:

❍ Click the From Parameter field, expand the Knowledge Relations

node and click the RatioforUDF variable.
=KnowledgeRelations\RatioforUDF displays in the From
Parameter field.

❍ Click the To Parameter field, expand the Loop node and click the
Inst_Ratio variable. = Loop\Inst_Ratio displays in the To
Parameter field.

❍ Click OK to validate.

32. Expand the SynchronizeParameters behavior node in the Behaviors tree. Right-click the

Activity variable, select the Activity object->Link To command and click the UDF_Act

variable located below the Knowledge Relations node.

33. Select the Loop combination in the Behaviors tree and click the Add To List Behavior

icon ( ).

34. Double-click the AddToList behavior. The AddToList editor displays:

❍ Click the List field, expand the Loop variables node and select
the List feature. = Loop\List displays in the List field.

❍ Click the Object: field, expand the BindUserFeature variables

node and select the UserFeature. =BindUserFeature\UserFeature
displays in the Object field.

❍ Click OK when done.

35. Expand the AddToList behavior node. Right-click the Activity variable, select the

Activity object->Link To command and click the UDF_Act variable located below the

Knowledge Relations node.

Business Process Knowledge Template Version 5 Release 14 Page 173

36. Right-click the Index variable, select the Index object->Link To command and click

the Iteration variable located below the Loop node.

37. Select the Loop combination in the Behaviors tree and click the VB Script Behavior

icon ( ).

38. Double-click the VBScript behavior in the behaviors tree. The VBScript editor displays.

❍ Click the ... in the VB Name field and select the

BktInfo.CATScript file.

❍ Click the Add button in the Defined inputs and parameters field
and add the following attributes:

■ Name: Iteration, Type: Integer, Quality: Input,

Value: 1

■ Name: Ratio, Type: Real, Quality: Input, Value: 0.1

■ Name: NextRatio, Type: Real, Quality: Input, Value:

0.15

❍ Click OK when done.

39. Expand the VBScript behavior node. Right-click the Iteration variable, select the

Iteration object->Link To command and click the Iteration variable located below the

Loop node.

40. Right-click the Ratio variable, select the Ratio object->Link To command and click the

Inst_Ratio variable located below the Loop node.

41. Right-click the NextRatio variable, select the NextRatio object->Link To command

and click the RatioforUDF variable located below the Knowledge Relations node.

42. Right-click the Activity variable, select the Activity object->Link To command and

click the Info_Act variable located below the Knowledge Relations node.
Business Process Knowledge Template Version 5 Release 14 Page 174

At this stage of the scenario, the

Behaviors tab should be similar to the
graphic opposite.

The definition of the behaviors is now over. Save your file and generate your workbench. (Click
here to display the generated .CATfct file).

Generating the Workbench

43. Click the Applicative Workbench Generation icon ( ) to generate a user

workbench. Enter the name of the workbench, Dominoes in this example, as well as the

workbench type, Part in this scenario.

Testing the Workbench

44. From the Tools->Options->Knowledgeware->Business Knowledge Template

menu, select All Users in the Access Rights scrolling list and click OK to work in a

User environment.

45. Open the BktDominoSystem.CATPart file.

46. Click the root of the specification tree, the icon, the root of the specification tree,
and click the DominoesSet icon to type the product.
Business Process Knowledge Template Version 5 Release 14 Page 175

47. Right-click DominoesSet (Part2) object and select the DominoesSet(Part2) object-

>Instantiation in Context command. The Dominoes are instantiated and a message

displays indicating that the instantiation will stop at iteration 6.

To know more about:

● The Loop behavior, see Loop Behavior: Data Sheet.

● The Add Item To List behavior, see Add item Behavior: Data Sheet Behavior.

● The workbench generation, see Generating a User Workbench.

Business Process Knowledge Template Version 5 Release 14 Page 176

Use Cases
The scenarios are taken from the interior packaging domain of vehicle design.

End-User: the use cases presented Designing the External Mirror

in this section are intended for end-
users only.
Computing the Optimal Mirror

Expert User: the use cases Creating a User Workbench: Indirect Vision
presented in this section are
intended for expert users only. They
aim at demonstrating how to create
useful workbenches.
Business Process Knowledge Template Version 5 Release 14 Page 177

Creating a User Workbench: Indirect Vision

This section provides the expert user with a detailed example. In this scenario, the expert user creates a new
user workbench designed to compute the indirect field of view of a car driver. The scenario is divided into 11
major steps. (See below.)

● Before you start

● Setting up the Working Environment

● Creating Technological Objects

● Defining the "Define Vehicle Data" Combination for the IndirectVision Object

● Defining the "Define Driver" Combination on the IndirectVision Object

● Defining a "Compute Optimal Mirror" Combination for the Indirect Vision Technological
Type

● Defining a "Generate Report" Behavior on the Indirect Vision Technological Type

● Defining a "Generate Indirect Field of View for a Classic Mirror" Combination on the Driver
Technological Type

● Defining a "Check Driver Position" Behavior on the Driver Technological Type

● Generating the User Workbench

Business Process Knowledge Template Version 5 Release 14 Page 178

Before you start

For the purpose of the scenario described in this Expert User use case, the expert user should
create an \Indirect_vision_data directory on his local drive and store all the provided and
generated files in this directory (see graphic below). This path is used by the behaviors to find the
required data.

If you do not have a E drive, edit the paths of the following behaviors in your *.CATFct
files before you generate the workbench:
● Load behavior

● LoadNew behavior

● VBScript behavior

● FilteredCatalog behavior

Copy Vehicle_Data.CATPart Into Indirect_Vision_Data

Copy Target_Part.CATPart Into Targets-Definition

Target.CATPart

Copy Report.html Into html

Business Process Knowledge Template Version 5 Release 14 Page 179

Copy ● Mirror_Part.CATPart Into Mirrors-Definition

● Mirror_Design.CATPart

● BktMirror.Catalog

Copy ● BktDriver.catalog Into Drivers-Catalog

● BktDriver2D5Female.CATPart

● BktDriver2D50Male.CATPart

● BktDriver2D95Male.CATPart

Copy ● BktSaveLastPart.CATScript Into VB Scripts

● BktLinkDriverToRepresentation.CATScript

● BktClassicIFVLegislationLink.CATScript

● BktAdvancedIFVLegislationLink.CATScript

● BktTestPublicationMirror.CATScript

● BktLinkMirrorToRepresentation.CATScript

● BktTestPublicationTarget.CATScript

● BktLegislationLink.CATScript

● BktTestPublicationDriver.CATScript

Copy ● BktClassicMirrorsChecking.CATPart Into Mirrors_Checking

● BktPlaneMirrorsSectionChecking.CATPart

Copy ● BktMirrorsCalculationEEC.CATPart Into Mirrors_Calculation

● BktMirrorsCalculationUS.CATPart

● BktMirrorsCalculationEEC.catalog

● BktMirrorsCalculationUS.catalog

Copy ● BktCheckingResults.CATPart Into Checking_Results

● BktAdvancedCheckingResults.CATPart
Business Process Knowledge Template Version 5 Release 14 Page 180

Copy ● IndirectVisionStep01.CATfct Into CATFct

● IndirectVisionStep01a.CATfct

● IndirectVisionStep01b.CATfct

● IndirectVisionStep02.CATfct

● IndirectVisionStep02a.CATfct

● IndirectVisionStep03.CATfct

To generate a user workbench and to work in user mode, some files saved in the \Indirect_vision_data
structure will have to be copied into the appropriate directories as shown below:

Copy ● IndirectVisionStep01.CATfct Into the \CATGraphicPath

directory. If this directory
● IndirectVisionStep01a.CATfct does not exist, create the
folder E:\temp. Make sure
● IndirectVisionStep01b.CATfct that this folder is empty
when beginning the
● IndirectVisionStep02.CATfct
scenario. The data will be
● IndirectVisionStep02a.CATfct saved here by the VBScript
automation.
● IndirectVisionStep03.CATfct

Copy ● BktSaveLastPart.CATScript Into the automation directory of

the path corresponding to
● BktLinkDriverToRepresentation.CATScript the \CATStartupPath
environment variable in your
● BktClassicIFVLegislationLink.CATScript customized workspace.

● BktAdvancedIFVLegislationLink.CATScript

● BktTestPublicationMirror.CATScript

● BktLinkMirrorToRepresentation.CATScript

● BktTestPublicationTarget.CATScript

● BktLegislationLink.CATScript

● BktTestPublicationDriver.CATScript

Copy Report.html Into the html directory of the

path corresponding to the
CATStartupPath environment
variable in your customized
workspace.

Copy The icons that you associated with the Into the icons\normal directory of
behaviors you created (if any). the path corresponding to
the \CATGraphicPath
environment variable in your
customized workspace.
Business Process Knowledge Template Version 5 Release 14 Page 181

Setting up the Working Environment

This task is the first to be performed by the expert user prior to starting defining the user
workbench.

1. Delete your CATSettings.

2. Open Catia V5.

3. From the Tools -> Options... menu, select General->Parameters and Measure-

>Knowledge, and check:

● With value, and With formula in the Parameter tree view field.

● Load extended language libraries, and All packages in the Language field.
(Click the graphic below to enlarge it.)

4. From the Tools -> Options... menu, select General->Parameters and Measure-

>Language, and check:

● Load extended language libraries, and All packages in the Language field.
(Click the graphic below to enlarge it.)
Business Process Knowledge Template Version 5 Release 14 Page 182

5. Select Infrastructure->Product Structure->Tree Customization and set

Parameters and Relations to Yes.

(Click the graphic below to enlarge it.)

6. Select Infrastructure->Part Infrastructure ->General and check (Click the

graphic opposite to enlarge it.):

●
Keep link with selected object

●
Only use published elements for external selection keeping link

(Click the graphic below to enlarge it.)

7. Select Infrastructure->Part Infrastructure->Display and check:

● Constraints

● Parameters

● Relations

(Click the graphic below to enlarge it.)

Business Process Knowledge Template Version 5 Release 14 Page 183

8. Select Knowledgeware->Business Process Knowledge Template and

check/select:

● All Users in the Access Rights scrolling list.

● Variables and attributes.

This option defines the access rights granted. In BKT the access rights
are set to Expert by default.

(Click the graphic below to enlarge it.)

9. Click OK to validate your settings and proceed to the next task: Creating technological

Objects.
Business Process Knowledge Template Version 5 Release 14 Page 184

Creating technological Objects

This task consists in:

● Creating the technological objects that the expert user will use when creating the behaviors
● Assigning them attributes.

The user creates the following technological objects:

● Vision and its sub-types: IndirectVision, and DirectVision

● Driver
● Passenger
● External Mirror
● Target Vision

1. From the Start->Knowledgeware menu, access the Business Process Knowledge

Template workbench. The workbench opens displaying a new Feature Dictionary.

Creating the Vision technological Object and its Sub-Types

2. Click the Create technological Type icon ( ) and enter Vision in the Create
technological type dialog box. Click OK to validate.

3. Click the Vision object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the

attribute

name:

Standard.
Business Process Knowledge Template Version 5 Release 14 Page 185

❍ Select the

attribute type:

String

❍ Enter the

attribute

value: SAE

and click OK

to validate.

4. Click the Vision object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: Legislation.

❍ Select the attribute type: String.

❍ Enter the attribute value: EEC and click OK to validate.

5. Click the Vision object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: Passenger1.

❍ Select the attribute type: Boolean.

❍ Enter the attribute value: False and click OK to validate.

Business Process Knowledge Template Version 5 Release 14 Page 186

6. Click the Vision object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: Passenger2.

❍ Select the attribute type: Boolean.

❍ Enter the attribute value: False and click OK to validate.

7. Click the Vision object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: PassengerCount.

❍ Select the attribute type: Integer.

❍ Enter the attribute value: 0 and click OK to validate.

8. Click the Vision object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: RearPassenger1Y.

❍ Select the attribute type: Length.

❍ Enter the attribute value: 0 and click OK to validate.

9. Click the Vision object and click the Create technological type icon ( ). Enter
Business Process Knowledge Template Version 5 Release 14 Page 187

IndirectVision in the Create technological type window. IndirectVision displays in the

specification tree.

10. Click the Vision object and click the Create technological type icon ( ). Enter
DirectVision in the Create technological type window. DirectVision displays in the

specification tree.

At this stage of the scenario, the

Feature Dictionary tree should
look like the one opposite.

Creating the Driver technological Object

11. Click the Create technological type icon ( ) and enter Driver in the Create
technological type window.

12. Click the Driver type and click the Add Attribute icon ( ). In the Add Attribute dialog
box, enter the following values.

❍ Enter the attribute name: L40.

❍ Select the attribute type: Angle

❍ Enter the attribute value: 25 and click OK to validate.

13. Click the Driver object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.
Business Process Knowledge Template Version 5 Release 14 Page 188

❍ Enter the attribute name: FootAngle.

❍ Select the attribute type: Angle

❍ Enter the attribute value: 42 and click OK to validate.

14. Click the Driver object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: AnkleAngle.

❍ Select the attribute type: Angle

❍ Enter the Quality: Output and click OK to validate.

15. Click the Driver object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: KneeAngle.

❍ Select the attribute type: Angle

❍ Enter the Quality: Output and click OK to validate.

16. Click the Driver object and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.
Business Process Knowledge Template Version 5 Release 14 Page 189

❍ Enter the attribute name: HipAngle.

❍ Select the attribute type: Angle

❍ Enter the Quality: Output and click OK to validate.

17. Click Driver and click the Add Attribute icon ( ). The Add Attribute dialog box
displays.

❍ Enter the attribute name: XPosition.

❍ Select the attribute type: Length

❍ Enter the attribute value: 1300 and click OK to validate.

18. Click Driver and click the Add Attribute icon ( ). The Add Attribute dialog box
displays.

❍ Enter the attribute name: YPosition.

❍ Select the attribute type: Length

❍ Enter the attribute value: 350 and click OK to validate.

19. Click Driver and click the Add Attribute icon ( ). The Add Attribute dialog box
displays.
Business Process Knowledge Template Version 5 Release 14 Page 190

❍ Enter the attribute name: ZPosition.

❍ Select the attribute type: Length

❍ Enter the attribute value: 220 and click OK to validate.

Creating the external Mirror technological Object

20. Click the Create technological type icon ( ) and enter ExternalMirror in the
Create technological type window.

21. Click ExternalMirror and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: Radius.

❍ Select the attribute type: Length

❍ Enter the attribute value: 2000 and click OK to validate.

22. Click ExternalMirror and click the Add Attribute icon. The Add Attribute dialog box

displays.

❍ Enter the attribute name: XPosition.

❍ Select the attribute type: Length

❍ Enter the attribute value: 40 and click OK to validate.

Business Process Knowledge Template Version 5 Release 14 Page 191

23. Click ExternalMirror and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: ZPosition.

❍ Select the attribute type: Length

❍ Enter the attribute value: 10 and click OK to validate.

24. Click ExternalMirror and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: Length.

❍ Select the attribute type: Length

❍ Enter the attribute value: 120 and click OK to validate.

25. Click ExternalMirror and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: Width.

❍ Select the attribute type: Length

❍ Enter the attribute value: 20 and click OK to validate.

Business Process Knowledge Template Version 5 Release 14 Page 192

26. Click ExternalMirror and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: VerticalAngle.

❍ Select the attribute type: Angle

❍ Enter the attribute value: 25 and click OK to validate.

27. Click ExternalMirror and click the Add Attribute icon ( ). The Add Attribute dialog
box displays.

❍ Enter the attribute name: HorizontalAngle.

❍ Select the attribute type: Angle

❍ Enter the attribute value: -6 and click OK to validate.

Creating the indirect Target Vision technological Object

28. Click the Create technological type icon ( ) and enter Target in the Create
technological type window.

29. Click Target and click the Create technological type icon ( ) and enter
IndirectTarget in the Create technological type window.

30. Save your file in a temporary directory.

You have created your technological objects and their attributes.

Business Process Knowledge Template Version 5 Release 14 Page 193

Proceed to the next task: Creating the Behaviors associated with the indirect Vision
technological Type.
Business Process Knowledge Template Version 5 Release 14 Page 194

Defining the "Define vehicle data" Combination

for the IndirectVision Object

In this topic, the expert user creates a combination that will enable the end-user to insert a
vehicle into his product.

1. Open the IndirectVisionStep01.CATfct file.

2. Click the IndirectVision object in the specification tree and click the Sequential

Combination icon ( ). Double-click IndirectVision to display the Behaviors tree, then

SequentialCombination: IndirectVision displays in the Behaviors tab.

3. Double-click IndirectVision in the Behaviors tab, then the SequentialCombination node.

The Sequential Combination editor displays.

Enter Define vehicle data in the Name field.

Select the icon you want to associate with the behavior (optional).

Click OK to validate.

4. Click the Define vehicle data behavior and click the Load Behavior icon ( ).
LoadDocument displays in the Behaviors tab.

5. Double-click the LoadDocument node. The Load Document editor displays.

In the Properties tab, select Expert&Administrator in the scrolling

list of the Behavior States and check the Activate check box.

Click OK to validate.
Business Process Knowledge Template Version 5 Release 14 Page 195

When the file path is unset for a Doc based behavior, a File Open

box will open at the beginning of the operation in the User

Workbench.

6. Click the Define vehicle data combination and click the Bind Object behavior icon ( ).

7. Double-click the Bind Object node. The Bind Object editor displays.

❍
In the Relative Name field, enter ../../..

".." indicates that the bind must be performed on the upper level.

This string is the third father of the Bind Object and will be, in the

User Workbench, the product associated with the IndirectVision

type.

❍
In the Properties tab, select Expert in the scrolling list of the

Behavior States and check the Activate check box.

❍
Click OK to validate

At this stage, the behaviors tree should

be like the one opposite.

8. Click the Define vehicle data combination and click the Insert Components Behavior

icon ( ). An InsertComponents behavior displays in the Behaviors tab.

9. Double-click the InsertComponents node. The InsertComponents editor displays.

❍
In the Name field, enter Component Creation.
Business Process Knowledge Template Version 5 Release 14 Page 196

❍
In the Definition scrolling list, select Existing Component.

❍
Click the Existing component field, expand the LoadDocument node

and selection the output Document.

❍
Click the Father product field, expand the BindObject node and select

the output Link.

❍
Set the number of instances to 1.

❍
In the Type Name field, enter Vehicle.

The technological type "Vehicle" will be associated with the created

instance when operating this behavior in the User Workbench.

❍
In the Allow sub-typing scrolling list, select false.

The end-user will not be able to sub-type the created instances when

operating this behavior in his workbench.

Click OK to validate. Your Behaviors tree is now identical to the one

below.
Business Process Knowledge Template Version 5 Release 14 Page 197

10. Save your file and proceed to the next task: Defining the "Define Driver" Combination

on the IndirectVision Object. (To see the result .CATfct file, click here.)
Business Process Knowledge Template Version 5 Release 14 Page 198

Defining the "Define driver" Combination on the

IndirectVision Object

In this topic, the expert user creates a combination that will enable the end-user to insert a
manikin into the vehicle that he inserted in the previous topic.

1. Click the Indirect Vision object in the Behaviors tab and click the Sequential

Combination icon ( ).

2. Double-click the Sequential Combination node in the Behaviors tab. The

SequentialCombination editor displays.

3. Enter Define driver in the Name field and click OK to validate.

4. Click the Define driver combination in the Behaviors tab and click the Bind Object

behavior icon ( ). The BindObject behavior displays in the Behaviors tree.

5. Double-click the Bind Object node. The Bind Object editor displays. In the Relative

Name field, enter ../../.. and click OK to validate.

6. Click the Define driver combination in the Behaviors tab and click the Bind Parameter

behavior icon ( ). The BindParameter behavior displays in the Behaviors tree.

7. Double-click the BindParameter node. The Bind Object editor displays. In the Relative

Name field, enter Legislation and click OK to validate.

8. Click the Define driver combination in the Behaviors tab and click the Link Parameters

behavior icon ( ).

9. Click the Define driver combination in the Behaviors tab and click the Filter Catalog

behavior icon ( ). The FilterCatalog behavior displays in the Behaviors tree.

10. Double-click the FilterCatalog node. The FilterCatalog editor displays. Click the ... button

and select the BktDriver.catalog file.

Business Process Knowledge Template Version 5 Release 14 Page 199

11. In the Filtering Keywords field, click the Add button and create a Name attribute:

❍
In the

Name

field,

enter

Name.

❍
In the

Type

scrolling

list,

select

String.

❍
Click

OK

twice to

validate.

12. Double-click the LinkParameter behavior. The LinkParameter behavior displays.

❍
Click the From Parameter field, expand the BindParameter node and

select the output link. =BindParameter\Link displays in the From

Parameter field.

❍
Click the To Parameter field, expand the FilterCatalog node and select

the Name feature. =FilterCatalog\Name displays in the To Parameter

field.

❍
Click OK to validate.

13. Click the Define driver combination in the Behaviors tab and click the Instantiate

Template behavior icon ( ).

14. Double-click the InstantiateTemplate node. The InstantiateTemplate editor displays.

Business Process Knowledge Template Version 5 Release 14 Page 200

❍
Click the Template feature field, expand the FilterCatalog node and

select the output feature. =FilterCatalog\Feature displays in the

field.

❍
Click the Destination field, expand the BindObject node and select

the output link. = BindObject\Link displays in the field.

❍
In the Valuation mode scrolling list, select UseIdenticalName.

❍
Click OK twice to validate.

(Click the graphic opposite to

enlarge it.)

At this stage, the behaviors

tree should be like the one

opposite

15. Click the Define driver combination in the Behaviors tab and click the AddType

Behavior icon ( ). The AddType behavior displays in the tree.

16. Double-click the AddType node. The AddType editor displays.

Business Process Knowledge Template Version 5 Release 14 Page 201

❍ In the Type Name field, enter Driver.

❍ Click the ... button in the Catalog Name field, and select the current

.CATFct file. (Note that your file should be saved).

❍ Click the Object to type field, expand the Instantiate Template node and

select the UserFeature feature.

❍ Click OK to validate.

17. Click the Define driver combination in the Behaviors tab and click the VBScript

Behavior icon ( ). The VBScript behavior displays.

18. Double-click the VBScript node. The VBScript editor displays.

In the VB Name field, click the button and select the

BktSaveLastPart.CATScript in the File Selection dialog box.

❍
Click the Add button in the Defined inputs and parameters field. In

the Name field, enter PartDocName. In the Type scrolling list, select

String. In the Value field, enter Driver_Part1.

❍
Click OK twice to validate.

18. Click the Define driver combination in the Behaviors tab and click the VBScript

Behavior icon ( ). The VBScript behavior displays.

19. Double-click the VBScript node. The VBScript editor displays.

In the VB Name field, click the button and select the

BktLinkDriverToRepresentation.CATScript in the File Selection dialog box.
Business Process Knowledge Template Version 5 Release 14 Page 202

❍
Click OK to validate.

Your Behaviors tree is now identical to the

one opposite.

(To display the result .CATfct file, click

here.)
Business Process Knowledge Template Version 5 Release 14 Page 203

Defining a "Compute Optimal Mirror" Combination for the

Indirect Vision Object

In this scenario, the expert user implement the "if … then …else…" pattern using a Knowledge Relations behavior.
This relation is a rule that drives the activity of two combinations.

1. Open the IndirectVisionStep02.CATfct file. Double-click on IndirectVision's Behaviors and then

IndirectVision in the Behaviors tab. The following graphic displays:

Note that:

❍ For IndirectVision object, a new combination called

"Compute Optimal Mirror", and a sub-combination called

"Mirror_EEC", have been created.

❍ The Load_EEC and BindPowerCopy behaviors that retrieve a

PowerCopy stored in a document have been created.

❍ The LoadNew, BindObject and InsertComponents behaviors

have been created: They create and insert below the

product IndirectVision the new part in which the powercopy

will be instantiated.

❍ The Find_External_Mirror_Part behavior retrieves the

feature part of the previous part document.

❍ The Imports creation combination creates all the external

references which will be inputs of the powercopy.

❍ The PowerCopySpecification behavior instantiates the

powercopy. Note that inputs have been created on this

behavior and linked to the previous imports.

2. Click the Compute optimal mirror combination and click the Knowledge Relations behavior icon ( ).

3. Double-click the KnowledgeRelation node in the Behaviors tab. The Knowledge Relations editor displays.
Business Process Knowledge Template Version 5 Release 14 Page 204
4. In the Name field, enter Trigger Load.

5. Click the Attributes tab and add the following attributes:

❍
Name: CurrentLegislation, Type: String, Value: EEC

❍
Name: Act_EEC, Type: Boolean, Value: false, Quality: Output

❍
Name: Act_US, Type: Boolean, Value: true, Quality: Output

To know more about the Quality field, see To know more about the Add Attribute

dialog box...

6. Add a rule to the behavior. To do so, proceed as follows:

Click the Content tab then the Rule icon ( ) in the Knowledge Tools toolbar to add the
rule. The Rule Editor opens.

Enter the name of the rule and click OK to access the Rule editor window.

In the Rule editor, enter the following rule and click OK twice to validate and to exit the

Rule editor:

if CurrentLegislation == "EEC"
{
Act_EEC =TRUE
Act_US = FALSE
}
else
{
Act_US =TRUE
Act_EEC = FALSE
}

7. Right-click the Trigger Load behavior

and select the Trigger Load object-

>Reorder command.
Business Process Knowledge Template Version 5 Release 14 Page 205

8. Click the Compute optimal mirror

combination: The Knowledge relation is

now located right below the Compute

optimal mirror combination.

9. Link the Trigger Load behavior and the Compute optimal mirror combination for the rule contained in the

Trigger Load behavior to be driven by the Legislation attribute defined on the IndirectVision object. To do

so proceed as follows:

● Expand the behavior model IndirectVision and its Attributes node.

● Expand Trigger Load and its variables node.

● Right-click the CurrentLegislation attribute and "Link to", then

select the Legislation attribute of the IndirectVision behavior: The
rule is now driven by the Legislation attribute defined on
IndirectVision.

10. Right-click the Mirror_EEC combination and select the Copy command.

11. Right-click the Compute optimal mirror combination and select the Paste command: A combination named

Mirror_EEC.1 was pasted below Mirror_EEC.

Business Process Knowledge Template Version 5 Release 14 Page 206

12. Double-click the Mirror_EEC.1 node. The Sequential Combination editor displays.

13. In the Name field of the opening dialog box, enter Mirror_US and click OK to validate.

14. Expand the Mirror_US node and double-click the Load_EEC node. The Load Document editor displays.

❍ Change the name to Load_US in the Name field.

❍ Click the button and select the Mirrors_Calculation_US.CATPart file.

15. Save your file and proceed to the next task: Defining a "Generate Report" Behavior on the Indirect Vision
Technological Type.
Business Process Knowledge Template Version 5 Release 14 Page 207

Defining a "Generate Report" Behavior on the

IndirectVision Object

In this topic, the expert user creates a combination of behaviors designed to open a html page
showing the values of 3 variables of 3 technological objects:
● Mirror

● Driver

● IndirectVision

1. Select the IndirectVision object in the specification tree and click the Sequential

Combination icon ( ). Sequential Combination displays in the Behaviors tab.

2. Double-click the SequentialCombination node to edit it. The Sequential Combination

editor displays.

3. In the Name field of the opening dialog box, enter Generate Report and click OK to

validate.

4. Select the Generate Report combination in the Behaviors tree and click the Sequential

Combination icon ( ). Sequential Combination displays in the Behaviors tab.

5. In the Name field of the opening dialog box, enter Retrieve Mirror and click OK to

validate.

6. Select the Retrieve Mirror combination and click the Bind Object behavior icon ( ).

7. Double-click the Bind Object node. The Bind Object editor displays.

❍ In the Name field, enter Bind Mirror.

❍ In the Relative Name field, enter ../../../../Mirror_Part. This path points out the

instance of product typed by Mirror in the User Workbench.

❍ Click OK to validate.
Business Process Knowledge Template Version 5 Release 14 Page 208

8. Select the Generate Report combination and click the Sequential Combination behavior

icon ( ) to insert a Sequential Combination behavior. The SequentialCombination

behavior displays in the Behaviors tree.

9. Double-click this behavior to edit it. The Sequential Combination editor displays.

10. In the Name field of the opening dialog box, enter Retrieve Driver. Click OK to

validate.

11. Select the Retrieve Driver combination and click the Bind Object behavior icon ( ).

12. Double-click the BindObject node to edit it. The Bind Object editor displays.

❍ In the Name field, enter Bind Driver.

❍ In the Relative Name field, enter: ../../../../Driver_Part1. This path points

out the instance of product typed by Driver in the User Workbench.

❍ Click OK to validate.

13. Select the Generate Report combination and click the Bind Object behavior icon ( ).

14. Double-click the BindObject node to edit it. The Bind Object editor displays.

❍ In the Name field, enter Bind IndirectVision.

❍ In the Relative Name field, enter: ../../.. This path points out the product

typed by IndirectVision in the User Workbench

❍ Click OK to validate.

15. Select the Generate Report combination and click the ActiveXURL behavior icon

( ).

16. Double-click the URL node to edit it. The URL editor displays.
Business Process Knowledge Template Version 5 Release 14 Page 209

❍ In the URL field, enter Report.html.

❍ In the Variables tab, create the following variables using the Add button:

1. Name: Driver, Type: ExternalObject, Quality: Input

2. Name: Mirror, Type: ExternalObject, Quality: Input

3. Name: IndirectVision, Type: ExternalObject, Quality: Input

❍ Click OK to validate.

17. Right-click the Mirror attribute

and select the Mirror object -
>Link To command.

18. Click the output link of the

Bind Mirror behavior.

19. Right-click the IndirectVision

attribute and select the Mirror
object ->Link To command.
Business Process Knowledge Template Version 5 Release 14 Page 210

20. Select the output link of the

Bind IndirectVision behavior.

21. Save your file and proceed to the next task: Defining a "Generate Indirect Field of View

for a Planar Mirror" Combination on the Driver technological Object.

Business Process Knowledge Template Version 5 Release 14 Page 211

Defining a "Generate Indirect Field of View for a

Planar Mirror" Combination on the Driver Object

In this topic, the expert user defines a combination that will generate the driver's indirect field
of view for a Planar mirror.

1. Expand the Generate Indirect Field of View for Planar Mirror combination. The following

graphic displays:

Some behaviors are already

created in this combination:

❍ The Define Part and Imports

creation combinations.

❍ The Load document,

BindPowerCopy, and

PowerCopySpecification

behaviors.

❍ The CreateNewFrom,

BindObject, and

InsertComponents

behaviors.

❍ A VBScript behavior.

2. Expand the Imports Creation combination.

3. Click the Imports creation combination and click the On Cancel behavior icon ( ).
Business Process Knowledge Template Version 5 Release 14 Page 212

4. Right-click the On Cancel behavior, select the On Cancel object->Reorder command

and click the Imports creation combination. The On Cancel behavior is now located

below its father.

5. Double-click the On Cancel node to edit it. The On Cancel editor displays. As you can

see the Children Objects and the Child Object to survey lists are empty.

❍ Click the Father object to survey field, and select the Imports creation

combination. The Children Objects now display the behaviors located below

Imports creation. A Cancel event can be tracked on these behaviors.

❍ Select the Bind Sketch Mirror behavior and click the right arrow. Bind Sketch

Mirror now displays in the Child Object to survey list. The On Cancel behavior

will react if this behavior is not executed properly.

❍ Click OK to validate.

6. Click the On Cancel behavior and click the Information behavior icon ( ).

7. Double-click the Information node. The Information editor displays.

8. In the Message field, enter the following string: "Sketch_Mirror and Mirror_Plane

must be published by the Mirror: the required publications are Sketch_Mirror

and Mirror_Plane ". This message will display if the Bind Sketch Mirror behavior is not

executed correctly.

9. Save your file and proceed to the next task: Defining a "Check Driver Position" Behavior

on the Driver technological Type.

Business Process Knowledge Template Version 5 Release 14 Page 213

Defining a "Check Driver Position" Behavior on

the Driver Object

In this topic, the expert user defines the passenger position. He creates a check that will be
updated whenever the behavior operates. As the behavior operates in Auto update mode, the
check will operate each time an input is modified.

1. Select the Driver technological object in the Behaviors tree and click the Knowledge

Relations behavior icon ( ). KnowledgeRelations displays in the Behaviors tree.

2. Double-click the KnowledgeRelations node. The Knowledge Relations editor displays.

❍
In the Name field, enter Check Driver Position

❍
Select Auto in the Update scrolling list.

❍
Click the Attributes tab and click the Add button to create the following

attributes:

1. Name: AnkleAngle, Type: Angle, Value: 0deg

2. Name: KneeAngle, Type: Angle, Value: 0deg

3. Name: HipAngle, Type: Angle, Value: 0deg

4. Name: HeelHip, Type: length, Value: 0mm

Business Process Knowledge Template Version 5 Release 14 Page 214

Click the Content tab and click the Check icon ( ) to create 4 checks.

First check Name: AnkleCheck

Type of Check: Warning

Check Body: AnkleAngle > 98 deg

Second check Name: KneeCheck

Type of Check: Warning

Check Body: KneeAngle > 45 deg

Third check Name: HipAngle

Type of Check: Warning

Check Body: HipAngle < 45 deg

Fourth check Name: HeelHipCheck

Type of Check: Warning

Check Body: HeelHip < 750 mm

❍
Click OK to validate. The 4 checks are created. Click OK to exit the editor.

3. Expand the Check Driver Position node and its Variables node.

4. Expand the Attributes node located below Driver.

5. Right-click the AnkleAngle attribute below the Check driver position behavior, select the

AnkleAngle object->Link To command, and click the Driver AnkleAngle attribute.

6. Right-click the KneeAngle attribute below the Check driver position behavior, select the

KneeAngle object->Link To command, and click the Driver KneeAngle attribute.

7. Right-click the HipAngle attribute below the Check driver position behavior, select the

HipAngle object->Link To command, and click the Driver HipAngle attribute.

Business Process Knowledge Template Version 5 Release 14 Page 215

8. Save your work in the directory corresponding to the CATGraphicPath environment

variable.

9. Close the file.

You are now finished with the definition of the CATfct file. You are now going to use the
technological objects and the behaviors. Proceed to the next step: Generating the User
Workbench.
Business Process Knowledge Template Version 5 Release 14 Page 216

Generating the User Workbench

In this last topic of the scenario, the expert user generates the end-user workbench. For the
workbench to be correctly generated, see Before you start and check that the files provided are
located in the appropriate directories.

1. Open the IndirectVisionStep03.CATfct located in the directory corresponding to the

CATGraphicPath environment variable.

2. Click the Generate Applicative Workbench icon ( ). The Applicative Workbench

Generation window displays.

3. In the Workbench Name field,

enter RearViewMirror.

4. In the Workbench Type scrolling

list, select Product.

5. Click OK to validate. A new user workbench has been generated (see picture below.)

6. To use the generated workbench, proceed to the End-User Use cases:

● Designing the External Mirror

● Computing the Optimal Mirror

Business Process Knowledge Template Version 5 Release 14 Page 217

Designing the External Mirror

In this scenario, the user instantiates the vehicle, the driver, the mirror and the target, and
checks the resulting field of view. This scenario is divided into the following steps:

● Starting the Rear View Mirror Workbench

● Defining the Type and Loading the Vehicle

● Instantiating the Driver

● Instantiating the Mirror

● Editing the Mirror Attributes

● Instantiating the Target

● Editing the Target

● Instantiating the indirect Field of View

● Generating a Report

● Sketching a new Mirror

● Publishing Elements of the new Sketch

● Generating the indirect Field of View

Starting the Rear View Mirror Workbench

1. Open Catia and close the default empty product.

2. From the Start menu, select

RearViewMirror.

If this workbench is not available, contact your expert user for him to copy the files
provided in the Before you start topic into the appropriate directories and to
generate the workbench enabling you to replay this scenario.
Business Process Knowledge Template Version 5 Release 14 Page 218

You are now in the user workbench. All the items defined in the .CATfct file now display in the
toolbar located in the right part of the screen. Note that the icons might be replaced with empty
check boxes if you did not associate icons with the types.

3. Select the root product in the specification tree, click the icon to initialize the
assembly context in the selected product (if need be) and click the root product again.

Defining the Type and Loading the Vehicle

4. Select the product and click the IndirectVision icon. The IndirectVision type is

associated with the root product.

5. Define the type and load the vehicle. To do so proceed as follows:

● Right-click the IndirectVision (Product1) object in the tree and select the
IndirectVision (Product1) object->Define vehicle data command. The File
Selection window displays.

● Select the Vehicle_Data.CATPart and click OK to validate. The vehicle is loaded. Its
type is "Vehicle".

Instantiating the Driver

Business Process Knowledge Template Version 5 Release 14 Page 219

6. Instantiate the driver. To do so proceed as follows:

● Right-click the IndirectVision (Product1) object in the tree and select the
IndirectVision (Product1) object->Define driver command. The Catalog browser
displays.

● In the catalog browser, select Driver-2D-95%-Male. The behavior instantiates the

selected driver. Click Yes in the Save As dialog box.

Note that if you do not have a e:\tmp file, you will need to edit the path in the
BktSaveLastPart.CATScript.

Instantiating the Mirror

7. Instantiate the mirror. To do so proceed as follows:

Business Process Knowledge Template Version 5 Release 14 Page 220

● Right-click the IndirectVision

(Product1) object in the tree

and select the IndirectVision

(Product1) object->Define

external mirror command.

● Click Yes in the Save As dialog

box.

A new empty part typed

ExternalMirror is inserted into

the product. (See picture

opposite.)

● Right-click ExternalMirror (Mirror_Part.1)and select the Mirror_Part.1 object->

Generate geometry command. The Mirror_Part has been created along with its

publications.

Editing the Mirror Attributes

8. Edit the mirror attributes. To do so, proceed as follows:

Business Process Knowledge Template Version 5 Release 14 Page 221

❍ Double-click ExternalMirror (Mirror_Part.1) in the specification tree.

❍ Double-click the VerticalAngle attribute. The Attribute dialog box displays.

❍ Set the value of the VerticalAngle to 18deg. Click OK to validate.

❍ Double-click the HorizontalAngle attribute. The Attribute dialog box displays.

❍ Set the value of the HorizontalAngle to -4.5deg. Click OK to validate.

❍ Double-click the Width attribute. The Attribute dialog box displays.

❍ Set the width value 40mm. Click OK twice to validate.

❍ Update the Mirror_Part.

❍ Expand the Mirror variables node and double-click the modified attributes to

check their values.

Instantiating the Target

9. Instantiate the target. To do so, proceed as follows:

❍ Right-click the IndirectVision (Product1) object in the tree and select the

IndirectVision (Product1) object->Define target command.

❍ In the Catalog browser, double-click Target and TargetTemplate. The target is

instantiated.
Business Process Knowledge Template Version 5 Release 14 Page 222

Editing the Target

10. Edit the target. To do so, proceed as follows:

❍ Expand Target_Part >

Geometrical Set.2 >

Target_Definition.1: As

you can see, Norm, a

published parameter of

the user feature, is

linked with the

legislation attribute of

Vision.

❍ Right-click IndirectVision

and select the

IndirectVision object >

Definition command.

❍ Set the Legislation

attribute US.
Business Process Knowledge Template Version 5 Release 14 Page 223

❍ Click OK to validate.

❍ Update Target_Part.

Repeat the steps above to match the EEC legislation.

Instantiating the indirect Field of View

11. Instantiate the indirect field of view for a classic mirror. To do so, proceed as follows:

❍ Right-click Driver

and select the

Driver object-

>Generate indirect

field of view for

classic mirror

command. The field

of view is generated.

(See picture

opposite.)

Generating a Report

12. Right-click IndirectVision and select the IndirectVision object->Generate Report

command: A html browser opens displaying the report.

Sketching a new Mirror

13. Sketch a new mirror. To do so, proceed as follows:

❍ Expand the Mirror_Part node.

Business Process Knowledge Template Version 5 Release 14 Page 224

❍ Select Mirror_Support located in the Results node below Mirror_Geometry,

and open the sketcher.

❍ Reframe on the external mirror and sketch a new mirror made of a rectangle.

The sketch we have created represents our new mirror. We now want to

generate the corresponding field of view. But to do that, we need to publish

some geometrical elements.

❍ Exit the Sketcher.

Publishing Elements of the new Sketch

14. Double-click Mirror_Part in the specification tree and select the Tools->Publication

command from the menu.

15. Select Mirror_Support and Sketch.1 and publish them as Mirror_Plane and

Sketch_Mirror.

16. Right-click Driver and select the Driver object->Generate indirect field of view for

planar mirror. The field of view is generated.

The parameters are published now.

Generating the indirect Field of View

17. Generate the indirect field of view. To do so, proceed as follows:

❍ Right-click Driver and select the Driver object->Control_Generate

indirect field of view for planar mirror command.

❍ Click Yes. The indirect field of view for the new mirror is generated.
Business Process Knowledge Template Version 5 Release 14 Page 225
Business Process Knowledge Template Version 5 Release 14 Page 226

Computing the Optimal Mirror

In this scenario, the user instantiates the vehicle, the driver, the target, and computes the
optimal mirror depending on his work context. This scenario is divided into the following steps:
● Starting the RearViewMirror Workbench

● Defining the Type and Loading the Vehicle

● Instantiating the Driver

● Instantiating the Target

● Changing the Legislation

● Checking the Driver Position

Starting the RearViewMirror Workbench

1. Open Catia and close the default empty product.

2. From the Start menu, select

RearViewMirror.

If this workbench is not available, contact your expert user for him to copy the files
provided in the Before you start topic into the appropriate directories and to
generate the workbench enabling you to replay this scenario.

You are now in the user workbench. All the items defined in the .CATfct file now display in the
toolbar located in the right part of the screen. Note that the icons might be replaced with empty
check boxes if you did not associate icons with the created behaviors when defining the .CATfct
file.

3. Select the root product in the specification tree, click the icon to initialize the
assembly context in the selected product (if need be) and click the root product again.

Defining the Type and Loading the Vehicle

4. Select the product and click on IndirectVision icon. The IndirectVision type is assigned
Business Process Knowledge Template Version 5 Release 14 Page 227

to the root product.

5. Define the type and load the vehicle. To do so proceed as follows:

❍ Right-click the IndirectVision (Product1) object in the tree and select the

IndirectVision (Product1) object->Define vehicle data command. The

file selection window displays.

❍ Select the Vehicle_Data.CATPart and click OK to validate. The vehicle is

loaded. Its type is "Vehicle".

Instantiating the Driver

6. Instantiate the driver. To do so proceed as follows:

● Right-click the IndirectVision (Product1) object in the tree and select the
IndirectVision (Product1) object->Define driver command. The Catalog browser
displays.

● In the catalog browser, select Driver-2D-95%-Male. The behavior instantiates the

selected driver. Click Yes in the Save As dialog box.
Business Process Knowledge Template Version 5 Release 14 Page 228

Note that if you do not have a e:\tmp file, you will need to edit the path in the
BktSaveLastPart.CATScript.

7. Check that the relations have been created at the root level between the driver

technological object and the driver part. To do so, expand the Relations node.

Instantiating the Target

8. Instantiate the target. To do so, proceed as follows:

❍ Right-click the IndirectVision (Product1) object in the tree and select the

IndirectVision (Product1) object->Define target command.

❍ In the Catalog browser, double-click Target and TargetTemplate. The target is

instantiated.

Click on Fit all In to see the target created (see picture below.)
Business Process Knowledge Template Version 5 Release 14 Page 229

Changing the Legislation

9. Expand the IndirectVision variables node, double-click the IndirectVision definition and

set the Legislation attribute to US.

10. Update the product.

11. Check that the whole product has been updated with the new value

Checking the Driver Position

12. Check the driver position. To do so, proceed as follows:

❍
Right-click Driver (Driver_Part.1) and select the Driver

(Driver_Part.1) object->Check driver position command. Two

warning boxes display pointing out the invalid attributes.

Business Process Knowledge Template Version 5 Release 14 Page 230

Optimal CATIA PLM Usability for Business

Process Knowledge Template

● *. CATfct files cannot be saved in ENOVIA LCA.

● In a user workbench context, the command enabling the user to set the context is not available (grayed
out.)
Business Process Knowledge Template Version 5 Release 14 Page 231

Reference Information
Essential reference information concerning the behaviors are available in this section.

Introducing the Structure Behaviors

Introducing the Infrastructure Behaviors
Introducing the Design Behaviors
Introducing the Event-based Behaviors
Business Process Knowledge Template Version 5 Release 14 Page 232

Introducing the Structure Behaviors

These 2 behaviors (Logical Combination and Sequential Combination) allow the expert user to automate a
process or part of a process. The user defines a combination of behaviors:

● Ordered in case of a Sequential Combination

● Not ordered in case of a Logical Combination

Logical Combination: Data Sheet

Sequential Combination: Data Sheet
Loop Behavior: Data Sheet
Generate Components Behavior: Data Sheet
Business Process Knowledge Template Version 5 Release 14 Page 233

Logical Combination: Data Sheet

Accessing
this This behavior can be accessed by clicking the Logical Combination icon ( ) in the Structure
behavior toolbar.

Describing This behavior is a combination of various behaviors enabling the user to work with the
this aggregation concept.
behavior

More The logical combination is designed to execute the behaviors that are
information ready for execution at a given time. When executing a logical
combination of behaviors, all you can know is if the combination can
operate the behaviors it contains. The order in which the behaviors
will be launched is not guaranteed. One behavior can be launched
while another one is operating.
For the behaviors to be launched in a defined order in a logical
combination, check the focus radio buttons in the behaviors properties
tab.
The behaviors belonging to a Logical Combination might be launched
simultaneously.
If the
behaviors
are
independent,
and one of
the
behaviors is
not solved,
the
combination
will be
shown as
solved.

Using this See Creating a Logical Combination of Behaviors.

behavior
Business Process Knowledge Template Version 5 Release 14 Page 234

Sequential Combination Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Sequential Combination icon ( ) in the Structure
behavior toolbar.

Describing This behavior is a combination of various behaviors. In a sequential combination, the behaviors
this execute in a pre-defined order. The creation order of the behaviors will be their execution order.
behavior

More In a sequential combination of behaviors, all the behaviors will be

information executed. The behaviors belonging to a Sequential Combination are
launched one after the other in a pre-defined order. The second
behavior is launched once the execution of the first behavior is over
and so on. The final status of a combination depends on the status of
the behaviors it contains. If one of them failed, the combination is
shown as failed.
If all the
behaviors
can be
executed
correctly,
the
combination
will be
shown as
solved.

In case of
error, the
combination
will not
execute to
the end and
will be
shown as
failed.

Using this See Creating a Sequential Combination of Behaviors and Using a Combination to Instantiate a User
behavior Feature.
Business Process Knowledge Template Version 5 Release 14 Page 235

Loop Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Loop Behavior icon ( ) in the Structure
behavior toolbar.

Describing This behavior is designed to enable the user to define sequences of behaviors that will be
this executed a given number of times (For i=1 to N).
behavior
Note that:

● The number of iterations can be driven by rules and formulas. Therefore, the loop will
operate its sub-behaviors a given number of times, depending on the context, if some
conditions are met.
● The objects generated by the behaviors at each iteration can be stored in the output list of
the loop with the AddToList behavior. It is a way for the expert user to store and retrieve
the results of the previous iterations.
● Loops of loops cannot be created: A loop behavior cannot be instantiated under an existing
loop. Other limitations: The behaviors contained in the loop cannot be structured using the
Logical and Sequential combinations.
● The behaviors located below the loop cannot be in auto update mode. Only Driven and
Single update modes are available in their properties pages.
● Loops inputs can be linked except the iteration.
● It is recommended to use the Loop behavior in combination with the AddToList behavior:
The outputs of the loop will be stored in the AddToList and the list will be valuated.

More Note that:

Information ● The NumberOfIterations variable matches the number
of iterations defined by the user.
● The AlwaysRegenerate variable means that if the loop
already executed once, the items that it created will be
removed and recreated at the next operation.
● The list variable can the output of the behavior.
● The Iteration is an internal parameter that will be
incremented at each iteration during the execution of
the loop. It cannot be driven by the expert but can be
used as the input of a formula, check, link... It is the
current iteration number.
Business Process Knowledge Template Version 5 Release 14 Page 236

Using this
Behavior
Interface

Name Name attributed to the behavior.

Comment Comment attributed to the behavior.

Loop definition Number of iterations Enter the number of iterations. This number
matches the number of times the loop and its
behaviors will be executed.

Current iteration Internal variable. Indicates the number of

iterations performed.

Create new data at each New data are created at each execution of the
execution behavior.

Using this
See Using the Loop Behavior.
behavior
Business Process Knowledge Template Version 5 Release 14 Page 237

Generate Components Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Generate Components Behavior icon ( ) in the
behavior Structure toolbar.

Describing This behavior enables to :

this ● Generate components,
behavior
● Create different instances of an object,
● Assign a type to the created instances,
● Insert the instances of the types into the components list located at the type level.

Note that:

● A Generate Components behavior should contain a "Add Item behavior" to valuate its
output list at each iteration or it should contain a loop.
● At each iteration, the behaviors located below the Generate Components behavior will be
automatically executed.
● It is possible to control the execution of the behaviors located below the Generate
Components behavior. To do so, select the Single Update mode in the Properties tab: Those
behaviors will be executed only once.
● A Generate Components behavior cannot contain other Generate Components behaviors.
● The behaviors located below the Generate Components behavior cannot be in auto update
mode. Only Driven and Single update modes are available in their properties pages.

Methodology To use this behavior, proceed as follows:

1. Create the Components list.

2. Create the Generate Components behavior.

3. Link the Generate Components and the List

using the Generate Components interface.

4. Instantiate the behaviors that create parts or

other items.

5. Create a AddToList behavior below the

Generate Components behavior and link the

Generate Components and the AddToList

Business Process Knowledge Template Version 5 Release 14 Page 238

behavior using the AddToList interface to

valuate the output list of the Generate

Components behavior.

More
Information ● The list is the temporary output of the
behavior: At each iteration, an item
must be added to the list. This object
will be typed depending on the
component type. To do so, use an Add
To list. This item will be typed
depending on the type created when
creating the components. The final
operational output of the behavior is the
component list on the TO.

● The NumberOfIterations variable

matches the number of iterations
defined by the user.
● The AlwaysRegenerate variable means
that if the generate components
behavior already executed entirely once,
the items that it created will be removed
and recreated at the next iteration.

For each iteration, the Generate Components

behavior is executed after its sub-components.
● If the list size matches the number of
iterations, the last item is typed. In this case,
the Legs_List[i] is valuated with the last item
of the Generate Components (Generate legs)
behavior. If the item cannot be typed, an
error panel displays.
● If the list size does not match the number of
iterations, an error panel displays.
Business Process Knowledge Template Version 5 Release 14 Page 239

Typing Rules when using the Generate Components behavior in the user workbench:

Given a .CATFct document containing 2 technological objects: Table and Legs.

● To define an object as a component of a

technological object, it must be
aggregated under this object in CATIA.
So, it is possible to put Prod2 in the
legs list since it is a sub-product of
Prod1. An error panel displays when the
user tries to add Prod3.
● The object in the component list must
be of the type defined in the .CATFct or
deriving from it.

● It is only possible to type the following objects: Products, Parts, Geometrical sets, and Part
Bodies.
Business Process Knowledge Template Version 5 Release 14 Page 240

Using this
Behavior
Interface

Name Name attributed to the behavior.

Comment Comment attributed to the behavior.

Target component list Component list Select a component list of the

name technological object.

List type This field is valuated when selecting the

component list. The name of the sub
type of the component list can be typed,
but an error is raised if a different type
is entered.

Number of components Number of This field is valuated when selecting the

components component list. Enter the number of
components. This number matches the
target size of the list. Note that it can be
inferior to the list but it cannot be
superior.

Current iteration Internal variable. Indicates the number

of iterations performed.

Create new data at See More information.

each execution

Using this See Designing a Table using the Generate Component Behavior.
behavior
Business Process Knowledge Template Version 5 Release 14 Page 241

Introducing the Infrastructure Behaviors

Implementation Behaviors ● VBScript Behavior

● Command Behavior

● URL Behavior

● ActiveX URL Behavior

● System Behavior

Input/Output Based Behaviors ● Link Parameters Behavior

● Synchronize Parameters Behavior

Bind Behaviors ● Bind Object Behavior

● Bind Parameter Behavior

● Bind Reference Behavior

● Bind Instance Behavior

● Bind Type Behavior

List Behaviors ● Add item behavior

● Remove item behavior

● Get item behavior

● Propagate Execution Behavior

● Information Behavior

● Add Type Behavior

Business Process Knowledge Template Version 5 Release 14 Page 242

Implementation Behaviors

This set of behaviors enables the expert user to reuse existing components like VB Scripts, CAA commands,
URLs, and executable files.

Please find below the list of the behaviors belonging to the Implementation behaviors.

● VBScript Behavior

● Command Behavior

● URL Behavior

● ActiveX URL Behavior

● System Behavior
Business Process Knowledge Template Version 5 Release 14 Page 243

VBScript Behavior: Data Sheet

Accessing this
behavior This behavior can be accessed by clicking the VBScript Behavior icon ( ) in the
Implementation toolbar.

Describing this This behavior is designed to run a VBScript or a CATvbs file.

behavior

MORE Note that the input of this behavior should be a CATScript file. For this behavior to be
INFORMATION correctly executed, use the syntax indicated in this file: BktwritingaVB.CATScript.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Macro VB Name
Use the button to select a .CATScript file.
Business Process Knowledge Template Version 5 Release 14 Page 244

For portable applications, note that the selected file can be located in the
directory corresponding to the CATStartupPath environment variable. Enter the
VBScript file name only.

Using this The expert user developed a macro that he wants to reuse. To get an example, see Using
behavior the On xxx Behaviors.
Business Process Knowledge Template Version 5 Release 14 Page 245

Command Behavior: Data Sheet

Accessing this
behavior This behavior can be accessed by clicking the Command Behavior icon ( ) in the
Implementation toolbar.

Describing this This behavior is designed to specify the execution parameters of a CAA Command. When
behavior working with CAA, a developer can create a new command. This behavior enables the
expert user to launch this command by specifying its name and the module where the
command is defined.
Note that the input of this behavior should be a command class and the module in which the
command was declared.

MORE The Focus option is now available for the Command behavior. It is checked by default but
INFORMATION the user will have to check the Focus radio button when defining undefined commands.
If the Focus option is unchecked, the command behavior will be launched asynchronously (it
will be executed later).
In case of a sequential combination, it is recommended to check the Focus radio button of
the Command behavior and the one of the behavior located below the Command behavior
(if both behaviors are linked). If not, the second behavior will not be executed.
● In case of an exclusive command, the focus option must be set.

● In case of a shared command located in a sequential combination, it is recommended to

set the focus. If the user decides that the sequencing is not important, he should insert
the Command behavior into a Logical combination.

● In case of an undefined command, it is recommended not to check the Focus option. If

the user wants to put the focus on the behavior, he should insert it into a Logical
combination. (Do not insert it into a sequence, it would get stuck).

To know more about undefined, exclusive and shared commands, see the CAA
documentation.
Business Process Knowledge Template Version 5 Release 14 Page 246

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Execute Command Name: Enter the name of the command class.

Module Name: Enter the name of the module in which the command
was declared.

Note that the module should be accessed through the "?" code/bin path.
Business Process Knowledge Template Version 5 Release 14 Page 247

URL Behavior: Data Sheet

Accessing this
behavior This behavior can be accessed by clicking the URL Behavior icon ( ) in the
Implementation toolbar.

Describing this This behavior is designed to open a HTML page.

behavior

MORE Note that the input of this behavior should be a html file located in the directory
INFORMATION corresponding to the CATStartupPath environment variable.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Web URL: Enter the name of the HTML file that you want to use

For portable applications, note that the HTML file can be located in the directory
corresponding to the CATStartupPath environment variable. Enter the HTML file
name only.
Business Process Knowledge Template Version 5 Release 14 Page 248

Using this A document is associated with the process that is being developed by the expert user. The
behavior expert user wants the end-user to access this documentation.
Business Process Knowledge Template Version 5 Release 14 Page 249

ActiveX URL Behavior: Data Sheet

Accessing this
behavior This behavior can be accessed by clicking the ActiveX URL Behavior icon ( ) in the
Implementation toolbar.

Describing this This behavior is designed to open a HTML page that can interoperate with CATIA V5 using
behavior VB Script.

MORE Note that the input of this behavior should be a html file located in the directory
INFORMATION corresponding to the CATStartupPath environment variable.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Web URL: Name of the HTML page that you want to use.
Business Process Knowledge Template Version 5 Release 14 Page 250

For portable applications, note that the HTML file must be located in the directory
corresponding to the CATStartupPath environment variable. Enter the HTML file
name only.

Using this The expert user wants to use a HTML page to generate a report. Click here to see an
behavior example.
Business Process Knowledge Template Version 5 Release 14 Page 251

System Behavior: Data Sheet

Accessing this
behavior This behavior can be accessed by clicking the System Behavior icon ( ) in the
Implementation toolbar.

Describing this This behavior is designed to launch an executable file (.exe) or a shell (.sh). This behavior
behavior launches the process synchronously.

MORE Note that the output feature of this behavior is an output.

INFORMATION

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 252

Process Process: Indicate the process path or the process name if the process
is recognized by the operating system (like notepad for
example) or if it is in the runtime view.

Source File: Enter the name of the file that will be used to generate the
input data for the process.
If no path is indicated, the CATTemp variable will indicate
the directory to use.
If no file is indicated, a temporary file name will be allocated
by the behavior.

Result File: Enter the name of the file that will be used to handle the
result of the process.

The process in invoked by providing:

● The input file which has gathered the behavior input.

● The output file that will be processed by the behavior to fill in the output after
the execution of the process.

Note that for portable applications, the process should be accessible in the run
time view.

Using this The user wants to use an external analysis application.

behavior
Business Process Knowledge Template Version 5 Release 14 Page 253

IO Based Behaviors

This set of behaviors enables the expert user to link or to synchronize parameters.

Given 2 variables A and B, the expert user is provided with 2 methods to bind them. He can

● Link the 2 variables: In this case, if B and A are linked, they share the same value. B takes the value of A. If
the value of A changes, the value of B will change immediately.

● Synchronize the 2 variables: In this case, if B is linked with A, B will take the value of A when the behavior
is executed.

Link Parameters Behavior

Synchronize Parameters Behavior
Business Process Knowledge Template Version 5 Release 14 Page 254

Link Parameters Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Link Parameters Behavior icon ( ) in the IO
behavior Based toolbar.

Describing This behavior is designed to link two parameters of the extended object. Given A and B, 2
this variables of same type (object or parameter) that can result from a Bind Object or Parameter.
behavior If you link A and B, the value of B will be identical to the value of A.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Link From Parameter: First parameter to be linked (selected in the

Behaviors tree.)

To Parameter: Second parameter to be linked (selected in the

Behaviors tree.)
Business Process Knowledge Template Version 5 Release 14 Page 255

Synchronize Parameters Behavior: Data Sheet

Accessing This behavior can be accessed by clicking the Synchronize Parameters Behavior icon ( ) in
this the IO Based toolbar.
behavior

Describing This behavior is designed to synchronize two parameters of the extended object. When the
this behavior is executed, both parameters have the same value: Given A and B two parameters: If
behavior A=5 and B=2, B=5 only after the behavior is executed.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Link From Parameter: First behavior (selected in the Behaviors tree.)

To Parameter: Second behavior to be synchronized (selected in the

Behaviors tree.)
Business Process Knowledge Template Version 5 Release 14 Page 256

Bind Behaviors

This set of behaviors enables the expert user to access resources not yet available at the definition stage. To get
more information about the Bind mechanism, see To know more about the Bind Mechanism...

Please find below the list of the behaviors belonging to the Bind behaviors.

● Bind Object Behavior

● Bind Parameter Behavior

● Bind Reference Behavior

● Bind Instance Behavior

● Bind Type Behavior

Business Process Knowledge Template Version 5 Release 14 Page 257

Bind Object Behavior: Data Sheet

Accessing
This behavior can be accessed by clicking the Bind Object Behavior icon ( ) in the Bind Based
this
Behaviors toolbar.
behavior

Describing This behavior searches for the object whose name or path is specified. To get more information
this about the Bind mechanism, see To know more about the Bind Mechanism...
behavior

More Note that the output feature of this behavior is a Link.

information

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 258

Bind Reference: In the Behaviors tree, select:

● An object or a behavior variable that will
contain a V5 item at run time.

● A behavior.

The search will start from the object indicated in

this field. If nothing is indicated, the search will
start from this behavior.

Relative Name: Enter the object name that you are looking for or
an access path (using the ../.. syntax).

Using this The expert user wants to find the root product of the document.
behavior
Business Process Knowledge Template Version 5 Release 14 Page 259

Bind Reference Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Bind Reference Behavior icon ( ) in the Bind
behavior Based Behaviors toolbar.

Describing This behavior searches for the reference whose name or path is specified. To get more
this information about the Bind mechanism, see To know more about the Bind Mechanism...
behavior

More Note that the output feature of this behavior is a Link.

information

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 260

Bind Reference: In the Behaviors tree, select:

● An object or a behavior variable that will contain a
V5 item at run time.

● A behavior.

The search will start from the object indicated in this

field. If nothing is indicated, the search will start from
this behavior.

Using this The expert user wants to find the reference associated with a product instance.
behavior
Business Process Knowledge Template Version 5 Release 14 Page 261

Bind Parameter Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Bind Parameter Behavior icon ( ) in the Bind
behavior Based Behaviors toolbar.

Describing This behavior searches for the parameter whose name or path is specified. To get more
this information about the Bind mechanism, see To know more about the Bind Mechanism...
behavior

More Note that the output feature of this behavior is a Link.

information

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 262

Bind Reference: In the Behaviors tree, select:

● An object or a behavior variable that will contain a V5
item at run time.

● A behavior.

The search will start from the object indicated in this

field. If nothing is indicated, the search will start from this
behavior.

Relative Name: Enter the object name that you are looking for or an
access path (using the ../.. syntax).

Note: To know the parameter naming convention, use the

Definition panel of this object: It lists the possible names.

Using this The expert user wants this behavior to find the parameter related to the height of a pad.
behavior
Business Process Knowledge Template Version 5 Release 14 Page 263

Bind Instance Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Bind Instance Behavior icon ( ) in the Bind
behavior Based Behaviors toolbar.

Describing This behavior searches for the instance whose name or path is specified. To get more
this information about the Bind mechanism, see To know more about the Bind Mechanism...
behavior

More Note that the output feature of this behavior is a Link.

information

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 264

Comment: Comment attributed to the behavior.

Bind Reference: In the Behaviors tree, select:

● An object or a behavior variable that will contain a
V5 item at run time.

● A behavior.

The search will start from the object indicated in this

field. If nothing is indicated, the search will start from
this behavior.

Relative Name Enter the object name that you are looking for or an
access path (using the ../.. syntax).

Note that if more than one instance have the same name as the one specified, the
instance returned will be the first encountered.

Using this Given a reference product, Vehicle, the expert user wants to find the instance of Vehicle in the
behavior root product.
Business Process Knowledge Template Version 5 Release 14 Page 265

Bind Type Behavior: Data Sheet

Accessing
This behavior can be accessed by clicking the Bind Type behavior icon ( ) in the Type Tools
this
toolbar.
behavior

Describing This behavior searches for an object whose type name or path is specified.
this
behavior

More Note that the output feature of this behavior is a Link.

information

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 266

Bind Reference: In the Behaviors tree, select:

● An object or a behavior variable that will contain a V5
item at run time.

● A behavior.

The search will start from the object indicated in this field.
If nothing is indicated, the search will start from this
behavior.

Relative Name: Enter the object name that you are looking for or an
access path (using the ../.. syntax). The last name of the
path is a type name.
 Business Process Knowledge Template Version 5 Release 14 Page 267

To know more about the Bind Mechanism...

Definition

The Bind mechanism is a generic mechanism that enables the expert user to navigate through the V5 spec tree and
specify how to find an object that does not exist when defining the behavior. Binds can be concatenated.

Example: The expert user creates an application that will enable the end-user
to instantiate passengers into a vehicle. To do so, the expert user creates a
FilterCatalog behavior for the end-user to select a manikin in a catalog, he
then creates a LoadDocument behavior, for the end-user to load the manikin, a
BindObject and an InsertComponents Behavior.

Different Types of Binds

The Business Process Knowledge Template applications is provided with 2 different types of binds: The Infrastructure
and the Design binds.

Infrastructure Binds Design Binds

V5 objects V5 mechanical features

● Bind Object Behavior: V5 objects Given a document, or a feature:

● Bind Part Behavior: A part
● Bind Parameter Behavior: Parameters
● Bind User Feature Behavior: A User Feature
● Bind Reference Behavior: An object reference
● Bind PowerCopy Behavior: A PowerCopy
● Bind Instance Behavior: An object instance
● Bind Publication Behavior: A publication
● Bind Type: A type
● Bind Product Instance Behavior: A product instance
 Business Process Knowledge Template Version 5 Release 14 Page 268
Bind Interfaces

To define a bind, the expert user uses the bind interface. There are 2 different types of interfaces depending on the Bind
type. The Structure behaviors are provided with the following interface:

Reference: Select in the Behaviors tree an output containing an object (part, V5 items), or a structure behavior. If
nothing is indicated, the search will start from this behavior.

Relative The Relative name field can contain an object name or an access path. The Relative Name may be
Name: indicated by:

● A Name: If the expert user wants to indicate

a name, he indicates the name of a behavior
in the tree or in the geometry. In the example
opposite the user entered ExternalMirror.
(Click the graphic opposite to enlarge it.)

● A path: The expert user can also indicate a

path. In this case he uses the ".." syntax, ".."
that enables him to go up one level in the
Behaviors tree ("../.." two levels, etc) to
access the extended object. (Click the graphic
opposite to enlarge it.)

● It is also possible to indicate a path and a

name if the object is one of the type children:
../../../../ExternalMirror for example.

The Design behaviors are provided with one of the following interfaces:
Business Process Knowledge Template Version 5 Release 14 Page 269

This interface is used for the Bind Part behavior. As

there is only one Part feature in a CATPart document,
it is not necessary to specify the name of this part.

From Object The expert user selects a feature or a document in the

Behaviors tree.

User Feature Name and PowerCopy Name The expert user indicates the UDF or the PowerCopy
name. If no name is specified in this field and if the
document contains several PowerCopies or User
Features, the behavior will return the first PowerCopy
or the first UserFeature name it can find.
Business Process Knowledge Template Version 5 Release 14 Page 270

List Behaviors

This set of behaviors enables the expert user to handle lists.

Add item Behavior: Data Sheet Behaviors

Remove item Behavior: Data Sheet Behaviors
Get item Behavior: Data Sheet Behaviors
Business Process Knowledge Template Version 5 Release 14 Page 271

Add item Behavior: Data Sheet Behavior

Accessing
this This behavior can be accessed by clicking the Add item Behavior icon ( ) in the List
behavior Management toolbar.

Describing This behavior enables to add an object whose type is identical to the type of the objects
this contained in the list (if any).
behavior

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.
List List: Select the list feature to which the object will be added.

Object to add Object: Select the object that will be added to the list.
At position Enter the position of the item that will be added.
Options Allow If checked, enables the user to insert the same object twice
duplicate into the list.
elements:
Business Process Knowledge Template Version 5 Release 14 Page 272

Using this
See Designing a Table Using the Generate Component Behavior.
behavior
Business Process Knowledge Template Version 5 Release 14 Page 273

Remove item Behavior: Data Sheet Behavior

Accessing
this This behavior can be accessed by clicking the Remove item Behavior icon ( ) in the List
behavior Management toolbar.

Describing This behavior enables to remove an object contained in the list at a given position. It is also
this possible to remove all items of the list.
behavior

More Note that the objects to be removed from the list given in the
information internal attributes list can be defined in 3 ways:
● By valuating the position of the object to remove (attribute index)
● By valuating the ListItem with the object to remove.
● By selecting the "Remove All" check button: The list will be
cleared.

When one of these options is selected, the others are disabled.

Using this
Behavior
Interface
Business Process Knowledge Template Version 5 Release 14 Page 274

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.
List List: Select the list feature of the Generate Components
behavior.
Object to remove Object: Select the object that will be removed from the list.
At position Indicate the position of the item to be removed.
Remove options Remove all If checked, enables the user to remove the items
contained in the list.
Business Process Knowledge Template Version 5 Release 14 Page 275

Get item Behavior: Data Sheet Behavior

Accessing
this This behavior can be accessed by clicking the Get item Behavior icon ( ) in the List
behavior Management toolbar.

Describing This behavior enables to retrieve one object from the list.
this
behavior

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.
List List: Select the list from which the item will be retrieved.
At position Enter the position of the item to be retrieved.
Business Process Knowledge Template Version 5 Release 14 Page 276

Propagate Execution Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Propagate Execution Behavior icon ( ).
behavior

Describing This behavior is designed to trigger the execution of a given object: If the object is a V5
this object, the update will be performed. If it is a behavior, the behavior will be executed.
behavior

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment associated with the behavior.

Operate Target: Select the object that you want to be executed in the
Behaviors tree.

Action Delayed: ● If unchecked, the behavior executes immediately.

● If checked, the selected behavior will not execute

before the current behavior executes to the end.
Business Process Knowledge Template Version 5 Release 14 Page 277

Using this See Using the Propagate Execution behavior.

behavior
Business Process Knowledge Template Version 5 Release 14 Page 278

Information Behavior: Data Sheet

Accessing
this
This behavior can be accessed by clicking the Information icon ( ).
behavior

Describing This behavior is designed to specify a message that will display when it executes. It is
this recommended to use it to display an error message for example.
behavior

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Error Message: String corresponding to the message that will be displayed.

Using this When executing a behavior, the expert user finds out that an object was not published. The
behavior expert user uses this behavior to display a warning message for the end-user to fix the
problem.
Business Process Knowledge Template Version 5 Release 14 Page 279

Add Type Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Add Type Behavior icon ( ).
behavior

Describing This behavior is designed to associate technology to an object. The selected type is to be
this specified, as well as the .CATfct file in which the type is defined and the object to extend.
behavior

More Note that the output feature of this behavior is the object being
information typed.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 280

Comment: Comment attributed to the behavior.

Type Name: Enter the name of the technological object.

Catalog Name: Enter the name of the CATfct file containing this type.

Object to Type: Select the object to type in the Classes View or in the Behaviors tab.

Using this The expert user created a product and wants to associate the Vehicle type with this product.
behavior
Business Process Knowledge Template Version 5 Release 14 Page 281

Introducing the Design Behaviors

Reuse Behaviors ● Instantiate Template Behavior

● Create External Reference Behavior

● Copy/Paste Behavior

● KWScript Behavior

Document Behaviors ● Load Document Behavior

● Create New From Template Behavior

● Filter Catalog Behavior

Bind Behaviors ● Bind Part Behavior

● Bind User Feature Behavior

● Bind Power Copy Behavior

● Bind Publication Behavior

● Bind Product Instance Behavior

● Display in Window Behavior

● Insert Components Behavior

● Knowledge Relations Behavior

● Knowledge Certify Behavior

Business Process Knowledge Template Version 5 Release 14 Page 282

Reuse Behaviors

This set of behaviors is designed to enable the user to use existing features like PowerCopies, UDFs, KWScripts,
to copy and paste features and to import features.

Please find below the list of the behaviors belonging to the Reuse behaviors.

● Instantiate Template Behavior

● Create External Reference Behavior

● Copy/Paste Behavior

● KWScript Behavior
Business Process Knowledge Template Version 5 Release 14 Page 283

Instantiate Template Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Instantiate Template Behavior icon ( ) in the
behavior Reuse toolbar.

Describing This behavior enables to specify the instantiation of a PowerCopy, a UDF or a Document
this Template. The expert user specifies where the template will be instantiated. In case of a
behavior PowerCopy and a UDF, it is a part or a body; otherwise it is a product.

When defining this behavior, the expert user creates a few inputs that will be valuating the
inputs of the template during operation. With the Instantiate Template behavior, the expert
user has two ways of instantiating the template feature into the user workbench :
● With the standard instantiation panel, so that the user will valuate the inputs when
operating the behavior, through selection or through the Use Identical name functionality.

● Without the standard instantiation panel. To do so, the expert user will have to pre-valuate
the inputs of the template feature on the behavior.

For the indirect instantiation, three different valuation modes enable the expert user to pre-
valuate the inputs of the template feature :

● Use Identical Name: Is similar to the Use Identical Name option that the user can use in
the standard instantiation panel.

● Inputs Initialization: Enables to valuate the inputs of the template feature by adding
inputs to the behavior. To do so, use the Add button in the Defined inputs and parameters
field. This option is to be selected for parameters or geometric features only.

1. Add a variable whose name is identical to the UDF input to valuate.

1. Valuate this variable (link for example).

This option enables the user to automate the instantiation for if all inputs are
declared and initialized on the behavior, they will be valuated in the template and
the standard instantiation panel will not display.

● Best Strategy: Uses the Use Identical Name option if need be and valuates the remaining
inputs by using the specifications indicated by the expert user:
Note that Document templates can now be instantiated using BKT.

To know more about UDFs, PowerCopies and Document Templates, see the Product Knowledge
Template User's Guide and the Part Design User's Guide.
Business Process Knowledge Template Version 5 Release 14 Page 284

More Note that the output feature of this behavior is a User Feature
information feature, the instantiated product of the document template, or
<unset> if the input was a powercopy.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 285

Definition Template feature: Indicate the name of the template feature

valuated by:
● The output of a catalog

● The output of a Bind PowerCopy/Bind

User Feature

Instantiation context Destination: Indicate the instantiation destination. The

destination can be a Part, a PartBody, a
Geometrical Set or a Product, depending on
the type of the template feature.

Valuation Mode: See above.

Defined inputs and Use this field to add, modify or delete parameters. To know
parameters: more, see the FilterCatalog Behavior.

More Info To get an example, see Creating a User Workbench: Defining the "Define Driver" Combination
on the IndirectVision Object and Using the Instantiate Template behavior.
Business Process Knowledge Template Version 5 Release 14 Page 286

Create External Reference Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the External Reference Behavior icon ( ) in the
behavior Reuse toolbar.

Describing This behavior is designed to create an external reference in a part by specifying a geometrical
this feature. To know more about the creation of external references in Show mode, see the Part
behavior Design User's Guide.

More Note that the output feature of this behavior is an Import

information feature.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 287

Comment: Comment attributed to the behavior.

Definition Feature to Indicate the feature to be imported. This feature can

import: only be the result (output) of a bind.

Import context Destination: Indicate the destination (a Part) of the import operation.

Show Mode: See the Part Design User's Guide.

Business Process Knowledge Template Version 5 Release 14 Page 288

Copy/Paste Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Copy/Paste Behavior icon ( ) in the Reuse
behavior toolbar.

Describing This behavior is designed to copy a feature and to paste it into a document. To know more
this about the Copy/Paste commands, see the Part Design User's Guide and the Shape Design &
behavior Styling manuals.

More Note that the output feature of this behavior is a

information PastedFeature.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 289

Comment: Comment attributed to the behavior.

Copy Feature to copy: Indicate the name of the geometric feature to

copy by selecting it in the Behaviors tree.

Paste Destination: Indicate the destination of the instantiation. It

can be an object or a body.
Business Process Knowledge Template Version 5 Release 14 Page 290

KWScript Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the KWScript Behavior icon ( ) in the Reuse
behavior toolbar.

Describing This behavior enables the user to specify how to execute a Generative Script. To know more
this about Generative Scripts, see the Product Knowledge Template documentation.
behavior

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

File path: Enter the name of the CATGScript to launch.

Business Process Knowledge Template Version 5 Release 14 Page 291

Note that the KWScript capabilities require the Product Knowledge Template license.
Business Process Knowledge Template Version 5 Release 14 Page 292

Document Behaviors

This set of behaviors is designed to enable the user to reuse existing documents.

Please find below the list of the behaviors belonging to the Document behaviors.

● Load Document Behavior

● Create New From Behavior

● Filter Catalog Behavior

Business Process Knowledge Template Version 5 Release 14 Page 293

Load Document Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Load icon ( ) in the Doc Based Behaviors
behavior toolbar.

Describing This behavior enables to load a document by specifying the name of this document. For all
this documents types, the expert user can:
behavior ● Leave the path unset. In this case, the behavior can operate and launches a File Open
dialog box enabling the user to select a file

● Specify the complete path

● Specify the name of the document: In this case, the system uses the directory indicated in
the CATGraphicPath.

If the CATGraphicPath variable is set to E:\users\xxx\Documents, the system will perform a

search in this directory.

More Note that the output feature of this behavior is a document

information corresponding to the name of the selected document.

Note that the system does not make the document active.

Using this
Behavior
Interface
Business Process Knowledge Template Version 5 Release 14 Page 294

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Document to File path:

open Click the button to select the document to open.

Using this I have a wheel that I want to instantiate 4 times into a vehicle. I use the Load behavior and I
behavior instantiate the wheels 4 times.
Business Process Knowledge Template Version 5 Release 14 Page 295

Create New From Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Create New From behavior icon ( ) in the
behavior Doc Based Behaviors toolbar.

Describing This behavior enables to perform a New from command. It enables the user to create a new
this document whose content is the same as an existing document. To know more about the New
behavior From command, see the Infrastructure documentation.

For all documents types, the user can:

● Leave the path unset. In this case, the behavior can operate and launches a File Open
dialog box enabling the user to select a file

● Specify the path

● Specify the name of the document: In this case, the system uses the directory indicated by
the CATGraphicPath.

More Note that the output feature of this behavior is a document

information corresponding to the document indicated in the File path of the
Definition tab.

Using this
Behavior
Interface
Business Process Knowledge Template Version 5 Release 14 Page 296

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Template document File path:

Click the button to select the document to
reference.

Note that this capability is available for the document types that support the New
From command.

Using this I have a manikin that can be the driver or the passenger (the positioning is different for the
behavior driver and the passenger). I use the New From behavior and I instantiate the result of this
behavior.
Business Process Knowledge Template Version 5 Release 14 Page 297

Filter Catalog Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Filter Catalog Behavior icon ( ) in the Doc
behavior Based Behaviors toolbar.

Describing This behavior enables the user to open a catalog containing documents of features (like
this PowerCopies, or User Defined Features) by using the catalog browser. If the user used
behavior keywords to accelerate the search, the value of the keyword that will be used as a filter can be
specified in the behavior.

More ●
It is possible to define a query to filter the catalog during
information the execution of this behavior. To do so add inputs to the
behavior, their values will be used to filter the content of
the catalog.
●
Note that this behavior has 2 different outputs:
- ChosenPath is valuated if the catalog contains
documents. Chosen path will be the path of the
selected document. Feature is not valuated. See
the screen shot of a catalog containing
documents below. Click the graphic below to
enlarge it.

Note that the item you select in the catalog is not

loaded in the session.
Business Process Knowledge Template Version 5 Release 14 Page 298

- Feature is valuated if the catalog contains User

Features or PowerCopies. Feature corresponds to
the selected object and Chosen path corresponds
to the name of the document that contains the
PowerCopy or the User Feature. See the screen
shot of a catalog containing PowerCopies below.
Click the graphic below to enlarge it.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 299

Catalog File Indicate the catalog file path. Note that you do not have to specify
document path: the complete path. Catalogs are located by default in the directory
identified by the CATGraphicPath environment variable.
Note that you may also leave the path unset. In this case, the end-
user will select a catalog file in the user workbench.
● It is now possible to insert catalogs from ENOVIA VPM V5. To do
so, make sure you have enabled the Enovia environment in the
Document Environments field (Tools->Options->General-
>Document.) Your documents will be accessible via the
Document Chooser.
● It is now possible to insert catalogs from specific directories that
are assigned a logical name, referred to as a "DLName". To do so,
make sure you have enabled the DLName environment in the
Document Environments field (Tools->Options->General-
>Document.)

Filtering Enables the user to add keywords whose names will be identical to the ones
Keywords: contained in the catalog. These keywords will be used to filter and to navigate
though the catalog.

Using this The expert user uses a manikins catalog and wants to retrieve the manikins whose size
behavior matches the EEC standards.
Business Process Knowledge Template Version 5 Release 14 Page 300

Bind Behaviors

This set of behaviors enables the expert user to access resources not yet available at the definition stage. To get
more information about the Bind mechanism, see To know more about the Bind Mechanism...

Please find below the list of the behaviors belonging to the Bind behaviors.

● Bind Publication Behavior

● Bind Product Instance Behavior

● Bind Part Behavior

● Bind User Feature Behavior

● Bind PowerCopy Behavior

Business Process Knowledge Template Version 5 Release 14 Page 301

Bind PowerCopy Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Bind PowerCopy Behavior icon ( ) in the Bind
behavior Based Behaviors toolbar.

Describing This behavior is designed to retrieve a PowerCopy from a document by specifying the name of
this this PowerCopy as well as the document or a feature contained in the document. (As of today,
behavior PowerCopy definitions can be stored in a CATPart document.) This behavior does not support
Assembly templates. To get more information about the Bind mechanism, see To know more
about the Bind Mechanism...

More Note that the output feature of this behavior is a PowerCopy.

information

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 302

Comment: Comment attributed to the behavior.

Bind context From object: Select in the Behaviors tree the feature or the
document from which the search operation should
be performed. The object indicated in this field can
be the output feature resulting from a Load
Document, or a Create New from action.

Power copy Name: Enter the name of the PowerCopy. If no name is

indicated, the search will return the first
powercopy encountered.

Using this The expert user saved PowerCopies in a part document and searches for one of these
behavior PowerCopies in the document.
Business Process Knowledge Template Version 5 Release 14 Page 303

Bind User Feature Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Bind User Feature Behavior icon ( ) in the
behavior Bind Based Behaviors toolbar.

Describing This behavior is designed to retrieve a UDF from a document by specifying the name of this
this UDF as well as the document or a feature contained in the document. (As of today, UDF
behavior definitions can be stored in a CATPart document.) To get more information about the Bind
mechanism, see To know more about the Bind Mechanism...

More Note that the output feature of this behavior is a UserFeature.

information

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 304

Comment: Comment attributed to the behavior.

Bind context From object: Select in the Behaviors tree the feature or the
document from which the search operation should be
performed. The object indicated in this field can be the
output feature resulting from Load Document action, or
Create New from actions.

User Feature Enter the name of the User Feature. If no name is

Name: indicated, the search will return the first User Feature
encountered.

Using this The expert user saved User Features (UDFs) in a part document and searches for one of these
behavior User Features in the document.
Business Process Knowledge Template Version 5 Release 14 Page 305

Bind Part Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Bind Part Behavior icon ( ) in the Bind Based
behavior Behaviors toolbar.

Describing This behavior is designed to retrieve a part from a CATPart document by specifying the
this document or a feature contained in this document. It can be associated with a Load
behavior Document, Create New From, or a Filter Catalog behavior. To get more information about the
Bind mechanism, see To know more about the Bind Mechanism...

More Note that the output feature of this behavior is a Part.

information

Using this
Behavior
Interface

Name: Enter the name attributed to the behavior.

Comment: Enter a comment attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 306

Bind context From object: Click in the Behaviors tree to select the feature or the
document from which the search operation should be
performed.
Business Process Knowledge Template Version 5 Release 14 Page 307

Bind Publication Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Bind Publication Behavior icon ( ) in the Bind
behavior Based Behaviors toolbar.

Describing This behavior searches for the publication whose name or path is specified. Given a part or a
this product, some elements (geometry and parameters) can be published. To get more information
behavior about the Bind mechanism, see To know more about the Bind Mechanism...

More Note that the output feature of this behavior is a Link.

information

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 308

Bind Starting From In the Behaviors tree, select:

● An object or a behavior variable that will contain a V5
item at run time.

● A behavior.

The search will start from the object indicated in this

field. If nothing is indicated, the search will start from
this behavior.

Relative Name Enter the object name that you are looking for or an
access path (using the ../.. syntax).

Using this ● Given a vehicle product, the expert user wants to find the floor.
behavior
● Given a manikin, the expert user wants to retrieve the H point.
Business Process Knowledge Template Version 5 Release 14 Page 309

Bind Product Instance Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Bind Product Instance Behavior icon ( ) in the
behavior Bind Based Behaviors toolbar.

Describing Given a product or a part, this behavior searches for the instance whose name or path is
this specified. If the input feature is a part, the output feature will be a product.
behavior Given a product Vehicle containing an instance of the product "Engine", this behavior enables
the user to find the instance of engine using the reference engine. In the case of a part used in
a product context, if the user specifies the part, the behavior will find the corresponding
product instance. If the product contains more than one instance, the behavior returns the first
one.
If the input feature is not a part, see Bind Instance Behavior: Data Sheet. To get more
information about the Bind mechanism, see To know more about the Bind Mechanism...

More Note that the output feature of this behavior is a Link.

information

Using this
Behavior
Interface
Business Process Knowledge Template Version 5 Release 14 Page 310

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Bind Reference In the Behaviors tree, select:

● An object or a behavior variable that will contain a V5
item at run time.

● A behavior.

The search will start from the object indicated in this field.
If nothing is indicated, the search will start from this
behavior.

Relative Name Enter the object name that you are looking for or an
access path (using the ../.. syntax).
Business Process Knowledge Template Version 5 Release 14 Page 311

Display in Window Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Display in Window Behavior icon ( ) in the
behavior Doc Based Behaviors toolbar.

Describing This behavior is designed to highlight or to display an object.

this ● If this object is a document, it will be displayed in another window.
behavior
● If this object is a feature belonging to the current document, it will be highlighted.

● If this object is a feature belonging to another document, a new window will display and
the feature will be highlighted.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Display context Feature or document to Select the output feature of a behavior whose
display: content will be displayed.
Business Process Knowledge Template Version 5 Release 14 Page 312
Business Process Knowledge Template Version 5 Release 14 Page 313

Insert Components Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Insert Components icon ( )
behavior

Describing This behavior is designed to enable the expert user to insert a component into a product. It
this enables to create a new component or to insert an existing component by specifying the
behavior number of instances. In the case of contextual parts or products, the user can choose to change
the context.
This behavior supports the automatic update mode: If the number of instances is modified, the
behavior executes:
● If the number of instances is greater than the number of instances initially indicated, new
instances are added.

● If the number of instances is inferior to the number of instances initially indicated, instances
are removed.

More Note that the outputs of this behavior is:

information
Note that the output of this behavior is the
GeneratedObjects: Valuated output list .
Business Process Knowledge Template Version 5 Release 14 Page 314

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Definition New component: The expert user can insert a component

by specifying its part number.

Existing component: The expert user can insert an existing

component. In this case, the field will
contain a load output feature of a
.CATPart or .CATProduct document or
the selection of a product in a document.

Instantiation Father product The expert user specifies the product.

context
Number of instances: The expert user specifies the number of
instances.
If located in a loop combination,
the number of instances is
automatically set to 1.
Business Process Knowledge Template Version 5 Release 14 Page 315

Change context for first instance If checked, enables the user to initialize
the context for the first instance. This
option is recommended if the inserted
part is contextual. To know more, see
the Product Structure User's Guide.

The Typing management field was removed from the user interface. This field
enabled the user to type instances and add sub-types. To do so, use the
Generate Components Behavior.

Using this
See Using the Insert Components Behavior: Auto update Mode.
behavior
Business Process Knowledge Template Version 5 Release 14 Page 316

Knowledge Relations Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the Knowledge Relations Behavior icon ( ).
behavior

Describing This behavior is designed to enable the user to specify Knowledge Advisor relations (Formula, Rule, or
this Check).
behavior

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Business Process Knowledge Template Version 5 Release 14 Page 317

Comment: Comment attributed to the behavior.

Immediate This check box is available only if the Automatic update mode is selected in the
update of Properties tab. If checked the Knowledgeware relations will be permanently active. If
the not, the behavior will be re-executed only when its input are modified.
relations:

The Content tab enables the user to access the Knowledgeware functions. The user can create:

●
Formulas. To create formulas, proceed as follows:

1. Create attributes in the Attributes tab (select Output in the Quality field). The
created attributes are displayed in the Content tab.
2. Right-click one of the output attributes in the Content tab and select the Edit
Formula... command.
3. Enter the formula and click OK. The formula displays under the Relations node in
the Content tab (see example below).

Rules by clicking the icon.

Checks by clicking the icon.

Sets of equations by clicking the icon.

To know more about the Knowledgeware capabilities, see the Knowledge Advisor User's
Guide.

Using this
See Knowledge Relations: Using the if...else syntax.
behavior

Note that the Knowledge Relations behavior requires the Knowledge Advisor license.
Business Process Knowledge Template Version 5 Release 14 Page 318

Knowledge Certify Behavior: Data Sheet

Accessing this
behavior This behavior can be accessed by clicking the Knowledge Certify Behavior icon ( ) in the
Knowledge toolbar.

Describing this This behavior is designed to enable the user to

behavior ● apply a rule base and
● specify the validation steps of his design and to automate its execution.

MORE To reuse existing rule bases, the user can save them into catalogs. A FilterCatalog behavior
INFORMATION will therefore be located before this behavior in the sequence.
It is possible for the user to define rule bases containing technological objects as well as
their attributes. These rule bases are defined in CATPart, and CATProduct documents and
saved in catalogs. To know more, see the Knowledge Expert User's Guide.

Note that this behavior has 2 output features:

● The Report: Report generated after running the rule base.
● Status: Red icon in the specification tree if the check failed or
green if the check ran correctly. This status can be tested by
other behaviors and enables the user to drive the design
accordingly.

Using this
Behavior
Interface
Business Process Knowledge Template Version 5 Release 14 Page 319

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Define knowledge Rule Indicate the "Rule Base to use" generally valuated the
base base output feature of the catalog.

Feature to certify Object Click in the Behaviors tree to select the output link of
bind object, bind part or bind UDF behaviors. It is the
object to which the rulebase will apply: "Object to
check".

To Know more To see an example, see Using the Knowledge Certify Behavior.
Business Process Knowledge Template Version 5 Release 14 Page 320

Introducing the Event-based Behaviors

This set of behaviors is designed to subscribe to an event to react to this event. The expert user either specifies:

● A behavior or
● A V5 feature or
● The child of a structure behavior: In this case the user should specify the name of the child. If many children
have the same name in a structure the event will occur several times.

Please find below the list of the behaviors belonging to the Event-based behaviors .

● On Create Behavior: Reacts when a behavior is created.

● On Done Behavior: Reacts when the execution of a behavior is over.

● On Remove Behavior: Reacts when a behavior is deleted.

● On Cancel Behavior: Reacts when a behavior is canceled.

Note that Onxxx behaviors should be located outside the sequences that they subscribe to, that
is to say, the Onxxx behaviors cannot subscribe to one of their ancestors in the specification
tree.
Business Process Knowledge Template Version 5 Release 14 Page 321

On Done Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the On Done Behavior icon ( ) in the Event Based Behaviors
behavior toolbar.

Describing This behavior is designed to track the completion of the execution of another behavior or the update of a
this feature. When the execution of the behavior or the update of the feature is completed, the On Done behavior
behavior executes.

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Track Father Object to Survey In the behaviors tree, select the father object whose
completion is tracked.

Children Objects This field displays the behaviors located below the main
behavior.
Click the Add button to add children objects.
Business Process Knowledge Template Version 5 Release 14 Page 322

Child Object to Survey Use the arrows to select the behavior that will be
tracked and that will activate the On Done behavior.

This object (available by default) enables the user to

subscribe to the update of a V5 feature or to the operate
Update
of a behavior.

Add button Use this button to add a behavior that will be part of the
structure.

Using this See Using the OnXXX Behavior.

behavior
Business Process Knowledge Template Version 5 Release 14 Page 323

On Create Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the On Create Behavior icon ( ) in the Bind Based Behaviors
behavior toolbar.

Describing This behavior is designed to track the creation of another behavior known as the Father Object. When the
this creation of the behavior is completed, the On Create behavior executes.
behavior

Using this
Behavior
Interface

Name Name attributed to the behavior.

Comment Comment attributed to the behavior.

Track Father Object to Survey In the behaviors tree, select the father.

Children Objects This field displays the behaviors located below the main
behavior.
Click the Add button to add children objects.
Business Process Knowledge Template Version 5 Release 14 Page 324

Child Object to Survey Use the arrows to select the behavior that will be tracked and
that will activate the On Create behavior.

Add button Use this button to add a behavior that will be part of the
structure at run time.
Business Process Knowledge Template Version 5 Release 14 Page 325

On Remove Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the On Remove Behavior icon ( ) in the Event Based Behaviors
behavior toolbar.

Describing This behavior is designed to track the deletion of another behavior known as the Father Object. When the
this deletion of the behavior is completed, the On Remove behavior executes
behavior

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Track Father Object to Survey In the behaviors tree, select the father object.

Children Objects This field displays the behaviors located below the main
behavior.
Click the Add button to add children objects.

Child Object to Survey Use the arrows to select the behavior whose deletion will be
tracked and that will activate the On Remove behavior.
Business Process Knowledge Template Version 5 Release 14 Page 326

Add button Use this button to add a behavior that will be part of the
structure.
Business Process Knowledge Template Version 5 Release 14 Page 327

On Cancel Behavior: Data Sheet

Accessing
this This behavior can be accessed by clicking the On Cancel Behavior icon ( ) in the Event Based Behaviors
behavior toolbar.

Describing This behavior is designed to track the failure of another behavior known as the Father Object. When the
this failure of the behavior is detected, the On Cancel behavior executes.
behavior

Using this
Behavior
Interface

Name: Name attributed to the behavior.

Comment: Comment attributed to the behavior.

Track Father Object to Survey In the behaviors tree, select the father object.

Children Objects This field displays the behaviors located below the main
behavior.
Click the Add button to add children objects.
Business Process Knowledge Template Version 5 Release 14 Page 328

Child Object to Survey Use the arrows to select the behavior whose failure will be
tracked and that will activate the On Cancel behavior.

This object available by default enables the user to subscribe

Update to the update of a V5 feature or to the operate of a behavior.

Add button Use this button to add a behavior that will be part of the
structure.
Business Process Knowledge Template Version 5 Release 14 Page 329

Workbench Description

This section contains the description of the icons and menus specific to the Business Process Knowledge
Template workbench.

The Business Process Knowledge Template workbench is shown below. Click the sensitive areas (toolbars) to
access the related documentation.

Type Tools Toolbar

Knowledge Tools Toolbar
Design Tools Toolbar
Infrastructure Tools Toolbar
Technological Object Toolbar
User Application Toolbar
Specification Tree Description
Interface Description
Business Process Knowledge Template Version 5 Release 14 Page 330

Type Tools Toolbar

The Type Tools contains the following tools

See Add Type Behavior: Data Sheet.

See Bind Type Behavior: Data Sheet.

Business Process Knowledge Template Version 5 Release 14 Page 331

Knowledge Tools Toolbar

The Knowledge Tools toolbar contains the following tools:

See Knowledge Relations: Using the if...else Syntax.

See Knowledge Relations: Using the if...else Syntax.

See Knowledge Relations: Using the if...else Syntax.

See Using the Knowledge Certify Behavior.

Business Process Knowledge Template Version 5 Release 14 Page 332

Design Tools Toolbar

The Design Tools toolbar contains the following tools:

See Load Document Behavior: Data Sheet.

See Create New From Behavior: Data Sheet.

See Filter Catalog Behavior: Data Sheet.

See Bind Part Behavior: Data Sheet.

See Bind User Feature Behavior: Data Sheet.

See Bind PowerCopy Behavior: Data Sheet.

See Bind Publication Behavior: Data Sheet.

See Bind Product Instance Behavior: Data Sheet.

Business Process Knowledge Template Version 5 Release 14 Page 333

See Instantiate Template Behavior: Data Sheet.

See Create External Reference Behavior: Data Sheet.

See Copy/Paste Behavior: Data Sheet.

See KWScript Behavior: Data Sheet.

See Insert Components: Data Sheet.

See Display in Window Behavior: Data Sheet.

Business Process Knowledge Template Version 5 Release 14 Page 334

Infrastructure Tools Toolbar

The Infrastructure Tools toolbar contains the following tools:

See Logical Combination: Data Sheet.

See Sequential Combination Behavior: Data Sheet.

See Loop Behavior: Data Sheet.

See Generate Components Behavior: Data Sheet.

See On Create Behavior: Data Sheet.

See On Done Behavior: Data Sheet.

See On Remove Behavior: Data Sheet.

See On Cancel Behavior: Data Sheet.

Business Process Knowledge Template Version 5 Release 14 Page 335

See VBScript Behavior: Data Sheet.

See Command Behavior: Data Sheet.

See URL Behavior: Data Sheet.

See ActiveX URL Behavior: Data Sheet.

See System Behavior: Data Sheet.

See Bind Object Behavior: Data Sheet.

See Bind Parameter Behavior: Data Sheet.

See Bind Reference Behavior: Data Sheet.

See Bind Instance Behavior: Data Sheet.

See Link Parameters Behavior: Data Sheet.

See Synchronize Parameters Behavior: Data Sheet.

See Add item Behavior: Data Sheet Behavior.

See Remove item Behavior: Data Sheet Behavior.

Business Process Knowledge Template Version 5 Release 14 Page 336

See Get item Behavior: Data Sheet Behavior.

See Propagate Execution Behavior: Data Sheet.

See Information Behavior: Data Sheet.

Business Process Knowledge Template Version 5 Release 14 Page 337

Technological Object Toolbar

The Technological Object toolbar contains the following tools:

See Creating a Technological Object.

See Adding an Attribute to a Technological Object.

The Generate Report icon enables you to generate a report. This function allows you to generate an
external file. The report will display all the objects under the Classes View of the specifications tree. It
will also display all the attributes associated with an object. To know more about this function, see the
Product Structure User's Guide.

The Unlink icon enables you to link or unlink behaviors.

Business Process Knowledge Template Version 5 Release 14 Page 338

User Application Toolbar

The User Application Toolbar contains the following tool:

See Generating a User Workbench.

Business Process Knowledge Template Version 5 Release 14 Page 339

Specification Tree Description

The specification tree displays three views

● Referenced Dictionary displays any external
dictionary files that are referenced in the
document. enables the expert user to load
an existing .CATfct file and to define model
behaviors depending on the use context. The
types and sub-types will differentiate the
fields of use.

● Classes View displays all types and sub-

types available in the document and created
by using the Create technological Type icon

( ). To know more, see Creating a

Technological Object.

● Behaviors View displays the behaviors

available in the document.

Symbols

This symbol indicates that the behavior execution is suspended.

This symbol indicates that the behavior needs to be updated.

This symbol indicates that the behavior mandatory specifications are missing.

This symbol indicates that the behavior is broken.

Business Process Knowledge Template Version 5 Release 14 Page 340

Interface Description

On the right side of the window, two tabs are available:

●
Behaviors

●
Attributes

The Behaviors tab displays the

attributes and behaviors associated
with the technological types.

The technological type is located at

the top of the tree. Its attributes
located below the Attributes node
follow and then the behaviors
associated with this type.

In the example opposite, the Driver

type has the following attributes:

● L40

● FootAngle

● XPosition

● YPosition

● ZPosition

● AnkleAngle

● KneeAngle

● HipAngle

● HeelHipDistance

4 combinations of behaviors:

● Generate geometry

● Generate indirect field of view

for classic mirror

● Generate indirect field of view

for planar mirror
Business Process Knowledge Template Version 5 Release 14 Page 341
● Check driver position

The Attributes tab displays the

inherited and the local attributes
associated with the technological
type.

The inherited attributes are the

attributes inherited by the type from
its "super type". In the example
opposite, the Driver type inherits
the following attributes:

● Percentile

● L40

● FootAngle

● AnkleAngle

The Local attributes are the

attributes added to the type
(XPosition in the example opposite).

To add an attribute to a type, click

this type in the specification tree,
then click the Add Attribute Icon

( ) in the Behaviors
management toolbar.

The Attribute value field enables you

to value the attribute.

The Delete button enables you to

delete local attributes.
Business Process Knowledge Template Version 5 Release 14 Page 342

Customizing

1. Select the Tools -> Options command. The Options dialog box displays.

2. Expand the Knowledgeware option and click the Business Process Knowledge

Template tab. The Business Process Knowledge Template tab displays containing the

following set of options:

❍ Access Rights

❍ Behavior operation

❍ Specification tree

Access Rights

This scrolling list enables the expert user to determine who will be able to access the generated

workbench.

All Users
Only the User can access the workbench.

Expert&Administrator
The Administrator and the Expert user can access the workbench.

Expert
Business Process Knowledge Template Version 5 Release 14 Page 343

The expert user is the only one who can access the workbench. This mode is used when the
expert user wants to test the generated workbench.

By default, this option is set to All Users.

Behavior operation

With messages
If checked, enables the expert to user to decide if he wants messages to be displayed or not when
testing the workbench.

Note that this option is available only if the user selected Expert or Expert in the Access Rights
field.

By default, this option is unchecked.

Specification tree

All variables
All variables belonging to the technological type and all parameters of the product are displayed in
the generated workbench under the "Variables" node.

By default, this option is checked.

Technological variables only

Business Process Knowledge Template Version 5 Release 14 Page 344

Only the variables belonging to the technological types as defined in BKT will be displayed in the
generated workbench.

By default, this option is unchecked.

No variables
No variables are displayed in the generated workbench.

By default, this option is unchecked.

3. Change these options according to your needs.

4. Click OK when done to validate your settings.

Business Process Knowledge Template Version 5 Release 14 Page 345

Glossary

Many of the definitions included in this glossary are only pertinent within the CATIA Business Process Knowledge
Template context.

Symbols
.CATfct The extension of a Feature Dictionary and Business Process Knowledge
Template file. A .CATfct file contains the technological objects and
behaviors.
.CATScript The extension of a macro file generated by CATIA Version 5.

A
activity A property which defines whether a relation is applied to a document or
not. The activity value is either true or false. It is indicated by an icon
in the specification tree and can also be read in the document
parameter list.
ActiveX URL Behavior A behavior designed to open a HTML page that can interoperate with
CATIA V5 using VB Script.

Add Type Behavior A behavior designed to associate technology with an object.

B
behavior A set of tasks performed on a technological object.

Bind Product Instance Behavior A behavior designed to search for a product instance.

Bind Publication Behavior A behavior designed to retrieve a publication.

Bind PowerCopy Behavior A behavior designed to retrieve a PowerCopy from a document

by specifying the name of this PowerCopy as well as the
document or a feature contained in the document.

Bind User Feature Behavior A behavior is designed to retrieve a UDF from a document by specifying
the name of this UDF as well as the document or a feature contained in
the document.
Business Process Knowledge Template Version 5 Release 14 Page 346

Bind Part Behavior A behavior is designed to retrieve a part from a CATPart Document by
specifying the document or a feature contained in this document.

Bind Object A behavior that searches for a specified object.

Bind Behaviors A set of behaviors enabling the user to access resources not yet
available at the definition stage.

Bind Parameter Behavior A behavior that searches for a specified parameter.

Bind Reference Behavior A behavior that searches for the reference whose name or path is
specified.

Bind Instance Behavior A behavior that searches for the instance of a specified object.

Bind Type Behavior A behavior searches for the type whose name or path is specified.

C
check A set of statements intended to provide the user with a clue as to
whether certain conditions are fulfilled or not. A check does not modify
the document it is applied to. A check is a feature. In the document
specification tree, it is displayed as a relation that can be activated and
deactivated. Like any feature, a check can be manipulated from its
contextual menu.

Command Behavior A behavior designed to specify the execution parameters of a CAA

Command..

Create New From Behavior A behavior designed to perform a New from command.

Copy/Paste Behavior A behavior designed to copy a feature and to paste it into a document.

Create External Reference Behavior A behavior designed to create an external reference in a part by
specifying a geometrical feature.

Display In Window Behavior A behavior designed to highlight or to display an object.

Business Process Knowledge Template Version 5 Release 14 Page 347

The set of parameters, operators, keywords, functions and other

components that make up the language to be used to write formulas,
dictionary
rules and checks. The formula, rule and check editors provide you with
an interactive view of the dictionary.

F
Filter Catalog Behavior A behavior that enables the user to open a catalog containing features
by using a catalog.

A behavior that enables the user to specify the instantiation of a

Instantiate Template Behavior
PowerCopy, or a UDF.

Insert Components Behavior A behavior designed to insert a new component into a product.

A set of behaviors that enables the user to reuse existing components

Implementation Behaviors
like CAA commands, VB Scripts, URLs, and executable files.

A behavior designed to enable the user to specify a message that will

Information Behavior
be displayed when a given event occurs.

K
The set of software components dedicated to the creation and
manipulation of knowledge-based information. Knowledge-based
knowledgeware information consists of rules and other types of relations whereby
designers can save their corporate know-how and reuse it later on to
drive their design processes.

A behavior designed to enable the user to specify a Knowledge Advisor

Knowledge Relations Behavior
relation (Rule or Check).

L
A behavior designed to link two behaviors of one of the extended
Link Parameters Behavior
objects.
Business Process Knowledge Template Version 5 Release 14 Page 348

A behavior designed to load a document by specifying the name of this

Load Document Behavior
document.

A combination of behaviors enabling the user to work with the

Logical Combination Behavior
aggregation concept.

O
A behavior designed to track the failure of another behavior known as
On Cancel Behavior
the Father Object.

A behavior designed to track the creation of another behavior known as

On Create Behavior
the Father Object.
On Done Behavior A behavior designed to track the completion of the execution of another
behavior or the update of a feature.

On Remove Behavior A behavior designed to track the deletion of another behavior known as
the Father Object.

P
parameter A feature defining a document property.

Propagate Execution Behavior A behavior designed to launch the execution of a given object.

R
relation A knowledgeware feature which, depending on certain conditions:
● sets parameter values

● displays a message

● or runs a macro.

Knowledgeware relations are formulas, checks, rules and design tables.

Business Process Knowledge Template Version 5 Release 14 Page 349

rule A set of instructions, generally based on conditional statements,

whereby the relationship between parameters is controlled. In addition,
depending on the context described by the rule instructions, CATIA
macros can be executed and messages can be displayed. A rule is a
feature. In the document specification tree, it is displayed as a relation
that can be activated or deactivated. Like any feature, a rule can be
manipulated from its contextual menu.

S
Sequential Combination Behavior A combination of behaviors designed to execute in a sequential order.

Synchronize Parameters Behavior A behavior designed to synchronize two behaviors of the extended
objects.

System Behavior A behavior designed to launch an executable file.

T
Technological Object An object used in the Business Process Knowledge Template
workbench.
A technological object is made up of three sets of components:
● A type

● A set of attributes

● A set of behaviors

U
URL Behavior A behavior designed to open a HTML page.

V
VBScript Behavior A behavior designed to run a VBScript.
Business Process Knowledge Template Version 5 Release 14 Page 350

Index

Symbols
.catalog

.CATDrawing

.CATfct

.CATProcess

.CATProduct

.CATScript

.CATvbs

.HTML

A
access path

access rights

accessing the end-user workbench

activate

activating the end-user workbench

activex url behavior

example

add item behavior

add type behavior

adding a component

adding an attribute
administration

creating an environment under unix

creating an environment under windows

creating the working environment

managing the data

Business Process Knowledge Template Version 5 Release 14 Page 351

reminder

aggregation

attribute
attributes

display

attributes node

autodelete

B
behavior

activex url

add components

add item

add type

bind instance

bind object

bind parameter

bind part

bind powercopy

bind product instance

bind publication

bind reference

bind type

bind user feature behavior

command

copy/paste

create external reference

create new from

creating

display in window

editing
Business Process Knowledge Template Version 5 Release 14 Page 352

executing

filter catalog

generate components

get item

information

insert components

instantiate template

knowledge certify

knowledge relations

kwscript

link parameters

linking

load document

loop

on cancel

on create

on done

on remove

propagate execution

remove item

synchronize parameters

system

typing, attribute

url

VBScript

behavior pattern

behaviors interface

behaviors view

bind behaviors

bind instance behavior

bind part

bind powercopy behavior

Business Process Knowledge Template Version 5 Release 14 Page 353

bind publication behavior

bind user feature behavior

bind instance behavior

bind mechanism

bind object behavior

bind part

bind part behavior

bind powercopy behavior

bind product instance behavior

bind publication

bind publication behavior

bind type behavior

bind user feature

bind user feature behavior

C
caa command

CATGraphicPath

catiaenv command

CATPart

CATReferenceStandardPath

CATStartupPath

CATStartupPath variable

CATTemp

CATUserSettingPath

CATUserSettingPath variable

check

classes view
combination

logical
Business Process Knowledge Template Version 5 Release 14 Page 354

sequential

combining behaviors
command

ActiveX Url Behavior

Add Attribute

Add Components Behavior

Add Item Behavior

Add Type Behavior

Applicative Workbench Generation

Bind Instance Behavior

Bind Object Behavior

Bind Parameter Behavior

Bind Part Behavior

Bind Powercopy Behavior

Bind Product Instance Behavior

Bind Publication Behavior

Bind Reference Behavior

Bind Type Behavior

catiaenv

Command Behavior

Copy-Paste Behavior

Create New From Behavior

Create Technological Type

Display In Window Behavior

External Reference Behavior

Filter Catalog Behavior

Generate Components Behavior

Generative Script Behavior

Get Item Behavior

Information Behavior

Insert Components Behavior

Instantiate Template Behavior

Business Process Knowledge Template Version 5 Release 14 Page 355

Knowledge Certify Behavior

Knowledge Relations Behavior

Link Parameters Behavior

Load Document Behavior

Logical Combination Behavior

Loop Behavior

On Cancel Behavior

On Create Behavior

On Done Behavior

On Remove Behavior

Propagate Execution Behavior

Remove Item Behavior

Sequential Combination Behavior

setcatenv

Synchronize Parameters Behavior

System Behavior

URL Behavior

User Feature Behavior

VBScript Behavior

component

concatenate

condition

control

copy/paste behavior

create an external reference

create external reference behavior

create new from behavior

creating a check

creating a formula

creating a rule

creating a set of equations

creating an environment under unix

Business Process Knowledge Template Version 5 Release 14 Page 356

creating an environment under windows

creating behaviors

creating the working environment

customizing

D
defining a workbench

defining technological objects

deploy

display in window behavior

document behavior

create new from behavior

display in window behavior

filter catalog behavior

load document behavior

E
editing behaviors

environment editor
event-based behaviors

en remove behavior

on cancel behavior

on create behavior

on done behavior

executable file

executing behaviors

execution error

execution messages

exploiting messages
Business Process Knowledge Template Version 5 Release 14 Page 357

external reference

externalobject attribute

F
feature dictionary tree

filter catalog

filter catalog behavior

fixing a problem

focus

formula

G
generate components behavior

generate report icon

generate workbench

part design

Product structure

product structure

system context

generating a report

generating a user workbench

generating the user workbench

get item behavior

global environment

H
html page
Business Process Knowledge Template Version 5 Release 14 Page 358

I
if...then...

if...then...else

if...then...else syntax

implementation behaviors

activexurl behavior

command behavior

system behavior

URL behavior

VBScript behavior

information behavior

input attribute

input error

insert components

instantiate a user feature

instantiate template

instantiate template behavior

instantiating objects

interface description

internal attribute
io based behaviors

link parameters behavior

synchronize parameters behavior

K
keyword

knowledge certify behavior

knowledge relations behavior

kwscript behavior
Business Process Knowledge Template Version 5 Release 14 Page 359

L
link parameters behavior

linking behaviors

list

list behaviors

ListSize attribute

local attribute

local operate

logical combination

loop behavior

M
manage errors

managing technological objects

managing the data

message

N
navigate in the product structure

O
object

on cancel behavior

on create behavior

on done behavior
Business Process Knowledge Template Version 5 Release 14 Page 360

on remove behavior

onxxxx behaviors

operate

operating behaviors

optimal catia plm usability

output attribute

P
part design

generate workbench
part structure

generate workbench

path

problem
product structure

generate workbench

propagate

propagate execution behavior

R
referenced dictionary

relative name

reminder

remove item behavior

replaying the process

report

reuse behavior

copy/paste behavior

create external reference behavior

instantiate template behavior

Business Process Knowledge Template Version 5 Release 14 Page 361

kwscript behavior
reuse behaviors

load document behavior

reuse models

rule

S
safe save

sequential combination

set of equations

setcatenv command

setting up the working environment

shell

specifications tree description

structure behavior

symbols

synchronize parameters behavior

system behavior
system context

generate workbench

T
TargetSize attribute

technological object

defining

technological specifications view

technological type

testing the process

toolbar description
Business Process Knowledge Template Version 5 Release 14 Page 362

Tools Options- Business Process Knowledge Template tab

TypeName_Instanciate

typing behaviors attribute

U
update

auto

driven

single

url behavior

use cases

user environment

user feature
user workbench

generating

working with a user workbench

using a sequential combination to instantiate a user feature

using the generate components behavior

using the insert components behavior

using the loop behavior

using the onxxx behaviors

using the propagate execution behavior

V
vb script

vbscript behavior

W
Business Process Knowledge Template Version 5 Release 14 Page 363

warning panel

working with a user workbench

working with behaviors

working with behaviors patterns

working with technological objects