Jump to content

Search the Community

Showing results for tags 'decisison'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Hornbill Platform and Applications
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Configuration Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Organisation


Location


Interests


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 1 result

  1. As you are probably aware it is not possible to have more that one input path into a business process decision node. Like this: However, there are scenarios when configuration requires that multiple paths converge at some point into one decision node. Like this: If you try and create a link the second node into the decision node, it will fail and this message will be displayed: "The target node has too many entry points". This scenario has been catered for by introducing an "intermediate" node in which all nodes converge before the decision, then create a single link between this intermediate node and the decision. There are occasions when this "intermediate" node is actually required in the process design but sometimes there isn't any so a simple choice would be to use a generic node. The obvious and most used choice is "Get Request Information - Get Request Details" node. Because this node one retrieves information/data about the request is not affecting the process progress or the associated request in any way. Like this: This is a valid configuration and works as intended and achieves its purpose. However, we think there is a better, more efficient and resource friendly way to achieve what you need (merging multiple paths into one decision node). Although there is nothing technically wrong using a "Get Request Information - Get Request Details" to act as a placeholder for a connector, it is not the most effective way, especially if is used in many places in the process. keeping in mind that the more complex the design, the more time it would take to run the process, use more resources, etc. Ideally, we would want to make it as efficient as possible. Therefore instead of using an automated task as placeholder, why not use a stage checklist node. The advantage is that you will achieve the same but without making the process more cumbersome. Like this:
×
×
  • Create New...