About content versions
As a content-sharing platform, Devo Exchange is a dynamic tool capable of providing new solutions when new needs arise or adapting existing solutions when those needs change. This is achieved through content publishing and updating.
Publishing content
Exchange's content catalog is managed and curated by Devo. Customers and end users can make requests, send content for validation and publishing, etc. through our content proposal tool. Customers can also use our dedicated email address if they need extra help.
Updating content
Devo Exchange supports content versioning, which enables the detection of new versions of the published content to facilitate keeping them always up to date. This applies to all types of content: applications, Activeboards, alert packs, lookups, content packs, synthetic data, and use cases. Whenever a new version is published, there will be a series of changes to inform you about that.
If the content is not installed
The version info and version history will appear inside the Version section when you open the content.
If the content is already installed
Items will display the Update orange sign instead of the Installed green sign, and they will be recommended in the Featured section when exploring the Discover category (see Browsing content for more info).
When you open the content in question, an additional Update button will have appeared at the top right. Moreover, the Version section will display the version installed and the latest version available.
In the case of alert packs, the Update button does not appear at the top right of the card, but in the corresponding alert row on the alert list (see Installing content in Exchange for more details).
In the installed content screen, an Update button is shown for each item with a new version available, except for alert packs, which show a Manage button instead (see Managing installed content for more info).
Catalog visibility
In general terms, all contents published in the catalog are universally discoverable and accessible in all Devo domains. It is possible though to define visibility rules for certain contents, making them available only in certain domains. These rules are configured by Devo at publishing time and are not configurable by end users.