Released on 2020/02/20. New features:
New page header design: the coordinates and timemachine button is now unified in the update indicator
Renamed "View" to "Report"
Node-styling now works for assets based on properties of their links
Many usability improvements for the Transformation Cockpit:
- Extended graph and table reports in the application-specific Discovery section
- Survey integration in the application-specific Discovery section
Assets can now be cloned easily in the Repository or in table reports
Usability improvements to surveys
A survey question can be answered with "Accept" if the data is already correct
Context-sensitive documentation and documentation search is now directly available from the main navigation
Timeline shows scheduling group as commit author
Database performance improvements
Improved general repository performance (search, importers etc.)
Increased compatibility with different OAuth providers
- Importers now parse numbers in different locales correctly
- Fixed an issue where multiple importers in the same scheduling group would overwrite each others changes, resulting in overall empty commits
- Fixed an issue where the "last modified date" was not assigned correctly to imported links under certain circumstances
- Improved handling of simultaneous changes on the same asset by multiple users
- Increased robustness of change propagation
Released on 2019/12/10. New features:
- Vastly improved Transformation Cockpit
- Assets now snap to the grid in the dependency view
- Deleted assets can now be restored using the time machine
- Ability to define importer priorities on a property level
- Markdown support for texts in surveys
- Key-based authentication for SSH importers
- Improved Cloud Proposals for application containing mainframe technologies
- Helper tools to read CSV/JSON from columns in importer
- Enhanced visualization of Cloud Proposals
This release includes possibly breaking changes:
- There is an upgrade process scheduled in the first server startup. Please note that especially for Txture deployments with long histories the first server startup can take up to a few hours. The upgrade performs a change in the persistence of the asset graph for reasons of performance optimization.
- The link importer options of the VMware importer always returned the same values, regardless of their direction (e.g. VMs -> Host returned the same as Hosts -> VMs). Please check that your settings still match the link importer direction.
Released on 2019/10/10. New features:
- LeanIX importer
- Kubernetes importer supports Amazon EKS
- Txture Excel importer for Cloud Transformation module
- Property importer improvements on value synchronization
- Aggregation visualization
- Change notifications (preview)
- Copying of importers
- Cloud Transformation Cockpit for improved process flow
- Improved Cloud proposals on operating systems and certifications
- Option to disable Cloud readiness rules individually
There is an upgrade process scheduled in the first server startup. Please note that especially for Txture deployments with long histories the first server startup can take up to a few hours. The upgrade performs a change in the persistence format of the asset graph for reasons of performance optimization.
Released on 2019/08/19. New features:
- HyperV Importer
- Improved VMware importer. This might require reconfiguration of your VMware importer.
- Cloud migration proposal have been extended to new technologies and products.
- OAuth implementation. Txture now allows to authenticate users via OAuth.
- The structure is now a view on its on an can be embedded in application outside of Txture.
- Increased sorting performance in the repository
- Significantly improved "Propose mapping" function for importers
Some VMware importer column names have changed, as the were erroneous before (e.g. RAM size was returned in bytes, when the column was named 'RAM in MB'). Please have a look at your VMware importer configuration to check whether any column names changed that were in use. Remap them to Txture properties accordingly.
Release of Txture on 2019/06/15. New features:
- Complete redesign of the view management tab
- New database engine with better performance and reduced on-disk size
- UX improvements for cloud migration reports and cloud pricing
- Rewrite of the table component with strongly improved performance and new features
- Views can now be shared with roles or specific users
- Simpler time machine UI and with details of the applied changes and graphical overview of changes over time
- New REST endpoint to export view assets via CSV
- Cloud proposals can now be marked as selected and will then be used for the migration roadmap
- New data sources for importers: SSH and WinRM
- Administration area now shows the configuration values of
- Option to send welcome emails to new users
Release of Txture on 2019/04/01. New features:
- Cloud pricing feature: cloud proposals now allow to estimate the costs for each proposal for various providers.
- Hierarchical cluster matrix: the cluster matrix feature was enhanced to allow grouping by several parameters on each axis.
- Performance improvements for the asset and survey timeline
- Several new asset importers for the AWS data source
- New importer for Oracle Cloud
- Various bug fixes
Release of Txture from 2019/01/29. New features:
- Extensions to Cloud transformation module
- Allows Txture users to plan cloud migrations based on the individual readiness of applications.
- Improved replacement options in the cloud for complete deployment stacks.
- New Gantt chart visualization (requires license update) for EAM use cases.
- Additional AD-Importer filter. Allows filtering the imported users without modifying the base DN.
Release of Txture from 2018/12/11. New features:
- Txture now runs on OpenJDK 1.8 eliminating the need for our customers to obtain support for Oracle Java 1.8
- Completely revamped export dialog. It is now also possible to export assets and links to Microsoft Excel™ documents.
- Active Directory importer. While similar to the LDAP import, the new AD importer removes a lot of configuration need.
- Improved column management in table-based views
- Possibility to use multiple dashboards and share them with other users or roles.
- The asset detail sidebar is now resizable.
- Improved matching rules for the association importer
- Applied node-styling rules are now explained in a legend for most views.
- Queries for Datetime-Properties can now be relative to now.
- Various improvements to surveys
Info:(Optional) Most views now have a legend indicating which node-styling rules have been applied. In order for this legend to work, [labels must be set](/administration/node_styling) for each node-styling rules.
Release of Txture from 2018/10/11. The following new features have been included in this release:
- Commenting and attaching files on assets and properties; both displayed in the asset detail sidebar
- Timeline per asset in the asset detail sidebar showing all past changes
- Adaptions and improvements to the query bar
- Upgrade of the survey feature including general surveys and asset-based surveys
- Cluster matrix visualization can resolve arbitrary paths to related asset types as row and column entries
- New "Waterfall" visualisation type for investigating change in amount over a given ordered property (e.g. application cloud migration phases)
- The following importers have been added:
- Red Hat Enterprise Virtualisation (RHEV)™
- Profile pictures for users
Release of Txture from 2018/08/13. The following high level features and functionality has been implemented:
- Pre-configurable reports via reporting templates with placeholders (*)
- Custom sub-captions for assets and links via node styling rules
- Property importers to import property values from external data sources onto existing assets or links
- New "Tree" visualisation type to display asset dependencies in a flexible tree layout
- Change propagation now supports filters on link properties during traversal to neighboring assets
- Improvements to importer transaction handling
- New importer types
- Google Cloud Platform
- Alibaba Cloud
Info:Link importers are not automatically scheduled and executed based on their corresponding asset importers anymore. As a consequence link importers now need to be scheduled explicitly.
Release of Txture from 2018/06/12. The following high level features and functionality has been implemented or was changed:
- User importers configurable in admin area
- Dynamically assignable roles from import data
- In txture.properties all keys starting with
txture.security.userimporterare deprecated and can be removed in Version 7
- Importers for Amazon Web Services and Microsoft Azure
- Importers for LDAP
- Better status monitoring of importers including log access via admin area
- Importers allow filtering of import data rows
- Importers allow dynamic columns for data transformation
- Application of node styling rules in asset sidebar
- Minor design improvements in dependency view
- Shifting from external configuration database to internal database
- In txture.properties the keys starting with
txture.persistenceare deprecated and can be removed in Version 7
- In txture.properties the keys starting with
- Improved file logging for importers and application
- Log files txture.log and error.log are continued as daily txture.log (including error log)
- loggerConfig.xml is obsolete
Info:User importers are now part of the administration user interface and the existing user importer, which was derived from settings in txture.properties, is mostly migrated automatically. As the scheduling is not migrated, the user importer needs to be re-scheduled manually via the user interface.
Release of Txture from 2018/04/06. The following high level features and functionality has been implemented:
- New visualization types
- "Count over time" to indicate e.g. historical changes to the use of a certain operating system in VMs
- "Donut chart" to indicate group-wise counts e.g. applications a division is responsible for that have low vs. medium vs. high mission-criticality
- "Cluster matrix" to group assets that have 1 or 2 properties in common, e.g. applications that are similar due to same mission-criticality and same range of operational cost
- Structure editor now supports refactorings to the information model during runtime and in a graphical way
modelDefinition.xml will be replaced by the new
modelDefinition.json which is created during startup of Txture. The
modelDefinition.json is not intended anymore for manual editing, as the administration area now offers a Structure Editor to perform adaptations to the information model.
During startup the information model definition is now more strictly validated and corresponding errors are reported in the logs similar to this example:
Information model validation errors and warnings
The validation of the current Information Model finished with 1 error(s) and 0 warning(s). The Information model is INVALID. The following is the list of issues encountered during the validation process. Information Model Validation: [ERROR] The Internal Name 'My Property' must be unique, but is used by multiple elements. Offending Element Txture ID: t:49e1de7a-2c68-4cd4-b362-8d78a61ca1d7 Offending Element Txture ID: t:08a58bdb-5aa9-4c26-9fa7-31fc2ca525cf
Any errors that occur need to be fixed as part of refactorings in the modelDefinition.xml, before Txture can be started and used again.
Once the validation passes
modelDefinition.json will be produced and the
modelDefinition.xml will be renamed to
Release of Txture from 2018/02/09. The following high level features and functionality has been implemented:
- Integration of the admin area into the client application
- User and role based access control based on information model elements like aspects, classes or properties
- Multi-tenancy supports the restriction of visibility of assets according to assigned tenants (*)
- REST API for external applications to interact with Txture
- Management of external application permissions and REST access tokens
- Script based propagation of asset state (BETA) (*)
- Management of custom icons for assets
- Rule based styling of assets and associations in visualizations
- Remove the first segment of the cron expression
txture.security.userimporter.trigger(only 5 segments are allowed, with the first segment representing minutes)
- Change namespace with the root element to
'... xmlns="http://www.txture.io/ModelDefinition" ...'
- Change namespace with the root element to
Release of Txture from 2017/10/06. The following high level features and functionality has been implemented:
- Application-wide language to query assets based on properties and paths
- Multi-column sorting in the repository and table visualizations
- Graph visualization now supports expandable asset groups
- Graph visualization now supports auto-grouping by properties, similar to groups by aspects/layers
- Graph visualizations can be zoomed in/out and panned
- Multiple assets can be edited/deleted at once
- Consistent undo/redo capabilities across all visualizations
- Information model properties for date/time has been introduced
- Information model properties for date/time ranges has been introduced
- Customizable, user-specific dashboards with configurable widgets
- Fine-grained, role-based access control for users, user groups, assets and read/write/create-delete actions
- Query-Bar for all visualizations types
Version 2 and prior#
A change log has been part of the distribution of Txture. See the README-style changelog files within your web archives.\*availability depends on license