Release notes version 7.2 - CTMS

Dear reader,

The CTMS of ResearchManager is being updated to version 7.2. Please find below the list of added functionalities and improvements. We are happy to answer any questions you may have about the update. For inquiries, please email us at support@myresearchmanager.com. 

 

  In short

Among other things in this version:

• Quick and easy navigation between related studies with the new Study Link component!
• Which organization is this contact person from? Enter it in the new 'organization' field.
• Data display components: now with the correct units and decimals.
• The maximum allowed number of characters in budget components has been increased.
• Due to the versatility of the review component, the items in the table are now called 'row' instead of 'review.'
• The speed of the export page and modifying assessment components has been improved.
• In the approval component, a reviewer can be linked to a row. Within this row, the reviewer can be granted a specific right, such as 'Edit comments.' This allows the reviewer to clarify their approval, but only within this specific row.
• Bug fixes: We’ve resolved as many issues as possible.

Read below for details on all the changes.

 

 

 New

• New functionality: Study link

A new component is now available: Study Link. This component allows you to easily link studies together and quickly navigate between related studies.

Features:

Table View: The Study Link component is a table that displays linked studies.

Automatic Mutual Linking: When ‘Study B’ is added to the Study Link table of ‘Study A’, the link is automatically created in ‘Study B’ as well.

Rights: Configure which roles can view, add, and edit studies.

Quick Navigation: Linked studies can be opened directly from the table by clicking the arrow (highlighted in yellow in the image above). If a user does not have access to a linked study, the arrow will not be displayed, preventing navigation to that study.

Specific Properties:

• • Define which studies can be added to the table based on study types and statuses.
  • Choose which fields are displayed in the table.

This new component makes it easier to visualize relationships between studies and efficiently navigate between relevant studies.

 

  Improved

• Data view components: now with the correct units and decimals.

If a unit was set for a numeric component, such as centimetres, the unit was not displayed when the numeric component was selected for a data view component. The same applied to the number of decimals set for the source component. Both are now correctly applied in the data view components.

• Budget component: maximum of characters increased
  

A maximum number of characters was set for several columns within the budget components. For the specific columns Price per unit, Time per unit, and Amount realised the maximum number of characters is increased to 70.368.744.177.664.

• Review component: items are now called 'rows'
  

The review component is a versatile tool, meaning they can also be used for amendments and contracts, not just for reviews. The term used for items within the review component was ‘review’, however we have changed this into ‘row’. For as long as a component is empty, this is an example of what can be shown:

Or in the pop-up if you want to delete a row:

• Comments of account requests included in email sent to requestor
  

While providing (dis)approval of an account request, the admin can elaborate on their choice in the box ‘Comments’. The entered comments were not included in the email that was being sent to the requestor. The mail only showed whether or not the approval was approved. The clarification will be integrated into the email by default.

• Review component: improved system speed
  

The system's performance when modifying review components was not optimal. The cause of this issue was the 'Rights' tab. This tab contains numerous statuses, each with dropdown lists for rights like Read, Edit, and Delete per role. The way the page was structured resulted in suboptimal speed, so we had to adjust the 'Rights' tab.

Previously, all roles and statuses were displayed on one screen, requiring users to scroll to modify everything.

It looks different now:

Now, at the top of the page, you select the role for which you want to configure rights—for example, the 'Researcher' role. The page then displays all statuses with a column showing the rights for the selected role. The top dropdown allows you to set rights for all statuses at once.

At the bottom of the page, a new function has been added: "Copy rights from the current role to the following roles."

This function enables you to copy the rights from the current page and selected role to other roles, streamlining the process.

• Export pages: improved performance

The speed of the page where you can create exports is improved.

• Approval component: additional right added

The review component is a versatile component that can be used for multiple purposes. Certain users can be added by default, users connected to the selected research- or support department can be added automatically, and it is possible to manually add users to this component. Consequently, users can be restricted to only filing their own approval. A nice way to specifically request a review!

