Berto2002 Posted March 4, 2022 Posted March 4, 2022 Hiya, I have a PCF where the person Requesting it can say they are logging it on behalf of someone else and select that person from a Co-workers lookup into h_custom_b. In the workflow, it then detects if h_custom_b is populated and proceeds to: Extract the UserID from Custom B. This works get the Line Manager's UserID from the above result: . This works Add the Line Manager as a Connection: . This works (the right LM gets added) Add the requester as a Requester Connection: . This works And then it is supposed to update the Customer using the same Regex result that was used to find the Line Manager. But this step doesn't work: . The Customer stays as per the person who logged the ticket The TimeLine shows the extracted email address (CustomerID) is correct: The overall sequence looks like this: So I am left asking why the flow does not update the Customer. Any ideas what I am missing here please? Thank you!
Guest Paul Alexander Posted March 4, 2022 Posted March 4, 2022 Hi @Berto2002 I'm not sure if this is helpful, but when we look for user info from a PCF, this is the process we use: So I'm wondering if rather than you looking at custom_b from the 'get request information node' at the very beginning, you need to be looking at the raw value of the PCF field instead?
Berto2002 Posted March 4, 2022 Author Posted March 4, 2022 Hi Paul. It doesn't feel like the issue is extracting the email address because the field value we extract through our route is the type of value required. And that route was put in by our hornbill Implementation team a year ago. My Update Customer node is returning this error: "customer not subscribed" so I guess my question is what does that mean? The value can be, in our case, an email address: And is is that in database direct:
Guest Paul Alexander Posted March 4, 2022 Posted March 4, 2022 Ok - my first thought here is: is the NEW customer a subscriber to the service that you're logging the request against? Assuming that all of the correct information is being extracted (which it looks like it is) I think this must be a Service subscription problem? So, in the Service page of the service which the request is logged against, does the 'new' customer show in the Subscribers list:
Berto2002 Posted March 4, 2022 Author Posted March 4, 2022 Oh man! That could be it. Let me check and test...
Berto2002 Posted March 4, 2022 Author Posted March 4, 2022 Paul, genius. Thank you. I should have twigged when I saw the word Subscriber. Have a good weekend.
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