Jump to content

Martyn Houghton

Hornbill Users
  • Content Count

    3,205
  • Joined

  • Last visited

  • Days Won

    69

Martyn Houghton last won the day on February 17

Martyn Houghton had the most liked content!

Community Reputation

401 Excellent

5 Followers

About Martyn Houghton

  • Rank
    Senior Member

Profile Information

  • Gender
    Male
  • Location
    Theale

Recent Profile Visitors

4,025 profile views
  1. @Michael M Our Initial issue is that unless we authenticate as an account which has the admin privileges to accept the permissions, MS365 will submit the request for approval, but the session being used to create the KeySafe item will not pick this up even if it is done straightway, so no keysafe value is able to be created/stored in Hornbill. i.e. the mailbox user will not have the privileges to get to the screen above. Also are you saying that a 'Hornbill Office365 Mail Connector' has to be set individually for each mailbox? Cheers Martyn Approval screenshot
  2. @Kelvin As it is a linked image, the current Edit Post option does not allow for the removal of the image. When we have had this before for GDPR purposes it has had to be undertaken by Hornbill. I believe it has been raised before as an enhancement request. @Victor is this still the case? Cheers Martyn
  3. Microsoft 365 Mail Connector application authenticates as the account context used to create it, so when you remove permissions from the Office 365 application to use the account, the Test Connection then fail. This is linked to post below where the you have to create the KeySafe using the global admin user to get it to create, but obviously we do not want leave the Office 365 application with rights to use the global admin user account. Cheers Martyn
  4. Whilst attempting to setup the Microsoft Office 365 Mail Connector - we have identified that it does not support Microsoft 365 Approval Process, where the request is made and then sent for approval. The process appears to require you to log in as a full global admin account and do the process inline as part of the single session. Can the keysafe process be amended to support approval process? Cheers Martyn
  5. @James Ainsworth Thanks for the update. Let us know if you want to discuss the planned overhaul. Cheers Martyn
  6. @Alisha This will only show whilst the request is at the Resolved status and disappears as soon as it is closed. If you BPM set it to closed automatically after you resolve the request that will stop them from appearing (or at least not for very long). I do not believe there is a way to turn them off, so we got around it by changing the text displayed using the translations. Cheers Martyn
  7. @Steven Boardman @James Ainsworth Is there an update on this popular and time saving enhancement? Cheers Martyn
  8. Can the 'Design New Service' screen be updated to include the 'Default Mailbox' setting. The new Service Domain fields where added, but not the Default Mailbox which was an earlier addition to the Service functionality. Cheers Martyn
  9. @Ann Have you set a On-Hold Sub Status or just using the default parent On-Hold status and setup the sub-status changes on the service? If you have a look at the post below this might also help. Cheers Martyn
  10. @Kelvin The trick is that both the source and target sub statuses have to be set active. You do not appear to have a On Hold sub status, therefore the source is not set to auto update. We put out request on hold with the sub status of "Awaiting Customer Response' which is a on hold sub status and set to automatic. Cheers Martyn
  11. @Jeremy As an alternative approach we use a mandatory field with a specific Regex validation on it, in essence they would need to know a specific value in order to be complete the form, to stop them from logging the request, but provides a way to allow them to log one in a special circumstances if we provide them with a code. Perhaps the answer is a End Node which does not spawn a BPM and sets it as closed? Cheers Martyn
×
×
  • Create New...