I have a portal that is reached by scanning a QR code and takes 1 url parameter and passes it into the initial page where the user can fill out some data. However, if the user navigates away from that page to another page on the portal, and then comes back, the rule input is blank and the url parameter has also been lost. Is there a way to save the user's data so they don't lose it when they navigate back, or at least a way to preserve the url parameter between pages so it can be passed back in to the form?
Thank you,
Jack
Discussion posts and replies are publicly visible
I don't think you can achieve it unless you hardcode that value within your code. Will your parameter always have the same value or every QR code passes a new value in the parameter?
Harshit,
Each QR code will pass a different parameter (a serial number for the product). So we can't hardcode the value. I also found your article on Appian Space titled "Preserving the State of Navigation/Selection" and it seems like that plugin would work (when called from a web API), however I can't figure out how to uniquely identify the user so I can retrieve the correct cashed data. Is there any kind of portal property that uniquely identifies the instance and doesn't change if the user changes the page?
Thanks for checking the blog. Appretiate it.
Coming to your question, plugins don't work on Portals. And as you said, there is no way to uniquely identify a user on the portals because portals are used for anonymous users.