Hi all,

We are working with Customer Service 8.6 and all 360 view tabs content are sourced from an external database through multiples Rest API.

All modifications on Pega side, directly or through Service cases, are pushed to external database by calling some Rest Service through Queue Processors (that handle retries if any fail occur).

The requirement is once the update is pushed properly to external DB and only then, i need to refresh the user section where this information is displayed.

I only see 2 approach :

1. Work with Refresh condition on Section
   1. Need to add a refresh condition on each Data Page sourced section
   2. Need to modify each treatment in Queue processor to force the refresh of each Data Page needed
2. Work with Notifications
   1. Need to modify each section to add notification through Action -> On load 
   2. Need to modify each treatment in Queue processor to do a publish to a channel (1 channel per section to update)

Is there any other approach ?

In both case, the difficulty will be to force the refresh of Data Page/screens.

Which approach do you think is the most appropriate, and less costly in terms of implementation/performance ?

If 2 users open simultanously the same 360 view, and only 1 do the change, will both see the changes once Rest Api submitted ?

Thank you.

Regards,

Shezad