After sailpoint iiq upgrade 8.4 in workitem approve/reject button not visible

IdentityIQ (IIQ) IIQ Discussion and Questions
1

After sailpoint iiq upgrade 8.4 in workitem approve/reject button not visible

2

@malarvanan12

Have you executed the upgrade_identityiq_tables script?

3

@malarvanan12 Check logs once you hit the page. See if there is some error getting generated. Also make sure that upgrade is completed with all the steps.

Thanks

4

it is not visible for particular workitem not for all

5

Here, It is one specific object/xml of WorkItem or one of the type of WorkItem ?

6

It is for one specific WorkItem (Manager approval), not all WorkItems. Other approval WorkItems of the same type are showing Approve/Deny correctly. Only this particular WorkItem does not show action buttons. The

7

Can you check the impacted xml of that Workitem ID and compare it with another. If any tag is missing.

8

not much info , both looks same, issue is only with - Manager Approval workitem

9

Can you share the screenshot for both?

10

image
image1506×291 20.6 KB

11

@malarvanan12

Are you able to see any exceptions in the sailpoint.log or catalina.out log?

12

Nope , no errors found

13

It could be some issue with the user. if it is not showing for any other workitem, all the workitems are showing approve/deny buttons to the approvers, it could be one off. May be could be when that person is submitting, a restart was performed of the application or could be other thing. if there is no error in the log, when you open it. It could be one off, and your system is working fine.

14

any update? having same issue.

15

@malarvanan12 @luisadrian17 Could you please try few things:

  • Have you tried forwarding the same work item to a new approver and see if they are able to approve/reject?
  • How are you validating? Are you login using the manager’s account and seeing it?
  • Please confirm if you have made customization to your commonWorkItem.xhtml file and to your LCM Workflow? If yes, you might want to review them after the upgrade.

Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(:heart:, :+1:, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

16

In my case, it turned out to be a cache issue. I had users try from a different browser and it worked fine. Seems the upgrade changed something with the existing cache so clearing it fixed this UI issue.