Apart from video subject line you explain each and every details thats what I like, being from Java developer background. Thanks!!! and keep it up please.
please explian report definition similar to that of activity in parts please. it would be very helpful. Thank you soo much for your time to explain the concepts so clearly.
Why we use Parameters- to make it reusable by different applications when required. In Pega we have a component design architecture. What it means, you create a component and that component will be reused in different applications. Lets consider an example- you created an activity Send Email and you are currently using in onboarding candidate applications to send email to candidates. You have created a “TO” property and map that in activity directly from work class. And stored candidate email address in TO property. In a later phase your organisation thought, they would use the same send email functionality for customer applications to send email to CUSTOMER address. So they dont waste writing the same functionality again. Instead they would take the send email functionality from onboarding applications team and reuse in their applications. But they don’t have that “TO” property . But they have a different property called customeremailadd. When they import, it will fail. Now think if you would have created a param.ToAddress. In onboarding application while calling send email, set your TO property and in customer application set Customeremailadd. So creating parameters helps making activity reusable and flexible. Hope its clear
The name itself indicates, Lets say, you have the below model - customer (page list) - address (pagelist) Address is inside customer, if you context is address, then embaded means all the pages inside address i.e address (1), address (2). Toplevel pages mean customer (1) and customer (2)
You explain things even better that the academy
thank you man!!
Thanks Noureddin
Loved your effort in teaching each tab,check box,....etc. Plz continue teaching me🧑🎓
Thank you, I will
Excellent explanation! you know where everyone struggles!
Thanks Anirban
As always, Awesome
Thanks Jagadish :)
Very informative video!!! Thank you😊
Thanks @Durga
Excellent explanation, now I am able understand activities thanks alot 👍
Thanks Allu for watching
Apart from video subject line you explain each and every details thats what I like, being from Java developer background. Thanks!!! and keep it up please.
Glad it was helpful! 😊
Good one for the beginners. Thanks brother
My pleasure
Thank you sir, now i got clear understanding on activity concept.upto now i have seen lot of videos but i am unable to understand.
I m so glad that u understood. Keep watching and keep learning 😊
Very good and detailed explanation.
Excellent exlanation!Detailed explanation
Glad it was helpful!
Thank you so much for such a detailed explanation, It helps me a lot.
You're very welcome! Keep watching
Lifesaver
Nice video and good explanation👏👏
Thanks a lot for your lovely feedback
please explian report definition similar to that of activity in parts please. it would be very helpful.
Thank you soo much for your time to explain the concepts so clearly.
Thanks already planned. Will be coming soon
Thank you man!! You explained well!!
Glad it helped! You welcome
Thank you so much sir ❤️
Thanks Chamarthy. Call me Sri :)
Sir , why we are providing parameters in activity,why we can't use the properties in our work class,and what is use of code pega list.
Why we use Parameters- to make it reusable by different applications when required. In Pega we have a component design architecture. What it means, you create a component and that component will be reused in different applications.
Lets consider an example- you created an activity Send Email and you are currently using in onboarding candidate applications to send email to candidates. You have created a “TO” property and map that in activity directly from work class. And stored candidate email address in TO property.
In a later phase your organisation thought, they would use the same send email functionality for customer applications to send email to CUSTOMER address. So they dont waste writing the same functionality again. Instead they would take the send email functionality from onboarding applications team and reuse in their applications. But they don’t have that “TO” property . But they have a different property called customeremailadd. When they import, it will fail.
Now think if you would have created a param.ToAddress. In onboarding application while calling send email, set your TO property and in customer application set Customeremailadd. So creating parameters helps making activity reusable and flexible. Hope its clear
@@pegahut yes sir,now it's clear to me.
Excellent explanation. Can u plz make video on Logs file
Thank you❤🌹🙏
No problem 😌
Could you please explain how to create headers and how to change the back ground color of headings
For any changes to header change in pycaseheaderouter. Background color and all , I would explain when I am going to explain the skin
only on pages and classes, pls make one explanation video.
Sure, 100%. I can understand how important this would be. Sure let me think of the content.
is this playlist is enough to learn about Activities ?
Yes Nayeem. And then slowly you will learn the methods. This playlist would help you learn to write an activity like a pro !!
bro u have missed to explains about primary pge can u pls explain.
Can you Explain the Report Definition, Joins, Reports etc, pls
Sure will make a video
Hi, what's the difference between top level page and embedded page ?
The name itself indicates,
Lets say, you have the below model
- customer (page list)
- address (pagelist)
Address is inside customer, if you context is address, then embaded means all the pages inside address i.e address (1), address (2). Toplevel pages mean customer (1) and customer (2)
can you please explain JMS Listener in pega