Anyone else experiencing this? I looked through the release notes and didn't see this mention so I am wondering if this is an OnDemand restraint.
No not seen this on 15.5 html portlets.
Do even basic scripts work like the below?
The way I was getting the user’s sessionId no longer works:
var currentSession = window.clarity.session.sessionId;
Which now returns as undefined.
There is the user's Id available:
var currentSession = window.clarity.session.userId;
The User ID is retrievable, but to read a NSQL, a Session ID is required. Is there is way to get that in Clarity 15.5. and above?
Thanks & Regards
If you check the below setting in NSA you will not get it. To make the system secure this was implemented.
Hey Suman, Is there any way to get the Session ID in ondemand environments?
We don't have access to CSA and we've deployed some HTML portlets which our users love because they close some UX gaps in the OOTB functionality.
What I ended up doing was spinning up a simple web service on one of our servers. The portlet calls it with the UserID along with an identity token. The web service lookup up the active session id via a web services query to PPM and returns it to the portlet.
This should be the case in both On Prem and SaaS env:
Marc, while everyone understands this is not (officially) supported, many of us implement HTML portlets to make up for deficiencies in the user experience.
For example, the OOTB experience of using Action Items to (e.g.) approve/return timesheets is not remotely user-friendly. A HTML portlet that calls the Action Item Approvals XOG can significantly improve the user experience, making for happier users.
Removing the ability to create these types of portlets would be a major retrograde step, and seems (much like removing the XOG page) ... punitive.