Prevent record progression/closure if certain fields are not completed.
under review
B
Bongi Simelane
Currently, the mandatory field for a task/record is Title, which works great as it's a primary field.
It would be tremendously powerful to prevent the user from changing the record status to CLOSED if certain fields are not completed in that record.
If we want to dive even deeper, it would even be better to tie ability to change to each status to completion of certain fields, where the user can only progress record to REVIEW status once certain fields are completed, then CLOSE only when all fields are complete.
This can easily streamline automation processes where, certain fields must be complete before it triggers.
Autopilot
Merged in a post:
❗️ Certain conditions must be met in order to set a specific status.
W
We Have A Tender
Certain conditions to be met to set a specific Status.
For example, a Custom Field needs to be filled in order to be able to set the Record as "In Progress" Status.
If those fields are not filled or checked or etc, then that specific Status cannot be set for the record.
Accounts 6 Stars Cleaning
ZOHO CRM had this ability in the "Blueprints" section. We used this before switching to Smartsuite
Nate Montgomery @ SmartSuite
Merged in a post:
Conditional Required Fields
Jon Darbyshire
Ability to use rules to enable fields that are required in a record. Example: User can not mark a status as "ready for review" unless the user has entered values in "x" fields that have been marked as required.
G
Gary Ford
yes - yes - yes
E
Esther craft
but this should be a optional feature for admin to turn on - meaning we can have mandatory fields - but if is not filled in - whether we can prevent it from being CLOSED - should be an optional feature for admin to turn on.
Landyn U
Commenting to add my support as well! I thought this was under the 'Dependencies' that is in progress, but the more I read into it, I don't think that's the case as Dependencies is based on other records instead of columns within a record.
For my use case, I have a trigger on status change where the customer is sent a copy of their invoice and order information. However, if the Invoice hasn't been created yet, it still sends the email without a copy of the invoice. Joël de Regt has a great write-up on how this would look.
Brian Dollen gave a great example of how to use automations to
temporarily
work through this shared below:When a record is updated where Status changes from Any to Ready for Review AND Invoice(concat formula) is empty, send an email and update record back to status "in process".
Y
YES Integrations
Y
YES Integrations
Y
YES Integrations
For our use case this is the biggest feature still missing. Adding this will allow us much more confidence in the integrity of our data.
Lowenna Luke
Jon Darbyshire would this be covered by the Dependencies feature that's planned?
Load More
→