How to Implement the Functional/Logical Connection Creation Check Business Logic?

The functional/logical connection creation check business logic allows you to define rules that are taken into account everytime a connection is about to be established between two ports (in context of their instance or reference), to actually continue or cancel this operation.

This business logic is launched everytime an interactive command or a programming interface (API) triggers an operation of functional/logical connection creation.

The functional/logical connection creation operation means:

A connection is established between two ports; each port being in context of its reference or of an instance coming from its reference.

There are two different possible patterns relatively to the functional or logical connection:

• Sibling: the connection links two ports of two instances located under the same reference.

• Parent/Child: the connection links two ports of a reference and of an instance (located under the previous reference).

The business logic behavior is illustrated below (with the logical domain on the parent/child case):

This section describes the objects defining the PLM opening: its global information, its kind of input object, its context object parameters.

The Business Logic can be invoked for at least the listed PLM Component Type. It means that your implementation can safely use the PLM attributes of the default PLM Component.

Since the Knowledge scripting technology supports inheritance, the actual component type may be any type that derives from theses two PLM Core types. Hence additional attributes defined by the inheriting types may be accessed depending on the context of the operation.

Let's implement the following rule (on the logical domain): The logical connection can be created only if the implied entities shares the same value for 'V_description' attribute.

To achieve this particular business logic implementation, a CATRuleExit file, known as family, declares the script to run everytime a logical connection is about to be established between two logical ports:

<Scripts>
     <Script OpeningID="FLConnectionCreationCheck"
             Type="RFLVPLMLogicalCustomizedPort"
             ScriptName="CATMyFirstConnectionCreationCheckRule" />
</Scripts>

This family tells to run the script CATMyFirstConnectionCreationCheckRule whenever a connection creation operation is launched with a logical port of PLM type RFLVPMLogicalCustomizedPort. This script is a CATRule file that contains the following business logic implementation:

let AssociatedConnectable(PLMEntity)
let TargetConnectable(PLMEntity)
let TargetPort(PLMEntity)
let Connection(PLMEntity)

set AssociatedConnectable = Parameters->GetAttributeObject("AssociatedConnectable")
set TargetConnectable = Parameters->GetAttributeObject("TargetConnectable")
set TargetPort = Parameters->GetAttributeObject("TargetPort")
set Connection = Parameters->GetAttributeObject("Connection")

if ((TargetPort.V_description == ThisObject.V_description) and (AssociatedConnectable.V_description == TargetConnectable.V_description) and (TargetPort.V_description==Connection.V_description))
{
   Validation = true
}
else
{
   Validation = false
}

if (Validation == false)
{
   Parameters.Message = "The logical connection cannot be created since the implied objects description is not compliant."
}

None