Try Extending ApplicationProfileSetup available activity to show some sort of Stream with custom alert code inside it.

This is an extension activity which gets called on launching portal after login.

Let me know how it goes.

We can include the javascript in the Harness of the Case Manager portal and show the popup using the script.

Also please find the below article which might be helpful.

https://collaborate.pega.com/question/auto-launch-modal-popup-upon-screen-load

Hi Ashfaaque,

Are you able to implement this requirement? We are implementing the similar requirement in our project and tried multiple approaches:

1.) Creating a default dummy access group,portal,harness , section of the popup window and trying to switch the access group of the operator in ApplicationProfileSetup

2.) Trying to use show-Harness OR pxlaunchHarness activities in ApplicationProfileSetup but nothing seems to be working.

Can you let us know what approach are you trying

1. Inside your harness, in any section add a button control and give any Test ID (like I have used "ScreenLoadModalButton"). Then add an event as Click and action as Launch Action. Mention the flow action which will be shown as modal popup on the screen. Make Visibility of the button as Never and Reserve space when hidden as checked. Else you can use visibility:hidden; to make it not visible on screen.

2. Create a js file with the following piece of code:

     $(window).load(function () {               document.querySelector('button[data-test-id="ScreenLoadModalButton"]').click();            });

3. Add the js script in Scripts and Styles tab of the harness where you have this section with modal popup.

4. Now launch the portal. On launch itself you should get a modal popup. You can also use Log Off action in the Cancel Button which will make the user logged off from the portal on click of Cancel.

Hi Sandeep,

For me it is working perfectly. Can you share the screenshot of your section where you have configured the modal and also the area in the harness where you have placed this section.

Also, are you testing the output from the Developer id? or any id other than Developer. With Developer id I meant id having SysAdm4 role in it. If you test from id having SysAdm4 role in it this should work. Operator ids not having SysAdm4 role will not give the desired output since they don't have pxTestID privilege in their ARO. To make this functionality work in ids other than developer add the pxTestID privilege to the ARO in their role. Then this should start working.

Regards,

Arpan