When you build BPM library from scratch, make sure you create Parent process that will include all child processes.
In this case, you will be able to export all the processes within one BPM-Requirement document.
BPM-Requirement document is being created using Doc button. Doc button that is available in the BPM generates MS Word document and includes highlighted process and all child processes of the highlighted process.
In this example, if user clicks Doc button then only "Develop Vision and Strategy" process and child processes of the "Develop Vision and Strategy" process will be exported to the document.
If this library had had the Parent process with the name, let's say "Process Frameworks", it would have exported all the processes presented on the picture at once. For the scenario above, users have to select each high-level process, click Docs and then manually combine all generated files into 1 document.
My recommendation is to have Parent/Main process in the BPM library since it will be easier to work and maintain such BPM .
In this case, you will be able to export all the processes within one BPM-Requirement document.
BPM-Requirement document is being created using Doc button. Doc button that is available in the BPM generates MS Word document and includes highlighted process and all child processes of the highlighted process.
In this example, if user clicks Doc button then only "Develop Vision and Strategy" process and child processes of the "Develop Vision and Strategy" process will be exported to the document.
If this library had had the Parent process with the name, let's say "Process Frameworks", it would have exported all the processes presented on the picture at once. For the scenario above, users have to select each high-level process, click Docs and then manually combine all generated files into 1 document.
My recommendation is to have Parent/Main process in the BPM library since it will be easier to work and maintain such BPM .
No comments:
Post a Comment