DocsInteract 4.0 – September 2020
This release note is for the 4.0 release of Blue Prism Interact (Interact) delivered in an on-premise configuration.
Important notices
Please review the limitations section before installing this release.
Enhancements
The following new features and enhancements are introduced in this version of Interact.
| Description |
|---|
|
Interact has been migrated to .NET Core 3.1 to ensure supportability. |
|
A new inbox feature has been added to the Submission tab. The inbox is the location which enables human/Digital Worker collaboration. A submission is moved to the inbox through using the Interact Web API service, this in turn allows a user (human) to work collaboratively with the Digital Worker, responding by updating requested information and reviewing returned content. |
|
The Interact installer has been added to manage and coordinate the installation process. Previous the installation required a Blue Prism consultant. |
|
To increase security, code obfuscation has been introduced into Interact in this release. |
|
All sensitive information in appsettings.json for Interact is now encoded. |
|
Load balancing infrastructures are now supported in Interact. |
Fixes and Improvements
The table below list the fixes and improvements made to this release of Interact.
| Description |
|---|
|
To support the on-premise version of Interact, the cloud services have been deprecated and alternatives such as RabbitMQ message broker and file services. |
|
The font face has changed in the user interface to Roboto for all languages except Japanese which uses the Kento font. |
Limitations
The table below list the limitations within this release of Interact.
| Theme | Description | Workaround |
|---|---|---|
| IADA | Number elements are delivered as ‘Text’ format into a Blue Prism queue | Cast to Number once inside Blue Prism |
| Get Submission | Number elements are delivered as ‘Text’ format when using the Get Submission Web API Service | Cast to Number once inside Blue Prism |
| Get Submission | Retrieving a Date element using the Get Submission Web API Service, returns the Date in ‘DateTime’ format | Cast to Text once inside Blue Prism. The use of Text is recommended to support the different Date formats within Interact |
| Create Submission | When creating a new submission using the Web API Service the submission will not be successful if a Number element is left blank | Submit Number element fields with a number set |
| Create Submission | When creating a new submission using the Web API Service the submission will not be successful if a Radio Group element is left blank | Submit Radio Group element fields with a value set |
| Create Submission | When creating a new submission using the Web API Service you cannot send anything back when using the Upload element | None, roadmap feature |
| Edit Submission | When editing a submission using the Web API Service you cannot send anything back when using the Upload element | None, roadmap feature |
| Interact Form Priority and SLA | Though the Priority and SLA can be set in the Interact Form creator, they have no significance in this release as IADA ‘Get Next Prioritized Item’ (GNPI) function is not available in an on-premise configuration. | Not applicable |
| Rules | Rules are not enforced when updating Interact Forms from Blue Prism. For example, a rule that reveals a hidden field when a flag is set, will not be initiated if the flag is set correctly when updated. If the field is not read-only a user can click in the field and then click elsewhere in the Form to see the Rule applied | You can use the Update Config Action in the Interact API Object to replace some rules. |
| Verification | Regex and other verification such as character string lengths are not enforced when updating Interact Forms from Blue Prism. If the field is not read-only a user can click in the field and then click elsewhere in the Form to see the Rule applied | None |
