Delivery and version handling of workflows

if the workflow was built against the earlier version of the contract and then persisted, then the message cannot be delivered.

www.clover.com
 

Hi @chpelk 

bpmn files can be placed in a specified folder in Git which will then be picked up by the installer.

More details here https://docs.ifs.com/techdocs/23r1/040_tailoring/500_business_process_automation/070_extending_workflow/#code_deployment

The ability to store, manage, and deploy workflows using Git and deliveries may depend on the specific Business Process Management (BPM) or workflow automation platform you are using. I'll provide a general overview of how this process can work, but keep in mind that the details can vary based on your platform.

1. Storing Workflows in Git:

• You can certainly store workflow definition files (e.g., BPMN files) in a Git repository. This allows you to version control your workflow definitions, collaborate with team members, and track changes over time. Each workflow should typically be represented as a separate BPMN file.

2. Delivering Workflows:

• Delivering workflows as part of a deployment or release process depends on the capabilities of your BPM platform. Some BPM platforms have built-in features for packaging and deploying workflows, while others may require custom scripting or integration.

3. Workflow Import/Upload:

• Importing or uploading workflows is a common method to bring workflows from one environment to another. This typically involves selecting the BPMN file and importing it into the target environment. The BPM platform should provide this functionality.

4. Custom Packaging and Deployment (if needed):

• If your BPM platform does not natively support packaging and delivering workflows, you may need to create custom deployment scripts or use automation tools to package the BPMN files and import them into the target environment during a delivery process.

5. Configuration Management:

• Some BPM platforms allow you to configure and manage workflows, including their parameters and variables, through configuration files or metadata. These configurations can also be version controlled in Git and delivered along with the workflows.

6. Integration with CI/CD Pipelines:

• To automate workflow delivery, consider integrating your BPM platform with Continuous Integration/Continuous Deployment (CI/CD) pipelines. CI/CD tools like Jenkins or GitLab CI can help automate the packaging and deployment of workflows.

7. Platform-Specific Features:

• The specifics of how to package and deliver workflows can vary widely between BPM platforms. Consult your BPM platform's documentation or support resources for guidance on best practices and available features.

8. Environment Promotion:

• Ensure that your workflow deployment process includes promotion between different environments (e.g., development, testing, production) to maintain consistency and avoid configuration drift.

In summary, the ability to store, manage, and deliver workflows using Git and deliveries is feasible, but the exact implementation details will depend on your BPM platform's capabilities. Check your platform's documentation and consult with its support or community to determine the best practices and tools for your specific BPM system. Clover Dashboard