Issue with the current “requirement” - it is set at the object level. What if we add a field later and want it required but will not need backfilled for prior Goals? For example, I made and initial test. I am adding some additional custom fields that I know we would use and attempted to make it required. However bc the required is at the Object level, I cannot bc that initial test “does not have any data” for that field...

Because these are goal, not all fields may be known at the time of “closing”. For example, if we have a start and end value. I would want to require “start value” when creating but not “end value”. However before setting a certain status I would want to require a “end value”.

In general, these are the same limitations we have CTA/ Objective field requirements…. I would hope the new tool would address those

Yes please! Huge pain as well that even with CTAs, the ‘required to close’ fields can still be omitted if you set the CTA status to ‘closed’ when you are creating the CTA.

There are three kinds of required fields 

• required field at object level which must have values for all records 
• required field for new records only. ie. value for field in mandatory only when a new record is created.
• required field when record is updated to achieved

Will add it to the roadmap.

Converted this Customer Goals Beta discussion into an Idea for Voting.

DITTO!!