Awalker Posted January 27, 2017 Share Posted January 27, 2017 Hello, it has been noted that when a new request is raised and it is not selected using the drop down next to the 'Raise New' button it does not follow the same progressive capture / process, how do i fix this; the icon in question is noted below in an image, basically i need to know where the setting is, that if someone uses raise new button instead of using the drop down next to the button to select a type, that is picks up the correct captures. Hope that makes sense Link to comment Share on other sites More sharing options...
Victor Posted January 27, 2017 Share Posted January 27, 2017 @Awalker "Raise New" has it's own progressive capture configuration via this application setting: Link to comment Share on other sites More sharing options...
Awalker Posted January 27, 2017 Author Share Posted January 27, 2017 hi @Victor, Is their not a way though, after they have input the information and then selected the change type it then picks up the progressive capture and process for that type, otherwise this seems counter productive. Link to comment Share on other sites More sharing options...
Victor Posted January 27, 2017 Share Posted January 27, 2017 1 hour ago, Awalker said: selected the change type it then picks up the progressive capture and process for that type @Awalker you could have the "Raise New" progressive capture jump to another progressive capture after the request type has been selected... I mean jump to the progressive capture corresponding to the request type.... but this would need to be configured in the "Raise New" progressive capture, is not something automatic... 1 Link to comment Share on other sites More sharing options...
Guest Posted January 30, 2017 Share Posted January 30, 2017 Hi @Awalker Just to expand on @Victors point about the difficulty some users have with analysts clicking the "Raise New" button - it has previously been a challenge because it has meant that you have needed to cover multiple eventualities in a single Progressive Capture ("new request"), covering multiple request types. And this can get very large, very quickly. But exactly as Victor has mentioned, the "Switch Capture" node alleviates this - and a common method that a few customers have already employed is to ask the Request Type as the very first question (on the "new request" progressive capture) and switch immediately to their Request Type specific captures from that point onwards. For the benefit of anyone reading this thread who might want to implement this after previously experiencing this issue, here is an idea of how it can be set up: Kind Regards Bob Dickinson Link to comment Share on other sites More sharing options...
Awalker Posted February 13, 2017 Author Share Posted February 13, 2017 Hi @Bob Dickinson Forgive my simple mind, but i am following your above process, but i cannot seem to get it to work, as it states i have nodes set up incorrectly and cannot work out the issue. Link to comment Share on other sites More sharing options...
Victor Posted February 13, 2017 Share Posted February 13, 2017 @Awalker you have decision nodes configured to branch the capture based on custom expressions (Incident, Service Request, etc.). However none of these decisions actually have an expression configured. You would need to add these expressions for this to work. Link to comment Share on other sites More sharing options...
Awalker Posted February 13, 2017 Author Share Posted February 13, 2017 @Victor, Thank you very much I have updated these and all works well. Link to comment Share on other sites More sharing options...
Victor Posted February 13, 2017 Share Posted February 13, 2017 @Awalker no worries, happy is sorted Link to comment Share on other sites More sharing options...
chrisnutt Posted May 24, 2017 Share Posted May 24, 2017 On 2017-1-30 at 11:16 PM, Bob Dickinson said: Hi @Awalker Just to expand on @Victors point about the difficulty some users have with analysts clicking the "Raise New" button - it has previously been a challenge because it has meant that you have needed to cover multiple eventualities in a single Progressive Capture ("new request"), covering multiple request types. And this can get very large, very quickly. But exactly as Victor has mentioned, the "Switch Capture" node alleviates this - and a common method that a few customers have already employed is to ask the Request Type as the very first question (on the "new request" progressive capture) and switch immediately to their Request Type specific captures from that point onwards. For the benefit of anyone reading this thread who might want to implement this after previously experiencing this issue, here is an idea of how it can be set up Kind Regards Bob Dickinson 1 Hi All, I've just been having this problem and have come across this thread. I had considered this solution before searching the forum though but had dismissed it as surely it renders the benefit of having the "raise new" button completely redundant, doesn't it? You may as well dispose of the button and just have the drop down. I'm going to try the branching after the request type choice, but further down the line and see what happens. I'll post back with results Chris Link to comment Share on other sites More sharing options...
Victor Posted May 24, 2017 Share Posted May 24, 2017 @chrisnutt I agree you do have a point regarding the "Raise New" button when you have progressive captures for each request type.... however the fact remains that "Raise Request" from an email uses the "Raise New" functionality, so you still need to have a progressive capture for "raise new"... Link to comment Share on other sites More sharing options...
Steve Giller Posted May 24, 2017 Share Posted May 24, 2017 Our ProCap for the Raise New button is a simple Select Service node. That way you hit 'Raise New' then select a Service/Catalog Item, then follow the ProCap for that Item as normal with (as far as I can tell) as few extra clicks as possible. Link to comment Share on other sites More sharing options...
chrisnutt Posted May 26, 2017 Share Posted May 26, 2017 Thanks, both. I ended up doing what is shown in the attached and it works well. Chris 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