Release Date: 13-03-2021
iPassport v3.5.7 is another small improvements release, adding a number of features across the application.
This change makes it possible to save progress on a competency test or assessment, allowing these to be completed in multiple sittings rather than forcing the test to be completed in a single visit.
This can be configured on a test-by-test basis, by configuring the Allow Progress to be Saved? option in the test template.
When you receive an email from iPassport relating to a controlled document this will include a link directly to that document. You just click the link and are taken directly to the doc in iPassport. We have expanded this so most task-based emails across the system will include a direct link to the record in question (e.g. an email relating to equipment maintenance task will include a link to the equipment record).
When editing a Contact record it is possible to select which company they belong to. However, this information was “one way” and contacts were not displayed on the Company record.
We have added a new Contacts tab to a Company record, making it easy to see any key contacts relating to that company. These contacts still need to be created and managed from the Contacts area but they are now visible when viewing the Company.
We spend a lot of time writing and updating our user guides with each iPassport release. We are aware that this resource is not utilised as it could be, partly because the guides are hidden away and difficult to navigate.
As a first step to address this we have moved the link to our user guides into the Global Menu, up in the top right of the screen.
We will be putting more effort into making our user guides more accessible in the coming months. The next step will include adding in-context links to the appropriate user guide, direct from the relevant part of iPassport. We hope these guides will prove to be a useful resource and our goal is to make it easy to find the information you need at the moment you need it.
This change fixes a hole when two iPassport settings are used in conjunction.
When both of these settings were enabled the user was able to authorise the doc from an email without entering a PIN. We have changed this so they will now be required to enter their PIN, even when authorising from an email link.
We have added the ability for site admins to customise the names of iPassport’s menus. This can be achieved in OU settings and will be applied to all users who have this OU set as their Home OU.
Based on customer feedback, when creating a new user the Home OU will default to that of the person creating the user record.
We also changed the permission checks so anyone with permission to create users in a given OU can automatically view and edit user records in that OU. (Previously they would explicitly need to have create, view and edit permissions to do so). This is part of our ongoing effort to simplify iPassport’s permission structures.
We have added a new user importer, allowing admins to populate details in a spreadsheet, save this as a csv file and import the collection of users into iPassport en masse.
We have added a CSV export to the Users search screen. This includes the users’ user groups, skilled groups and distribution lists.
When user accounts are created iPassport assigns a secure password, which is emailed to the user. As a security measure new users will now be forced to change this password on first log in.
Previously control of which users could verify non compliance action was based on whether the user had permission to add non compliance actions. It was not possible to set up a group of users who could add but not verify NC actions.
We have added a new permission: Non Compliances: Verify Actions to allow further control around NC actions. This permission has been added to all roles assigned Non Compliance:Manage Actions, meaning the functionality for your users will be unchanged. However, if you would like to specify that users can add actions but not verify then you can now achieve this by creating separate user groups and fine tuning the permissions assigned to each.
The following default sort orders have been added:
We also fixed some incorrect/confusing permission checks:
This improvement will only affect Enterprise accounts who are subscribed to the optional Account Export Service. It is now possible to limit backups to specific facilities in addition to OUs.
For customers using iPassport’s Staff Leave feature we display a summary of leave in the left menu bar. This did not check the Staff Records:View Leave permission to see if the current user has permission to view leave requests. We have added this check. Staff leave will now only be visible in the left menu to users with this permission.
It was discovered that control over who could create training events (Training Schedule area) was actually being granted based on users having permission to create training courses.
This has presumably never been an issue as most accounts set up their training course admins so they can create courses and then schedule them. This only came to light because one of our customers wanted to separate out which users could create training course records and which could schedule training events.
This has been corrected. In order to schedule training courses users must have Training Events:Create Training Events permission.
It was reported that clicking the unsubscribe from all iPasport emails link (at the bottom of any iPassport email) was not working. This has been resolved.
We are constantly patching bugs between releases and tend to only highlight bugs which are noteworthy in the release notes. For a full list of bug fixes you can see the iPassport change log at any time. Just go to Help (top right) / About iPassport and change the filter from ‘Releases Only’ to ‘All Updates’.
Validations documents are not included with minor releases. Full validation documentation for these new developments will be published when we launch the next major update of iPassport (v3.6.0).