_zzz_

Comments

  • How would you accomplish that? We had to create the Manager field as a custom client field (text) as indicated in the initial post. I'm not sure how you would read that text into an action rule and then take appropriate action on it.
  • Has anyone found a method to do this yet? We would like to do something similar: if a purchase request comes in, route it to the manager listed in AD for approval before sending it to the acquisition team.
  • I get that; except we don't necessary want a separate rule for each manager. We are looking for a way for the approval process to check the requester's manager in AD (via LDAP lookup), and use that criteria to send that person the approval email, rather than create a lot of explicit rules.
  • Not yet; that's my next step is to try and parse the AD garbage and just output the name.
  • We just migrated to 365. What settings did you use for the mailboxes: IMAP, POP, EWS? Also, was your mailbox a user mailbox or shared?
  • What configuration did you use? We are getting set up in 365 post migration now.
  • Thanks for the tip. Tried to use the “REASSIGN” tag in a test ticket, and got the following. I’ve confirmed the address in the [email address] section matches exactly what shows as the primary email in the tech Account Info page. Your request to reassign Ticket 10718 could not be completed due to the following error:…
  • We have it working in our preview environment with WHD 12.7.1 - Build #12.7.1.538. In Okta: * Create new app, SAML 2.0 * Enter name, and upload icon * Enter SSO URL: <domain>/helpdesk/WebObjects/HelpDesk.woa * Enter SP Entity ID: <domain>/helpdesk/WebObjects/HelpDesk.woa * Name ID Format: EmailAddress * Application…