Share Processes

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio Collaboration Services > Studio Collaboration Services subscriptions >

Share Processes


During process automation, you may find yourself in a situation where you need to share your processes with other Studio users. Bizagi helps you share your processes along with their business rules, parametric values, forms and other settings, with the options available in the Import/Export menu.


Export/Import menu with all the avaiable options: Deploy process, microdeployment, share processes and import from process modeler, import process and import from the Process Xchange


Important Considerations

We strongly recommend that you select the Enable metadata validations option when you import a shared process. This validation detects two of the most common errors that occur during an import:

oReferences to objects that don't exist in the catalog: When an imported object has a reference to an object that doesn't exist in the package or in the target database this validation is triggered.

oProcesses without an associated version: When objects like rules or experience elements don't have an associated process version, this validation error is triggered. If this happens, you must review your export configuration and make sure you selected an associated version for these objects.

These validations are important because they reduce errors substantially.




It is only possible to copy processes that have the same platform (.NET to .NET or Java to Java).

You can only export processes in the following scenarios: within the same Bizagi Studio version, from a lower to a higher version. It is not possible to export processes from a higher to a lower version.

What is exported: All global objects including roles, forms, processes, business rules, parametric values, among other settings.

oWhen you select a process, all objects the process needs are be included.

oWhen you export a parameter entity, it will include its attributes and values.

The Experience objects such as Stakeholders, Context, Actions, Relevant to Me, My Stuff and Data searches cannot be exported.

When you import the same process more than once, your latest import will create a new process version.

Keeping data consistency is one of Bizagi's main priorities. As part of this, deleted attributes from the source entity will not be deleted in the target entity and new attributes of the source entity will be created in the target entity.

Bizagi cancels the action when an imported process might present data inconsistency. Possible scenarios that trigger this effect, include, but are not limited to:

oExperience objects that start a process that is missing in the target project.

oMissing attributes in forms migrated from older Bizagi versions.

oAn entity in the target project with the same name already exists as an entity inside the .btex file.

oRules referencing attributes not included in the package or target project.

You can import Rules and other global objects with replicated names.


What you need to do

To share your processes, you need to follow these steps.

1.Export the processes in a .btex file.

2.Import the .btex file contents to your project.


Exporting processes to share

Once your process are ready to share, head to the Export/Import menu and select the Share Processes option.


Bizagi Studio with the menu Export/Import and the Share process option highlighted


A window appears where you can select the processes and their versions you want to share.


Export wizard with a list of the available processes for export


To add an optional description click Description and type in a brief description for the shared package.


Export process description field


Once you're finished selecting your processes click Export to generate the .btex file.


Export window with a process selected and the Export button highlighted


A window appears showing that the export was successful.


Export finished successfully window


You can check the contents of the exported package by clicking View Package. Another window appears where you can navigate the contents.


Window with a list of all the exported contents

To finish, close all the windows.

You can now share your processes through the .btex file you've just created.


Importing the shared processes

When you receive the shared package file, head to the Export/Import menu and select the Processes option under the Import category.


Bizagi Studio with the menu Export/Import and the import process option highlighted


A window appears with the import wizard. Click the Browse button to navigate to the shared .btex file.


Import widow


Select the package you want to import and click Open.




When the file is selected all the process information is displayed on the window.




You can view the objects you are importing by clicking View process object to import. A window appears with all the objects inside the file.




Additionally, you can view the package description when you click View description. A window appears with the package's description.




After you've checked the package's information, click Apply package to import it. Once Bizagi is done importing, a message appears informing so.




To finish, close all windows.

After this, the shared processes are part of your project.