All product information in wiki.bizagi.com is only valid for Bizagi BPM Suite 9.1.X.
For newer Bizagi BPM Suite versions (10.X and up) please visit the User Guide.
 

Authorization considerations in the different environments

From Business Process Management, BPM and Workflow Automation Wiki | BizAgi BPMS

Jump to: navigation, search

Authorization considerations after deployment

After making a deployment to the test, or production environment it is possible to change the configuration of the Authorization at any time via the Management Console:

1. Go to start and select in the Bizagi folder the program Bizagi Management Console.



2. Select the Security option and then the Authorization menu.




Bizagi distinguishes the elements that have been changed in the test environment or production from their original settings in development environment. Those items that have not been changed are displayed in gray; those that have been changed are shown in bold.



The next image displays the difference between items when you have made changes in the test environment: The color of the element under Applications has changed to indicate that the configuration is different from the development environment. On the other hand the color of the element under New Cases remains gray because it has the settings brought in the deployment.



Note:The changes made in the test environment are not taken to the production environment. The configuration given in development will be set in every environment. If you have made changes to Authorization in the testing environment and need them in production, it is necessary to perform them in the development environment and deploy again.


Restore to original values

Once you have changed something in the Production environment you can restore it to the initial settings.

On the Management Console select the item you wish to restore.

Click on the Reset to original values button available in the ribbon on the Authorization menu.



Note:Any element in Authorization that has the original values will be overwritten in future deployments with the configuration of the development environment.

  • If you make changes to the authorization options in the production environment, they will be preserved in future deployments.
  • If you want to overwrite production’s settings with changes made on the development environment you should restore to original values and then perform a deployment.


<comments/>