Compute parameters to Merge Two Branches (EHIMerge_ComputeMergeBranchParameters)

An opening ID is an entry point used to customize business logic. The Compute parameters to merge two branches opening ID is available in the Electrical physical system design resources set and it is used to compute the default properties of the merging branches.

Note: For more information about customization by business rules, see Installation and Setup: Customize: Behavior: Data Setup: Customization by Business Rules.

This page discusses:

General Information

This opening ID is invoked during the Merging Branches command. The computation rule is when merging of the branches starts.

The table below provides you with information related to the definition of the Opening ID.

PLM Opening ID: EHIMerge_ComputeMergeBranchParameters
Customization intent: Computation
Execution context:Client

Input Objects

Input objects must be of the following types:

  • ThisObject: First branch to be merged.
  • Parameters corresponds to the context object. Message attribute will be displayed in a warning if the validation fails.

Context Object Parameters

Parameter NameTypeRead/WriteComments
Branch2Instance (input) PLM Entity ReadSecond branch to be merged.
MergeOnASupport (input integer) PLM Entity Read
  • 0 if the merge point is not a support.
  • 1 if the first branch ends on a support and the second branch ends on a point coincident with the last support point.
  • 2 if the second branch ends on a support and the first branch ends on a point coincident with the last support point.
  • 3 if the first branch ends on a support and the second branch ends on the same section inside the same support.
MergeSegments (output)PLM Entity ReadIf not null, the two segments next to the merge point are merged at the end (default value is 0).
RemoveMergePoint (output)PLM Entity ReadIf not null, the object defining the merge point is removed from branches if it becomes useless (possible only if MergeOnASupport=0) Default value is 0.
RemoveLocalSlack (output)PLM Entity ReadIf not null, the local slack defined on the merge part is removed (possible only if MergeOnASupport=0) Default value is 0.

Message: Standard information to allow specifying a special message corresponding to severity (useful only if severity is not null).

Severity messages:

  • Severity= 0 the treatment is to be continued (no message).
  • Severity= 1 the treatment is to be continued and only a warning raised.
  • Severity= 2 the treatment is supposed to be undone and an error is raised (Merge operation is not performed).