@Nikita Kanoria.... Nice Explanation. i have a doubt. May i know why Resource is "Int" class in get method of service rest and "work" class in post method of Service rest?
Hi Nikita , great content and easy way of explanation , i have a doubt , do we need to use the int- or data- classes rather than work classes while creating or refereeing the rest or any other integration rules please help clarify
The class naming conventions are incorrect, service-related classes should be grouped under a single dedicated class(in pega int classes), and having request and response properties within a business logic (work class) is a poor practice that violates separation of concerns.
Hi Anjan. Body means payload which can be of any format. Mostly now a days json is mostly used. It is of the format: { "prop1": "value1", "prop2":"value2" }
![MISSING: SLIM SHADY [Expanded Mourner’s Edition Trailer]](http://i.ytimg.com/vi/xh8qgHrOO1g/mqdefault.jpg)
Superb
thank you so much
U r doing good stuff buddy, appreciate ur efforts,
Keep rocking🎸🎶🎶
thank you so much
please create more small easy projects for teaching us the concepts
Please show service call using postman and error handling steps
How can we do api automation testing with PEGA application
Hey is it possible to do connectors as well
Hi Mam... You are really great 👍.. Do you take pega online classes? If yes I'm interested to join
Hi Balaji, no I am taking any online class as of now. Only youtube videos.
If we need to post 50 properties. Do we need to write each and every property in activity?
@Nikita Kanoria.... Nice Explanation.
i have a doubt. May i know why Resource is "Int" class in get method of service rest and "work" class in post method of Service rest?
Hi Rajesh, well the class does not matter. You can have either but best practice for Service rest is using work class.
@@NikitaKanoria
Thank you👍🙂
@@NikitaKanoria that is not true actually
Hi, can this Rest service create a case while a user with access group of Users (not Authors).
Hi Nikita , great content and easy way of explanation , i have a doubt , do we need to use the int- or data- classes rather than work classes while creating or refereeing the rest or any other integration rules please help clarify
Hi Govardhan, yes for integration rules we generally use int and data classes
The class naming conventions are incorrect, service-related classes should be grouped under a single dedicated class(in pega int classes), and having request and response properties within a business logic (work class) is a poor practice that violates separation of concerns.
Hi, how can use to app recovered data from the rest.
We say for GET we don’t have Body and for POST method we have body , what does exactly body means .? and it’s purpose .?
Hi Anjan. Body means payload which can be of any format. Mostly now a days json is mostly used. It is of the format:
{
"prop1": "value1",
"prop2":"value2"
}
Hi can u teach pega plz