.png)
Guardian’s Delete Protections helps ensure critical elements placed within the project model will not be accidentally deleted. By adding Guardian’s Monitor, Guide & Prevent protections to the delete command, administrators can add protections to help prevent pre-defined elements from being deleted while communicating to the user why the deletion of those elements may cause issues or inform them of all the additional hosted/dependent elements also being deleted.
To assist administrators, Guardian comes pre-loaded with Delete Protection Rules predefined for the most common elements that are known to cause the most amount of time fixing when deleted.
In Revit, there are many instances where you can delete additional elements without really knowing. Yeah, the yellow warning box does inform users, but they’ve become conditioned to ignore that out of hand. This can include hosted elements and associated views. To help prevent this problem, Guardian’s Delete Protections let you and your users know when protected elements are being deleted.
When Delete Protections is first enabled within Project Configurations under the Custom Interactions tab, it will be adopted by each project model once the model is registered. Delete Protections can be further customized at the project level within Project Settings on a model-by-model basis.
Editing and creating rules under Customize behaviors when deleting elements will activate Delete Protections.
Select the settings cog to configure rules that will automatically apply the Delete Protections to any elements that meet the rules conditions.
Select the New button to create a new rule to identify which modeled elements that will be protected by the Delete Protections. Create as many rules necessary for the elements that need to be protected. Please note, the rules will be processed in the order in which they are displayed. Use the arrow buttons to arrange the proper order of the rules.
Different AND/OR statement types can be used to create rules to meet specific needs for the Delete Protections.
The different conditions that can be utilized include:
Category conditions can be used to specify specific categories that should be protected. Administrators can also specify categories that should be ignored by the rule.
The protection mode can be customized for each rule:
The category and element parameter conditions can be used to specify specific elements that should be protected from being deleted.
The Deletes Other looks for the hosted or dependent elements that will also be deleted when the primary element is deleted. This is important to use when wanting to notify users of all the secondary elements being deleted by listing those elements in the Command Message.
The username condition can be used to target the protection to certain users or even to exempt users from the rule.
When an end user attempts to delete an element, Guardian will alert them with the custom Command Message provided by the Project Administrator (If the Protection Mode is set to guide or prevent).
If set within the Custom Interactions settings for Delete Protections, the end user will be required to provide a comment to proceed with deleting the protected element.
If set to Prevent mode, the end user will be required to provide the Project Password or One-Time Password to proceed with hiding the element.
There are two ways for Project Administrator to receive notifications; Project Central and Email Notifications.
Any Delete Protections rules that have been triggered will appear automatically within Project Central’s activity feed.
Enable email notifications in the individual rule set dialog by checking Send email. When an end user attempts to delete an element that has been protected, the Project Administrator will be notified with an email containing the pertinent information.
Creating effective AND/OR rule sets can be a bit challenging at first. To help you get quickly started, we've developed a set of pre-configured Delete Protection rule sets. These templates serve as both practical examples and ready-to-use solutions, allowing you to implement robust protections right away while you familiarize yourself with the system.
Used to show all hosted or dependent elements being deleted when the selected items have been deleted.
Used to keep a data trail of all elements deleted not covered by the previous rules to help troubleshoot when needed.
Reach out to learn more, ask any questions, or meet the team! We'd love to learn more about your challenges and explore the more proactive solution.
