Jump to content

Victor

Administrators
  • Posts

    5,677
  • Joined

  • Last visited

  • Days Won

    168

Everything posted by Victor

  1. @Tina.Lapere there is no password (in Hornbill) for an oAuth2 connector... the connection is made using the token created when this was set up. When the token was created the authentication was performed in Azure context so using your (and your admins) username and passwords provided by Microsoft. Here is a summary of how the setup was performed for an oAuth2 connector: 1. In Hornbill we create a keysafe for the O365 email connector 2. We use the "Connect" option on keysafe to create the token 3. Microsoft then does an authentication sequence to approve and authorise this token. This all happens in Microsoft context, not Hornbill. 4. Once all is approved (in MS/Azure/O365) the token is created and this is what Hornbill email connector will use going forward to connect to your O365.
  2. @samwoo ummm.... why? ... what "worries" me more is this post is in Integrations section... which might indicate you are using this for integrations... which would be... ermm... not good
  3. @samwoo you mean like progressive captures with specific questions and answers?
  4. It will be matching SR00060093 which has been cancelled thus the email will not be applied to it. If the rule is to replace an SR with an IN you can simply change the reference as: [inIN]{2}[0-9]{8} Note this only works for when you want to specifically look for an IN.
  5. @QEHNick ok, I understand. May I suggest a support request so we can gather all info we need to discuss this with dev team?
  6. @QEHNick have you refreshed (F5) the app page (where you raise a request) after changes to PC? The PC data is cached in browser (for performance reasons) so any changes to PC definition will require a page refresh for the browser to then cache the new PC (with the changes)...
  7. @QEHNick where is this, is it when you design the PC or when a user actually uses it to raise a request?
  8. @Emily Patrick from my understanding your instances is fine so you can update your user base.
  9. @all This might sound as some sort of deja vu but we do have a solution which is being deployed to instances at the moment.
  10. Ok, we are investigating why some instances seem to not have picked up the patch, please bear with us...
  11. @LifeOfJonny can you give it another try now?
  12. @all We have performed a hard cache reload on front end apps which we believe was causing the patch not to take effect. This has now been addressed and request list should be accessible now.
  13. @George Warren it is a bit difficult to troubleshoot this on forums... may I ask you to raise a support request so it can be investigated? One thing to mention is that email template variables will not resolve on request timeline updates, specifically this: ... will not result in the variable value being displayed. The variable in {{ ... }} format is only resolved in email templates.
  14. @Stefania Tarantino are they listed as Service Manager users in this section? (note the context is Service Manager and not Platform Configuration)
  15. @Mark (ESC) button won't enable if there are mandatory fields with no value...
  16. @will.good if you want to avoid you performing a manual exercise, an option would be to request this as an expert service with Hornbill.
  17. For future reference, issues can be raised here: https://www.hornbill.com/support/
  18. @Berto2002 ...sigh... ok... well... you know, support request and such...
  19. @Berto2002 when on this form if you click on "All Assets" then click on "My Assets", would this now display the correct/expected items in the assets list on this form?
  20. @Alistair Young one of our infrastructure nodes if having some issues (that are being addressed), if I am not mistaken your instance is affected, I'm afraid... we're working on it.
  21. Yes. Technically, this is a global settings for ALL emails (which means any/all mailboxes).
  22. @Berto2002 I'm afraid that's not how it works... email template variables and workflows are not related to one another... the email templates have their own (independent) way of resolving variables while "Get Request Details" workflow node only provides runtime values for the workflow (these are values that are used inside the workflow but nowhere else). Therefore for email template variables to work, there is no requirement for workflows to have any specific configuration (e.g. "Get Request Details" node).
  23. @Ruth are you using request categories alongside closure categories? If not this would be an option to consider. Another option is to make use of custom fields that you can expose on request details. You can use them for reporting... On a side note, is this (also) your forum user @Ruth Hicks?
×
×
  • Create New...