User’s need: Medium
Developer’s need: Low
Is it possible to have a widget to be implemented inside the application for the state saving module.
Personally I feel like the top left button is enough but for some users that are not used to the application it can be a bit challenging.
Having a button or an alternative way to save a workshop (state saving) would be amazing.
As a workaround, you could create default values for variables instead of promoting them / flagging for state saving, which are loaded from a dedicated object type saving your state - including action etc.
Then you can create your own custom buttons and workflows around that. But then again… a lot of work and maintenance for adding a different UX.
Yeah that is a solution I had in mind and one used by a colleague.
For a little amount of variable to save it is worth it but otherwise it is too much maintenance and work
I’ve added a note of this request to our internal tracking of this feature request
@evanj I totally second this issue. Having a button like widget to place it at desirable location and configure it appropriately would be nice. Do you estimate when this feature might be available in the workshop? Thank you.
@Flackermann I am trying to do the same i.e. implement a cutom button to save the state of all variables and also apply some additional custom function/wokflows at the same time.
I understand the native state saving feature where variables can be promoted or flagged for state saving. Could you please elaborate your idea on how creating defaults for the variables can facilitate a custom button with state saving feature?
The only way I could think is actually passing all of the ObjectSet filter variables to a function and then saving them as is like json somewhere (in a file, or as a property of a new Objecttype specifically designed for handling state saving). However, I am still stuck on how would I present those json property back.
In my case, I am building a sort of requesting system so I need to capture all of the parameters/filters of the request (filters from different ObjectSets and types) and eventually be able to present it back as a tracking system. The later presentation serves the read-only purpose but definitely need to be better than json raw strings. 
Much appreciate if you have could elaborate on your idea to see if this might work for my use case.
Thanks.
Hm. I see the problem regarding the filter variables. Here, you cannot simply reload a value as a string. Every idea that comes to my mind seems to be too much of a hack. Maybe we should define a good feature request instead…
I see a certain overlap with scenarios. You can save actions applied in a scenario to an object type with additional metadata to be reloaded later. Also in the case of saving scenarios it could be beneficial if the same saved object would store the promoted variables so that you can replicate a certain state of the app…
