I have a fundamental question on revising and releasing documents using the Document Management Widget under the Collaborative Industry Innovator and governing/tracing through Change Actions (CA). Here are my doubts/concerns:

Problem: as part of a single change, I have to update multiple documents. And we currently require the documents to be tied to a CA in order to be revised and released. This is causing delays in new Change Actions to be created because we are waiting on other CA's to be completed.

Context: Approval flows can be lengthy depending on the changes. not all documents are usually updated at the same time during the course of a change action, but in order for me to revise these documents I need to tie them to the CA prior to initiating the CA along with its approval route.

Questions:

 1. If I remove the CA requirement to update a document, and allow users to revise and release documents outside of the CA, and request that they attach the newly revise document in a task to show that the action has been completed, will I be too exposed to any issues? or is this a common practice across the board?

2. Can I add a custom attribute of any sort to request users to add any information or comments prior to releasing a document?

Thanks in advance!  we are fairly new ENOVIA users so any guidance would help.