Jump to content

Search the Community

Showing results for tags 'substatus'.



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 3 results

  1. Currently the 'Wait for Status Change' node only completes when the primary 'Status' changes i.e. from 'OnHold' to 'Open'. It does not trigger is the SubStatus is changed within the same parent 'Status', i.e. changes from 'Open->Pending with AM' to 'Open->Pending with Analyst'. Can the node be extended to have the option to trigger on a change to the SubStatus or can a new Suspend Node be for this. i.e. 'Wait for SubStatus Change'? Cheers Martyn
  2. I'm having a moment, does anyone know where the setting is that allows a request to be automatically taken off hold if a customer updates the request from the Portal? I'm also hoping that I can reference this in the BPM to check to see if a customer has updated the request by email or portal and then progress based on this?
  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
×
×
  • Create New...