Jump to content

Steve Giller

Hornbill Staff
  • Posts

    6,498
  • Joined

  • Last visited

  • Days Won

    268

Posts posted by Steve Giller

  1. That looks like an outdated format for the config file to me.

    I would suggest reviewing the Hornbill Documentation site, ensuring that you have downloaded and configured the latest version from Github, and posting any remaining issues here.

    The first line of the logs will indicate the version - the json above looks like a version 3 config, this has changed significantly for version 4.x particularly in the connection area.

  2. 4 minutes ago, Sahana. Shenoy said:

    Could you please advice, where can I configure the settings for receiving an email notification for @Mentions.

    There is no setting to receive emails for Mentions - these are designed for communicating within Hornbill.
    The options available for Mentions are the notification within Hornbill and Desktop notifications from your browser.

  3. On 23/01/2024 at 16:33, will.good said:

    how can we define this to be used on either Closure or Request (in place of the ones we use currently)

    If it's a Request Category, you build it under "Request" or for a Closure Category, you build it under "Closure"

    To ensure only the Coding Tree category (and its sub-categories) are used for a Service you filter using the Request/Resolution Category Level as appropriate.

    image.png

    Then you will see the relevant Profiles on the Request Category Action:
    image.png

    and Resolution/Closure Category Action:
    image.png

  4. 2 minutes ago, HGrigsby said:

    When we have a major incident we can end up with a lot of incidents logged for the same thing waiting for a fix and need to put them all on hold.

    Just being pedantic here but, in the context of ITIL, if the affected Customers are waiting for you to fix it ... shouldn't the requests be Open? On Hold is when you're waiting for the Customer.

  5. After testing, simply removing the caret worked fine in my Instance.

    image.png

    image.png

    Also, I noticed on a second look that the "pipe" after the period was redundant as well - it wasn't breaking anything, it was just pointless.

    image.png

  6. 1 hour ago, will.good said:

    we are also seeing the reqeust source when analysts are raising a new linked request via the Link Request action - is this expected?

    Yes, this is as designed; in the same way that when an Analyst raises a Request from a Workspace Post it has the source of "Post" the Linked Request was raised from another Request, so has that as the Source.

    If you think of the Source as "from" and not "by" it should be clearer.

  7. The Log New Request node returns the Reference of the new Request.
    You can use that variable to put the Reference of the original Request in the External Reference of the new Request.
    Once the new Request's Task is completed, you can use its External Reference to put the outcome of the Task into a Custom Field on the original Request.

    I think that would be the most efficient way of achieving this.

  8. source of "Post" means that the Request was raised from a Workspace post.

    source of "Request" means that the Request was raised by another Request's Workflow, so they would not be raised by an Analyst and would not have that as a source.

    • Thanks 1
  9. I've tagged this as an enhancement for you.

    Please note that this does not mean that it will be accepted, but the Board Manager Developers will see this post and consider the Enhancement.

    I've also moved this to the Board Manager forum.

×
×
  • Create New...