The Process Mapping Metastorm BPM Procedure Documenter

"Full Metastorm BPM technical documentation at the touch of a button. If you purchase just one add-on for Metastorm BPM this is the one! "

Metastorm BPM procedural documentation can be time consuming to create and maintain. Organisations investing in BPM technology today do so to enable process change/refinement to be applied quickly and efficiently. Legacy documentation is of no use to anyone - only documentation that is current has any real value in today's business world.

The Process Mapping BPM Procedure Documenter provides a solution to this problem by producing Metastorm BPM procedural documentation in HTML format in seconds! It details all procedural elements in the process including Forms, Roles, Flags, Processes etc in a hierarchical tree that can be expanded or contracted as required. Other features include:-

• Notes for all the procedure elements can be viewed instantly
• Provides validation and information on Flags, Role Alert lists and Action Matrix
• Convenient HTML format that can be opened/saved in MS Word if required

The add-in also provides further functionality to

• perform extra validation checks on the procedure
• allow the user to quickly change role assignments in a procedure

Open the Procedure Documenter Setup zip file and double click the Proc Doc Setup.msi file

The Procedure Documenter Setup Wizard is displayed:-

Click the Next button to confirm the installation.

Once installed, the Installation Complete dialog is displayed. You are prompted to use Windows Update to check for any critical updates to the .NET Framework in your environment.

Process map and form images can be included in your documentation, but form images must be saved first in your procedure via the Component | Save As Picture command.

NB: Form images should be saved to a subfolder of the procedure documentation file called 'Forms'.

If you are evaluating this software, you will be prompted to name your procedure "Evaluate".

Your online documentation is generated in HTML and can now be viewed:-

• variables that exist in the database but not in the procedure. These variables can then be deleted (all data for the variable will be lost).
• compare maps in the database to those in the procedure and warn of maps that exist in the database but not the procedure. You are then able to delete the maps from the database (all data for the map will be lost).
• forms that are not used in any actions or stages. This check will not be run against a library, since forms may be for use in procedures.
• roles not assigned to a user in the database.
• roles in the procedure that are not referenced
• flags that do not trigger any actions in the procedure. They may trigger actions in another procedure in which case this warning can be ignored.
• stages with their To Do or Watch list set to 'originator' that may have been created from a flag and hence have no originator
• actions with their 'Available to roles' property set to 'originator' that may have been created from a flag and hence have no originator
• actions with their 'Available to roles' property set to 'To Do list' or 'Watch list' where those properties on the stage are blank