I have working processes with a number of Dynamic Windows calculations; to dynamically build the user data entry form. In order to ensure that the users "request something" the first attributes that build the window are set (by calculation to mandatory). There is one flaw that users seem to fall into more than we thought. The user MUST put something in the Mandatory field; however if they use the available process actions (like Submit to IT); they are prompted that the data has not been saved if in fact that is the case. If they simply ignore that warning - then the action is executed and the data is all lost (not saved - of course because the used did not do so).
Anyone used any cleaver methods to force a save operation to occur? I suppose another calculation to read say a sequence number as the window is loaded - and then increment the number each time the window is saved. Then I can look at runtime to at least see if the current value incremented each time the mandatory field is changes is higher than on read. This seems a lot of checking just to force a save vs. giving the users the option to skip the save. Anyone know of how to either:
* Force a Save (I doubt this exists)
* Remove the option to ignore and continue (No) when the user seems the warning that there is unsaved data.
* other clever ideas (or point me to the stupid OOTB solution).