2.29: risr/advance

New Features

• User Documents library transitions to Files area

  • We are retiring the Document library. In its place users have a consolidated, searchable and read-only view of all files previously attached to or uploaded to events, and any files previously added directly to a user’s Documents library will also be retained.

  • We have introduced a new look for the Files area (formerly Documents library), including improved filtering and search functionality. Folder structures previously used in the Documents library are incorporated into the names of files denoting what those file paths were. It is not possible to create new folders in the Files area.

• New File field attributes

  • Administrators can add a file field to an event type (form) to prompt users to add required documentation to an event. To make the file field more robust, additional attributes are available for administrators to limit and give guidance to trainees around what types of files they can upload. The new attributes include: ‘Allowed file types’ (Word, MS Office, PDF, Images, Video), ‘Maximum size in MB per file (up to 1000MB)’ and ‘Allow multiple files to be uploaded’.

• Retirement of the “Attach document” functionality

  • Users will no longer be able to add documents using the generic “Attach document” that was automatically available on every event section. Instead, organisations can specify precisely where file uploads are available and required as part of an event workflow by including a file field. This also enables administrators to control whether users can delete or replace files on an event by assigning the relevant permissions.

  • The option to attach a document as a comment on a completed event has also been removed.

Watch a video on these new features and find a list of FAQs in our risr/advance knowledge base. Information text available in the side bar of the following pages has also been updated to indicate the key changes above: when a user is filling in a section, accessing the Files area and editing event type sections.

Improvements

• Improved searching of files within the timeline and Files area

• Removal of user storage limits

• Inline preview of files (for supported PDF and image file types) so users don’t have to download files in order to view them

• Permissions to view files now fall into line with the permission to view events. Users always see the Files area of another user and are only able to view those files which are attached to events they have permissions to view

• A progress bar now indicates the progress of file(s) being uploaded to file fields

• The word “links” has been removed from report outputs when users are reporting on goal progress for goals with no defined targets and so now only the number of linked events is outputted

• Reports containing aggregations and groupings will now display the total number of records being outputted e.g. 'Showing 1 to 50 of 500'

• It is now possible to filter and output ‘Organisation admin’ as a role in Reports

• The ‘Download PDF’ function available when viewing completed events now names the downloadable file according to the name of the event and the current date e.g. Event_name_2024_06_25

• Bulk importing of files now supports importing files to blueprinted file fields in events

• The ability to reject an event section is now available within quick fill

• The text describing risr/advance when a user changes organisation on the login page has been updated to be more contemporary and in line with our rebranded modules

Fixes

• Fixed the error when sorting the list of available reports by name

• When draft event sections were deleted, links to goals were not being updated accordingly

• Deleted private events were not correctly associated with goals

• Users assigned the ‘Organisation admin’ role could be invited to fill in the next section of any event

• Uploading and updating profile pictures was not working

• File custom fields and blueprints could not be uploaded to events via the API

• Files could not be uploaded to file user fields

• There was no validation that a file had finished uploading to a file field before when an event section was submitted