-
Open an
MQL window.
-
To create the
Derived Output Parameter object, execute these commands:
set context user creator;
add bus "Derived Output Parameter" <DOP-NAME> <REVISION> policy "Derived Output Parameter Policy"
vault "eService Production";
Where <DOP-NAME> is the name you define for the object and <REVISION> is the revision level.
- To modify the
ECADInteg-GlobalConfig object to use the Derived Output Parameter object, execute these commands:modify businessobject "ECADInteg-GlobalConfig" CadenceAllegroGlobal TEAM
"IEF-DerivedOutputTypeDefaultParameterObjectMapping"
"<DO-NAME>|Derived Output Parameter,<DOP-NAME>,<REVISION>";
modify businessobject "ECADInteg-GlobalConfig" CadenceAllegroGlobal TEAM
"IEF-DerivedOutputParameterObjTypeMapping"
"<DO-NAME>|Derived Output Parameter"; Where: <DO-NAME> is the name of the type that will use the Derived Output Parameter file when generating derived output.<DOP-NAME> and <REVISION> are the name and revision of the object created in Step 2. - To check the javascript file into the
Derived Output Parameter object, execute these commands:tcl;
cd <path to DOP file>
exit;
checkin businessobject "Derived Output Parameter" <DOP-NAME> <REVISION>
format generic append "<DOP-Name>-<DO-Name>.js"; Where: <path to DOP file> is the location on the server where the javascript file is stored<DOP-NAME> and <REVISION> are the name and revision of the object created in Step 2.<DOP-Name>-<DO-Name> is the name of the javascript file that conforms to the required syntax.
- If the javascript file requires supporting files, execute this command for each file:
checkin businessobject "Derived Output Parameter" <DOP-NAME> <REVISION>
format generic append "<FILENAME>.<EXT>";
|