Currently when a user locks themselves out of Chorus they are presented with a canned message that states "Your user id has been locked due to multiple sign-on failures. Please contact your supervisor to reactivate it." Depending on how security is handled for a given client it is quite possible that "your supervisor" is not the correct person to contact to activate your id. For example for us you would need to contact the help desk. Making this message configurable would be clearer for end users and save time and frustration. ... View more

I'd like if the Object Conversion Utility (OCU) could be a Chorus Workspace, so I wouldn't have to log onto it separately from Chorus BPM.  Thanks! ... View more

Enhancement request to have the ability for the system to tell you if the user being disabled is an owner of a case like it does with work in the worklist.  Product Management provided the following feedback as to enhancements in the works:   We have User Admin requirements in play right now and this use case has not been addressed yet. User Admin is undergoing enhancements to support the ability to DEACTIVATE a user ... which is different than just disabling their status. Today, disabled is both a temporary and a permanent availability status. When you intentionally disable somebody ... it is because you want to take away permissions (security, privileges, configurations for various teams - like a case team). We check today to handle assigned work. We don't check on any memberships anywhere else. This is a good use case. ... View more

Ability to code get work based on LOB values such as specific dealers.  Another workflow system has a user coding screen that basically has a drop down that has the ability to add parameters to define their work selects and one of the parameters is the Dealer value, as an example. ... 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