RAP_Home_edited.jpg
Release Notes

Release 1.4

Status of 'Controlled' only set if residual risk = target risk

For a risk to marked as 'Controlled' all of the actions must be completed, all controls must be in status 'Green' and the residual/current risk score must be at least as low as the target risk score.  If there is no residual/current score or no target score, then the status simply depends on the actions and controls.

Icons for platforms other than IOS

New icons have been added which are used when bookmarking the website.

Clicking edit on an action should put the focus on the action tab

On the action list page, the 'edit' icon which is at the far right hand side of the list  now takes you to the action plan tab of the risk page,

Notification sent to old risk/issue or action owner

When the owner of a risk/issue is changed a notification is now sent to the new owner and now also to the old owner, if it is not the old owner ,making the change.

Notification queue monitoring page under admin

There is a new page within the 'Maintenance' section of the website called 'Notification Queue'.  This page shows the queue of notifications which are waiting for an email to be sent to their recipient.  At the moment the page is only available to root level administrators as the entire queue is shown.

Multiple Manager Notifications

It is now possible for any user to request notifications of changes to risks/issues on any org unit to which they have access.  This is done using their 'My Details' page where they can set their notification level against any org unit on which they have at least 'viewer' access.  The level is set in terms of the appetite rating of a risk/issue and can be set for example to see only those rated as 'Extreme', or to those rated ' Medium' or above, or to all, so you will get a notification regardless of the risks score.  As usual, a notification will only be sent to you if you are not the person making the change.  Notification levels can also be set by the administrator using the employee maintenance page.

Unique Login ID

This is another change which has been introduced to cater for multiple companies sharing.  When you log on you must mow use your email address instead of your username.  Email addresses will only be required to be unique within each company and the company you are logging on as is determined by the address used.  So if you go to http://acme.riskassuranceplatform.co.uk then you email address is validated against the list of users for the company 'Acme'.

Ability to Search By Risk ID

The system does not currently support searching by risk id.  This has been added but currently searches within an entire installation.  In future this will be amended to just search within the company you are logged on for.

Clickable Matrix

The first element on the dashboard page is now a matrix showing the numbers of risks and issues with each combination of impact and likelihood.  Each cell on this matrix is clickable and will take you to a list of the items making up that number.  Once in the risks/issues list you are also now able to search for items with a specific combination of impact and likelihood.

Risk Numbering Within Each Company

Risks and issues are now numbered from 1 for each company within the same instance of the product.  When combined lists are displayed the risk/issue number is prefixed by an abbreviation unique to the company so that items with the same id can be distinguished.

Menus and Pick-Lists Now Only Show Accessible Org Units

When navigating around the system, users should now never see any org units outside their own company.  They should also have fewer inaccessible items displayed purely for navigation purposes.  In other words, if a user only has access three levels down in the hierarchy then they won't see the first two levels.  Previously they would have seen all levels above the accessible level but wouldn't have been able to select them.

User Cannot Be Assigned Access Above Their Company

In an instance which includes multiple companies, it should not be possible to assign a user permission to access parts of the hierarchy which are outside their own company.

Top Risks and Top Issues Should Always Show Something

The top risks and top issues panels on the dashboard should now always show the user's top 5 of each.  Previously they showed items with a rating above a certain threshold.  This meant that the panels were quite often empty even though the user had risks/issues.

Product Skin For Each Company

Where multiple companies are hosted within the same instance they may now each have a different skin.

Improved and Responsive User Interface (New)

The user interface for the product has been redesigned to improve it's appearance and to allow pages to re-size automatically according to the size of the screen being used.  This enables the product to be more easily used on small devices such as iPhones and iPads.  It is also now compatible with all modern browsers.

User Name Has Company in Brackets (New)

When presenting the user with a pick-list of potential owners for a risk, or action, etc, the system now displays the user's department in brackets after their name, or their company if they are in a different company.

'Personal' List is now Only Items I Own (New)

Previously the 'personal list showed all items on which the current user had a role.  This has now been amended so that it shows only those items which the user owns.  In the case of risks, this will include risks which the user has authored but which haven't yet been assigned an owner.

Employee List Shows Company or Department Depending on View (New)

In the maintenance section of the product, the employee list now shows each users department where they are in the same company, or their company name if they are in a different company.

Bug fix

  1. Inconsistent message on length of password - On the change password page there is a message indicating how long a password should be.  When actually changing the password a pop-up warns you if the length is wrong.  The message on the page and the pop-up message were inconsistent but this is now fixed.