Jump to content

Leaderboard

  1. Ricky

    Ricky

    Hornbill Product Specialists


    • Points

      2

    • Content Count

      201


  2. Ehsan

    Ehsan

    Hornbill Developer


    • Points

      1

    • Content Count

      834


  3. AlexTumber

    AlexTumber

    Hornbill Developer


    • Points

      1

    • Content Count

      1,086


  4. Victor

    Victor

    Administrators


    • Points

      1

    • Content Count

      4,778


Popular Content

Showing content with the highest reputation on 04/14/2021 in all areas

  1. @AndyGillyI can see that the Manage Executed Processes feature does not allow resuming a process after failure. I have asked the Dev team to look into the issue and if it is possible to implement the feature. The interface used for both BPM and Runbooks; however, Resuming a process is not supported for Runbooks. I will get back to you as soon as I get a reply. Ricky
    1 point
  2. Hi @Ricky thanks for coming back, we have been using this view I was more after my options once we have a executed instance that has an error currently it seems we only have the re-run process option, but it very likely we dont want all steps to be re-run. Ideally, you would want the option for the runbook to restart from the failure point. hope that makes sense thanks Andy
    1 point
  3. Hi @AndyGilly, I will chat with the dev team and get an update on any progress. Ricky
    1 point
  4. @Alisha we will have to raise a support request to investigate this. EDIT: we have raised it you should have received a notification email in this regard.
    1 point
  5. Hi Alberto, This is one of those tough scenarios where there is a difference of opinion on the behaviour. At the moment, the default visibility is only meant as the starting point for when you open a request. This is why refreshing the page returns to the default, as it behaves like you are opening the request. While I am more aligned with you, others suggest that they want these to persist for the duration of an agent looking at the ticket. For example an agent has multiple customer facing updates that they want to apply, and the default is set to team, they want to set the visibilit
    1 point
  6. Hi All, We have updated your Hornbill instances with the fix for this issue. Ehsan
    1 point
  7. @Ann thanks for your post. This functionality is still relatively new and we have many more things planned for the integration, including different points/triggers for starting and stopping these events. We did consider the idea of being able to pause an event when first developing the functionality but ultimately it led to multiple scenarios that we didn't feel we should cater for. As an example, we have something in the pipeline that will give an overall metric of time spent with a supplier for each request, regardless of the number of events that occur. We feel this is better than gettin
    1 point
×
×
  • Create New...