This section provides the following procedural standards for maps:
If the attribute mapping does not include relationship
management,
copy the source attribute to the destination attribute (see "Copying a source attribute to a destination attribute").
- Important:
- Do not map the
ObjectEventid attribute. InterChange Server Express reserves
the ObjectEventId for its own processing purposes. Any
custom code that has ObjectEventId as destination attribute will
not execute properly.
Attribute comments can improve the readability of your map. However,
Map Designer Express does not automatically generate a comment for
an attribute. Table 15 provides some suggested standards for attribute comments
based on the type of transformation associated with the destination
attribute.
Table 15. Settings for the Attribute Comment
Situation
| Setting for Attribute Comment
|
If the child business object is not mapped
| =No mapping
|
Set Value transformation
| =SET VALUE(value)
|
Move transformation
| =MOVE
|
Join transformation
| =JOIN(srcAttr1, srcAttr2,
...)
|
Split transformation
| =SPLIT(srcAttr[index])
|
For
child business objects, when the mapping is done without calling a
submap to indicate the object has to be expanded to see its attributes
| =Mapping here
|
If the code to call the
submap is generated
| =SUBMAP(mapName)
|
Custom transformation that is not one of those listed above
| =CUSTOM(summary)
|
If the attribute's code does not contain anything except setting the
verb
| =SET VERB
|
