Anonymous_User Absent Member.
Absent Member.
141 views

Integration Activity: Output multiple results to flowdata


I am trying to generate a pick list on an approval form listing all the
group entitlements on an AD driver.

To do this I have an integration activity invoking the getCodeMapValues
resource web service request. (I'm only interesting in the <displayName>
of each of the returned <codemapvalue> nodes in the result.)

In the post activity of the Data Item Mapping for the IA the Web Service
Output Field has the following:

Envelope/Body/getCodeMapValuesResponse/result/codemapvalue/displayName

and the target expression is

flowdata.Activity/Envelope/Body/getCodeMapValuesResponse/result/codemapvalue/displayName

Unfortunately, when i then map this flowdata object to the pick list on
my approval form, there is only one result displayed. On the
pre-activity data item mapping for the approval form I have used
flowdata.getObject('Activity/Envelope/Body/getCodeMapValuesResponse/result/codemapvalue/displayName')
and invoking the size() function on this object indicates it is only 1.

I have been unable to find any method of getting all the values in the
result stored in a single flow data variable. I have been able to get
individual results stored in independent flow data variables by using
multiple occurrences of the web service output field mapped to it's own
target expression but this is not of any use since the number of actual
entitlements returned will vary so I can't set the 'Occurs' value in
advance.

If anyone knows the correct method for storing results involving
multiple nodes in flow data I would be grateful for the assistance as I
can't find any documentation explaining how this can be done.

Thanks


--
KKnowles_Praxism
------------------------------------------------------------------------
KKnowles_Praxism's Profile: https://forums.netiq.com/member.php?userid=538
View this thread: https://forums.netiq.com/showthread.php?t=47692

Labels (1)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.