To prevent against notification spam and to ensure a smooth launch new behavior or changes to existing behavior can be rolled out gruadually and without notice.
Those that notice changes in behavior of a part of a page they use frequently or those that wonder what is new can consult these articles for updates on recent changes in behavior for all users.
This article contains information about the following topics:
New releases
Each user uses the platform diffrently.
Notifications made on Even if new feature are released or changes it could be that
are made users might not be using that part of the feature.
For those that are curious what "that new button" or "that new page" is on the platform this article contains an introduction of what the change is about.
For these features often only basic or slightly outdated support material is available as this gets updated as we go.
Along with helping people out in support the articles often get updated and if questions that were asked can quickly be found explained in an article the next week.
New status workflow - ISO 19650
Projects that enabled draft revisions before 2 October 2025 will continue to see the legacy status workflow.
For projects where shared revisions were enabled after 2 October 2025 the new status workflow is enabled by default.
Projects that want to start using the new status workflow can request for this to be enabled for their ongoing projects.
There is no migration of the legacy draft revisions to the new shared revisions.
Draft revisions remain in the project and can be published, but cannot be migrated to shared revisions yet.
With the new status workflow the tabs workspace a and published are visible towards the top of the documents and models pages.
Revisions will start out as shared revisions and can be published to become published revisions after which they appear in the published tab.
Read more about revision publishing here.
New validation workflow
Projects that enabled draft revisions before 2 October 2025 will continue to see the legacy validation workflow.
Projects where shared revisions were enabled before 2 October 2025 will continue to see the the legacy validation workflow.
Projects that have not previously enabled draft or shared revisions can now start using the new validation workflow by enabling shared revisions.
New projects that are created based on a template project where the new validation workflow is enabled will see the legacy validation workflow.
It is often best to enable this feature at the start of a new project as team membership might have to be adjusted for new ways of working.
Work continues to be done on the new approval workflow and while the following differences between the old and the new validation workflows exists these might improve in the future:
Markups are only visible in the file review of open and closed approvals.
Topic templates are not available for the new approval workflow.
Many of the settings in topic templates are moved to the new workflows page.
Topics cannot be generated as a result of the publishing of an approval with the new validation workflow.
After giving the final approval for a document the published document is exactly the same as the shared revision that was published. Annotations in markups on the approval remain in the approval and cannot be viewed on the published revisions. Annotations in markups are neither transferred nor do they become part of the document in the published revision.
The new approval workflow does not have notifications.
Only the English translation is available.
The new approval workflow can only be enabled if shared revisions were not previously enabled. Projects created based on a template project where the new legacy workflow is enabled will have the legacy validation workflow enabled. It is only possible to see the new validation workflow in projects based on template projects where shared revisions have never been enabled.
Only one approval request step can be active at once.
All documents in an approval request step have to either be approved or denied before the approval request can advance to the next step.It is only possible to either approve or reject.
Comments can be added via markups but there is no approve/reject with comment like in the legacy validation workflow.
Enabling on-demand features
Some features can be requested to be enabled for existing projects by the contact person for your Catenda license while others can be enabled with a setting in the project.
When a new feature is requested to be enabled, a meeting will be set up with a support representative to discuss the current status of the feature.
If a project is not already available where the new feature can be tested a dummy project will be created for a limited time where the new feature can be tested.
Requesting for on-demand features to be enabled
Some features can be requested to be enabled for existing projects by the contact person for your Catenda license while others can be enabled with a setting in the project.
When an on-demand feature is requested to be enabled, a meeting will be set up with a support representative to discuss the current status of the feature.
If a project is not already available where the on-demand feature can be tested a dummy project can becreated for a limited time where the on-demand feature can be tested to consider if the feature is ready to be used.
Objects page
Search on any content from your IFC with logic.
The objects page is an on-demand feature that can be requested to be enabled for ongoing projects.
New projects that are created based on a template project where this feature is enabled do not have this feature enabled.
For example all "Door entities" from "Model A" that are taller than 2 meters.
Configure columns to display the relevant properties for each row element in the table.
If filter results have an object in the 3D viewer this object can be selected in 3D.
Export selected elements with the configured property columns that are displayed to excel.
Similar to the QTO feature objects that are selected in 3D can be filtered as well.
Compared to the QTO feature it is not a problem to load thousands of rows in the table.
Report editor
Create report templates for topics and documents so project members can select topics or documents from the table and use the report action to generate a report.
The reports page is an on-demand feature that can be requested to be enabled for ongoing projects.
New projects that are created based on a template project where this feature is enabled do not have this feature enabled.
Separate templates can be created for topics and documents.
When a template is available in a project the report action can be used with selected topics and documents to generate a report based on the selected template.
Support for how different values can be displayed on the page is offered by Catenda.
If you would like a custom report tailored to your company we can get you in contact with a consultant that can help with this.