Jump to content

Search the Community

Showing results for tags 'closure'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    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. If we are seeing a common issue within the company we normally raise a problem or known error and associate all the relevant calls that have been logged to them. When we close that problem or known error is there a way for users of all the calls that have been associated to be emailed the resolution? Not sure if this in existence, if not it would be very useful as did exist in Support Works.
  2. Hello, Following on from this: @samwoo's topic which is related to the issue that I'm going to explain below. We have an issue at the moment with the 2 Stage Closure node in Business Process and we are not sure why or what is the problem. When the request ticket is resolved, it would wait for 5 days before it automatically close the ticket if the customer did not reopen. However last day of resolved is on 18th June therefore it should close on either 23rd June or 25th June. I checked today and it did not close, I even went into request BPM ID to checked and edited the process from 5 days to 3 minutes to test whether it would close the ticket but nothing happened. There is no error or anything but it seems to be stuck on the node. (Please see below) Hopefully I would get answers from you guys to solve this. Kind regards, Aaron Summers P.S. Just to confirmed it not a single ticket issue as we think it MAY affected all BPM after the changes we made on the 15th June.
  3. Good morning, I am in the process of creating a new request process for my company, and an error occurred when trialling the process, I can not progress this any further as the process has failed which is fine, but how od i force close the request so it doesnt stay open and show an error in the service portal? At present, the timeline shows the error, but i would like to force this to closed as attached,
×
×
  • Create New...