Here’s a round-up of this month’s highlights:

Latest Releases

Enhancements to Our Ever-popular Dependency Map View

One of our five most-used views, our Dependency Map view is excellent at communicating upstream and downstream impact. It helps present how different logical (e.g., business capabilities, references to a service) and physical (e.g., servers, network devices) components of the organization are connected and interrelated. With its popularity in mind, we have made two new enhancements to our Dependency Map View.

1. URL Field Types: Now available in Dependency Map, Swimlane & Black Diagram Views

What: URL field type (a hyperlink that points to a web page, file, or other web-based resources inside and outside of Ardoq)

New feature: Now available to visualize and create additional actions on your components and references. Also available in our Swimlane and Block Diagram Views 💪

Usage: Linking to additional information about your data. Adds value and increases engagement by allowing easy access to supporting information.

Example: You have conducted a Customer Journey Workshop and want to compile ideas from it. You can do so in an external design tool such as Miro and add a link out to it in Ardoq.

Suggestions: Ardoq supports many techniques natively but modeling tools are not the best approach for all things. If using the URL field type creates additional value for your story, your next iteration could be to integrate Miro (or other external design tools) using our Rest API. Integrations can be made to external design tools and the results imported back to Ardoq.

2. Component Hierarchy Depth view modifier: Hide or display data as needed for your target audience

What: Component Hierarchy Depth view modifier

New feature: You can now show collapsed relationship elements when using this modifier such as when you have data that needs to be collapsed to be useful to your target audience.

Usage: Ability to have additional data present or hidden away for cleaner views depending on your target audience.

Example: You have Ideation data (for example, Automate common customer questions with a chatbot) but you want to analyze and view its relationship with supporting your Key Results data (for example, Reduce time spent on common customer issues by 33%). Hover over your data after applying the Component Hierarchy Depth view modifier, and you will be presented with a pop-up that will reveal the relationship elements which were hidden. You now have the best of both worlds 😁

Improvements to Scheduled Imports to Ensure the Accuracy of Your Data

Scheduled imports now fetch data based on the column name instead of the column index. The result is a seamless import and better data accuracy for all your scheduled imports.

Previously, the scheduled import jobs relied on the order of the columns mapped in the configuration, which could introduce data errors if there was a change to the structure of the columns. This could happen, for example, in cloud integrations where it is possible also to import tags on some resources. In this case, deleting or adding tags in the source integration would remove or create new columns in Ardoq, thus changing the order of the columns and causing the data to be imported in the wrong Ardoq field.

With this improvement, changes to the column structure won’t compromise the data accuracy during scheduled imports anymore.

Stay Connected. We Are Protecting Your Data.

In line with good security practice, we added a new field in Preferences > Organization settings > Manage organization > Settings tab where you can specify who we should contact if Ardoq detects unusual activity in your account.

We respect the privacy of your personal information. The email address, or list of email addresses, will only be used for this purpose.

Head over to our Information Security page to learn more about Ardoq’s approach to safeguarding the confidentiality, integrity, and availability of information stored and processed by the Ardoq Cloud platform.

New Guides to Learn and Upskill

Help Articles:

Blog Posts:

Did this answer your question?