[doc issue] Expected mapping example targets only first element sourcePath":"$.members[0].value"

[GunomeMidare]

Issue description

Should the expected mapping code syntax not be:
{
"sourcePath": "$.members[*].value",
"preserveArrayWithSingleElement": true,
"optional": true,
"targetPath": "$.members[?(@.value)]",
"functions": [
{
"function": "resolveEntityIds"
}
]
},

The "sourcePath": "$.members[0].value" targets only value of the first element in the members array....

Feedback Type (Optional)

incorrect statement

Page Title on SAP Help Portal (prefilled)

Configure Single and Multiple Origins

Page URL on SAP Help Portal (prefilled)

https://help.sap.com/docs/cloud-identity-services/cloud-identity-services/target-configure-single-and-multiple-origins?locale=en-US

[sap-doc-bot]

Thank you for your valuable feedback contribution, @GunomeMidare! So that we can recognize your contribution in the SAP Community, please check your SAP Community user ID (this is a number) in your personal settings page and share it with us in a reply to this comment. Make sure you just include the number in the reply.

Your user ID is displayed as follows:

Change display name for User ID N

where N is your user ID. For example, 53 is the user ID of the user 'qmacro'.

Please note that we are currently refactoring our profile and badge system on the SAP Community, and will start assigning badges again when that's complete.

[IvelinaKiryakova]

Hi,
Thank you for your feedback.
Using [0] in "sourcePath": "$.members[0].value" is valid for the specific scenario described in the note above. In the case of provisioning users with multiple origins, the goal here is to demonstrate how applying a function to one object results in two objects on the target system.

You can use [*] to access all elements in the members array, but that would represent a different scenario, and it would not be appropriate and won't work for this particular example.

Hope this helps.
Best regards,
Ivelina

[GunomeMidare]

Ok, but when performing testing with multiple user assignment to a group the "$.members[0].value" only assigns 1 user and leaves out the other user assignments when provisioning. That is not the intended behaviour I was looking for...

[IvelinaKiryakova]

Hi,
Thank you for reaching out again.
Could you please clarify the behavior you're expecting? The example in the documentation targets provisioning users with multiple origins. Does your testing scenario require provisioning a user with multiple group assignments in addition to multiple origins?

Best regards,
Ivelina