You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NB: This release contains migrations! NB: :application/public is renamed to :event/public (in application_event table eventdata column). NB: :expires-on is renamed to :application/expires-on (in application_event table eventdata column). NB: :last-activity is redundant and removed from the event (in application_event table eventdata column).
The tables take advantage of a new paging feature. Especially, the handler Actions page and its handled applications table uses paging and only fetches handled applications when so requested. The first 50 rows are only fetched by default. Paging can be also configured per table, if the default is not good (page size 50 rows). (Speed up Actions page #3191)
If reminder email is configured for the, expirer bot, it will delete an old draft application if and only if the reminder email is sent and the specified amount of time has passed. Previously it would just delete if the application was very old (esp. when enabling expiry for the first time).
Allow leaving :form field away from catalogue item creation API calls. Previously the value was optional but now the key too.
Application action buttons now wait until request has completed. This should prevent duplicate concurrent requests caused by repeated clicking. (Restrict action spamming #3204)
Additions
(Experimental) Workflow can be configured to enable voting for the approval. Currently all handlers can vote (including bots). Use :enable-voting. (Demo voting for DAC approval #3174)
Cache reloading can be configured using the new :buzy-hours config. REMS will then try to avoid reloading during the specified time spans. (Configurable cache reload timing #3194)
Workflow has new option to anonymize handling users. When enabled, applying users may only see "Handler" in events where handling user's name would appear. Event emails to applying users similarly show only anonymized name where handling user's name would appear. Application API also returns only anonymized name to applying users. Anonymized name is customizable with translation key :t.roles/anonymous-handler, which defaults to :t.roles/handler.
Fixes
Email template parameters for :application-expiration-notification event are now documented. The parameters are different from standard event email parameters, which may have caused confusion.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
NB: This release contains migrations!
NB:
:application/public
is renamed to:event/public
(inapplication_event
tableeventdata
column).NB:
:expires-on
is renamed to:application/expires-on
(inapplication_event
tableeventdata
column).NB:
:last-activity
is redundant and removed from the event (inapplication_event
tableeventdata
column).Changes
:form
field away from catalogue item creation API calls. Previously the value was optional but now the key too.Additions
:enable-voting
. (Demo voting for DAC approval #3174):enable-extended-logging
), for additionally logging the content of mutating operations. (audit log: store relevant id and change #3184):buzy-hours
config. REMS will then try to avoid reloading during the specified time spans. (Configurable cache reload timing #3194):buzy hours
config too.:t.roles/anonymous-handler
, which defaults to:t.roles/handler
.Fixes
:application-expiration-notification
event are now documented. The parameters are different from standard event email parameters, which may have caused confusion.This discussion was created from the release v2.34 "Santakatu".
Beta Was this translation helpful? Give feedback.
All reactions