-
Copy the inputs of the parent automation process (the inputs that are defined in the
specifications logic of the parent) to the trigger logic.
-
Define the output lists that the trigger logic must return depending on the inputs
expected by the child automation process (the inputs that are defined in the
specifications logic of the child).
-
Implement the EKL trigger logic code.
It analyzes the inputs of the parent and fills the output lists with the elements to
use as inputs for the execution of the child.
Note:
An administrator can do the following:
- Define a view automation process as child of a sheet automation process to automate
the creation of views under a sheet: create one view for each 3D part under a root
product.
- Copy the inputs of the parent automation process. If we assume that the sheet
automation process is working with a single input which is of type ProductOccurrence for
the root product, the administrator needs to copy that input.
- Define the output lists returned by the trigger logic. If the view automation process
is working with a single input which is of type ProductOccurrence for a 3D part
selection, the administrator needs to define an output which is of EKL type list and
that list must contain ProductOccurrence EKL objects.
- Implement the EKL code of the trigger logic so that it fills the output list of 3D
part occurrences. If we assume that the input of the sheet automation process is the
root product, the EKL code of the trigger logic can navigate on the occurrences under
the root product, identify all the 3D part occurrences, and add them to the output list.
In this way, the execution of the parent and child lets you automate a sheet with
multiple children views under the sheet (one view for each 3D part under the root
product).
|