Jump to content

Search the Community

Showing results for tags 'reason'.

  • 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
    • IT Operations Management
    • 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 4 results

  1. Related to the post below about having access to 'Snippets' in the request view 'Update' action, can I also request that they are also made available in the 'Reason' field when completing Human Task/Activity as well. Cheers Martyn
  2. We are implementing the use of Sub Statuses which are updated both by the BPM and manually. Though not an issues when updating by the BPM, when you manually change the Sub Status through the Live user app, a pop up window appears prompting for a reason every time. This creates more work and becomes annoying very quickly. Though there are certain scenarios where we would want to make the pop up and completion of the reason a required process, there needs to be the ability within the setup of the sub-status to configure if changing the request to said status requires the prompting fo
  3. Hello, One of my colleague raised this interesting request few days ago. He asking for the reason box when use substatus of the request to be remove, because the substatus should be clear of what it means without need to add reason on it. Also he mentioned that if necessary to add information then he would use comment box instead of reason box for update. (Please see example below). I wonder if there is possible to add new ability to turn on or off for each individually of substatus if need to keep reason box. Thanks, Aaron cc: @samwoo
  4. As with additional 'Outcome Fields' on Human Tasks, add the ability to enter a 'Placeholder' description for the generic 'Reason' field, so guidance can be provided to the person assigned the activity. This saves having to disable the Reason field and add additional 'Outcome Fields' just to get a supporting description. Cheers Martyn
  • Create New...