When inputting a comment, the text area is too small and only shows two lines. You do need to scroll to see the full comment if its longer than two lines.  We have users that paste input or paste large comments and it would be helpful to see more of the comment when doing so.  ... View more

We have a lot of users minimizing search and create cards.  When they have a few of them at the bottom it would be helpful to be able to see what was searched in the BA/WT/Queue Date or Status.  Also, if it could display a count of the number of items in the search/queue.  ... View more

Would like Copy and Paste from the comment section to work like Classic does now.  If there are line breaks or carriage returns in a comment it will copy the same way into Word, OneNote, or an Outlook email.  Currently in Processor Workspace it is all one continuous line unless you paste into a Notepad or a Sticky Note.  This adds extra steps to get it to format correctly.  ... View more

We would like to have the option to change the default setting on the comments.  We have a lot of Batch/System comments that are important for our users to see and it would save a lot of clicking to be able to adjust the default comment view to whatever the user needs.  This would also reduce potential mistakes by our users missing important comments.  ... View more

There is no option to undo in classic forms on Chorus. Please can we have an undo "Ctrl z" functionality? This will save time when creating forms and be a HUGE help for the overall user experience.  Every time the users move something by mistake they can't easily take it back, leading to a lot of frustration as this action is common in most applications, especially design. Although the UX builder is coming there are still a substantial amount of historical forms designed in classic thus this feature is still required for small changes in a lot of businesses, and shouldn't be overlooked due to the UX builder.   ... View more

Allow the user to select font, font size, and font color in Processor Workspace view history.  Our clients complain the current text color is too light and small to read easily. ... View more

We have identified a potential risk in the EQM emailing capability which we’d like to mitigate by requesting an enhancement. With regards to emails being sent out via Chorus in the Non-Prod environments during testing, if the user incorrectly provides actual production data (e.g. a client’s email address) there is no system level fail-safe to prevent test case emails from being sent out unintentionally to these parties. We've been advised that it is possible at a process level, but we would prefer this to be configured at an environment level instead as a over-arching fail-safe. We’d therefore like to request that a new field be introduced (possibly in the AWD Configuration Console where the mailboxes are captured). This field would allow us to capture, at a system/environment level, an override email address(es) that will always be used when sending emails, instead of the ones provided in the Chorus work items. Field: Override Email Address Format: semi-colon delimited text values of the email addresses which should always be used when sending emails for that mailbox (e.g override1@email.com;override2@anotheremail.com). in the Production environment, either the field would be left blank, or alternatively you could provide an explicit checkbox to indicate if it should be used or not. ... View more

We would like to have the ability to direct a section to a new page/section.  This would enable a dynamic way of viewing information on the form based on certain conditions/buttons. For example,          ... View more

An enterprise customer (Chorus/ Bridge/ Document Automation) uses the capture process to ingest images that originate in emails. Because the sources are sent as a packet that should be worked as a single work-item in Chorus, they would like to send them as one transaction to Document Automation.  Our request is to facilitate transitioning this customer to be able to submit multiple sources into a single DA batch. ... View more

Right now, BP does not have trigger-based run features, which are much needed in automation. This is something that can be added in the BP, as there is no native trigger-based mechanism. It is much needed and useful in many use cases where users don't want to keep polling and occupying licenses. ... View more

In Chorus when a user views the work items history the KE/ST steps in the workflow do not appear. This causes confusion for the user if they anticipated a step being done. It is also an audit concern because it is not a true history of everything done to the work item. Moreover, the KE/ST should not only appear in the history, but it should print as well. We print out the history for the purposes of audits to validate processing procedures were met. ... View more

It would be beneficial if we had the ability of exporting credentials from one version of BP such that they can be imported into a newer version of BP. Issues were experienced during our migration from V6.8 to V7.1 such that it was strongly advised for us to do a migration of automations over a few weeks, instead of over a weekend. Our migration required about 190 bots to be migrated. Future migrations could be double or more. Having to extract the password from BP by running get credentials once per user and then manually keying those across to 7.1.2 was very time consuming and annoying. ... View more

The ROS plugin, when activated, automatically opens two windows which are visible to the user -- Word and Excel.  Users can accidentally close one or both of these windows, resulting in errors.   Can the windows open invisibly in the background? ... View more

Hi, We have been rolling our Chorus users to the New Processor Workspace (from Classic and Legacy) and the Screen Image Capture (SIC) feature garnered some excitement, but there was some disappointment that it didn't also include the feature to actually perform the Screen Image Capture itself (unless we've missed something)?  Users therefore have to use the Windows "Snipping Tool" or "Snip & Sketch" and perform that step in those applications and then paste the result in the SIC, making it more effort. It would be amazing if there could be a button directly inside the SIC that provides the same ability.  I'm sure users would find this feature much more intuitive and simpler. Thanks for listening.  Chorus BPM  ... View more

In Document Splitter, all annotations on pages added to new subdocuments or compound documents are preserved, i.e. copied from the original documents.  In some customer implementations, these annotations need to be deleted manually each time a new document is created.  An option on not copying the annotations in creating new documents is required.  The option default (copying vs not copying) should be set at the system level or even at the user level. ... View more

We have a mix of Users who either love or are overwhelmed by Processor Workspace (as compared to Classic Workspace).  Some of our Users find Cards ability to go anywhere and not have a permanent Docking (or Pinning) Spot (for each Card on Workspace) can be overwhelming.  With an update to allow Docking (or Pinning) of Cards the Users would be able to Move and Pop out Cards (which they have with current functionality) or Dock/Pin in permanent spot to be similar to Classic depending on each Users own preference.    #ProcessorWorkspace #Cards #Chorus #DockingCards ... View more

My client feedback on the new Processor workspace: the scroll bars is just too thin (the width is too narrow), very hard to use. This applies to both the horizontal and vertical scroll bars. My client is undergo the upgrade to 23.x, so they tried both 22.x and 23.x. I feel the same, and tried on 23.x regarding the Worklist, Search card, Forms, etc ... View more

As a user, I want to a rules engine that can: Can handle rules at scale Tech-savvy BA’s can partner with IT to author and maintain rules with min developer involvement Source control and change management to see what was changed and by who, and to test in lower environments API integration Can handle complex rules outside of code ... View more

Many business procedures have standard comments that are copy pasted onto an item, and then modified as needed. To streamline the process, as a user, I want an option for AWD to populate standard comments for a given Business Area/Work Type combination so that I don’t have to copy paste them from elsewhere.   ... View more