Currently only "plain text" comments can be added in Chorus's Processor Workspace. Enhancement would be to extend that to other formats such as HTML, to allow for content markup (bold text, hyperlinks. embedded images etc.).
Enhance manual comments to allow comments to be flagged as either private/internal or public/external/global.All comments would be visible to users in Processor Workspace, but the RESTful API would be enhanced so that only comments explicitly marked ...
Chorus client Sanlam have a specific business requirement to alert a defined set of users if an attachment is added to a work item.Principal use case: an attachment is uploaded and attached to an existing work item via API from an external (non-UXB) ...
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...
The display language for the Chorus Portal has always been tied to the language set for the browser - the suggestion would be to make this a "user preference" instead, picking from a list of supported languages.
The challenges with tying to the brows...
Ability to reorder the results in the "Search Results" card comes up as a regular ask in requirements gathering with clients, with ability to switch ordering between "oldest first" and "newest first" being top of the list. So essentially, something l...
MS Graph is now the go-to requested API for mailbox access, with IMAP4 now generally requiring a security waiver to implement, especially on Exchange 365.
The main product ask here is the ability to add 0..n custom SMTP message headers (name/value pairs) as inputs to the AWD Email Service "SendEmail" SOAP operation.The client side/Portal part the client could implement themselves as a separate form wit...
Maybe this could be achieved with a single "user resource access rollup" database view or table in (or visible to) the BI/OA database that was a rollup of user resource access (direct access and via group membership), similar to the privilege rollup?
Ideally search results should be sortable in the same way the work list is when displayed in tabular form, not just by create date, but by other data points as well.
