v2.4 (Version 2, Build 932) - Released October 3, 2018
The new release of Riffyn contains the following new features and bug fixes.
Show/Hide of Columns
Experimental data is displayed horizontally in measure mode, which sometimes leads to a lot of scrolling left and right if your step contains many resources and properties. The 2.4 release allows a user to hide properties, components, resources, or even all the inputs or outputs allowing for display of the most important data. These entities can be hidden by right-clicking on the column header and choosing the appropriate show and hide options, and also from the variables panel in on the right hand side.
Any change made will be available while the user is logged in, and there is also an option to save this view for all users, similar to how run aggregations can be saved and recalled.
The 2.3 release allowed the last transfer executed on a step by the current user or another to be recalled to allow similar transfers to be executed rapidly on different experiments. This release will allow input and output plate IDs to be entered using copy and paste keyboard shortcuts, and sequence fill down, to enable new plate transfers to be rapidly defined.
Prior versions have also only allowed plates to be merged e.g. 4 x 96-well plates into 1 x 384 well plate. It will now be possible to split plates e.g. 1 x 384 well plate into 1 x 384 well plate.
The right hand panel displays the process procedure in both design and measure mode. In 2.4 it is possible to export this procedure as a PDF. This PDF will also contain embedded images of content added to a procedure step.
Improved Data Entry Speed
Our last release contained some noticeable lagging when data was rapidly typed into a property across runs. We have improved the performance to allow for rapid typing without any impact on user experience.
Parsely has always assumed that a standard uploaded file contained at least one row for the column headers (or row headers if transposed). The 2.4 release allows Parsely configurations to be defined for files which do not contain any headers e.g. files outputted from instruments.
Multi-Factor Authentication (MFA)
As part of the 2.1 release, Riffyn started using Okta for identity management for enhanced security. The 2.4 release expands on this by providing organizations with the option of enable multi-factor authentication (MFA) for their users. MFA requires users to authenticate with two or more pieces of information e.g. a password that the user knows and a code generated by a device that the user has in their possession. Riffyn will support a password and a code generated by the Google Authenticator application.
Riffyn now supports Single Sign On (SSO) login for federated users. Riffyn uses SAML 2.0 and SCIM 2.0 to establish SSO and synchronize identity with a customer's user directory.
API & Integrations
The API has been updated to support multi-factor authentication (MFA) through the provision of 2 new endpoints: v1/auth and v1/verify. The 'verify' endpoint will not be functional until MFA is enabled. The existing 'login' and 'logout' endpoints are still functional but users should start using the 'auth' endpoint instead as 'login' is being deprecated.
Future API versions will include more functionality for API key and access token management.
To provide better protection against Cross-Site Request Forgery (CSRF) users can no longer see endpoints in a browser, you will instead need to use tools such as Postman (https://www.getpostman.com). The API documentation page can still be viewed using the browser.
The 'addRunData' and 'batchAddRunData' endpoints now require runIds or runGroup as part of the request. A bug with the 'createTeam' endpoint has also been fixed.