R2.3. includes new way to create and define many-to-many relationships with Blueprint Designer.
Release date: 11.6.2018
Also includes one important fix related to Audit misinterpreting optional relationships.
|Blueprint Designer||Available Relationships|
Previously Blueprint Designer used any matching tables as possible m2m relationship between two records. That was sometimes confusing, since most of those tables are not meant to be relationships. For example Incident table is not meant to be m2m relationship table between User and Group.
Now with "Available Relationships" definitions the DCM Admins can define which tables to use as m2m tables. Application includes most commonly used m2m tables, but it's easy for admins to manage the definitions. In addition to these definitions, blueprint designers can still choose to use any table referring to both source and target as m2m table.
|Licensing||Free version||Free version now includes maximum of 2 blueprint versions.|
|Blueprint Designer||Recreated relationship creation window||Recreated the Relationship creation window. Changes mainly related to using the new Available Relationships definitions.|
|Navigation||Added "DCM" to Application name||Now it's easier to find all DCM related modules, since Application name includes "DCM" in the beginning.|
|Audit Results||Mandatory links after an optional link|
Additional fix was applied to this previously implemented fix. Now can handle 1..* multiplicity for source record, that previously still gave invalid results.
|Audit / Blueprint designer||Minor fixes||Minor fixes related to Audit results and Blueprint designer.|