Hello Sunil,

I think you might have done little R&D on tracing the code while switching the app from designer studio. As we all know, the ApplicationSetup is being called and the other inner activities are used to set some of the initial stuff like portals, properties, threads etc. From these collection of activities, we have call to Code-Security.ApplicationProfileSetup and is basically allowed to extend or do the customization from the customer side changes. Even in our apps also, we did change this activity instead of main activity: ApplicationSetup. But, ours is a different story compared to your requirement. Based on my understanding with your requirement, I think the same activity: ApplicationProfileSetup can be changed with all your logic. As we are using our apps since so long time, we didn't see any issues after making the changes as I mentioned above and I think we took the suggestions from Pega on this earlier too. To me, you can think in that direction but let's wait & see how Pega experts recommend in this context.

Thanks,

Ravi Kumar Pisupati.

>> >we have an entitlement system,which maintains user attributes like Access Group,Workbaskets,Skills,Roles and Work Group for a user.All these attributes are assigned to a session at the time of login.

• customizing ApplicationSetUp and ApplicationProfileSetUp would work during the login time.

>>> While the user switches the access group,we want the other attributes like workbaskets,skills,roles and work group assigned during the login to get wiped off and set to new values.Its mostly like re-running the authentication activity again.

• RedirectAndRun is the activity that would be called which consider AccessGroup parameter.
  • Call ApplicationFreeClipboard is the extension activity where we could feed our customization.
• so I doubt in switch application use case - customizing ApplicationSetUp and ApplicationProfileSetUp would work or not.

Please correct my understanding post your observations, Thank you!

psahukaru