We have several local actions to be potentially launched upon click in the log-in page.
Each local action loads a pop-up table from a different data page. These tables include links (open work by handle), and icons configured to launch report-definition in pop-ups.
Once the first local action is launched, the table in the resulting pop-up is displayed, and the user clicks on an icon to launch a report definition in a pop-up everything works fine.
After this, we close the current local action pop-up and try to other another one. The other local actions on the home page open but no longer properly launch their respective report definitions, or opening the work-items using the links.
No error is observable in the tracer, but trying to click a link open obj by handle action displays an error on the browser “empty work handle”.
The local action launched initially, which launched the first report definition, still works fine when it’s re-opened.
@BatoulS8 if the documentation about Obj-Open-By-Handle method does not clarify how the product should behave could I suggest that you log a support incident for this and provide the INC reference here to help us track it?
Yes I have opened a support ticket (INC-256999). As mentioned, the open-obj-by-handle is being passed a correct handle and works normally in the pop-up (local action) first launched upon login (whichever one that may be). It is in the subsequently launched local actions that the launch report and open-obj-by-handle stop working.
@BatoulS8 I can see that the support ticket was resolved.
The issue was put down to the use of a custom close button on modal template which was using an action to refresh the harness. This was introducing the loss of context.
Techical root cause is not clear, but using an alternative configuration (Refresh other section in place of harness refresh) resolved the issue.
Since the issue is only occurring when the Refresh Harness is being called the support team looked at some alternative ways to configure this as we did not believe that refreshing the entire harness to update the link labels is the best way to do this.
Some suggestions below.
Regarding the 8.7.4 patch release, please note that this is not an upgrade but a patch with latest fixes for the 8.7.x platform version. As detailed in the Pega software maintenance program documentation Pegasystems expects all clients to stay current. Additionally It is often the case that issues raised as support cases are found to be fixed in later patch releases.
The support eam asked that you test this same on the latest available patch release to first confirm that the issue is not resolved by applying this patch.
The latest patch for the 8.7.x platform is 8.7.4
The 8.7. platform will go into extended support on the following schedule once the final patch has been released July 1, 2023 – January 31, 2025.
Next Steps:
review the suggestion. :
Instead of using Refresh Harness action on the close button can we try using Refresh Other Section and just refreshing the section rather than full harness?
Is there any reason that we cannot submit the local action rather than close it? When you submit a modal flow action there is normally a refresh that occurs so I wonder if we could make use of this to keep the configuration from needing a custom button. For example as shown below could you use the OOTB “Modal Button Submit” (pxModalButtonSubmit) control in place of your current close action? The button can still be labeled as close. There is also a pxModalButtonCancel control which is a newer
Another option could be to use a Run Script action in place of the Refresh Harness and call the OOTB function pega.desktop.infinity.refreshCaseSections. You can pass this the name of a section to refresh and I have had some good results using this with pxButtonModalCancel as shown in the attached screen shot. In this example the HomeMain is the section containing my list of links. I think for you this would be NBA_Dashboard_SBDM. Could we also try this instead of the harness refresh?
