SS&C Corporate Policy dictates that email accounts used by applications (such as Capture) must only be accessed by a Domain Service Account vs directly being accessed by the email account username and password.  SS&C has asked the BPO to implement this with Capture by 2023.    The pursuit of this ask for SS&C is twofold:   One:  It is more secure and provides a better audit policy to have a single service account that can access multiple mailboxes rather than multiple active domain accounts needed to support each account individually.   Two:  As SS&C and more clients move to using Microsoft Exchange Online, the ability to have a single licensed user (the service account) able to access multiple mailboxes results in reduced costs for Office365/Exchange Online licensing fees.     Currently Capture does not support using a single account to access multiple mailboxes.  The login and email address are 1:1.  This enhancement requests is asking for a development change to Chorus Capture to allow a single login the ability to access multiple mailboxes.     ... View more

Remove the need for sessions and session replication and make the application server stateless. ... View more

TA Portal Quality screen needs better formatting. Error Code Selections should be a list box or Check boxes with multiple columns. Also allowing for descriptions to be added to Errors to display so users can intuitively select the appropriate codes not leverage an outside reference. Here’s an example of how bad it looks because we have screen-field level error codes ... View more

It would be nice to have a Predictor (i.e. which will give a drop down of Options containing the eligible LOB field/Variable – for Example If we type ‘RO’ It should give the Variables/LOB fields which start with that).  This would be very beneficial when developing as we have to currently wade through the complete list of LOB fields/Variables/Inputs/outputs to map what we need. ... View more

Allow security to be driven by Work Step in a Process – When defining a process, it is very easy for management to see the user tasks, and think in terms of ‘who should work items in that step.’ It would be very beneficial if work types associated to processes were governed by a security paradigm that was based on the step, as opposed to BA/WT/STAT/QUEUE ... View more

Broader data privacy, data transfer terms to accommodate more regions than adding them on country by country basis. ... View more

Data Formatting: Add a bank of regular expressions for use instead of having to google it.  So we drag in the expression for formatting this to a phone number and then do the function. ... View more

Identify additional portions of the product which can be a self service for customers like us. ... View more

Also there is no way to clear the errored email from the screen so you do not know if it was resolved until you locate the original work object. In many cases the issue is a malformed email address, we built a service that attempts to prevent it but it is not 100% accurate so items still fall through the cracks. ... View more

Currently, the views of owned cases by teams or team members is limited to 10 cases per page (with the ability to page through).  Would like to see this increased to at least 50. ... View more

UI Integration/Messaging Marshalling API – We have created several UI customizations for our AWD instance.  It is difficult to allow custom UI components interact with other native AWD UI components.  For example, I’d like to add a javascript on my form, that with the click of a button, will execute a search and bring up results on the search results panel.  A UI API would allow our customizations to interact seamlessly with native AWD, and give a better process experience.  It would also plot a path forward for UI customization stability during upgrades. ... View more

User Administration: User Info – more info via Admin to show when an ID logs in and logs out. This would be particularly useful now that we’re all WFH. ... View more

Ability to code users for primary queue. Work can be same Unitcd/worktype but across multiple queues. IF user coded for: Unitcd = fundco Worktype = purchase Queue = processing and quality Currently user would then get the work based on FIFO or priorities. But there should be a way to get and finish all the work in the Processing queue first and then Quality.  Without having to code and recode at user or role level ... View more

We (and our Risk team) would like an audit trail to report on AWD process flow changes. We need to know who made an update, when, and what was changed. ... View more

Rules Integration – I would like to see a toolset, like Drools, embedded into the AWD UI. I would like to define “Rule Automation Services” that invoke those rules. It should all be integrated into the user experience, and give the appearance that AWD process development implements the ability to administrate complex rules. ... View more

The Rule Automation Services should be able to be modified outside the processes that consume them, just like automation services.  Perhaps this would be administrated separately from process administration. ... View more

Automated Workflow-to-Process Conversion – We literally have several thousand workflows that have been built over time. It will take forever to go through business process modernization initiatives to rewrite or replace these, and therefore it will take a long time until these business processes can benefit from the AWD Process automation capabilities. Sure there are Interop Services, but it will become unwieldy to manage full automation through this capability. What I would like to see is a tool that works something like this: 1. Select a BA/WT 2. Automatically reverse engineer all the status routing steps and UIs 3. Select a target BA/WT 4. Auto draw a process that depicts the original workflow (yes, I know there are hurdles and things to deal with here, but I have some suggestions) 5. Allow the admin to deploy the new process a. Optional – Inherit Permissions form the original workflow b. Replace BA/WT/STAT fields and Update button with Next Step ... View more

Currently we have a custom code applicated that was created with AWD Toolkit to allow a bulk number of work items to be moved to a different business area/work type/status/queue combination upon request. As part of this custom code application, we also add a comment stating who requested the items be moved and the corresponding ticket number so that each work item has a history line stating why it was systematically moved. This is information that is verified during our audits. While AWD Portal has the Process Monitor to bulk move items, it does not have the ability to add comments. Our request is to add an optional comment field so that when items are moved comments can be applied. ... View more