Question

3
Replies
261
Views
 Praveen Kumar Gyarampalli (PraveenG15)
Virtusa Corporation

Virtusa Corporation
US
PraveenG15 Member since 2014 7 posts
Virtusa Corporation
Posted: May 5, 2017
Last activity: May 5, 2017
Posted: 5 May 2017 1:16 EDT
Last activity: 5 May 2017 17:11 EDT
Closed

Using Ticket behavior

Hi,

When i used a Ticket set on assignment in flow, the control is jumping to ticket shape assignment when ticket is set, but after i submit that flow action the control is going back to previous assignment instead of going further from assignment where ticket is set.

Has anyone faced this similar behavior ? Please share your thoughts.

Thanks,

***Moderator Edit: Vidyaranjan | Updated Categories***

Praveen.

Case Management User Experience
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 4 years ago
Posted: 5 May 2017 2:34 EDT
Santanu Bhattacherjee (Santanu)
PEGA
Senior Manager - Sales Automation
Pegasystems Inc.
IN

Hello


Can you please provide a screenshot of your flow ?


Technically this should not happen. But if I can take a look at your flow , I can comment further.
Posted: 4 years ago
Posted: 5 May 2017 2:35 EDT
Pankaj Rawal (rawap)
PEGA
Sr Architect, Case Management
Pegasystems Inc.
IN

Could you share your configuration screenshot on where ticket is configured and how it is raised?
Posted: 4 years ago
Posted: 5 May 2017 17:08 EDT
Praveen Kumar Gyarampalli (PraveenG15)
Virtusa Corporation

Virtusa Corporation
US

Hi,


Please see attached screenshot of flow.


Work object assignment is currently at left side assignment "Verified by CAU Message" since the ticket is set in backend control jumped to right side ticket assignment "Restart of service".


Once i submit the flow action "Action restart of service", flow control went back to previous assignment where work object was and processed "CRM Notification" flow action and change stage happened, which is not expected behavior.


Thanks,


Praveen.