Jump to content

Search the Community

Showing results for tags 'decision'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


Last Updated

  • Start


Filter by number of...


  • Start








Website URL





Found 10 results

  1. I am trying to find details of the format to enter a static date as part of a decision node custom expression. In the example below we want to change the routing in the workflow when a request is logged against a certain service but only do so from the 1st July. At the moment the custom expression when logged against Service ID 245 is equating as true, even though the date logged is still June. Is there a specific format the date value needs to be entered as for the date/time condition to work? Cheers Martyn
  2. So when I have gone into a decision today that looks for contains it seems that it has split the word/phase into separate individual components? Why has this happened and does this affect new decisions do we now need to set them up like this (as this is very labour intensive!)?
  3. When logging certain requests we make decision based on users email addresses but when we log into the new portal it does not honour these decisions.... basically if you have a @port.ac.uk email address it let's you proceed and if you have any other email address it will refuse your request with an incorrect account message. New Employee Portal Current Portal allows access: The PCF decision is as follows:
  4. Possibly a very stupid question but when I am using the variable picker i know longer see Flowcodes as an option. Was this changed to Hornbill Automations at some point and I have missed it? As per above we have set up decisions using the flowcodes previously but when I have gone it to make a change there are no flowcodes option.
  5. We have a PCF with a custom form which includes a date/time field, is there a way to make a decision from this so if for instance the date is between two dates then it can push you to another confirmation node? Node: Attempted decision (that doesn't work)
  6. Hi there, In our progressive capture form for Change management we have a customised form to capture impact and urgency. What I want to do is use the information captured for impact and urgency to then determine the priority of the change via decisions in the business process. Like a prioritisation matrix. Is there a way I can base a decision in our business workflow on the information captured from customised form in progressive capture?
  7. Hi, we have quite a few different priority levels that all have separate SLAs. When trying to set this up in the business process, I realised that decision nodes can only have a maximum of 3 outcomes. This means that in order to include all of our different priorities, we would need decision node after decision node. This makes the business process an awful lot more complicated than necessary. Is the number of possible decision node outcomes something that could be changed in the future? Thanks, Melissa
  8. As far as I understand, the custom expressions for decision nodes have to use literal values when using a static value. It would be really useful to be able to use wildcard and the like operator to be able to branch based on a matching value, i.e. if the Service name beginning with 'HR' follow this branch, rather than having to enter each literal value of the Services that begin with HR. Cheers Martyn
  9. Not sure if it is something I doing wrong in the process editor, but the Decision Node, seem to be limited to three output connections, i.e. four connectors on each point of the diamond, one is for your incoming process (at least), leaving only three options for the expression, but in reality you will normally always use one of these for 'No Match', so in essence you can only have two conditional paths from one decision node. Is the four connections the current limit and if so is there any plans to increase this? Cheers Martyn
  10. At the moment it is only possible to use a single variable in a Decision Task and the variable has to be the output of the previous BPM node. Which means that if you have multiple decision tasks in your process which are based on the Request Details or Questions you have to prefix each with a Get Request/Question node. Can we request a change request for the following options:- Variables/Parameters to persist in the whole process or stage, to remove the necessity of multiple Get Request/Questions nodes Decision Tasks to have the ability to reference these persistent variables rather than just the output of the previous node. Decision Tasks to support structured expressions using multiple variables, rather than be restricted to a single variable evaluation. Thanks Martyn
  • Create New...