convedo Tech Talk

Covid-19/Coronavirus Releated Solutions Learn more

    Workflow Model Types

    Conceptual-level Workflow Models

    Conceptual-level Workflow Models typically provide an end-to-end view of an entire Business Process unless the Business Process is so complex that it requires more than one conceptual level. The purpose of a conceptual-level Workflow Model is to organize and link together the more detailed models that are based on their Activity Usages.

    If the Business Process was properly decomposed by first using the Process Model, all of the Activity Usages in the conceptual level of the model should be the subjects of other Workflow Models.

    Elemental-level Workflow Models

    Elemental-level Workflow Models typically provide the detailed responsibility needed for understanding the nature of current work or for providing the operating procedures for implementing the changes in revised Business Processes. They are usually the lowest level of Workflow Model needed to document most Business Processes.

    Task Flow-level Workflow Models

    Task Flow-level Workflow Models are optional models that provide a detailed understanding of the specific tasks that an Actor is responsible for between handoffs from and to other Actors. In a Task Flow model, all of the Activity Usages are in the same Workflow lane. The only Workflow links that should cross Workflow Lanes in this model type should be the one(s) from the contextual object(s) to the first task in the sequence or the one(s) from the last task in the sequence to the contextual object(s). 

    This level of the Workflow Model can usually be documented by simply listing the task-level steps in the description of the Activity Usage. In other words, document the steps textually rather than building another Workflow Model with all Activity Usages in the same workflow lane. Creating Task Flow-level Workflow Models is very expensive and should be avoided unless all of the following are true:

    • The Activity Usage that the model is based on is performed frequently enough that even small (task-level) changes could yield significant results.
    • All of the tasks are not performed all of the time. The Task Flow-level Workflow Model will have at least one Decision Point.

    7 steps to BPM Success

    Topics: Business Process Management- Workflow

    Previous Post

    The OpenText Process Suite ABC Glossary - WS AppServer Package part 2

    Next Post

    What is new in OpenText MBPM version 9.4.2?

    7 steps to bpm success

    Free Whitepaper: 7 Steps to BPM Success

    A Pragmatic Approach to Leveraging BPM Technology for Business Success

    This whitepaper provides the reader with a 7 Step model that seeks to suggest ways in which organisations can maximise their business returns. The model sets out to blend the benefits of non-technology approaches with the more technological ones.

    Download Whitepaper Now

    Have a project in mind?

    We'd love to chat with you and find out how we can help solve your process and automation challenges.

    Get in touch with us

    SUBSCRIBE TO CONVEDO WEEKLY!

    Get all the latest updates on Intelligent Automation.

    Fill out the form below to subscribe to the convedo newsletter.

    Subscribe to Email Updates

    100% Privacy. No Spam.

    Recommended Reading

    Posts by Tag

    See all

    Start Delivering Business Applications Faster.

    Start Your Digital Transformation Journey Now