RELATED IDEAS
Conditionally Required Fields based on workflow status
Make fields required based on workflow status. I would like the ability to make fields required once they reach a certain workflow status or statuses. This would foster the notion that at creation and exploratory, we may not know all the details and that acceptable, but once we commit to develop something, those details must be defined.
-
ADMIN RESPONSEFeb 11, 2021
Thank you for your idea. We have a feature in progress that will allow you to link custom layouts to workflow statuses. One use case which aligns with what you are requesting here is that you could hide fields on records during the early phases of your workflow and have them show once the workflow reaches a certain status.
This feature will be available soon as part of our Enterprise+ plan.
1
MERGED
Make Initiative fields mandatory before stage transition
It would be good to have the functionality to make certain (custom & standard) fields required before the Initiative is transitioned into the next stage. This way there's less human error in entering certain pieces of info before the initiativ...
0
Shipped
I don't know the implementation as I am not on the enterprise+, but if the screen that is displayed includes the option to set some fields as required as does the standard layout, then it should meet the ask. However, it would be beneficiial if the admin could clarify.
Why is this marked shipped but doesn't address the ask? Please reply if you are going to consider requiring fields based on status.
I have a similar idea, but what your responding with is not exactly what is being asked here. "Required" is the key ask, how can you force fields being entered, not just show or hide, before moving to next state.