Releases: finos/waltz
1.61
Noteworthy
EUDA Taxonomy Mappings
In 1.60 we added support for linking EUDAs to flows and assessments. In 1.61 EUDAs can now be also be linked against taxonomies (e.g. Capability), providing a way for us to more accurately document our IT landscape. Aggregate views will correctly show the mix of Applications and EUDAs.
Note: We shall be looking (in a future release) to remove the ability to 'promote' apps to EUDAs now that they have feature parity with applications.
Physical Flows
Waltz has often aggregated flow information from various sources. However it can be difficult to refer to flows outside of using their Waltz database id's. This release ensures each physical flow has a simplified external identifier (we won't overwrite any provided id's).
As part of the change external identifiers can be used in URLs which will simplify deep-linking into Waltz.
The new Ids take the form:
| ext id example | desc |
|---|---|
PF_000001 |
Physical flow identifier |
PS_000001 |
Physical spec identifier |
LF_000001 |
Logical flow identifier |
Search
Data types can now be searched for by their external ids (stored as code in the database)
1.60.2
A minor release addressing bugs.
Changes
- FIX: Flow Data Type editor not showing read-only entries correctly
- FIX: Taxonomy Management - 'merge node' feature fixed
- FIX: Capability Attestation - minor presentation fixes
- All Issues
1.60.1
Noteworthy
Flow Classifications
Consumer classifications
We have extended the flow classification rules in Waltz to allow for a consumer view of data types. This allows for rules to be registered that will discourage direct flows to and from a given system (e.g. a rule could be System A discourages all Book Data flows from all suppliers).
The changes made to Waltz include:
- Updating the views to show both producer (i.e. Auth Source) and consumer ratings
- Reworking the flow rule calculation engine to incorporate consumer ratings
- Previewing the producer and consumer ratings when updating data types to logical flow
- Allowing custom messages for flow classification rules which display when modifying data types e.g. "Users should no longer send book data to System X, register the flow against the consumer instead"
Flow classification UI
- Simplifying the registration of Flow Classification rules
- Consumer classifications shown on source/target graph popup
- Producer/Consumer classifications shown in flow datatype editor
End User Applications
It is increasingly important that the usage of End User Applications are captured in data flows. Previously this required us to 'uplift' end user applications into full application records in Waltz via a promotion process. With Waltz 1.60 end user applications are now first-class entity type in Waltz and can be direct participants in flows (along with the existing Actors and Applications). To support this change we have added
- A new End User Application page (incl. assessments, bookmarks, notes, people)
- Integration of End User Apps to flows
- End User app flows supported in Flow diagrams and filterable in the details
- Site search has been extended to include End User Apps
- Flow related API's have been updated to include End User App information
- End User Applications can be rated against Flow classification rules
Other
Applications
App export
The bulk application UI view (e.g. from Org Units) was including columns which were not included when exporting from the UI. This has now been fixed and the export matches the UI.
All
All closed issues: https://github.com/finos/waltz/milestone/181?closed=1
Full Changelog: 1.59.1...1.60.1
All issues
1.59
Merge pull request #7042 from deutschebank/db-contrib/waltz-7032-flow… …-classifications-add-directionality Db contrib/waltz 7032 flow classifications add directionality
1.58.2
Noteworthy
- Physical flow registration name error by @davidwatkins73 in #7026
Full Changelog: 1.58.1...1.58.2
All Issues
Contributors
Assets 5
1.58.1
Noteworthy
- Data Type Decorator section has been updated to show more information on logical flow view #6986
- Assessments can be added to involvement kinds #6908
- Waltz Svelte Component now cascades destroy events from ng to svelte #7000
- Physical flow name has been made visible #6159
Full Changelog: 1.58...1.58.1
All issues
1.58
1.57
Noteworthy
Measurable Ratings
- Each rating now has a dedicated page. This allows us to link in other entities like bookmars, people and assessments.
- For example you may want to have a jurisdiction assessment combined with an applications capability mapping.
Primary Ratings and Assessments
- Users can now select (only) primary ratings to be included in Report Grids
- Primary measurable ratings and assessments can be seen in the ratings sections
Applications Section
Rewritten to support primary ratings and assessments
Flows
The application flow detail section now shows assessments on flows and has more filtering options
OAuth Authentication support
LeadingPoint have contributed a fantastic addition to Waltz to enable integration with external OAuth providers.
Other
1.56
Merge pull request #6890 from davidwatkins73/waltz-6889-mini-fixes Fixing occasional failure of phys flow table
1.55.3
Merge pull request #6871 from deutschebank/db-contrib/waltz-6834-more… …-flow-table-tweaks Db contrib/waltz 6834 more flow table tweaks