There is currently no "lookup" operation offered by the Utility task, meaning that any in-process lookups (e.g. for "match-and-attach") have to call the lookupObjects operation on the AWD Processing Service SOAP web service. This creates an inefficiency as the call goes out of the container and back in through the web server, creating a new execution thread in the process, rather than being a simple inline call from the Service Engine. Adding this operation to the Utility task then also avoids the need to import the WSDL for the AWD Processing Service (for this specific operation at least!) and configure the parameters from scratch - so from a user (process designer) perspective, makes process creation easier, as the operation is already "pre-configured" out of the box. ... View more

Currently the "Create Source" function offered by the Utility task in Design Studio only allows for a source to be created from a Content ID - so effectively can only be used in a Capture process where the Content ID is already known and the content is already present in the image store. For the main "Create Source" use case, where the *content* is already known, but the ID isn't, the "createObjects" operation on the AWD Processing Service SOAP web service must be used, so: The call goes out of the container and back in through the web server, creating a new execution thread in the process, rather than being a simple inline call from the Service Engine As a separate execution thread, that update is in a separate database transaction, so won't roll back if an error down the line in the current process triggers a transaction rollback ... View more

The utility task in the Chorus BPM design studio currently only has operations for work/source/folder creation. It is a regular design pattern in Chorus process design to want to update another work item (or less commonly, source or folder) within the same Chorus instance, given its object key. To do this currently requires use of the "updateObjects" operation on the AWD Processing Service SOAP web service, so: The call goes out of the container and back in through the web server, creating a new execution thread in the process, rather than being a simple inline call from the Service Engine As a separate execution thread, that update is in a separate database transaction, so won't roll back if an error down the line in the current process triggers a transaction rollback ... View more

We are currently storing a lot of detail around the emails ingested by Capture in the Chorus database (AWD061/62/63) but there is no current mechanism to display this information holistically within the Chorus Portal. This means that the data are currently only available by SQL query (the GetCapturedEmail operation oh the AWD Email Service returns info from those audit tables, but only for a single email at a time). The main use case here would be an indicator of "failed" emails so that remedial action could be taken. I think the view would just need to be a filterable, pageable tabular list of ingested emails. ... View more

Problem Statement: Currently we have a number of use cases which require Python scripts to complete specific NLE activity or to support with the management of files such as: encrypting/ decrypting with specific PGP keys converting protected PDF documents to unprotected, editable and readable documents for OCR extraction managing multiple PDF documents such as deleting pages, merging documents These scripts are currently utilised as standalone py files which are triggered via Blue Prism; but not within Blue Prism. Proposed Solution: Include Python as a supported language within Blue Prism code stages Provide Python as an installable supporting application alongside core Blue Prism product installer Provide the ability to run 'pip install' to obtain dependencies for scripts all within Blue Prism. ... View more

As at version 22.1 Chorus only supports Basic Auth for SMTP. Support for OAuth2 authentication was added for IMAP4 in Chorus Capture a few years back in order to ensure forward compatibility with Exchange365, for which Microsoft have mandated they are removing support for Basic Auth for IMAP4/POP3 (as of Oct 2022). Microsoft have not yet given an end-of-support date for SMTP with Basic Auth for Exchange365, due to the very long tail of applications that use SMTP and can't easily be updated to use OAuth2. However, in order to keep up to date with best practice for protocol security, we should add OAuth2 support for SMTP to the product set Affected Chorus BPM components: Communications AWD Email Service Fax Out WebFOCUS (report distribution via email, email notifications) Business drivers/considerations for this enhancement: Clients' security teams start mandating that SMTP should only be used in conjunction with OAuth2, not Basic Auth Microsoft announce a sunset date for SMTP/Basic Auth, after which any enhancement would be against an externally-imposed deadline ... View more

Clients receive generic "object failed to update -an unknown database error occurred" causing significant troubleshooting to determine the issue.  1. The error message was received when an automation service was attempting to populate a value that was too long. Updating the error message to "Value in service exceeds limit" would significantly decrease the troubleshooting time. ... View more

Unretiring a schedule as per current model requires create Schedule permission. in our scenario , we have separate teams for management and operations . So it is better to have a separate unretire schedule permission where operations can just retire or unretire based on business needs without updating the schedule. Thanks. ... View more

