Skip to main content
Version: 6.1

Deployment & Publishing

Deployment

Deployment in B2Win Suite is the process of publishing a workflow so that it becomes available in a production environment. This allows the workflow to be executed by end users, external systems, or scheduled tasks outside of the development or design phase.

Steps to Deploy a Workflow​

  1. Open the workflow you want to deploy.
  2. Click on the Deploy button located at the top-right corner of the builder.
  3. In the deployment dialog:
    • Preserve Current State: If there is an already deployed version of the workflow, you can choose to preserve its current state. This ensures that the existing workflow’s state (e.g., scheduler timings, query values) is maintained. If it is a new deployment (no prior version exists), no state will be set by default. Optionally, you can choose to use the development state as the starting state for the production deployment.
    • Select Triggers: Choose which triggers (e.g., HTTP, Schedule) should be active in production.
  4. Click Deploy to publish the workflow.

After Deployment​

  • The workflow will now run continuously in the background.
  • All specified triggers will be active and ready to execute their respective tasks.
  • The workflow will serve its purpose seamlessly in production mode, independent of the builder being open.

Key Features​

  • Trigger Control: Activate only the required triggers during deployment. Inactive triggers can be enabled later as needed.
  • State Management:
    • Preserve State: Retains the state from the previously deployed workflow, ensuring smooth transitions without data loss.
    • Development State: Optionally deploy workflows using the current development state.
  • Environment Separation: Keep development workflows isolated from production.

Managing Deployed Workflows​

ActionDescription
RedeployUpdate the deployed workflow with new changes.
UndeployRemove the workflow from the production server.
View LogsAccess execution logs from the deployment panel.

Best Practices​

  • Preserve State: Use this option to ensure continuity when updating workflows.
  • Selective Triggers: Activate only the necessary triggers during deployment to avoid unexpected executions.
  • Testing: Always test workflows thoroughly in development mode before deploying to production.

By deploying workflows, B2Data ensures that business processes and tasks run reliably, efficiently, and independently of the development environment.