This idea has been merged into another idea. To comment or vote on this idea, please visit CSPM-I-109 Set Mandatory Property Per Status in the Workflow.
When an instance is created some users may wish to temporarily save the instance and come back later to provide more data. Currently to make fields mandatory in multistage forms a transition is used (requierd conditions). When trying to save temporarily the form with the SAVE button the required conditions kick in.
Kiril Tasev
Thank you for submitting your idea. We understand the desire for it and will consider it for a future release.
Note that this ONLY affects newly created forms. As soon as the form is created, it can be saved in the current status without requiring a transition. Due to the system architecture, when starting to fill out a new form instance it needs to go through a transition from not existing to some starting status.
As a workaround for this, you can select more than one status as starting status to give the users the ability to choose to save it in either status. As an example, you could give the users options to save in either status Submitted or Draft at creation. By selecting the Draft status first, it will become the default button, with Submit being the secondary.
This will allow users to save as Draft before they Submit, or Submit directly if they complete the form in one go.
I think this is almost same like other idea "Set Mandatory Property Per Status in the Workflow"
If SYNCHRO can have mandatory field per status, this I believe it will solve this issue.