This release note is just a preview and should be treated as an aspirational goal by the product team. Features described here are not guaranteed to be made available within any particular time frame or at all.

In the 4th quarter of 2020 we want to focus on strengthening 3 core value propositions of our product:

Salesforce clean-up & metadata dependency mapping

We are committed to building the best, most precise and robust metadata clean-up and analysis tool. We made significant progress with the dependency trees and field population & usage insights. But there are more things to come:

  • Record types dependencies: We will work on supporting record type dependencies by listing metadata that reference record type IDs, labels or API names.

  • Flows on flows dependencies: To aid users in their declarative work, we will expose flows <-> flows dependencies and flows <-> process builders in our dependency trees.

  • Email alerts dependencies: We will work on exposing email alerts dependencies, including where they are used in code, process builder workflows, or flows.

Business analysis

The core value proposition of our product is to help business transform faster while minimizing the risk. To that end we are currently working on the following solutions:

  • Risk assessment on user stories: We want users to be able to generate dependency trees from user stories, highlight different types of risks and actively assess the impact of any change to create an accurate change manifest.

  • Requirements/stories improvements: We recognize that business requirements and user stories are not the easiest part of our product to use. That is why we are actively working to make them easier to raise and manage. We are working on supporting list views, grid grouping, and improving the overall UI.

  • Release management: To make management of releases' scope that much easier, we are working on including business requirements & user stories in the release view. That way users will be able to plan not only which diagrams are being changed, but what changes are driving them and will be deployed.

Org Documentation

We want to support our partners by providing the capability that would allow them to import pre-build documentation sets and templates into the client Orgs.

  • Documentation packaging: Consultants, ISVs and big customers will be able to document an Org Model, package their work and make it available for all or just selected customers. This will allow our users to import pre-built documentation sets into their Orgs and streamline any documentation / learning efforts.

General Improvements

Other than "big" changes and additions, we are also mindful that certain parts of the product could and should be easier to use. Below is the list of a few such improvements currently on our minds:

  • Reporting: We want to make reporting more intuitive for our users. At the moment customers are not always aware how/when they can generate reports and what these reports would contain. On top of that, there are several new reports that we want to add to our repertoire.

  • Interface cues: We want to make it easier for our users to find content. That is why we will be working on introducing cues throughout the interface to inform users of things they might want to inspect. These would, among other things, include counters on feedback, change & documentation icons to communicate how many items are present in those tabs.


  • Flowline behavior: We have received reports of diagram flowlines sometimes misbehaving. We plan to address this and make sure they continue to work intuitively and cause no further irritation. 

If you have any questions about the planned functionality reach out to us. Again, this is just the plan and the actual list of features may change. 

Did this answer your question?