This update will include a change of this component, which has to do the rights. Five rights were available for each role: Read, Add, Edit, Review, and Delete. Users with the right ‘Review’ can only review that specific line. Other fields in the same line, for example the field ‘Comments’, cannot be edited if the user only possesses the right to review. In order to make changes, the user be provided with the right to ‘Edit’. This was often not desirable, since all fields can be edited in the component, including those of other users. The option to fill out the section ‘Comments’ was desirable, so that the user could clarify the review. As a result, we have added a new right: ‘Edit comments’

If you want your users to only be able to (comment on the) review: select for that role the rights ‘Review’ and ‘Edit comments’.

Old rights structure:	New rights structure:
Read Add Edit Edit comments Review Delete	Read Add Edit Review Edit comments linked rows Delete

Important changes:

• "Edit" and "Edit Comments linked rows" (Edit CLR) are exclusive:
  • In case Edit is selected, the Edit CLR will be disabled automatically, and cannot be activated.
  • In case Edit CLR is selected, the Edit will be disabled automatically, and cannot be activated.
• Rights and field access:
  • Edit: Users can edit all rows and fields, including the field Comments.
    
  • Edit + Review: Users can edit and review all rows and fields, including the field Comments.
    
  • Review: Users can only review the rows that have been assigned to their role.
    
  • Review + Edit CLR: Users can review assigned rows (in the grid), and only edit the field Comments. Other fields, like Deadline date, will remain grey and noneditable
    

This modification allows a clearer separation between editing all fields and specifically editing the Comments in assigned rows. As a result of this, the user experience will be improved. Next to that, the risk of undesirable changes will be reduced.

• GDPR message enhanced

When logging in for the first time, users are shown a message about the General Data Protection Regulation. However, this message was only displayed to users logging in with a username and password, and not when using Single Sign-On. The message has been updated and will now be shown to all users again when they log in for the first time after this update.

 

 Bug fixes:

• In case that a process is shown based on conditions, the dependents are only findable per chapter, subchapter, paragraph, and component. The process is then dependent of a component. While editing chapters, subchapters, paragraphs, and components, a tab with dependencies is shown that displays which components of the system are dependent on the selection. The conditions of the processes were initially not shown here, even though this is desirable. Therefore, these are added now.

• In some cases, the preview of the calculation was shown incorrectly while editing. This did not have any consequences for the calculation, however the preview should correctly reflect the calculation. This has been resolved.

• Initially, the first-shown status in the drop-down list of document statuses changed during uploading one and more documents. From now on, the status that is shown first in the settings, will be shown first in the drop-down list.

• In the component ‘Approvals’ the sorting of rows in the table changed, once approval was given. This was not desirable. Moving forward, the sorting of the rows will remain unchanged if approval is edited.

• In the username and password fields while logging in and the user settings allowed the last character to be a blank space. From now on, this will be automatically checked and corrected.

• During editing of the Contacts component, the field ‘correspondence’ was not shown in the columns (active/inactive/mandatory) of the specific properties tab. Instead, an empty row appeared in the column. The field will now be displayed correctly.

• In the SAE-component, the sorting based on ‘date added’ is working again.

• At the Sites management page: if clicked on ‘Block’ or ‘Activate’ for a row, a browser pop-up appeared asking for confirmation. This should have been an internal pop-up. This is resolved.

• The filters on the page of share requests for the columns ‘date sent’ and ‘date received’ were not working, which is now resolved. The page is only available for applications that have a connection.

• In exports where grid-components like Contacts or Sites were selected, the first Excel tab showed a column with the title of the grid-component. The data of the grid-component are shown on their own Excel tab in the file. The columns of the first tab are deleted.

• If a user had read linked rows access, instead of read, they never received notifications for the Review / Q&A component. Now they do.

• The reminder mails were not send from the approvals component if the component was place in a subprocess, we have solved this.