Mapping configuration
Parameter propagation mechanism (deep copy, no copy, PODataMapping) is configurable at domain level or per TP in Fulfillment Provisioning Catalog. Each TP can use a different mechanism.
PO Forward Mapping and PO Backward Mapping instances are defined in files loaded at Fulfillment Provisioning startup. Extension is *pdm. It has same format as datamapping files for cartridge work orders (*.dm). In *pdm file, each section describes both forward and backward mapping :
PO_MAPPER:Activate.Voice
[
MAP_FWD
[
// here instruction for forward mapping
]
MAP_BWD
[
// here instruction for backward mapping
]
]
When PO Mapping is selected, an instance of PO Mapper associated to the target TPO is invoked using the engagement policy defined previously. If the PO Mapper instance supporting the data transformation for a source TPO does not exist, the mapping is ignored but the process continues.