Skip to Main Content

Share your product feedback

Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit A-I-9965 Require fields by status.

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.

  • Karie Kelly
    Reply
    |
    May 28, 2022

    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.

  • Ryan Johnson
    Reply
    |
    Mar 15, 2021

    Why is this marked shipped but doesn't address the ask? Please reply if you are going to consider requiring fields based on status.


  • Ryan Johnson
    Reply
    |
    Feb 16, 2021

    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.

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...
Praseetha Balakrishnan about 4 years ago in Strategy 0 Future consideration