Failing to persist session data on reload or navigation from one mashup to another

Question

Scenario:
User sets a value that needs to be persisted for the session until the user logs out or sets a new value himself.
 
What's done so far : 
 
1. Created thingshape > added it to the user subsystem > property in the ThingShape is persistent
2. On the mashup there's a text box to accept value from the user > set button which calls the setter service with following code :
 Resources["CurrentSessionInfo"].SetGlobalSessionStringValue({
	name: "unitNumber" /* STRING */,
	value: unitNumber /* STRING */
});
3. There's a label widget on the mashup to show the value set by the user, which calls the Resources["CurrentSessionInfo"].GetGlobalSessionValues which returns a persistent property value unitNumber, set above by the setter service.
4. ServiceInvokeCompleted event from the setter service is bound to the Getter to return this value.
5. This works fine
 
Problem:
Once the mashup is refreshed or user navigates from current mashup to another and comes back, the session value for unitNumber set by the user disappears.
 
Not sure if I am missing any further step to persist this. Could someone please help point my mistake here
 
Thanks!
 
EDIT:
TWX version : 8.4.2

bootstrap · Accepted Answer

Ok I think i found the issue, it is about setting textBox widget value directly with the session parameter. This should not be done, (also noted in that article I added in my previous response)

To make it persistent value need to run through the setter service and not via the Session parameter in the mashup.

VladimirRosu_116627 · Answer

Hi,

If the getter only executes on service invoke completed of the setter, you will not be able to see the session value on a new page load.

Bind as a trigger to the getter the mashup loaded as well - or bind the session variable directly.

If you're interested, in developer tools you can also use TW.Runtime.Session.GetSessionValue("MyKey") to see what value is stored on the client side - use it only to check, but not in production code, as it's not guaranteed not to change in future.

Sign up

Please use your PTC eSupport account.

Welcome to the PTC Community

Please use your PTC eSupport account.