Salute💂......I don't have words for me to respect you. Thanks a lot. If we pay lakhs for some blogs or institute also we don't get this information. I don't know how to show my Respect and gratitude to you. Thanks a lot bro.
Thanks for everything what ever you are doing for us.. I want you to do video on 1. How to customize connection problem flow and add sent mail to DL about failure request. 2.How customise Error handling Template and enable in response data transform. 3.How to log errors in data page for failures of service or mandatory files and log success as well. 4.For Example the output connect REST is mapped to UI fields and those fields are mandatory but unfortunately Connect REST failed to provide response due service unavailability, but Case need to advance to next stage how to we handle those required fields. And case to next assignment. 5.How to re queue failed services to get response. 6.How to display failed or validation messages in UI for connect REST Please make a video on mentioned points.. It really helps a lot.. Thanks a lot ❤️🙏🙌
Is easy, if you got both int and data layer, then create the exact property name in both the layer, and set them in either request data transform or response data transform depending on where the field is added
Thanks for sharing knowledge, I have one question, based on the connect rest result I want to change background color of screen, let's take an example if connector success, back ground color should be in green, if connector fails color should be rest. How to configure this scenario
Create 2 section with applying different backgrounds color. Put a when conditions depending on pyhttpresponsestatus If pyhttpresponsestatus = 200 ( show green section else show red section
This is very useful. Thank you! I have a question regarding running the REST wizard twice, once for GET and again for POST, which results in two separate classes (Employee and Emp). I'm curious to know if this approach is a standard practice in Pega development when creating REST connectors. Or is it just the result of this being a tutorial? I would think it would be better to have a main class (maybe called EmployeeAPI) which would have all the classes for different methods. Once again, thanks for the informative tutorial!
The approach is standard practice, even in real time, and the reason behind this is often the URL for create and get is different. Now you can use one connector and can use both get and post but you won’t be able to set the URL by using DRS. Then you need to define this during run time. By creating the connect rest, using Wizzard, you won’t be able to achieve both routes in same class. Having said that many projects they create this Manually too exactly the way you said. By creating manually we actually re-use a lot of property Property in a better way. But that’s time-consuming so it’s really depending on the projects. The default practice is we create by running the Wizard to save time
I have a scnerio where mentod is Post, it is returning http response code as 200 But we don't have any return payload to confirm so wizard is not allowing me go ahaed.. Do we have fix for this.. Or we need to manually crate in this scnerio
Hey Have you run that API in the wizard? You sure you don’t have a status: success in the response too? Have you tried clicking on run and then submit? Is it OK for you to share the postman screenshot for me to see how it looks. If yes, share me in pegahut.au@gmail.com. If you cant share, then I will give you a work around
@@pegahut i Am Also Facing Similar Kind of Issue. Getting 202 Response But Not Having Return Payload So I am Unable to Move Forward With Wizard. Is there Any Soluton ?
Wonderful Sir, very excellent explanation.
Super.
Knowledge Hut For Us.
Thanks Patil
Very good video to learn about Rest API, Thankyou for creating these videos..
U welcome
Salute💂......I don't have words for me to respect you. Thanks a lot. If we pay lakhs for some blogs or institute also we don't get this information. I don't know how to show my Respect and gratitude to you. Thanks a lot bro.
Thanks for the lovely feedback. Just spread the word and make sure it reaches to the maximum soo like you other can learn too 😊
Thnqs bro for sharing indetailed explanation about different layers and its usage.
Thanks 😊
nice sir, I saw all the vedios for integration. It's good and helped me for my projects..Thank you
So happy that you understood and could implement
Thank you so much. Great explanation.
really awesome explanation.. loved it
Thanks a lot 😊
Excellent Sir, Thank you so much for the detailed Video with clear explanations.
Thanks Sri for detailed explanation about integration concept!!!
You welcome Durga !! Thanks for taking time and proving feedback
Just wow 👌
Thanks 😊
Thanks for everything what ever you are doing for us..
I want you to do video on
1. How to customize connection problem flow and add sent mail to DL about failure request.
2.How customise Error handling Template and enable in response data transform.
3.How to log errors in data page for failures of service or mandatory files and log success as well.
4.For Example the output connect REST is mapped to UI fields and those fields are mandatory but unfortunately Connect REST failed to provide response due service unavailability, but Case need to advance to next stage how to we handle those required fields. And case to next assignment.
5.How to re queue failed services to get response.
6.How to display failed or validation messages in UI for connect REST
Please make a video on mentioned points.. It really helps a lot.. Thanks a lot ❤️🙏🙌
I have answered you on the comments. Hope it clarified
just awesome.. no word to prise you sri .. thanks a lot for your effort
Thanks a ton for the feedback
you are a savior man....
Thanks 😊
Very good explanation bro thanks a lot , keep the good work going it will help for new pega aspirants like us . Once again thanks a lot .
U welcome Arvind. Thanks for taking time for your feedback
Super Bro , Really really nice explanation
Thank you so much 🙂
I cannot thank you enough. Words cannot express Sri❤️
😍😍 Thanks for taking your time to provide your feedback !!
😍😍 Thanks for taking your time to provide your feedback !!
Nice explanation. if upstream system adds one more property in request or response, how to handle this in pega
Is easy, if you got both int and data layer, then create the exact property name in both the layer, and set them in either request data transform or response data transform depending on where the field is added
Very Nice video sir, could you please do an video on how to verify the pega logs and pega log analyzer tool to verify the logs.
Sure Sreenivas. Will add that in backlog
Thanks for sharing knowledge, I have one question, based on the connect rest result I want to change background color of screen, let's take an example if connector success, back ground color should be in green, if connector fails color should be rest. How to configure this scenario
Create 2 section with applying different backgrounds color. Put a when conditions depending on pyhttpresponsestatus
If pyhttpresponsestatus = 200 ( show green section else show red section
You are really amazing brother 💕
Thank you so much 😀
This is very useful. Thank you!
I have a question regarding running the REST wizard twice, once for GET and again for POST, which results in two separate classes (Employee and Emp). I'm curious to know if this approach is a standard practice in Pega development when creating REST connectors. Or is it just the result of this being a tutorial?
I would think it would be better to have a main class (maybe called EmployeeAPI) which would have all the classes for different methods.
Once again, thanks for the informative tutorial!
The approach is standard practice, even in real time, and the reason behind this is often the URL for create and get is different. Now you can use one connector and can use both get and post but you won’t be able to set the URL by using DRS. Then you need to define this during run time. By creating the connect rest, using Wizzard, you won’t be able to achieve both routes in same class.
Having said that many projects they create this Manually too exactly the way you said. By creating manually we actually re-use a lot of property Property in a better way. But that’s time-consuming so it’s really depending on the projects. The default practice is we create by running the Wizard to save time
I have a scnerio where mentod is Post, it is returning http response code as 200 But we don't have any return payload to confirm so wizard is not allowing me go ahaed.. Do we have fix for this.. Or we need to manually crate in this scnerio
Hey Have you run that API in the wizard? You sure you don’t have a status: success in the response too? Have you tried clicking on run and then submit?
Is it OK for you to share the postman screenshot for me to see how it looks. If yes, share me in pegahut.au@gmail.com.
If you cant share, then I will give you a work around
@@pegahut sure I will share screenshot to mail
@@pegahut I sent details via mail, Thanks
@@pegahut i Am Also Facing Similar Kind of Issue. Getting 202 Response But Not Having Return Payload So I am Unable to Move Forward With Wizard. Is there Any Soluton ?