850_update_bulletin - Progress Sonic Product Update Bulletin 8.5

Improvements for Responsive Business Integration: Sonic and DataXtend SI
marked as "collection = true", represents a collection of values and is rendered as
parameters[] {xq:paramHolderType}. In the response mapping page, you can define a
mapping rule for such interface parameters and state whether the collection of values are
to be added as:
● New Message Parts
● New Message Headers
● New Process Context Properties
As part of the DataXtend SI service, the typed service works on the request interface
parameters and set the output context that is output parameters from service context. You
should ensure that these output parameters are propagated to the next in-flight process
message; that is, the message going out of the service. To achieve this, you must define
response mapping rules from service output parameters to next in-flight process message
constructs; that is, headers, parts, and process context properties. In the event of a service
fault, XQmessage is added to the service fault box and the fault context is set; that is, fault
parameters for the given operation are specified. You must define fault mapping rules to
ensure the fault parameters are propagated in the fault message.
In the mapping pages, the mapping rule for interface parameter with a collection of values
is displayed. However, at the time of process run, this mapping rule is evaluated for each
collection element. This is indicated to runtime by adding the following syntax to source
participant expression: ${esbdl.output'purchaseOrders'.each}
On the target side, pattern/expression is evaluated for every collection element and
generates a unique identifier for the given XQMessage construct type (Part, Header, and
Process Context property). This construct is initialized with the service response
parameter value (after applying transformation actions).
You can also configure the mapping rule with transformation details. This transformation
action is applied to each element in the collection. For configuring transformation action,
all supported transformation actions are listed. You must correctly configure the
transformation actions. Also, because the source parameter is a collection of unknown
values, configured transformation action might or might not be applicable for every
element in the collection. You can further configure transformation details for the
mapping rule. Available transformation actions are filtered on the basis of type and
content type of source interface parameters.
Sonic 8.5 has changed the following dialog boxes to provide for the collection values:
● Mapping Rule Participants dialog box — While specifying the target,
pattern/expression is evaluated for every collection element and an unique identifier
is generated for the given XQMessage construct type (Part, Header, and Process Context
Progress Sonic Update Bulletin 8.5 25