Best Practice for Customizing a Report (Access Request Report)

[MuhammadMustafa]

Which IIQ version are you inquiring about?

IIQ 8.4

Please share any other relevant files that may be required (for example, logs).

iamaccessRequestStatusReport__.pdf (49.6 KB)

Share all details about your problem, including any error messages you may have received.

Currently, the environment follows a 3-Level Approval system (Application Owner, Workgroup and Manager) for access requests. The customer expects an access report that includes all access requests, with details of approvals, including intermediate approvals, reflected in the report.

For instance, in the case of a user named Susan King(PFA the report attached for reference), whose request is pending final approval, the current awaiting stages are not showing up in the Access Request report. In other scenarios, when all the approvals are completed for a request, the intermediate approvals that occurred for them are not populating the report.
We need the report to include all approval stages—those that have already been approved, as well as any requests still awaiting approval—for the same access request.

We would appreciate your opinion on best practices and workarounds as well.

[Arun-Kumar]

Hi @MuhammadMustafa,

The OOTB Access Request Status report is designed with a Java datasource, which limits customization options, especiallyincluding all the approval details. If you want to include extra information or data in your report, you’ll need to explore a different solution.

One effective solution is to utilize an HQL datasource with the IdentityRequest object. By doing so, you can create a custom report tailored to your specific requirements.

<DataSource objectType="IdentityRequest" type="Hql">

Using the IdentityRequest object allows you to access detailed approval summaries associated with each request. From these summaries, you can extract relevant information about the different levels of approvers involved in the process.

Regards,
Arun