Jump to content

David Hall

Hornbill Developer
  • Posts

    653
  • Joined

  • Last visited

  • Days Won

    34

Posts posted by David Hall

  1. Hi @Joshua T M

    Thanks for posting.  This reference has appeared earlier than intended as a result of some ongoing development work where it should have been hidden behind a flag.  We'll hide it in the next Service Manager update.

    Given that this reference could make its way back in the future,  it would be good to understand from your perspective why you would want to hide these references or what problem making the reference visible poses.. we can then feed that back when developing changes in this area.

    Kind regards,

    Dave.

    • Like 1
  2. Hi @Tina.Lapere

    I've linked a previous post which may suggest a couple of reasons why some emails would not get applied to tickets... additionally I would check if the sender email address is associated to more than one user in your instance as this will result in failing to apply as the sender cannot be uniquely identified.

    If you don't have any joy with these suggestions please post back.

    Kind Regards,

    Dave

     

     

  3. Hi Martyn,

    I've had a look and the documentation is correct in terms of hid being expected for both the Category and Category (From Variable) fields, there has never been provision for the textual code so both fields do essentially operate in the same manner from a data perspective.  I can't say for sure but IMO the distinction of two variables was probably just created to provide a clear difference in the UI so that manual selection of Category would open the category selector popup while Category (From Variable) was available for automated population.

    Kind regards,

    Dave.

    • Thanks 1
  4. Hi @Adrian Simpkins

    Yes when a request is cancelled it should remove any escalations and notifications as part of the cancellation process.  There haven't been any changes I can see in this area for more than 2 years now so nothing should have changed.  If it becomes a persistent problem then the logs would need to be checked to see if there is something failing within the cancellation process.

    Kind Regards,

    Dave.

    • Like 1
  5. Hi @Paul H

    If it has stopped working without any changes then I wonder if its due to the recent deprecation of the old service level functionality.  The following post details this and the steps to migrate going forward.  If you need any further assistance please feel to post back.

    Kind Regards,

    Dave.

     

  6. Hi @Mike Hillman

    Just as a follow up to this.. it appears the issue you experienced is directly related to the copying of an older automation node.  Following the deprecation of a number of entity flowcodes recently, the old node when copied can cause the panel not to load correctly.  I believe the issue has been corrected but when copying these older nodes its possible it may stall where it tries to load content that is no longer valid.  Reselecting the drop down options, creating the nodes from scratch or using a copy of a recently created node should continue to work correctly.

    Kind Regards,

    Dave

  7. @Mike Hillman

    I've just double checked with our cloud team to make sure there are no performance issues with your instance and all looks good there.  I've just tried editing some BPMs locally and as per @Paul Alexandercomment I can't see any issues around loading/editing/drag and drop.

    Ideally as you suggest it would be good to confirm if this is an issue for anyone else in your organization to confirm if its Edge/security settings related or something else.

    Regards,

    Dave.

  8. Hi @QEHNick

    Thanks for the post.  As you have correctly identified, department is not something that can be used when assessing SLAs, we don't store this directly against a request and to my knowledge its not a scenario that we have come across before. There is no current plan to extend this functionality further but if there is enough customer demand then we can look to consider adding this to the future enhancements list.

    As a possible workaround to this, you can access the custom request fields from the SLA rules... so perhaps in your BPMs before you initialise the SLA, you could retrieve the department value from the customer using one of the user tasks e.g.

     image.png
     

    and then store the retrieved department value against the request in one of your custom fields?  You could then reference the custom field in your SLA rules?

    Kind Regards,

    Dave

     

     

×
×
  • Create New...