I have received a hint / question from a client regarding the count of user sessions in Pulse when a user is logged on to PAW. The question is, if multiple widgets within a PAW workbook are counted as sessions individually, leading to an incorrect number of displayed user sessions in Pulse.
PAW uses the REST API to connect to the TM1 Server, which introduced a Session ID as consequence of this change, the Thread ID is shared amongst various sessions, which before the introduction of the REST API was the unique identifier for the user’s sessions. The current Pulse 5.x uses the old TM1 API in order to connect to the TM1 sever, this API only provides data regarding the Thread IDs.
Pulse 6 with the use of the REST API will fix this situation.