17. Creating A Service REST in PEGA from Scratch || POST method

Поділитися
Вставка
  • Опубліковано 9 січ 2025

КОМЕНТАРІ • 24

  • @sudheerreddy5761
    @sudheerreddy5761 2 роки тому +2

    U r doing good stuff buddy, appreciate ur efforts,
    Keep rocking🎸🎶🎶

  • @TheRouteShow
    @TheRouteShow 2 роки тому +1

    please create more small easy projects for teaching us the concepts

  • @sigfigronath
    @sigfigronath 2 роки тому +1

    Hey is it possible to do connectors as well

  • @vivekkale3969
    @vivekkale3969 2 роки тому +1

    Please show service call using postman and error handling steps

  • @sajid2861
    @sajid2861 10 місяців тому

    Hi, can this Rest service create a case while a user with access group of Users (not Authors).

  • @kommarajesh6540
    @kommarajesh6540 2 роки тому

    @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?

    • @NikitaKanoria
      @NikitaKanoria  2 роки тому +1

      Hi Rajesh, well the class does not matter. You can have either but best practice for Service rest is using work class.

    • @kommarajesh6540
      @kommarajesh6540 2 роки тому

      @@NikitaKanoria
      Thank you👍🙂

    • @danielsanchez512
      @danielsanchez512 4 місяці тому

      @@NikitaKanoria that is not true actually

  • @y.c.breddy3153
    @y.c.breddy3153 5 місяців тому

    How can we do api automation testing with PEGA application

  • @mageswaranjanarthanan391
    @mageswaranjanarthanan391 2 роки тому

    Hi, how can use to app recovered data from the rest.

  • @jacksully9904
    @jacksully9904 5 місяців тому

    Superb

  • @govardhanab7223
    @govardhanab7223 2 роки тому

    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

    • @NikitaKanoria
      @NikitaKanoria  2 роки тому

      Hi Govardhan, yes for integration rules we generally use int and data classes

  • @balajik3176
    @balajik3176 2 роки тому +1

    Hi Mam... You are really great 👍.. Do you take pega online classes? If yes I'm interested to join

    • @NikitaKanoria
      @NikitaKanoria  2 роки тому

      Hi Balaji, no I am taking any online class as of now. Only youtube videos.

  • @sanjus4364
    @sanjus4364 8 місяців тому

    If we need to post 50 properties. Do we need to write each and every property in activity?

    • @NikitaKanoria
      @NikitaKanoria  Місяць тому

      You can create a data transform for that

  • @anjankumar888
    @anjankumar888 2 роки тому

    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 .?

    • @NikitaKanoria
      @NikitaKanoria  2 роки тому

      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"
      }

  • @nara9912
    @nara9912 2 роки тому

    Hi can u teach pega plz

  • @danielsanchez512
    @danielsanchez512 4 місяці тому

    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.