Showing ideas with label Chorus: Administration.
Show all ideas
The search drop down list within Processor Workspace is forced to be in alphabetical order. We are given the ability to specify the order that lookups are in within the LOOKUP resource parameters list, so the drop down should obey this order. Having frequently used searches at the top of the list is more streamlined and user friendly for the end users. This used to be functionality that existed but was taken away.
... View more
When a process model is deployed the only place that the details of who deployed it are located within the Design workspace. If a model is undeployed there is no record of who did it or when. This can cause issues if a process model is accidently undeployed. Having who made the change in the Admin Audit Trail would be helpful in locating who made the update and react accordingly.
... View more
There is currently no separate data field in User Admin where the user's email address can be set. The "User Alias" field can currently be used as a "stop gap" measure, but only for implementations where that field is not needed for user sign-on with an ID longer than 8 chars that isn't also the user's email address.
... View more
Chorus is unable to store email addresses of more than 75 characters. Email standards allow for up to 320 characters in email addresses and we cannot control the addresses used by our clients/CMOs so we need Chorus to store email addresses of the full 320 characters. This is currently leading to email uploads failing silently and requires urgent remediation.
... View more
Status:
Needs More Info
Submitted on
24-07-24
08:08 PM
Submitted by
doran.george
on
24-07-24
08:08 PM
There are no Resource Access Controls on Chorus Rest API's which provides a greater attack surface for attackers. Resource Access Controls per UserID could be system level or granted by individual Rest API.
... 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
As a Chorus administrator, I'd like to be able to import and export (using CSV format) fields configured in the field value domain. Additionally when importing, I'd like the options to overwrite, add, or merge with values already configured in Chorus.
This configuration can often have hundreds/thousands of entries for a given field and often needs to be populated from a list provided by a customer. Manually comparing and updating can be a very time-consuming exercise. The only alternative requires a resource with database-level access.
... View more
We have different Business Areas who like their users to get different amount of work while they use get work (work select). Currently this is a global setting. We like to have the ability to set the count per work group or Business Area/WorkType. Another setting is release on log off that would be helpful to follow similar path.
... View more
Status:
Under Consideration
Submitted on
23-05-22
02:23 PM
Submitted by
Brian_Hesse
on
23-05-22
02:23 PM
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
