Share all details about your problem, including any error messages you may have received.
Hello Everyone,
We are trying to include a read only form in the approval work item which will be available to the approvers as a “View Form” Button. The provisioning form that will be available to the requester during the access request submission, will be shown to the approvers during the approvals. The selections for different applications will be shown to approvers in separate sections for application. The Manager would see the selections for all the applications made during the access request. However, the entitlement owner will see the selections only for the application related to them. We are using the question object from the workflow case and approvalItem object from the work item to determine for which application the selection is for. We are using a provisioning approval subprocess.
Questions:
Can we have the questions separated, based on the entitlements? Because some of the applications would have entitlement specific questions. Currently the question object does not give us the info for which entitlement this question is, to compare against approvalItem? Is there any approach we can use?
The form shown to the approver are read-only form and they cannot make changes to the form. However the form has a save button which is OOTB and that cannot be removed through code. This is actually misleading. Is there any way we can remove that save button.
The “View Form” button on the approval workitem, needs to be made more prominent by changing the background color of the button or making the letters bold. Is there any way we can do that?
I do not have any plugin handy, but please go through the plugin documentation provided by Sailpoint for plugin development. It is an easy Plugin, ad you are just hiding few buttons, try it yourself, if you face issues. let me know, and we can troubleshoot and fix it
Hi Naveen! I stumbled upon your response just now. I guess to clarify, is there already a plugin available for this? Or is this something that’d have to be custom built?
Hello Rounak, I wouldn’t try to derive the entitlement directly from the workflow-case Question object. Provisioning-policy fields are stored as questions on the provisioning project after the plan is compiled, while the ApprovalItem objects are built from the provisioning plan. IIQ doesn’t maintain a reliable one-to-one link between them, especially when multiple entitlements for the same application use the same provisioning form.
Use the approvalSet available on the current work item to determine which requested items that approver is reviewing. In the standard flow, the manager receives the full approval set, while the owner approval stage builds the relevant approval items for each owner.
For entitlement-specific questions, you will need to capture that relationship while building or processing the requester form. Store the answers in a workflow map using the same values available on the approval item, for example application, attribute name and requested entitlement value. Include the account or native identity as well when the application can have multiple accounts.
Then build the read-only approver form from the current work item’s approvalSet. Manager sees all matching answers, each entitlement owner sees only the answers matching their approval items. If that association isn’t stored earlier, IIQ can’t reliably reconstruct it later from the Question object alone.
@naveenkumar3 is right, a plugin is the way to go for Q2 and Q3.
For the Save button, readOnly=true only controls whether the form fields can be edited. The Save button in your screenshot is part of the OOTB modal footer, not a button defined inside the Form XML, so changing the form definition won’t remove it.
A small plugin snippet with a scoped stylesheet is a good approach here. Load the CSS only on the work-item page using the snippet’s regexPattern, then target the specific View Form modal and hide its Save button. Avoid using a generic selector like .btn-primary, otherwise other buttons on the page may also get affected.
The same stylesheet can make the View Form button more visible by changing its background or font weight. No Java classes or REST endpoints needed for these CSS-only changes. You just need the plugin manifest and stylesheet packaged as a plugin ZIP and installed through the Plugins page. I’d confirm the exact selectors in browser dev tools on 8.4p2 before finalizing, since the rendered HTML can differ between patches.
