Call Behavior: Data Sheet  

Accessing this behavior This behavior can be accessed by clicking the Call Behavior icon ().
Describing this behavior This behavior enables you to reuse existing patterns of behaviors without duplicating data. These patterns are sequence behaviors. Only the behaviors declared in the Knowledgeware Index can be reused by the behavior call mechanism. For more information, see Using the Call Behavior or the documentation related to the Knowledgeware Index in the Infrastructure User's Guide.
Methodology The very first task consists in exposing a sequence behavior in the Knowledgeware index. To do so:

  1. Select the sequence that you want to expose.

  2. Click the Call Behavior icon ().

Note that only main behaviors which do not contain external links (links from one of the sub-behaviors pointing outside the scope of the main behavior) can be exposed. Once exposed, the main behavior can be reused using the Call behavior.

Defining the Call Behavior

  1. In an existing .CATfct, expose a sequence in the Knowledgeware Index as explained above. This sequence will be available for the Call behavior and will be re-used later.

  2. Add the Call behavior to the .CATfct and set the mandatory inputs i.e. the name of the called behavior. To do so, click the ... button in the Behavior Name field.

  3. Add other inputs to the Call behavior such as the local redefinition of the inputs and the outputs of the called behavior. To do so, click Add in the Defined inputs and parameters /Defined outputs and parameters field.
    You create an exact matching between the called behavior attributes and the local redefinition of those attributes on the Call behavior. The name, the type and the quality must be identical for every attribute, if not, the operation of the Call behavior will fail. To map the attributes of the Call behavior with those of the process:

    • If the information concerning the called behavior can be directly accessed at definition time, i.e. if the .CATfct file containing the called behavior is located in the <CATGraphicPath> directory, those attributes can be created by clicking Map attributes. This mapping is automatic and is created without any user interaction.

    The CATfct file containing the referenced exposed sequence must be available in the <CATGraphicPath> directory in order for this mapping to be possible. Otherwise, no attributes will be created.

    • You can also use the Add command to add the inputs/outputs.

    These additional inputs enable you to plug the Call behavior to the general process. They represent the external view of the behavior pattern exposed via the Call behavior. There is no physical link between the Call behavior and Called behaviors.

Operating the Call Behavior

The operation of the Call behavior is made up of 3 different sub-operations:

  1. When running the Call behavior, the behavior instantiates a hidden copy of the called behavior. This copy is aggregated to the Call behavior. The life cycle management and the operating of this copy is performed by the Call behavior which is the external process view of the called behavior.

  2. The inputs and the outputs of the Call behavior are mapped to the ones of the called behavior. When operating, the Call behavior status is Failed if the matching fails. In this case, an error message is displayed.

  3. The Call behavior operates the called behavior. The status and result of this operation can be seen on the Call behavior: The symbol changes depending on the behavior status.

The Call behavior is an operation proxy of the called behavior. Its different operation states are the ones of the called behavior. If the called behavior is failed, the Call behavior is Failed, if the called behavior is suspended, the Call behavior operation state is is suspended.
More Information  The Call behavior can reuse patterns of behaviors that can also embed Call behaviors in their definitions.
Using this Behavior Interface

Behavior name Name of the called sequence.
Click the ... button to access the Knowledgeware Index browser which shows a list of all exposed sequences. Select the name of the sequence that is to be re-used and click OK in the browser.
Source file Indicates the name of the .CATfct that contains the selected sequence.
Defined inputs and parameters Add/Modify/Delete Click Add to add inputs and parameters to the exposed sequence. These inputs are designed to link the Call behavior to the other behaviors.
Defined outputs and parameters Add/Modify/Delete Click Add to add outputs to the exposed sequence. These outputs are designed to link the Call behavior to the other behaviors.
Map attributes Enables you to map the called behavior attributes and the local redefinition of those attributes to the Call behavior. This mapping is automatic and is created without any user interaction.
If the CATfct is not available, add the attributes by clicking Add available in the Defined inputs and parameters and in the Defined Outputs fields.
Using this behavior See Using the Call Behavior.