What Are Field Dependencies?
Currently, this functionality is still in the testing phase and only displays dependencies related to Automations and Conditionals. Keep in mind that not all instances using the field are shown at this stage.
Field dependencies represent all instances where a field is used within your pipe, such as:
Automations
Conditionals
Connections
Interfaces
Email Templates
Dynamic Fields
How to Access Field Dependencies?
Via the Form Editor
Open the form editor (either the start form or a phase form).
Locate the desired field and click on the three-dot menu next to it.
Select Field Dependencies.
Via Field Details
When editing a field, click the Field Dependencies button located in the bottom left corner of the screen.
Why Is This Important?
Before editing or deleting a field, it is essential to check its dependencies to:
Prevent automation failures that rely on this field.
Ensure conditional rules continue to function properly within the process.
Protect connections and views, avoiding negative impacts.
Minimize workflow interruptions and rework for the team.
Best Practices for Using Field Dependencies
Review regularly: Use this feature periodically to maintain pipe governance.
Collaborate with your team: If the field impacts other users, notify them before making changes.
Document changes: Keep track of edits for future reference.
The Field Dependencies feature is an essential tool to ensure safe and well-planned edits. Use it to maintain smooth workflows and avoid unexpected issues!