How to remove dependencies before deleting a Webform (Widget)?
Overview
This article guides you through the process of identifying and removing mandatory dependencies linked to a Webform (Widget) that is scheduled for deletion. You must remove all mandatory links to other system features before the Webforms (widget) can be permanently deleted, ensuring critical enrollment processes are not accidentally disrupted.
Permissions Needed
Module | Permission Name | Description |
Webforms (Widgets) | Template Manager > Delete Widgets | Allows you to permanently remove Webform (Widget) from the account. |
Step-by-Step Instructions
Step 1: Navigate to the Widgets Listing Page, disable the widget (toggle status to OFF), and click the vertical three dots icon (⋮), then select Delete.
Step 2: If the widget has dependencies, a sidebar will appear showing two sections: Mandatory and Non-Mandatory.
Step 3: Review Mandatory Dependencies (e.g., Automations, User Allocation Logic, Webhooks etc). These must be removed.
Step 4: For each Mandatory Dependency, click the View Details button next to the configuration name. This will redirect you to the page where the dependency is active (e.g., the Automation Setup page).
Step 5: On the redirected page, remove the link to the Webform (Widget) from that configuration. Repeat this process until the Mandatory Dependencies section in the sidebar is empty.
Step 6: Handle Non-Mandatory Dependencies. The sidebar will also show non-mandatory dependencies (e.g., Saved Views, etc.). These do not require manual removal for deletion, but note that features relying on the deleted widget will fail to return the desired result or may show an error upon execution.
Step 7: Once all Mandatory Dependencies are cleared, the system will prompt you to confirm deletion. Type DELETE (case-sensitive) in the input field to enable the final Delete button.
Step 8: Click the Delete button to remove the widget from your account.
Points to Keep in Mind
- Mandatory vs. Non-Mandatory: Only Mandatory Dependencies (Automations, Webhooks, User Allocation Logic etc) block deletion and require manual removal. Non-mandatory dependencies (e.g., Saved Views, etc.) are not required to be cleared, but note that the feature relying on the deleted webform (widget) will fail to return the desired result or may show an error upon execution.
- Link Removal: When clicking View Details, you are redirected to another configuration page (e.g., an Automation). You must edit that configuration to remove the specific widget link to clear the dependency. Make sure you have necessary feature access to remove widget dependencies from that feature.
- Case Sensitivity: The confirmation word DELETE must be typed exactly as shown to proceed with the final step.
Conclusion
You have successfully cleared all mandatory dependencies for your widget. This process ensures that removing the widget does not disrupt any active enrollment or data management workflows, allowing you to safely complete the deletion and maintain an organized, efficient system.
Related Articles
How to Delete a Webform (Widget)
Overview This article provides the essential steps and requirements for permanently removing an unused Webform (Widget) from your account. Deleting unused widgets helps maintain an organized lead-capture workspace and ensures system efficiency. A ...How to Create a Webform (Widget)
Overview This article provides a complete, step-by-step guide to help you successfully create, customize, and publish a new website Webforms. These Webforms are essential tools for capturing new leads from your website. By following these steps, you ...How to remove dependency to delete custom field in Leads?
Overview This article guides you through the process of identifying and removing mandatory dependencies linked to a Custom Lead Field that is scheduled for deletion. You must remove all mandatory links to other system features before the Custom Lead ...How To Delete Lead Fields?
Overview This article guides you through the process of permanently deleting a custom field that is no longer needed. To successfully delete a field, you must first disable it and resolve all mandatory dependencies to ensure no active process is ...How to Delete Events in Calendar Pro?
Overview Deleting Events in Calendar Pro allows users to remove Event Config, Event Fields, and Events that are no longer needed. Event Config Removal: Delete unnecessary event configurations. Field Cleanup: Remove event fields no longer in use. ...