You can also use the ECT Resulting Object change transition in association with a lifecycle template setting the documents' lifecycle Change Transitionfrom their current in work state to a post-change Release state. This way, when you complete an ECN you can release any number of resulting document versions on its ECTs.
If you put your documents under revision control, then the ECT/ECN approach not only allows you to track the history of revision changes, but also gives you an easy way to create new revisions when a block of documents change at the same time in the future because you can 1) search from them using a ;-delimited "Number" search in Advanced Search, 2) Copy the search results to your Windchill clipboard, 3) Paste those results as Affected Objects on an ECT, and 4) use the "Revise" button on the ECT to easily make new revisions of all those documents into the Resulting Objects section of the ECT. If you have any linked parts or other objects that must revise with the documents, then there is a Collect Related Objects button on the ECT to help with that (although for Reference Documents you probably don't want to collect anything). Once you set up your new revisions, you can use your ECT/ECN process to assign the work of completing and uploading the new content, then electronically reviewing and approving the new revisions prior to releasing them all together via the change transition when the change completes.
If you just have a one-time batch release, then promotion request is good. If you have a process by which you want to control changes over time, then use the change process. If you like both approaches, you can Promote initial releases, then use changes to make revisions. For us, we tend to use Change objects to do initial releases by simply adding resulting objects with no affected objects in order to use the same workflow for new releases as for new revisions of previous releases.
Al
