Question
Younicorp
NL
Last activity: 15 Feb 2023 2:33 EST
Data objects Knowledge check: Preference has No system of record, why?
Hello,
I was executing the knowledge check on the Data Objects topic and came across something I couldn't quite grasp.
In this exercise there's a few data objects that you have to assign to either Pega SOR, External SOR or no SOR. The exercise is explained like this:
You are building a new customer service application in Pega Platform, with a case type that allows customers to submit feedback on orders that they placed with a legacy product application. Customers can specify their preference for the application display, which affects how they enter feedback. The following data objects are necessary:
- Preference for the user preference for the application display in their browser
I left out the other three Data Objects, since my question is solely regarding the Preference Data Object. If I'm looking at the image a little higher up in that topic, there's several questions to determine whether and what SOR you would need.
The first question is "Do you need to save the data outside of the case?". The preference object doesn't have a connection with the specific case, since it's to determine user preferences.
I figured I needed to save these preferences in an SOR, so that the next time the user opened the application, the preferences could be preloaded again.
Why is the correct answer that the Preference object should have no SOR?
Kind Regards,
Hello,
I was executing the knowledge check on the Data Objects topic and came across something I couldn't quite grasp.
In this exercise there's a few data objects that you have to assign to either Pega SOR, External SOR or no SOR. The exercise is explained like this:
You are building a new customer service application in Pega Platform, with a case type that allows customers to submit feedback on orders that they placed with a legacy product application. Customers can specify their preference for the application display, which affects how they enter feedback. The following data objects are necessary:
- Preference for the user preference for the application display in their browser
I left out the other three Data Objects, since my question is solely regarding the Preference Data Object. If I'm looking at the image a little higher up in that topic, there's several questions to determine whether and what SOR you would need.
The first question is "Do you need to save the data outside of the case?". The preference object doesn't have a connection with the specific case, since it's to determine user preferences.
I figured I needed to save these preferences in an SOR, so that the next time the user opened the application, the preferences could be preloaded again.
Why is the correct answer that the Preference object should have no SOR?
Kind Regards,
Daniël Pollmann
Accepted Solution
Updated: 15 Feb 2023 2:18 EST
Pegasystems Inc.
US
@Risturbeat @Risturbeat Hi Daniël,
My read of the question is the preferences are selected for each feedback case, and the preferences determine how you submit feedback for that particular case.
In the question, there is this: (You) can specify (your) preference....which affects how (you) enter feedback.
Think about a time when you interacted with an application, and there was a step that asked, "Would you like to provide feedback about your experience with us today?"
If you select Yes, the next question might be, "How would you like to provide feedback?" and the options are Text, Email, Pigeon.
So, the answer to "Do you need to save the data outside of the case?" would be No = No system of record.
Does this help clarify why your preferences for submitting feedback do not need to be saved in a SOR?