Publishing and Deployment
Introduction
With the IYOPRO Portal not only experienced but also occasional users find it comfortable to utilize their organizational process documentation and to participate at workflows.
The Publishing and Deployment features in IYOPRO ensure, that the process documentation shown in the portal consists only out of released and approved process models.
With the integrated lifetime management you can control the validity period of your process landscape and navigate on the timeline in a very easy way.
Conceptual Overview
The Publishing and Deployment process is based on the following steps:
-
Edit
Create one or more BPI-Projects and describe your process models. -
Publish
Click on the publish button in the modeling tab of the ribbon. The upcoming dialog is used to create a deployment package. -
Deploy
The deployment package can be released or declined by an auditor. This can be done on demand or guided through a workflow, depending on your team settings.
Note, that the team settings also allow to auto deploy a deployment package. That means, that the deployment is automatically done within the publishing step.
After a successful deployment, the process documentation is available in the teams process documentation folder.
Publish
To publish a process documentation to the process portal first open your BPI-Project which contains your process documentation. Then click on the Publish button on the modeling tab in the ribbon.
| Depending on the team adjustment, how process documentation has to be published, the following dialogs may differ. |
The publishing dialog consist out of four sections:
Destination
Specify the destination, where to insert the process documentation into your existing documentation folder tree.
To create a new folder within the tree, click on the New Folder button and specify a folder name. The folder will become part of the deployment package and therefore it will be visible not until the deployment package is released.
Options
Specify, which elements of your BPI-Project should be part of the deployment package. You may necessarily exclude diagrams which have not been completed or which shall not be published.
To exclude en element highlight it and click on Exclude. Excluded elements will be marked with an exclude icon.
To include an element highlight it and click Include. All elements are included by default.
It might be necessary to keep an existing element of the process documentation when deploying a new version. If you wish
to keep an item, mark it and click the Keep Existing button.
Entry points are root diagrams (usually process maps). They are visualized in the root of the process portals documentation node. To mark a diagram as entry point highlight it and click on Entry Point.
If you wish to create a folder for the solution beneath the destination folder check the Create Folder for Solution
toggle.
If you wish to create a folder for each project beneath the desired parent folder check the Create Folder for Projects
toggle.
Deployment
Specify how the deployment process will be archived. This setting is affected by your team settings.
- Package reviewer group
-
Specify a group of users which are responsible to release the process documentation.
Specify the release mode:
- Immediate package releasing
-
If you wish to release the package immediately to the portal without auditing choose this option
- Manual package releasing
-
Choose this option if a member of the package reviewer group needs to review the documentation package and will deploy the package manually
- Run Release-Workflow
-
Choose this option if you wish to automate the release process with the IYOPRO workflow system.
Manual Deployment
The manual deployment is done by an auditor which must be member of the package reviewer group. The auditor can navigate through the process documentation and will find the deployment package at the specified location.
The auditor can navigate through the deployment package as it would be deployed to verify, that the package is complete and correct.
The auditor then has two options:
- Release Package
-
Click on the Release Package button to deploy the package. This makes the documentation available for the readers.
- Delete
-
Click on the Delete button to decline the package. This will delete the deployment package. The author now can revise his work and repeat the publishing process.
Workflow Deployment
The release of deployment packages in IYOPRO may be performed by a release workflow. This has the advantage, that the release is documented and that the publisher can monitor the state of the release process.
In order for a workflow to be used as a release workflow, it must have the tag "Documentation Releaser" set in the Workflow Build Options and be built and set active.
Here, you find a step by step guide to set up an example documentation release workflow.
If you have created at least one release workflow it can be chosen in the publishing dialog:
