Janett Dervish Posted April 26, 2022 Share Posted April 26, 2022 Hi, I was hoping someone could help with a problem I'm experiencing in a BPM I have a 'Goto if' node in a process which depends on an amount entered in the pro-cap, if the amount is over 250 the process runs in one direction and if under in another direction. Upon testing regardless of what amount is entered the request always runs in the route for under 250. I have attached a copy of the Pro-cap setting also the setting in the Goto. Thank you Janettgo Link to comment Share on other sites More sharing options...
James Ainsworth Posted April 26, 2022 Share Posted April 26, 2022 Hi @Janett Dervish I'm interested in the NewCard vs RenewCard. Within Intelligent Capture I'm assuming that you have two questions or an option to select either a New Card or to Renew a card. The user will not be selecting both. So, if I select the option for a new card and enter a card limit of £1,000,000, this will be stored in the NewCard variable. The value in the RenewCard variable will be null which will be viewed as a value less than 1. The result would be that either one of these OR statements will always be true. Even though I entered 1,000,000 for the new card, the RenewCard will have a value less than 250 (null), so it will take this route. Link to comment Share on other sites More sharing options...
James Ainsworth Posted April 26, 2022 Share Posted April 26, 2022 From your screen grab of your configuration it looks like you are storing the card limit value in h_custom_27. In your BPM, rather than having two custom expressions testing the values submitted in Intelligent Capture, you could have one statement testing the value stored in h_custom_27. You may need a Get Request Information -> Request Details Hornbill Automation before your decision node that gets the values of the custom fields. Once you have that, you can compare the value. It should like It is always good practice to have a No Match branch, just in case something goes wrong. You could have two branches, the one described above and then the No Match which would include everything below 250 without having to specify < 250. Hope that makes sense. Link to comment Share on other sites More sharing options...
Janett Dervish Posted April 27, 2022 Author Share Posted April 27, 2022 Thank you James for your response, Yes, I have separate nodes for re-new a card and new card which use the same custom field 27. I will update my process following your advise. Thank you again Janett Link to comment Share on other sites More sharing options...
Janett Dervish Posted April 27, 2022 Author Share Posted April 27, 2022 Hi James, Just to let you know, I've updated my process as you suggested which has now resolved the issue. Thank you again Janett 1 Link to comment Share on other sites More sharing options...
James Ainsworth Posted April 27, 2022 Share Posted April 27, 2022 Great to hear that you have it working. 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