These releases contain any new features, improvements and bug fixes worked on for this period.
New + Improved
* New Federated SSO
FastDraft now supports multiple identity providers on a single instance. This means that Customers with their own SSO will be able to connect seamlessly to FastDraft without enrolling onto ours. A support article will be available soon through our help centre.
* New contract information
My Contracts page and the Contract Summary report have been updated to allow you to see which contracts are using their own custom template and which are pointing at a master template to understand which contracts will benefit from a master template update and which contracts will need their own custom contract template to be adjusted. and also show which template is being used (or was used to create the custom template) Additionally, it will be helpful to know which contract template is being used by each contract so that there is understanding of which contract(s) will be impacted when a change is made to a master template
* New tool tip
We have added a new tool tip to aid the creation of a new contract. Users get confused about the *contract type* and sometimes worry if it's not correct but, in reality, the contract template is the most important part and this tool tip will help.
* Improved date validation
We have added support to allow completion/secondary dates beyond 2079. Previously there would have been an error.
* Improved handling of selections on Manage System User page
Previously when navigating away from the Manage Users page (either by applying an action such as Active or Deactivate or simplify navigating away from the page) when returning to the page, any user(s) previously selected, remained selected. This, naturally caused confusion. We have now ensured that the previous selection is cleared when navigating back to this page. There is also a clear selection button that can be used whilst in the page.
* Improved Power BI Middleware logging
Previously the power BI middleware only logged errors but now it has been updated to know which user requested a specific report, when they requested it and what instance it relates to. This will allow us to see who, when, what and where (instance) the report was viewed. This information can be used to track any reports of incorrect data access / views.
*Bug fixes
The following bugs have been rectified: -
- We have updated the Contract RAG report – previously we did not cater for special characters being used in notifications -this was causing the report to fail for one of our customers.
- Custom fields were sometimes failing to be added to Aggregate reports due to CustomField temp table size limitation on dynamic SQL for aggregate reports. This has now been rectified.
- We have ensured that the Reporting services API contract summary report will load even if any contract was using the new party structure of Contract Administrator > Supervisor > Supplier which was released in the previous release.
- We have resolved the issue where users were unable to raise contractor extensions via ‘Create Related’ button when the current reply required date was failing to load.
- We have corrected the communication rules for a user on Batch Payments.
**Notes**
^^ Items marked with a double up arrow require specific permissions or subscription types before they are available.
** Items marked with a double asterisk will provide improved scalability, performance and reliability for the platform.
Comments
0 comments
Please sign in to leave a comment.