The cards in Processor WS must be expanded each time you open a work item. As most work forms are longer than the current default card size, users must resize every single work item they open. Cards should open based upon the size of the form associated with the work so users don't have to manually expand them ... View more

Currently the only way to access Doc Splitter is to use the Action Menu option. As it is often part of the flow within a process, it would be ideal to have the same feature available as a button on the form of a work item ... View more

Client has a need to split a doc and create several separate docs from one doc, then create a specific work item for each of the new docs. Currently you must select the work type for each doc created. It would be nice to be able to designate the work type name to be created that would apply to all. For example, if a doc is split into ten new docs, and i want all ten to have a new work item created called INVOICE, I can select that work type once, and ten items are created, each with one of the ten source attached. ... View more

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

Focus on modernization of peripherals piece-meal (Fax, AFT) toward API calls Hosting spends a lot of time on AFT, IR, Fax Get rid of AFT server --> write directly to data store Consolidate IR, CV, DocSplitter ... 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

Custom Searches in portal that do not require manual building of Stored Procedures. Use Case: As we look to move groups to AWD Portal, the smaller outlying groups they have custom processes that leverage specific Lookups through Viewstation that are not available by default in Portal. Historically creating Stored Procedures has been difficult and there is little to no support from Customer Care, unless you want to enter a Professional Services engagement. ... View more

Automatic data packaging for TA / TRAC APIs – I think this one was already on the roadmap, but AWD so format the data in the exact way the APIs need it.  We should not need to manipulate the data for the APIs. ... View more

Communication/notification tool that provides insight to shareholders/representatives on the status of work – this could be integration between TA/AWD and other CRM tools, etc. This would help reduce status inquiries to Contact Centers, potentially address NIGO work more quickly, and share information across internal departments as appropriate, etc. ... 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

On premise option for customers or availability of SaaS service in more regions (EMEA, Asia etc..) ... View more

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

The dashes in the SSN/phone #s seem to always come through as questionable even when typed and clear. ... View more

Being able to delete cases if needed (like duplicates). I think these drop off after 7 days, but the ability to delete would be nice to have. ... 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

We need a ‘birds-eye view’ of which Processes, Automation Services and Presentation Services are being used, so that it would very helpful to know if workflows are not being ever traversed through, which will allow us to retire and simplify our ‘code base’. It will be easier for us to navigate and maintain the flows when it gets more and more complex. ... View more