HGrigsby Posted May 6 Share Posted May 6 Hi I have followed a couple of threads on this and thought I was getting there, but I have hit a snag and could really do with some help. I am trying to set up an authorisation to go to the manager of the person raising the request. I have added a Get Customer Detail and then a Get User Manager Email but when I add it in the authorisation node it seems to skip the authorisation and give me a gotoif error on the decision after it. I tried adding the manager email address into a custom field but that didn't seem to do it either. Can anyone give me an idea? This always happens when it is needed in a hurry! Thanks Helen Link to comment Share on other sites More sharing options...
Conor Posted May 6 Share Posted May 6 Hi @HGrigsby This method definitely works: Link to comment Share on other sites More sharing options...
HGrigsby Posted May 6 Author Share Posted May 6 @Conor Thanks for the reply but can't open the link! Link to comment Share on other sites More sharing options...
Conor Posted May 6 Share Posted May 6 @HGrigsby It should just be an image? Basically it's get customer info -> Get User Manager Details -> pass the email output from that node into the 'to' field for the external auth and/or the custom field and that works for me. Make sure it's the customer ID that goes into the Get User Manager Details node in the User ID field, rather than the customer name Link to comment Share on other sites More sharing options...
HGrigsby Posted May 6 Author Share Posted May 6 Hi @Conor Ahh Ok still can't open it but I have the get user manager details but it just doesn't seem to do what I expected it to. It looks like it's right but it just doesn't work Helen Link to comment Share on other sites More sharing options...
HGrigsby Posted May 6 Author Share Posted May 6 Link to comment Share on other sites More sharing options...
Steve Giller Posted May 6 Share Posted May 6 Just being picky, but your Node config says "Authorise" and "Decline" and your Decision branches say "Authorise" and "Reject" If you had (as is recommended for all decisions) a No Match branch you could at least use that to push the values to the Timeline and compare them with what you expect to see. 1 Link to comment Share on other sites More sharing options...
HGrigsby Posted May 6 Author Share Posted May 6 @Steve Giller Not surprised! - I've changed everything today to get the manager to populate in the authorisation. I've tidied the names up now though I just took the get manager node out and went to add it and it says its missing a mandatory input parameter has not been set. Not sure what it is missing. Link to comment Share on other sites More sharing options...
HGrigsby Posted May 6 Author Share Posted May 6 (edited) @Steve Giller Not surprised! - I've changed everything today to get the manager to populate in the authorisation. I've tidied the names up now though I just took the get manager node out and went to add it and it says its missing a mandatory input parameter has not been set. Not sure what it is missing. If anyone has any ideas I'd be grateful, otherwise I'll log a support call on Monday Thanks Edited May 6 by HGrigsby Adding screen shot Link to comment Share on other sites More sharing options...
Steve Giller Posted May 6 Share Posted May 6 @HGrigsby It's not possible to advise without seeing the config of the node, I'm afraid. Link to comment Share on other sites More sharing options...
HGrigsby Posted May 6 Author Share Posted May 6 @Steve Giller The user id was blank so I tried adding in the variable and still get the same Link to comment Share on other sites More sharing options...
Steve Giller Posted May 6 Share Posted May 6 With this settings I do not see any errors. I'd recommend deleting the node and adding a new one, especially if there's any chance it was copied from elsewhere. Also, can you give the full variable - the right hand end may be important and it's hidden in the image. Link to comment Share on other sites More sharing options...
HGrigsby Posted May 9 Author Share Posted May 9 Thanks @Steve Giller deleting the node and adding re-adding it seems to have fixed the issue. Just wish I could stop the authorisations sending out the standard email afterwards, we want to send a more polite one than the default. thanks again for looking at this for me Helen Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now