being able to save but not push forward workflow
It seems like there should be a difference between fields required before a workflow can be pushed to the next stage, vs. being able to save any change to a document.
I think you should always be able to make changes and save a document, but just the workflow button should be disabled until the required fields are populated.
Comments
Thank you for your contribution on this topic Arlette.
Currently we are looking at providing this feature request from the following perspective:
At a per workflow state level, you should be able to define where a setting (boolean) to define the mandatoriness of fields that blocks the document from transitioning to any other state but not for saving the document.
Let us know if it is aligned with your use case.
Yes, that would be perfect and very helpful. Thanks.
I am hoping this is getting onto the short list for deployment. It is definitely giving me lots of difficulty. I am having several scenarios where someone needs to gather information over a period of time, saving the pieces as they are figured out, and then at the end, push the workflow forward. Under the current design, this is just impossible.
Please sign in to leave a comment.