there is no easy way to accommodate this requirement.
As the OOB Approval Configuration uses the Manager of the User, a custom Approval process would need to be created, and the values from the Service Request questions pushed down to the SRM:Request form for use in the custom Approval process.
This however would be be tricky with the GetNextApprover and Prep rules in the custom Approval process to define and configure to be exactly what you needed for 10 different Users.
The OOB solution using the On Behalf Of feature would at least track each request to an individual User and pass auditing concerns, although it means 10 separate requests to be submitted.
I think I've found an appropriate idea to solve my problem:
I developed an advanced interface form where the "requested by" user can select multiple "requested for" uses. all selected users are stored in another regular form. (similar to the example "multiple IMCD requests")
when the user presses the submit-button for all users stored in the "hidden form" a new service request should be created. (each service request having the manager of "requested for"-user as approver.
I have read a few things up to know and it seems SRM:AppInstanceBridge is the right form to push service requests to.
Is this correct, and is there any recommendment how to "manually" create service requests from other AR-forms or workflow?
any ideas appreciated!
you might want to look into having a standard SRD for this type of request, with the appropriate Approval, and then submit multiple entries using the SRM Interface form to this SRD passing in the appropriate User details.
You can "hide" this from the public (using Entitlements) and still use it in workflow from the AIF form. That way if you needed to modify the process at any stage, you have the standard editing tools available.
The thing to note here is that the SRD that the AIF will be attached to will need a backend fulfilment process, therefore you may end up with an additional fulfilment record (IM. WO or CHG) for the whole series of requests.
You could somehow incorporate the first selected user to be used with the SRD/AIF combination using workflow from the AIF, then you would only need to generate the additional requests (up to 9)