We are working on a custom report on IdentityEntitlement filter, and the requirement is to create a custom column in report from debug, get the “value” of the IdentityEntitlement to this column, perform some calculations in this column renderScript.
We are able to achieve this by adding new ReportColumnConfig entry. However, this column should not show up in the list of columns in the Report UI and also in the report results obviously.This is like a temporary column to perform few customizations to write logic to save a custom object, create a custom audit etc. You may ask to write this logic in any other visible column, but if the user selects that column to not display in report results, then that logic will not be executed!
Hence, we need a custom temp. column which should be executed always and doesn’t show up in columns list or report results.
Thanks for your suggestion. We have tried this already, when we put hidden=”true”, that column is being hidden in the UI and report results, but its renderScript logic is not being executed! We need that logic to be executed here..
Use-case: We implemented custom audit creation and updates to a custom object for every row when the report is executed. The logic is placed in the “classifications” column, where the renderScript retrieves the IdentityEntitlement value and performs the required custom processing.
However, the business team is excluding this column from the report. When the column is not included, the renderScript associated with it is not triggered, and therefore the custom logic does not execute. As a result, the expected custom audit records are not created or updated.
Hi @Harikrishna_06 , Yes, we can do that, but we parked it for worst case. As we don’t want to restrict the requester to stop from hiding any column. We cannot make any column mandatory in the script though.
Hi, the concern is that in iiq the renderScript only runs if the column is actually included in the report output. Since users can hide any column, the script may not always execute, so it might not be reliable for this use case.
@jairam_lankala Is your data which you want to store in audit or custom, depends on any of the column details? If not, you can try setting this in QueryScript.
You can inject your logic and return the query object as is without changes.