Posted: 4 Jan 2017 8:47 EST Last activity: 9 Jan 2017 13:47 EST
In Screen Flow- if SLAs,Routing to different operators needs to be done,How it can be achieved?
In a ScreenFlow-If SLAs,Routing to different operators needs to be done in ScreenFlow,How it can be achieved? Business wants the UI look of Screen flow but has functionalities of routing to different operators,SLAs etc..
I am using Version 7.2 .How can we have a normal flow that has a look and feel of screenflow but has the functionality of flows like routing to different operators etc..? Is there any such configuration in Flow? Please let me if there is any such configuration possible
I think it is not possible to achieve this requirement without custom UI Screens..I wish if Pega can introduce a special flow type in its higher version which has UI look of a screenflow but has normal flow processing features.
What specifically do you want from a screen flow? Bread crumbs? The idea is that a screen flow is done by a single user so things like navigating around through the data makes sense. If you have different users for different points in the flow, things get a lot more complicated. Do you want to drop the user on the confirm harness if they click to a point in the flow that is an assignment for a different user and then route? Should the system fire off integrators with third pary systems again? I think it might be easier for us all to offer advice if you could be specific about what screen flow functionality your business folks want and what is the business need they are trying to meet with it. Likely, you will need to create some custom records to make that happen, but if you focus on what specific elements you need, you might be able to minimize the customization.