I'm in the process of re-building forms and migrating from thoughtonomy to interact. Through the design and build stage, i can't find a way to stop submissions. For example in the Thoughtonomy platform, we would have a radio button with 4 options, 2 of which we would continue with the form/journey and 2 of which would indicate that not enough information is available. If these 2 options were selected a 'text paragraph' would be presented with some help text guiding the agent in the right direction. We would also have a 'mandatory' field with its role set to hidden and another rule basically saying that if the 2 incorrect options are selected the mandatory field becomes mandatory (although still hidden). This would stop the agent submitting the case however i'm unable to replicate this in interact, as any time a field is made mandatory it becomes visible. Can a status be introduced where the rules do not override the initial state allowing us to stop submission and reduce exceptions? ... View more

I've seen an issue within interact where a radio button or select drop down with multiple choice selections and has different rules associated to each selection, the rules are not dynamic if an incorrect selection is chosen but then corrected.  For examples  What are of the country do you live? South East South West  North East  North West If South East was selected incorrectly and South West was then selected both the rules associated to each selection would appear. This means agents are having to refresh forms to avoid mistakes leading to higher handling times and issues with engagement. ... View more

When a front end user is completing a form, they have to tab/click out of a field they are completing to enable rules to kick in. For example a lot of my forms have their fields 'initial state' set to hidden, so only 1 filed is present at a time, but to have the next field appear an agent would need to click out of it or Tab to allow the rule to 'kick-in'.  We've come across examples of agents pressing enter which allows the submission of the form, even with subsequent filed to complete which will ultimately  lead to a high level of exceptions if this can not be rectified. ... View more

This is functionality that exists in Legacy Processor workspace and would be very helpful to add to Modern Processor workspace.  Currently, all columns in the history have the same width and the width cannot be adjusted.  This is a challenge because the Comments column can have lengthy test, which is very hard to read if only a couple words can fit on each line.  We should be able to adjust the column width and the system to remember preferred column width.  Also, the Comments column should default to being wider than the other columns. ... View more

Clients looking to retire KE/ST need the ability to change the queue without making a status change. It’s very common to have an intake step start in a process to classify the work, resulting in a work type change that is in an existing workflow.  Clients cannot retire KE and ST until we can solve for this gap with interoperability.  https://confluence.ssnc-corp.cloud/pages/viewpage.action?pageId=606807093 ... View more

Ability to configure the Quick Search (LKQSRCH) within an automated service or presentation flow using the base line web service called AWDProcessingService - lookupObjects operation.  This is a ticket submitted by Nationwide - CS0013505.   This search writes a sql query when you enter data on the Search screen.  This is different from the other searches which can be configured using the lookupObjects operation. An enhancement is necessary to be able to configure this call successfully. Please enhance to support this search using a web call within the Design studio. ... View more

Solution: Please add support for teams that are able to access the tickets that were created by all members of the team. This will make it much more easier to collaborate during the daily supporting tasks. Background: Currently only the opener of a ticket is able to access and work with his own tickets. Using the Cc option is limited and unreliable. Cc can only be added after creation of a ticket. And Cc does not work every time (for unknown reason). And attachments or embedded screenshots will get lost in most cases. All this makes it much more complicated to collaborate during daily supporting tasks. ... View more

Text annotations that are applied to any model do not save and must be re-entered when an update is completed to a design model.  This has been happening since 20.x release.  A support ticket was opened to address, but nothing has ever been done to fix. ... View more

Using 7.0.0 - Unlock All Processes currently loses all unsaved code changes for all other developers.  Providing a Warning message would greatly reduce the chances of lost code changes.  Restricting the Unlock All Processes functionality to Administrators would also be an effective solution to this problem. ... View more

Sometimes we need to search a lot of items in a queue to set as an exception or to change the deferral date and is quite sweaty to do only one search at a time. There could be a way to search for more than one, for example, searching item keys between semicolons (;) or quotes("). ... View more

Current version of Decipher v2.1 has a weak point in limiting the Decipher's user password field up to 20 chars. In current days, by using cloud resources and some automation - it is possible to brute force passwords. It would be nice to have at least 64 chars limitation if any limitation is needed at all. ... View more