<TBL-x-Revision_Index>
<basic>revision</basic>
<rel>none</rel>
<iterative>false</iterative>
</TBL-x-Revision_Index> |
Newly introduced for TBL (table) Acrofield fields, the TBL-x-
notation provides a generic way to map fields between 3DSpace and
the PDF Rendition Document Template file that is Revision sequence type independent.
Using the -0- (for Revision 0 ) implies that we are locking in the mapping to Numeric
only Revision fields that Document Business Objects must use to gain mapping of TBL
fields (same applies to use of -A- locking into Aphabetic Upper Case Revision mapping
only). In this exampleTBL-x- means that Acrofield named ending with
Revision_Index will be mapped to the Controlled Document Business
Object property revision, but governed by Revision level. This
encapsulated in an element named <basic> – since it is a basic
property of a Controlled Document business object. Its value can be obtained directly
and so the need for a relationship specification <rel> value is
none. Since this is a single value, <iterative>
is marked false. |
<TBL-0-Release_Date>
<attribute>attribute_EffectiveDate</attribute>
<rel>none</rel>
<iterative>false</iterative>
</TBL-x-Release_Date> |
This node with its child elements maps the Any row Acrofield named
Release_Date to the Controlled Document Business Object attached
attribute Effective Date. The use of -0- means that the mapping is
limited to numeric Revision Sequences only. The encapsulated in element named
<attribute> infers that the mapping is to an attribute that is
used by the Controlled Document business object. Its value can be obtained directly
and so the need for a relationship specification <rel> value is
none. Since this is a single value, <iterative>
is marked false. |
<TBL-A-Approvers_Names>
<prog>ENODOCORenderPDF</prog>
<method>getCAApprovers</method>
<arg>objectId:id</arg>
<basic>Approver(s)</basic>
<rel>none</rel>
<iterative>true</iterative>
</TBL-A-Approvers_Names> |
This node with its child elements maps the Any row Acrofield named
Approvers_Names to one or more Approvers via Controlled Document
Business Object id and a JPO method whose output is used to extract the names of the
Approvers. Because of the use of -A- in the parent node name, this field mapping
demands that the Revision sequence is Upper Case Aphabetic in order for the mapping to
occur. Any Acrofield row named Approvers Names that is specified with
prefix of TBL-A- to TBL-Z- for example, will be mapped to a list of Approver(s) that
is obtained thanks to a Program (JPO) known as ENODOCORenderPDF and whose method is
getCAApprovers whose input argument is id. There is no relationship
involved so this is set to none. This is, however, iterative because
there are going to be multiple Revisions involved in the response from this method,
that will return a List of Maps (meaning there can be a list of Approvers per each
Revision). |
<Document_Title>
<basic>id</basic>
<attribute>attribute_Title</attribute>
<rel>relationship[Active Version].to</rel>
<iterative>true</iterative>
</Document_Title> |
Here we have a single/standalone Acrofield named
Document_Title that is being mappped to the Title
attribute on an Active Version, and this Title attribute is retrieved
by means of a relationship named Active Version from the Parent
Document Business Object and we are going from the Business Object to the Version
Object via this Active Version relationship. Now because you can have
multiple Active Version relationships per Document Business Object, this is iterative,
and the appropriate Title will be picked based upon the Version's object id (the
<basic> element here). |
| The header and footer of this file
are <AcroField-Enovia-Mapping>
<Insert
your nodes as above here – indented./>
</AcroField-Enovia-Mapping> |