It took us a long time to publish a new article on our blog but here we are. If you are a partner you definitely saw the work we have done over the summer. We also prepared a few articles for the coming weeks to talk about graph, PLM and why their alliance is a real disruptor on the PLM market to solve the enterprise-wide configuration management.
We have not communicated much for each of our previous release, therefore we need to catch up on the features we delivered so far. We are on a monthly release frequency and our current implementation projects can benefit from this by easily upgrading their instance without our assistance during their development.
Just a quick reminder before we get into the 1.2.2 description. We use a 3 digits version description. We apply the SemVer methodology. The ground rule is the following:
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards compatible manner, and
- PATCH version when you make backwards compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
What's new in 1.2.2
We improved the upgrade process to allow new types of change which would impact your datamodel and/or your database in a way that it would require some sort of scripting.
We updated our server to support the latest Neo4j version and also allowed to support either you have SSL enabled or not.
We made a few small bug fixing, and enhanced the user experience around the Engineering Change Order. We also added a datepicker when you need to edit dates directly in Grids.
The method editor needed a few design fix (nothing functional, just visual) and we had to review the translation process to reduce the amount of translation needed and make it easier to directly set the translation in the default language. It is now also possible to change the counter actual value for node numbering.
We added a test file to allow customers to add test that complies with their datamodel. Our test may not be relevant when you define your own datamodel therefore you have a file now to do it. If you need assistance to write test, send us a message at Ganister support. We are developing our dev training class which will also explain how to build a full test for your customized solution.
Main evolutions since 1.0.0
Since 1.0.0 we already made quite a lot of improvement while supporting upgrades. If you started working on 1.0.0 (we even started with earlier version for our two first customers) you can upgrade to the latest version.
Most of the work has been done to improve the partner's experience to configure and customize the solution more efficiently to make sure that more time is spent on the PLM functional consulting than on the implementation part.
If you are registered as a partner you can have access to the list of changes on our secure portal.
Looking forward to the next releases
We will try as much as possible to publish a blog post every time we release a new version. It Should be every month then !!