Allows mapping of remote operation arguments to input values,
including all nodes of a composite graph.
The Input Mapping screen includes an input mapping
figure that allows the MBO developer to work with input mappings in these ways:
- Add a link from an MBO to an argument structure, and individual
mappings from attributes into sub-arguments are added based on matching name and
type. Some automatic mappings may be added incorrectly, for example, if you had
changed the name or data type of attributes.
- Removing a link from an MBO removes all individual mappings from
the attributes of the MBO.
- Add or remove individual mappings from attributes into
arguments.
- Add or remove mappings from Personalization Keys into arguments
or argument structures. Dragging the argument or argument structure to the left
hand side and dropping it onto the Personalization Keys folder opens the New
Personalization Key wizard, with the type defaulted to match the argument type.
Finishing the New Personalization Key wizard creates the Personalization Key,
and adds a mapping into the argument.
- Add or modify Personalization Keys in the WorkSpace Navigator,
and the changes will be reflected in the Input Mapping tab.
- Add or remove mappings from Client Parameters into root
arguments. Dragging the argument or argument structure to the left hand side and
dropping it onto the Client Parameters folder creates a Client Parameter
matching the type of the argument, and adds a mapping into the argument. When
you map a Client Parameter into an argument, the type of the Client Parameter is
changed to match the type of the argument. You can add or modify Client
Parameters on the Client Parameters tab, and the changes will be reflected in
the Input Mapping tab.