1.39

Target release date: 25 Jan 2022

Highlights

Survey Management / Action UI Overhaul

As the volumes of surveys have steadily increase we have noticed deficiencies in the UI which has made it difficult for users to see their 'queue' of both surveys to complete and those to approve.

Split across many issues.

Survey Copy function (WIP)

This will allow users to copy the responses from one survey into another survey (of the same type). User will be able to select which questions/sections to copy and whether to overwrite existing responses.

#5818

Docker build

Release builds will create a docker image and publish it to the GitHub / FINOS packages repo.

#5801

Self Service Report Grids

Allow users to create ad-hoc report grids. Private grids can be shared to select users by there owners and administrators can promote the grid to be public, which gives access to all users.

#5682

Source and Target Flow Diagram Improvements

Continued making improvement to the new source and target diagram. Users can now easily flip direction (inbound vs outbound) and filters work against entire hierarchies (rather than just the visible bit). Much more contextual information is shown when various elements on the diagram are selected.

Housekeeping

• Package rename (com.khartec -> org.finos)
• More integration / unit tests
• Javascript Library refresh(Java lib refresh will be part of 1.40)
• Issue templates (should we add more, make them more structured etc)

Hello 👋🏻

Waltzing into 2022.

Olá!

Hi!

Hello :)

hi! Aitana Myohl from FINOS

Hi! Cathy from RBC Capital Market.

Hi :)

Noted from @Russell-G over Webex chat ...

Would it be worth getting a forum prioritisation of new features (including the APIs discussed) so people that are in interested in contributing can understand what where they will make the biggest impact. There must be common features/problems that we are experiencing.

Hi from Russell

Hey 👍

Is there a quick and easy "getting started with Waltz" tutorial that one can run using docker-compose locally and would take less than 20 minutes for a newbie to run?

EDIT: it would have to include a sample dataset

EDIT 2: There is one! https://github.com/finos/waltz/blob/master/docker/DOCKER.md

Meeting Minutes

• Run through of release v1.39 as documented in the following GitHub comment ...
  • 13th January 2022 - Waltz Project Meeting #5813 (comment)
• Create a label for community issues raised to categorise the ideas and requests coming from the wider FINOS community.
• It was suggested first good issues and fixes are tagged for community developers to get involved with.
• It was suggested use cases are created to define how Waltz is being used so others can follow.
• A public sandbox was suggested with running examples of how Waltz is being applied
  • cc @pedroleaoc for Waltz Working Group : Charming Waltz with Juju - Wed 26 January 2022 - 9am ET / 2pm UK #5852
  • It was suggested Legend could supply this through their common data types and common APIs.
  • Standardising on data and taxonomy would be useful, this can then be consumed by Waltz.
  • Waltz can then compare the data and taxonomy against internal banking applications.
    • List out the highest priority entity types and find out how they can be added to Legend.
  • This could be a use case for the public Waltz entity
• Waltz getting started videos shared - https://waltz.finos.org/blog/index.html
• Run through of pull request dockerize waltz #5801 💯 💯 💯
• Waltz community invited to raise issues against dockerize waltz #5801 when found.
• Docker improvements and next steps - Helm Chart and Kubernetes integration.
• Waltz Working Group : Charming Waltz with Juju - Wed 26 January 2022 - 9am ET / 2pm UK #5852 created and invitation sent to the Waltz project group.
  • @ljubon it would be awesome if you can own dockerize waltz #5801 and join the call with @davidwatkins73 as I'm sure the Docker contribution will be referenced.
• Will Waltz support data table attribute level lineage?
  • Waltz team does not have the capacity to do this as very complex.
  • Have discussed solidatus integration in the past.
    • https://www.solidatus.com/data-lineage/
  • Community contributions are welcome.
  • Legend does support attribute level lineage, so having a link between Waltz and Legend will be useful.
• Waltz conversation needed with the Deutsche Bank Legend team to understand priorities.
• FINOS All Community Call introduced to the group.
  • FINOS Q1 2022 All Community Call - February 2nd at 11am ET / 4pm UK community#152
• GraphQL raised as a possible JS framework for Waltz APIs.
  • Create issue for the API technology discussion.

Hi @davidwatkins73 , i would be glad to help! Also, I would consider helm charts too, as it's wider accepted imho.
For sure, I'll be happy to learn what's the options/benefits with Juju charts since so far I worked only with Helm

Hi @ljubon. Looking forward to the session @2pm uk ( #5852 ). Speak to you later.

Hi @davidwatkins73 @mcleo-d Please can you share what is our approach and next steps on setting up the public Waltz instance / public sandbox? Thanks!