Approvers

You can

• add a custom field to the PersonWantsOrg and ShoppingCartItem table (CCC_UID_PersonApprover)
• Fill this field during product selection in the WebFrontend. Requestproperties in V9+ should provide reasonable selection mechanisms and filter criteria. With WebDesinger you likely need a custom component.
• Have a custom ApprovalProcedure (plus workflow and policy), that selects the content of the field as approver

I have not had the case where multiple approvers needed to be selectable. In theory that should be possible with a multi-value field, but configuring the selection and approval procedure might might much more complicated.

You probably want a few sanity checks or additional approval steps in those usecases. I also recommend configuring timeouts for such workflows, as "random" approvers tend to ignore such requests.

A few usescases where I had similar requirements:

• Product to select a new Responsible/Sponsor for an external
• Request that need to approved by "the workers council" but no way to figure out automatically who the specific workers council (group) is responsible

Thank you for advice. We do some change but in second paragraph we can`t add custom component.

Can you help us with this? Maybe some advice in guide can help us.

• Fill this field during product selection in the WebFrontend. Requestproperties in V9+ should provide reasonable selection mechanisms and filter criteria. With WebDesinger you likely need a custom component.

I recommend studing the relevant documentation:
https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.2.1/it-shop-administration-guide/9#TOPIC-1802244 or
https://support.oneidentity.com/de-de/technical-documents/identity-manager/9.1/it-shop-administration-guide/9#TOPIC-1875079

Note that the "old" WebDesigner Portal only supports the "obsolete definition" way for request properties.
You can be more flexible in WebDesigner with Product-Dependent references and custom components. But this is a more involved customization, I would recommend to contact your sales representative or your implementation partner for that. For a simple person-search, the standard request properties (even obsolete) should be enough.

You might want to search the forum for "request properties", it is disussed a few times. Namely the folloing page might fit your case roughly: www.oneidentity.com/.../request-property-and-data-from-personindepartment

I recommend studing the relevant documentation:
https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.2.1/it-shop-administration-guide/9#TOPIC-1802244 or
https://support.oneidentity.com/de-de/technical-documents/identity-manager/9.1/it-shop-administration-guide/9#TOPIC-1875079

Note that the "old" WebDesigner Portal only supports the "obsolete definition" way for request properties.
You can be more flexible in WebDesigner with Product-Dependent references and custom components. But this is a more involved customization, I would recommend to contact your sales representative or your implementation partner for that. For a simple person-search, the standard request properties (even obsolete) should be enough.

You might want to search the forum for "request properties", it is disussed a few times. Namely the folloing page might fit your case roughly: www.oneidentity.com/.../request-property-and-data-from-personindepartment