Allow multiple responses for a single task on an issue
Issues can be sent out for review by multiple people. Each person often has two or three different points that need to be addressed within the document. It would be good if each person that responded was able to log each of their points as a separ...
over 1 year ago
in Core CDE
1
Future consideration
Support Editing Renditions (Add - including correction, Remove) in the API
As a developer I want to be able to use the BCDE API to add, and remove renditions from a document. Notes Need to be able to add a rendition to a document. Add a rendition (from device) Add an existing document as rendition (from BCDE) Need to be ...
Implement the ability to choose what versions are returned when searching in the API
As an application developer I want to be able to search for documents and control which versions are returned to reduce load on the API of filtering out all but the latest version. I.e. I want to be able to get: All versions (which match the searc...
Out of office capability for users involved in workflows
As a user I want to be able to tell BCDE when I am out of the office. As a project manager I want to be able to set a user as out of office if they are incapacitated and cannot do so themselves. As a project manager I want to be able to see when m...
about 2 years ago
in Core CDE
0
Future consideration
"Download Documents" from Issue to support Primary Documents AND Renditions
As a user I want to be able to download Primary Documents AND their Renditions as an option from the Issue page. From the issue view/issue response page, support: "Download Documents" "Download Documents and Renditions"
Provide the ability to fulfil placeholders and upload renditions similar to Add Documents with Renditions
As a project manager I want to prevent new documents from being added but allow multiple placeholders to be fulfilled at once with primary documents and their renditions. To upload a zip file with both primary files and renditions it is required t...
over 1 year ago
in Core CDE
2
Future consideration
Support multiple language specific strings for ENUMERATED METADATA FIELD VALUES
As a schema designer I want to be able to define an enumerated metadata field (single select drop down/multi-select drop down/taxonomy) that supports multiple languages - i.e. one value per language to reduce administrative overheads around schema...