What's New

Attributes are your way of adding extra info to components in Revision—your own custom metadata. Revision has had attributes since day one, though they have only been rather basic text fields.

Attribute Types

Starting today, you can choose exactly what kind of data an attribute holds, anything from Revision team members to custom list items:

This makes it way easier to keep things structured and thus useful.

Attributes for Specific Component Types

Not every attribute belongs everywhere. You can now set attributes to only apply to certain types of components, with support for both bundled and custom types.

For example: Add a “.NET Version” attribute for your application components, and it won’t even show up for things where it doesn’t make sense.

Required Attributes

Some attributes are too important to miss. For example, you might decide that every Application needs to have an Owner. Such an attribute can now be made required, and Revision will let you find components where it’s missing.

Better Filtering

The dependency view also plays nicely with the new attribute types. Filter exactly the way you want, using any combination of attributes in your model.

What About My Existing Attributes?

No worries—all your old attributes are still there. They have been converted into Text attributes in the new system.

Visit our documentation if you'd like to learn more. We can’t wait to see what you do with these new attributes, and how much richer your models become with them!

We have added Dependency Graphs, a new feature that lets you visualize and understand your architecture. This new type of view provides an interactive way of exploring the relationships (dependencies) between your components.

What are Dependency Graphs?

Dependency Graphs offer a visual representation of how different parts of your architecture connect and depend on each other. Instead of sifting through diagrams or documentation to understand architectural relationships, you can now see the complete picture at a glance.

With smart filtering options, you can limit your overview to—among other things—specific diagrams, components, types, layers, or attributes.

Benefits for your team

• Quickly identify and understand how systems interact
• Spot unintended dependencies or missing links
• Simplify onboarding of new team members
• Communicate architectural insights more clearly
• Save time by avoiding manual exploration of relationships

Migration from Query Views

Dependency Graphs are replacing the previous Query Views, offering similar analytical capabilities but with enhanced ease of use.

If you have existing query views you would like to preserve, they remain accessible at https://your-organization.revision.app/query for a while longer. If you want help with migrating these to Dependency Graphs, reach out to our support and we'll help you out!

We have launched an API for Revision, giving users a way to programmatically interact with and manage their Revision data.

Starting off, and available today, is an API for components, where you can fetch, create, and update components in your organization. We are committed to supporting the API, and we will be working on adding more endpoints & respective documentation in the future—keep an eye out!

To get started, have your organization administrators grab an API key from your organization's security settings, and check out our new documentation!

Users spend most of their time in the Revision editor. Since the beginning, we have aimed for it to be as efficient as possible for one purpose: drawing diagrams. However, it has lacked some important features, such as the ability to easily use an unlimited canvas, freely pan around, and zoom with the keyboard.

All of this has now been fixed!

The tables in Revision have always had the ability to have their columns shown and hidden, filtered, and sorted, et cetera. However, when you made changes, these preferences were not saved. As a result, after navigating back to the table, you would lose all your viewing options, and you would have to start over.

This issue has now been resolved, and all user display settings are saved to your account. When you make changes to a table, these settings will always be applied for you.