#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

New Designelement: Workflow

Why not adding Workflows as a designelement within Dominodesigner?


But PLEASE(!), DON'T use "Lotus Workflow" or something similar for this idea! Just take a look into several other products released by the competition (like ServiceNow i.e.) and have a look how they are handling workflows!

  • Guest
  • Jul 20 2018
  • Under Consideration
  • Attach files
  • Guest commented
    13 Jan, 2020 03:35am

    This is very strategics. Make a new "Lotus Workflow"!

  • Guest commented
    9 Feb, 2019 04:12am

    We wrote 2 systems of Document Management System class on Domino.

    I will describe in a few words if it will be interesting to someone.

    The route is divided into blocks.
    The blocks are of the following types:
    - activity: familiarization, execution, coordination with a variety of options;
    - condition - CASE-transitions to other blocks;
    - action - anything, from writing/deleting a list of fields, to calling agents, services, etc.

    Routes are:
    - basic - own for each form of document - in the course of movement the document statuses (states) change; intended for vertical movement of documents;
    - auxiliary - at each step of the route, users can send a document on their small routes (for execution or familiarization); document statuses do not change; intended for horizontal work with the document.
    There can be only one main route per document and there are no restrictions on the number of simultaneous auxiliary routes. Different groups of people can simultaneously work with a document on their questions, often without even seeing each other’s work (regulated by access in block settings).

    At least at each stage, with some exceptions, the employee may respond positively or negatively.
    If the answer is negative, depending on the settings of the block, the document can go either to the previous stage or to the beginning to the initiator of the activity.

    If suddenly something went wrong (happens very seldom), the DMS administrator can manually return the document to the desired state.

    With rejection, versioning is supported. A version can be created from any document in the version hierarchy. Using third-party utilities, one can compare the text part of two selected hierarchy documents.
    Etc. :)

  • Guest commented
    26 Jul, 2018 09:53am

    And I may add:

    • Allow for 'models' supporting Static and Dynamic workflows ie whether statuses in Documents change on the server side and/or sent as tickler mails to the next recipient
    • Force automatically (or by prompting) Views to be added 'WorkFlow' required attributes if the workflow component is 'imported'
    • and have perhaps more Views propagated, needed for Workflow purposes, like Workflow agents that has to monitor and act on flows on the server side.
  • Guest commented
    20 Jul, 2018 10:45am

    Voting for!

    It is desirable that BMPN be used here.

  • Guest commented
    20 Jul, 2018 09:33am

    Yes... and every workflow will process every document in a unified way!


    But the key to success of this design element would be the kind of implementation!!!


    - Make it simple

    - Make it editable with a great (browser based?) editor using state of the art frameworks (like Bootstrap or similar)

    - Make it deployable by simply copy & paste! (I.e. the guy(s) from Microsoft, who wanted to have workflows in Sharepoint never used them or never knew how to do it for real-use in real applications...: Who needs workflows, which have to be configured for every new version on each system by clicking and typing it in?!)

    - Don't restrict processing of Workflows! Make it open to developers with a unified API to enable events and custom code AND allow Domino-based technologies! (i.e. @Formulas for validation etc)

  • Admin
    Thomas Hampel commented
    20 Jul, 2018 09:15am

    Interesting approach. it will allow to assign a workflow to more than one type of Document.

  • Guest commented
    20 Jul, 2018 07:59am

    PS: ... ELO Enterprise is using Workflows also with a AWESOME Workflow Editor also!