We have custom attribute named "BO" (for BusinessOwner) directly on the entitlement. We would like to use this information as resource userid of the of the user. This field is populated in PostProcessor method of Entitlement Collector with the id of user.
The tricky part is, we may have multiple BOs for an entitlement. Therefore, we need to understand if we can set multiple BOs to the corresponding entitlement attribute in concatenated form (ex: BO1;BO2;BO3) or do we have to set only 1 BO name to this field?
As explained in this answer when you use an SQL select node, even if your query returns set of attributes you are able to use a single workflow variable to pass multiple user information as resources. How about above mentioned scenario?