Guardian 2.4

April 7, 2021

2.4 Release Notes

Our version 2.X releases have each addressed a challenging aspect of standardization in Autodesk Revit® and 2.4 is no different.

In another industry first, Guardian now prevents the duplication of families when loaded from other projects! We're excited to bring Family Mapping to your Revit experience, along with many other great features and improvements. Check it out! 

You can now use the familiar tools in Guardian to safely remove, rename and map your families. As with other properties, Guardian's powerful rules engine also automates these decisions across your firm for more consistent, leaner projects.

In fact, Guardian can now even prevent the unnecessary duplication of identical families when they are added to your projects AT SCALE.

New Family Mappings

Any time you need to swap families, you can now use Guardian. The most common cause for this is when Revit duplicates families when they are brought from another project. For example, BreakLine.rfa will become BreakLine1.rfa because Revit thinks they are different. The theories as to Revit's logic in determining 'different' are many, but it continues to be a pain point because the families usually aren't different or they have very minor differences and combining them is very tedious.

Guardian addresses these needs in both an automated way and a manual way. Check it out!

Mapping Rules Dialog

Our customers love having Guardian automate their standards enforcement. We believe that it is healthy to always be improving the naming conventions in your standard and we are here to help make sure that those changes apply when old properties are added to your projects or families. To make this even easier, the Mapping Rules dialog has been an area of focus for us in this release. You'll appreciate a better display of information and ability to search, sort, copy-paste and even merge entire Mapping Configurations.

Sync™ Improvements

We couldn't be more excited about Guardian Sync™. Our customers love being able to easily store their line and fill patterns away in a non-version dependent format AND keep them synchronized across projects. By uploading and syncronizing Sync™ properties, you are truly identifying your standard and can be ensured that they will stay identified, even as you make changes, etc.

In this release, we're adding several features to improve the experience. We definitely have big plans for Sync™ this year and we are making sure to do it strategically.

Backstage™, UI Improvements

This has been a large area of focus for us during this release cycle. Our last 2.3 release added many new features, including an 8x increase in the activities that can be tracked. We also added a new 'Monitor' mode. Because of this, interest in Backstage™ has increased significantly.

While Backstage™ related improvements aren't necessarily tied to our client release, we try to time the availability of features together. Here are these improvements and their status:

  • We made a significant structural change to how Backstage™ works. We now use independent tables for each company, rather than table views. This will result in much better performance when refreshing data. This also allows you to use the data more creatively, including Microsoft Power Flow routines (you could set up a notification stream to your Microsoft Teams channels, for example)
  • We added additional tables for Project Setting Overrides, Guardian Sync properties, Installations, and License Usage
  • Cleaned up some data schemas for Added, Modified and Deleted transactions. You will no longer see duplicate “Guardian Cleanup” transactions.
  • Projects Dialog: your list of projects will now load dynamically as you scroll, rather than background downloading of the list when Revit opens. This also means the list will show currently registered projects and their settings without needing to restart Revit.

Other Notable Improvements & Fixes

  • We added a tooltip that will now appear when hovering over any mapping rules that are applied. This will provide needed transparency in multi-user environments.
  • We added alerts to indicate when problematic usages exist. There are some situations where Guardian does not have API access to make a change, such as instances used in groups or checked out elements. Now, these will be shown with an alert symbol. When processing, only these usages will be skipped and the property will remain.
  • We added options when choosing to ‘Reset Default’ settings on project settings. Now, you will be able to remove all overrides (Project settings will stay synchronized with the Company settings) or simply refresh/copy the current state of the Company Settings.
  • Viewport types will now ALL properly map, overcoming a well-known limitation within Revit where it will not purge unused viewport types.

We are eager to begin working with you as you work to improve your processes. Please fill out the form at the following link to learn more about this release: