Overview
Once the process automation cycle has been completed, Bizagi lets you publish processes for use.
Deployment of Bizagi processes involves promoting the processes into a Test or Production environment.
Bizagi promotes agile management of continuous improvement, so you can apply changes easily to your target environment.
Bizagi Environments
A Bizagi project has several environments. An environment in Bizagi is an independent application of a Bizagi project (it has its own Work portal, Database, and Scheduler service).
By default Bizagi presents three different environments, each with its own major objective: a Development, Test, and Production environment for the same project.
When using the Deployment feature, it is strongly recommended to use these three environments.
•Development: It is the Authoring environment. This is the only environment in which processes are modeled and their implementation details are specified. Design and construction stages are part of this environment, in which the data model, the forms, and the business rules are created, along with the performers, interface definitions, and other specifications. Work in this environment takes place through Bizagi Studio.
•Test: This environment simulates the Production environment. The development team carries out user acceptance tests for the functionality and certification of processes. The target environment is administered through the Bizagi Management Console.
•Production: This is the actual operating environment in which the client's processes are available to end users. Through the Bizagi Management Console, management tasks and configurations can be carried out in the Production Work Portal such as editing business policies, user administration and authorization configuration, and administration for the SMTP server or ECM systems.
Before actually performing a deployment, it is important that you review Preconditions and requirements.
Last Updated 7/5/2023 11:46:28 AM