Passing Dates Between Mashups and Returning Values on Back Button Click

[Aishwarya_Patil]

Hello Community,

I’m working on a scenario where I need to pass selected dates from Mashup 1 to Mashup 2 using the navigation function, and then return the same dates back to Mashup 1 when the user clicks a back button in Mashup 2.

Currently, I can successfully pass the selected dates from Mashup 1 to Mashup 2 using the navigation function and mashup parameters. However, I’m struggling to return the same dates back to Mashup 1 when navigating back.

I’d appreciate any suggestions or best practices on how to handle this back-and-forth data exchange between mashups. Is there a recommended approach for maintaining these values? I am currently working with Thingworx 9.5 version

Thanks in advance for your help!

[wcui]

@Aishwarya_Patil 

Mashup parameter can help you transfer data from Parent Mashup to Child Mashup however the reverser difection is not supported.

You can use session parameters to save data on Child Mashup while Parent can also access the data.

The session parameter data is maintained when a user navigates between different mashups.

Refer to Help Center and articles: CS249180, CS232199 for more information on Session Parameters

[Constantine · Accepted solution]

Hello,

you have three main options:

1. You can pass mashup parameters bi-directionally between parent and child mashups in "contained mashup" hierarchy. For that you'd need to replace you Navigation structure. This is the cleanest and easiest approach, but will require a certain UI redesign on your side.
2. You can use Navigation function to navigate back from Mashup 2 to Mashup 1.
3. You can use Session parameters, but be ready to test for side effects, as those parameters get sent to the server side, and apply to all your browser tabs at once.

/ Constantine