Very clear explanation. Please continue posting videos
@pegahut2 жыл бұрын
Thanks Arjun
@krishnamahato4685 Жыл бұрын
Just completed the series, most efficient video on you tube to understand Connect-REST. Thanks a lot
@pegahut Жыл бұрын
Thanks Krishna
@rohanzutshi98772 жыл бұрын
So much Nice Explanation bro. This gives the clear understanding of the basic concepts of Postman tool using PEGA.
@pegahut2 жыл бұрын
Thanks Rihan :)
@DannyLearnsPega Жыл бұрын
Great explanation. Thanks!
@navyaupsc9550 Жыл бұрын
Super explanation sir ❤
@apavansyam32842 жыл бұрын
Excellent explanation, Can you please go with the concept of SOAP integration also, thanks for Your sharing
@pegahut2 жыл бұрын
Thanks 😊. Sure
@mavurisarika5953 Жыл бұрын
Thank you for the easiest explanation. Have gone through many sources for integrations but this video stands among best. Could you please include various ways of Exception handling in this series(by possible practical demonstration)? Also please demonstrate on fallback activity implementation, which I remember you mentioned you will cover at the end of this series in practical.
@pegahut Жыл бұрын
Thanks for the feedback. The reason i didn’t cover the Exception handling as its purely depending in the project. Depending on where are you using, are you using in the screen or using the api call, based on that it will be handled. There are lots of things. Probably i will try and cover them in a single video
@mavurisarika5953 Жыл бұрын
@@pegahutThank you. It surely helps us all.
@bamartya Жыл бұрын
Nice explanation. Really liked it. Thanks for devoting so much time to create this video series. I've one question, if the PK consists of two keys, say car insurance table having PK of Car VIN and Driver License number. Where each car and driver combination have to be separately insured (may not be good example but hope I can explain the technical requirement I'm trying to). Means, the car insurance table will have one row for each valid Car VIN and Driver License combination and the two columns Car VIN and Driver License together forms the PK. In this case if we want to have a GET / PUT request to search/ update the details, how will the URI part look like. You discussed about the disadvantages of sub-APIs in your previous video, so as per that .../Car/{carID}/Driver/{DriverLicense} is not a great design. Shall we go for query params? Please suggest the best approach for both GET and PUT. POST is simple as everything will go inside the body as a JSON request.
@mopuru.sarathchandrareddy62642 жыл бұрын
Looks good bro.That would be much appreciated if you can share info about param.request using deserialisation . Because that topic looks new and mostly no one will be aware of that from beginers. Hope you got what i mean bro.once again thanks for all your efforts.
@pegahut2 жыл бұрын
Sure, will release that soon
@mopuru.sarathchandrareddy62642 жыл бұрын
@@pegahut thnqs bro..
@pegahut2 жыл бұрын
@@mopuru.sarathchandrareddy6264 hey, the video you requested is live now. Stay until end, i have used para.request and deserialised
@sushants149 Жыл бұрын
Can u plz make dedicated video on job scheduler and queue processor
@pegahut Жыл бұрын
Just published one on job scheduler
@sushants149 Жыл бұрын
@@pegahut thanks
@jhojournal2 жыл бұрын
Hi bro! Your videos are very informative bro! And can you upload video on enabling security auditing and customizing the memo for an audited rule? Thanks in advance
@pegahut2 жыл бұрын
Sure Jho thanks for the feedback. Customising audit rules is definitely in my list
@jhojournal2 жыл бұрын
@@pegahut thanks a lot
@nikhiljanasenani2 жыл бұрын
Does your activity work for adding multiple users in the data type?
@pegahut2 жыл бұрын
Hey it won’t because we have created the interface to inly accept one for video purposes. However you can change it to multiple and you can loop that pagelist and add one by one