Onestop Administration Portal
  • Onestop Admin
  • Getting Started with Onestop
  • Managing Services
    • The Basics of a Service
    • Building the Workflow
      • Adding a step to your workflow
      • User Task Types
      • Service Task Types
      • Managing Stages
      • Tutorial - Example Workflow
    • Managing Forms
      • Using the Form Builder
        • Form Field Types
        • Field Validators
        • Field Dependencies
        • Form Submission Identifiers
        • Field Tags
        • Linked Fields
      • Sharing Form Submission Links
    • Configuring Workflow Notifications
    • Configuring Billing
      • Billing Task
      • Payment Task
      • Configuring Payment Forms
    • Document Templates
      • Creating Document Templates
      • Using the Document Template Editor
      • Designing a Document Layout
      • Using Document QR Codes
    • Context Tags
    • Managing Workflow Access for Teams
    • Advanced Settings
  • Databanks
    • Databanks and Datasets
    • Creating a Databank
    • Creating Datasets
    • Adding Data to Datasets
    • Using Datasets
  • Portals
    • Managing Portals
    • Configuring Mail Servers
    • Creating a New Portal
    • Managing 2-Step Verification
    • Customizing Portal Menus
  • Teams
    • Managing Teams and Permissions
    • Creating User Accounts for Workers
  • Organization & Departments
    • Managing Departments
  • Appendix
    • Tips and Techniques
Powered by GitBook
On this page
  1. Appendix

Tips and Techniques

PreviousManaging Departments

Last updated 1 year ago

Recursion

You may have a scenario where you need an activity to be always available to a user in your workflow. Onestop uses recursion to support a BPMN loop activity ().

The concept is straight forward to implement: Make the next step of your current step to be that exact current step.

https://methodandstyle.com/repeating-activities-in-bpmn/