We wanted to introduce a way to distribute important announcements to our user community. This has now been implemented in the form of a bell shaped icon toward the top right of the NIAH page. When notifications are available, the bell becomes shaded in, and a slight pulsating border can also be seen. Clicking on the bell reveals a drop down window, where the notifications may be read. Once read, clicking on "Mark as Read" will grey the message out and move it below any remaining unread notifications. Note if wanted, you may mark a read notification as unread if you want to. Once all notifications have been read, and marked as such, the bell icon returns to its unshaded state. Notifications are linked to the user, so each user can update the notifications as they wish.
There are many places in NIAH that display, use or accept entry of the current date and time. We noticed there were a few occasions where the British Summer Time difference was not utilised correctly. This has now been resolved.
This change will not be seen in the process history shown in a NIAH task at this time. This will be included in a future release.
In the Document Details (header) part of a NIAH task, the RPA developer can implement a 'drop down' selector allowing the user to select the required field content from a set list of available options. This functionality has now been added to the Line Items part of a task.
When viewing a NIAH Task within Document Details, having selected in from the Action Manager, you have the option to assign this Task to another user. If selected, a list of users within your team would be presented to you, to enable selection. Some of our customers would like certain users to be unavailable for reassignment, and therefore to not appear in this list. This functionality has now been introduced, and our support team can help with marking users as unavailable for reassignment as required.
Due to sporadic issues with Azure Key Vault, a change has been implemented to bring the API key functionality 'in house', implementing AES encryption for the API keys within NIAH.
In many areas of NIAH, the team(s) a user is assigned to plays a part in what information this user can access, such as a personalised list of Unassigned Tasks, the Jobs available to view in Activity Feed, and some Extraction Rule settings. No functionality has been changed in these areas, but the complex logic behind the scenes has been redesigned to improve the performance, thus leading to a faster and better experience for our users.
With the ever growing amount of process history content, the rendering of this content via either Action Manager / Document Details, or Activity Feed / View modal, occasionally caused issues for our clients (eg. 500 error). Performance improvements have been implemented in this area, to alleviate this issue.
An Approval Task in NIAH can move between various Teams. Although there was already checks in place to ensure when a Task is removed from the user's team it was no longer available, a user from a team earlier on in the approval chain that still had the Task open for edit (or had saved the URL), was still able to perform some updates on the task, despite being in a (now) invalid team. This has now been resolved.
When viewing Jobs in the Activity Feed, you are able to view more details of each, by clicking the "View" button. This brings up a popup window, within which several tabs of information is available. One of these tabs, "Tasks", displays a list of all the Tasks associated with this job. In some rare circumstances, some related Tasks were not appearing in this list. This has now been resolved.