Retaining parameter value when navigating between forms - is it possible?

ajackett
New Contributor III

Hi all,

I am building some form templates for my workflow profiles, and have a query regarding the best way to setup the form template and entity parameter (setup below):

 

ajackett_0-1706716447054.png

ajackett_1-1706716532246.png

I would really like to be able to have users navigate between the forms, and the entity POV that they have selected in the parameter remain constant between forms. As it is now, when they move from a form, it always goes to the top entity in the list. I have some workflows with 20+ entities, and it may be that someone is working on the forms for just 1 entity at a point in time so has to re-select the entity each time. I've seen a "Sticky POV" idea raised on IdeaStream, but that hasn't moved since 2022. 

I have seen mentioned at Splash that there's an option to have the user state pov remain through a business rule, but haven't seen anything other than a SetUserState? And I'm not really sure how to write the code and apply it here. 

Any advice would be really helpful.  

1 REPLY 1

MarcusH
Contributor III

'UserState' refers to a table in the application database (XFUserState) where the state information is stored. If you search for USERSTATE in the rules snippets you will get examples for the Get and Set. The information in UserState is available the next time the user logs in. If you just want the info stored for the session use Globals (globals.SetObject and globals.GetObject).

GetUserState and SetUserState are used in an OpenPlace application (Data Import Schedule Manager - DSM). Look in the Dashboard Extender DSM_SolutionHelper for complete functions that use them.