v2.30 "Kellosaarenranta"

[aatkin]

Changes

• Some API methods have been unified with the rest by using the command pattern: (Align category API with other APIs #3036)
  • Categories have a new POST /create and a PUT /edit endpoint like the others.
  • User settings have a new PUT /edit endpoint.
  • User has a PUT /edit endpoint, /create remains "create or update".
  • The changes should be backwards-compatible as the old endpoints remain.
  • The non-standard endpoints have been been deprecated and will be removed later.
• The text for saving has been changed "Alice saved a draft." -> "Alice updated the application.". This will be clearer in the future when autosave is enabled (Autosave improvements #3045)
• When continuing an old application, the applicant will be shown a warning about problematic fields. (Autosave improvements #3045)
• Data Use Ontology (DUO) is no longer shown in application UI if none of the resources contain DUO codes. (Hide DUO codes in application UI if no resources require DUO codes. #3048)
• Mondo codes have been updated to version v2022-09-06. (Update Mondo codes to latest #3031)

Additions

• There is an experimental autosave mode that can be enabled. The application is automatically saved soon after the applicant makes a change.
  • Enable it with :enable-autosave true.
  • You may also want to turn on save compaction at the same time with :enable-save-compaction true to show less save events in the event history.
  • In the future, autosave may become the default mode. (Autosave in the background #2767)
  • Applications don't yet automatically get reloaded, should another person be viewing the same application.
    This is a potential future feature. (see Collaborating on an application #2622, Invited member has very little application permissions #2244)
• Data Use Ontology (DUO) codes are now rendered in application pdf. Rendered pdf styles have also been tuned for more consistent look. (DUO codes to application PDF #2857)
• Organization owners are now allowed to edit their own organizations owners. (Organization owners could be allowed to edit their own organization owners #2828)

Fixes

• License, create/edit license and create/edit catalogue item administrator views have been updated to display localized fields the same way other administrator views do. (Unify the displaying of localized fields on admin pages #1334)
• Don't needlessly complain about the config keys that are passed automatically from system properties and the environment. (Improve config merging #2935)
• Application warning and error links were not functioning correctly for attachment fields. This is now fixed. (Required attachment field fixes #2955)
• DUO fields are no longer editable in the UI when application is not in editable state. (DUO fields should not be editable in submitted application #2997)
• Organization edit now requires user to be either owner or organization owner of the organization. (Organization owners could be allowed to edit their own organization owners #2828)
• Organization owner is no longer allowed to toggle enable/disable and archive organization actions. These are available only to owner user. (Organization owners could be allowed to edit their own organization owners #2828)
• Test/demo data creation now uses configured languages. Mismatch between configured languages and data localizations may cause issues in certain UI components. (Demo data and languages #2334)
• Multiselect field is now correctly rendered in application pdf again. More than one selected value resulted in empty field value. (Pdf rendering multiselect field is broken when containing multiple values #3059)

---

This discussion was created from the release v2.30 "Kellosaarenranta".