Jump to content

Search the Community

Showing results for tags 'outcome'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Hornbill Platform and Applications
    • OpenForWork
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • IT Operations Management
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document 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 5 results

  1. We have a task that uses a dynamic simple list as we don't want to input it everytime we use it, with the options of Yes, No, N/A but to display these in that order we have to ade 1,2,3 to the Item value to allow sensible ordering. However when the task is completed the outcomes show the Item Value rather than the display value (see below), is there way to change these to be the display values? As it makes reading the outcomes of the task a lot easier than remembering 1=Yes etc. Task outcomes: Simple list:
  2. Hi, Can someone look into this please and see if I have unearthed a bug... We have a 'Human Task' in our Incident BPM called "Investigation and Resolve". When looking at the timeline in the Incident, the outcome answers are being logged twice in the timeline update. Here is the config behind the outcome called 'Completed' Example of timeline entry When I clicked on the blue 'Investigation and Resolve' link in the timeline entry, this is what I got. Any ideas please folks...??? This is happening every time this outcome is chosen in the "Investigation and Resolve" task/activity. Thanks Steve.
  3. I am getting the following error when the outcome for a task 'More information required' is selected. flowcode ("s1"/"flowcode-07ca230e-2786-499e-f987-a499190ca29a") execute: at 1/125: "Uncaught TypeError: Cannot read property 'outcome' of null" ((function(s){ return true || s !== undefined? s: "" })(functions.getTaskParams("task-8974dc14-ec21-4bda-ec95-309f03ab4592").outcome))" ---------------------------------------- ((function(s){ return true || s !== undefined? s: "" })(functions.getTaskParams("task-8974dc14-ec21-4bda-ec95-309f03ab4592").outcome) I am assuming that the node where i am trying to update the request timeline with the custom outcome for the task is the issue here. I have set it as so: I believe the function is incorrect and prehaps the task code is the wrong one, if this is the case how do i find out what he task code is for that node? When i go to variable picker- tasks- i get 2 options 'get additional info' becasue i have 2 task nodes with the more information required button on them It doesnt matter which option i select they both come back with the same error? Jsut with the differnet Task code: flowcode ("s1"/"flowcode-07ca230e-2786-499e-f987-a499190ca29a") execute: at 1/125: "Uncaught TypeError: Cannot read property 'outcome' of null" ((function(s){ return true || s !== undefined? s: "" })(functions.getTaskParams("task-8974dc14-ec21-4bda-ec95-309f03ab4592").outcome))" ---------------------------------------- ((function(s){ return true || s !== undefined? s: "" })(functions.getTaskParams("task-8974dc14-ec21-4bda-ec95-309f03ab4592").outcome) Or flowcode ("s1"/"flowcode-07ca230e-2786-499e-f987-a499190ca29a") execute: at 1/125: "Uncaught TypeError: Cannot read property 'outcome' of null" ((function(s){ return true || s !== undefined? s: "" })(functions.getTaskParams("task-57c5d569-4a57-4801-25eb-59fd5a90f381").outcome))" ---------------------------------------- ((function(s){ return true || s !== undefined? s: "" })(functions.getTaskParams("task-57c5d569-4a57-4801-25eb-59fd5a90f381").outcome)) Hayley
  4. At the moment it is not possible to make use of the response/reason text entered into the system when completing a a human task, as it is not accessible as a variable in the email templates. It would be really useful to have an option on each outcome from a human task to generate an email notification using a template and pass the response/reason text into the template as a variable. For example you would be able to generate an automated email to advise that your request has been put on hold with the following update. Where as at the moment you have to do a manual email from the request then complete your activity as well. Cheers Martyn
  5. At the moment the Business Process nodes all realte only to the request entity and it related objects, however there is no ability at the moment to determine the 'current context' i.e. who is undertaking the action or operaiton which is completing a step or tiggering the end of suspend operation. In Support Works you had the field last updated by on the primary table which allowed you do ascertain some form of context, but there is no equivlany field in the Requet Entity. The reason for wanting this is to be able to branch within a workflow depeding on 'who' completed the last action. For example within our workflow we have a Wait for Request Off Hold suspend node, which when it comes off hold immedialty creates a follow on human task agasint the request owner. However there are a number of reasons why the request may come off hold, one of these could be that it is being chased by our 1st Tier as we have not had a response from the customer and need to put it back on hold. Inorder for them to send a chasing email to the customer they have take it off hold, which creates an activity for the request owner not the person taking it off hold. Similarly if it has come off hold automatically (i.e. like the old Support Works Off-Hold status) we may want to automate the chasign process in the workflow. Therefore it would be good if the BPM nodes, in particular the Supped Nodes had Outcomes specified to determine 'what' the outcome was, i.e. Hold Time expired, Manually taken off Hold, and 'who' undertook the operation, i.e. 'System', analystid etc. This way you could follow the suspend node with a decision branch to automate what happens if the request comes off hold after it expires or if it is taken off hold manually by someone other than the owner we could create a human activity for the analyst who took it off hold rather than for the owner. In short have the BPM being aware of the 'context' of the update allows a much wider dimension for controlling and routing the workflow, compared to the current request entity only standpoint. Is there any plans to add on this context type of information into the BPM? Cheers Martyn
  • Create New...