As a document controller I need autotagging to support multiple rules per project. I.e. to extend capabilities beyond small set of standard naming conventions based upon standards. Reasons for lots of rules: Different naming conventions in each re...

As a user I want to be able to upload NNN - i.e. hundreds - (e.g 100) files up to NNGB (e.g. 20GB) in size to BCDE.

As a designer I want to be able to send a document version from PW into BCDE for approval via workflow and for the status and comments to be updated and available in PW against the original document version. I.e. To be able to update metadata in B...

As an issue sender or controller I want to be able to reopen a users completed tasks on an issue if I need them to repeat the task. E.g. As part of an RFI process - require that the response to the RFI is revised. Requirements New action to reopen...

At the moment in order to use the API to find a list of issued documents in a container you need to iterate through and ask each document individually if it has been issued. It would be good if there were keyword language search parameters you cou...

As a project manager I want to be able to see actionable placeholder information including the total number of pending deliverables, delivered deliverables and Percentage complete. Dashboard information should link through to "reports" that permit...

As a schema admin I want to be able to restrict "Save and Issue" and "Save, submit selected and forward" when the automated Workflow engine is handling document based workflow.

As a developer I want to be able to upload HUGE (>10GB) files to BCDE. As a developer I want to be able to optimise my use of memory when uploading HUGE files to BCDE. As a developer I want to be able to upload across a stable connection that i...

As a workflow designer I want to be able to configure the send email task to be sent by a nominated actor - both event and role options should be available. At present, the workflow is sent as the creator of the workflow.

As a schema admin I want to be able to specify the order of reasons for issue/field sets on a per issue basis. As an end user I want the order of reasons for issue/field sets to be respected in the distribution section when viewing or creating an ...