Feature Overview: Data Validation And Required Fields

To ensure the data in your CRM is complete and uniform, you can use Streak's Data Validation. This can help prevent errors the moment they occur so that they can be fixed immediately.

Adding a Rule in Data Validation will enable the Pipeline Admin(s) to ensure certain pieces of data are filled in when the user tries to change the Stage of a Box. Streak will block users from making an edit to a Box that would break a rule.

Creating Data Validation Rules

Pipeline Administrators may create, update, or delete a Box Validation Rule. 

  1. Navigate to the Pipeline
  2. Click the More dropdown at the top of the Pipeline
  3. Select Data Validation from the menu to open the Data Validation rules
  4. Set your rules (see below)
  5. Click Save to create your new Data Validation rule

After you create these rules, your teammates will have to abide by them. If they make any edits to a Box that go against the rules, Streak will provide a friendly error and prevent incomplete data in the Box.

Admins of the Pipeline have to play by the same rules, but they are given an option to override the rule if they choose.

Simple Rules

Simple rules can be easily phrased in plain English: "If a Box is in the Closed stage, make sure the Source field is filled out". Streak would then prevent Boxes from being moved to the 'Closed' stage if the 'Source' field was not completed.

 Tip: For guided step-by-step instructions in the extension, follow the In-App Tour "How to create a simple rule"

Possible conditions for Box:

  • Is in <Stage>
  • Assigned to <User>
  • Has <Fields(s)> Set

Possible assertions:

  • <Fields(s)> Set
  • <Fields(s)> Not Set
  • Deny Edit

Formula Rules

We've only just begun to discuss what we can can accomplish with Box Validation using Simple Rules. Using Formula Rules, we can create more complex, granular rules. 

Formula Box Validator rules run javascript to determine if a Box is valid or not. They functions similar to Formula Fields, except they should evaluate to true or false depending on if they see the Box being changed or created as valid.

 Tip: For guided step-by-step instructions in the extension, follow the In-App Tour "How to create a formula rule"

When creating Formula Rules, they should evaluate to True (valid) or False (invalid). For example:

if ($'Stage' === 'Launched' && $'Type' === 'Non-Feature'){ $'Root Causes'.length > 0 }
else
{ true }

The above rule will do the following checks:

  • If the stage is launched and if the type is Non-Feature, check if the Root Causes tag field has tags set:
    • This will evaluate true if greater than 0
    • Otherwise this will evaluate false if there are no tags set
  • If the stage is not launched or if the type is not Non-Feature always return true
    •  Because this rule is not relevant

Custom Messaging 

Advanced custom messages can be written for users to help your team pinpoint exactly what they did wrong. You can also configure to "Reject" the action, which will prevent the action from taking place, or "Warn" users, which will allow users to violate the rules but give them a friendly warning that they are doing so.

Contact Us