# Modifying "View" Button Work Items Page

**URL:** <https://developer.sailpoint.com/discuss/t/modifying-view-button-work-items-page/218553>\
**Category:** IIQ Discussion and Questions\
**Tags:** identityiq, work-items\
**Created:** [August 10, 2026, 12:34pm UTC](https://developer.sailpoint.com/discuss/t/modifying-view-button-work-items-page/218553 "2026-08-10T12:34:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![cantasasiz](https://avatars.discourse-cdn.com/v4/letter/c/e9c0ed/32.png) [@cantasasiz](https://developer.sailpoint.com/discuss/u/cantasasiz)\
**Post date:** [August 10, 2026, 12:34pm UTC](https://developer.sailpoint.com/discuss/t/modifying-view-button-work-items-page/218553/1 "2026-08-10T12:34:08Z")

</div>

Hello Everyone,

I have an issue about “View” button on Work Items Page. When I right click this button, there is no option to open new tab on any browser. When I inspect from browser devtools, this button call scripts not links. In this situation, how can i modify “View” button on Work Items page as being open new wab on browser? or Do you have any ideas to fix this problem?

Thanks&Regards,

Can

---

<div class="post-metadata">

**Author:** ![punna0001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/punna0001/32/42011_2.png) [@punna0001](https://developer.sailpoint.com/discuss/u/punna0001)\
**Post date:** [August 10, 2026, 3:56pm UTC](https://developer.sailpoint.com/discuss/t/modifying-view-button-work-items-page/218553/2 "2026-08-10T15:56:48Z")

</div>

Hello Can TASASIZ. The View control uses a scripted action rather than a normal `<a href>`, which is why Ctrl or middle-click doesn’t offer “open in new tab”.

One option is to use IIQ’s documented direct work-item URL:

`https://<host>/identityiq/ui/rest/redirect?rp1=/ui/index.jsf&rp2=commonWorkItem/<workItemId>`

IIQ notification templates also use the hash-fragment form:

`https://<host>/identityiq/ui/index.jsf#/commonWorkItem/<workItemId>`

with:

`$spTools.formatURL('/ui/index.jsf#/commonWorkItem')/$item.id`

If you want the View action itself to behave like a normal link, I’d suggest using a [plugin snippet](https://developer.sailpoint.com/docs/iiq/plugin-developer-guide/manifest/). You can scope the snippet to the Work Items page using `regexPattern`, get the work-item ID for each row, and either replace the View action with an `<a>` or add a separate “Open in new tab” link using `target="_blank"`.

A similar plugin approach has been used to [modify OOTB Work Item actions](https://developer.sailpoint.com/discuss/t/remove-forwarding-option-ui-button-from-access-reviews/80610). An SSB XHTML override may also work, but it would be less upgrade-safe and may require reconciling changes after IIQ patches or upgrades.

I would first verify whether it is the work-item type. SailPoint’s [direct-link documentation](https://documentation.sailpoint.com/identityiq/help/lifecycle_manager/create_direct_links_to_iiq.html) lists Forms, Approvals, and Request Violations as supported for this route. Other types, including manager access reviews, may need to use the desktop page instead.

---

<div class="post-metadata">

**Author:** ![naveenkumar3](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/naveenkumar3/32/39339_2.png) [@naveenkumar3](https://developer.sailpoint.com/discuss/u/naveenkumar3)\
**Post date:** [August 11, 2026, 1:07am UTC](https://developer.sailpoint.com/discuss/t/modifying-view-button-work-items-page/218553/3 "2026-08-11T01:07:27Z")

</div>

Hi Can,

There is no Option for OOTB, to open in a new window, but can be achieved by using a plugin .

Write a small plugin to inject at workItems,jsf page and write a js to Add a new icon/button such as:

- 🔗 Open in New Tab .

---

<div class="post-metadata">

**Author:** ![cantasasiz](https://avatars.discourse-cdn.com/v4/letter/c/e9c0ed/32.png) [@cantasasiz](https://developer.sailpoint.com/discuss/u/cantasasiz)\
**Post date:** [August 11, 2026, 6:44am UTC](https://developer.sailpoint.com/discuss/t/modifying-view-button-work-items-page/218553/4 "2026-08-11T06:44:57Z")

</div>

Hi @naveenkumar3 and @punna0001 ,

Thanks for your priceless support. I will try offered solutions.

Can

---

<div class="post-metadata">

**Author:** ![kallajayaram](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kallajayaram/32/35609_2.png) [@kallajayaram](https://developer.sailpoint.com/discuss/u/kallajayaram)\
**Post date:** [August 20, 2026, 4:12pm UTC](https://developer.sailpoint.com/discuss/t/modifying-view-button-work-items-page/218553/5 "2026-08-20T16:12:23Z")

</div>

Hi @cantasasiz

If the View button is calling JavaScript instead of using an `<a>` link, that is probably why you don’t get the browser option to open it in a new tab.

I would first check the JavaScript/function behind the View button and see what URL or action it is triggering.

If it is ultimately opening a specific IIQ URL, you could create a custom link/button and use `window.open(url, '_blank`’) to open it in a new tab.

I would avoid changing the OOTB JSP or JavaScript directly, as those changes could be lost during an upgrade or patch.

If you can share the JavaScript/function called by the View button, we may be able to identify a cleaner way to customize it.

---

<div class="post-metadata">

**Author:** ![neel193](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/neel193/32/34038_2.png) [@neel193](https://developer.sailpoint.com/discuss/u/neel193)\
**Post date:** [August 24, 2026, 7:41am UTC](https://developer.sailpoint.com/discuss/t/modifying-view-button-work-items-page/218553/6 "2026-08-24T07:41:49Z")

</div>

@cantasasiz If you want to open workitems in different tabs just for viewing purpose that should be fine. You can go ahead with the plugin.

But in case you are expecting workitems owners to take decisions on these tabs, there is a risk that changes in tab will override the other open workitems and you may see unexpected outcomes. It is not recommended to edit same object types in multiple tabs of the same browser to avoid this risk.
