Absolute Clean Explanation thank you for your video please do more of this kind .we don't have any knowledge on how real time work works . Subscribed for your clean explanation 😊 Hope your channel grows to 1 lakh one day .
Thanks Subhash. Keep watching and sharing with your friends. Although I would focus on a topic for the video but while explaining I would explain a lot of other concepts while covering these videos. Please watch them thoroughly so you wont miss anything.
Great effort Sir...pls post a video on some complete application developed in Pega..just to see how it looks in real time..i never seen a complete website or web application developed in Pega
This is good explanation and very helpful to freshers who are going to work on pega development already built-on applications. Can u make more videos of like this development based real time experience it's would be very helpful to everyone
Hey thanks a lot for the appreciation. Not sure I am justifying that title. Bit trying my best to get the best content with easy explanation so you would understand
Can you pls make a video on this. Class also is a container of rules.. Rules set also container of rules.. How both are linked.? Can't find answer for it..
Rules are associated with classes, and stored in a ruleset. When you create an application, it will create a class and the application ruleset will store all the rules you create for the class
Hi bro, its really helpful, when i do private edit ,make the change,then test its working but once i check in and test it is not working but if i check out then its working Very strange, could you help
Hai bro, a small doubt. Why did we create branch seperately and merged it to new ruleset version 01.01.02. Can't we create this same process by save as from the previous 01.01.01 to 01.01.02 without creating branch?
Hey there, Yes, you can do that. But there are many reasons why you shouldn't do that. First let's say you have 4 developers are working in different user stories. and the same rule needs to be edited by 2 person for their respective changes, by keeping them in branch gives you a privilege for each developers to checkout and change to the same rule in respective branches. Else if it's in the same ruleset, until you checkin- the other person can't do the changes to the same ruleset Second, when you write a code it must be reviewed before we merge into a ruleset version as we take the ruleset version to higher environment and we consider that a properly reviewed code. and in Branch your lead can review the compliance score and guardrail score so you can correct everything before merging. Lastly - let's say you have worked on something which is no more required and another person worked on the same rule which we need to deploy to higher environment, then keeping them branch is so easy that we just need to delete the branch. But if you have already put that in ruleset version it's very hard to delete the changes that you have done as it's not more needed. if you delete something wrongly it would break others functionality. Hope this clarifies your query.
The BEST and Awesome Video available on youtube for a beginner
Nicely explained.Very useful for people not having real time experience on Pega
Thanks Durga
Nice very clean explanation sir. Need a series of complete case life cycle with a example which covers all the rules involved in it.
Sure I will plan them accordingly
thank you so much ,the way u are explaining was so simple and straight forward, it clarify my doubts regarding check-in and checkout .
Thanks Santosh for your lovely feedback
Absolute Clean Explanation thank you for your video please do more of this kind .we don't have any knowledge on how real time work works . Subscribed for your clean explanation 😊 Hope your channel grows to 1 lakh one day .
Thanks for all the lovely word
Good explanation. Learned a new thing from this video. Good one. Thank You
Thanks 😊
very informative video sir please post as many as possible pega videos for beginners.
Thanks Subhash. Keep watching and sharing with your friends. Although I would focus on a topic for the video but while explaining I would explain a lot of other concepts while covering these videos. Please watch them thoroughly so you wont miss anything.
Valuable demo and simple explanation , thanks!
Thanks 😊
very nice explanation and keep go on...Thanks
Nice video..Very nicely expalined for fresher like me..Keep doing more video.
Thanks Bikranta
Awesome🤩 . Many Thanks for your Very clear explanation.💯❤. Keep Rocking✌ . I am waiting for more videos from you
Thanks 😊
Thank you so much for sharing this context sir
You welcome 🤗.
Unique content!!!! Thanks for making it.
Thanks Akhil
Great effort Sir...pls post a video on some complete application developed in Pega..just to see how it looks in real time..i never seen a complete website or web application developed in Pega
Thanks King. I would try my best to show one. Keep watching and stay tuned 😊
Nice explanation. Was able to understand it
Glad to hear that
This is good explanation and very helpful to freshers who are going to work on pega development already built-on applications. Can u make more videos of like this development based real time experience it's would be very helpful to everyone
Thanks Revanth for your lovely feedback !!
thank you for sharing the videos which will really help us .
Thanks Sudarshan 🙏🙏
Very useful. Thank You
Yeah this is going to be one important lesson for people who don’t have real time experience
@@pegahut Please make video on Decision tree and decision table with use cases. Will surely help many.
pls make a video on how to think in terms of pega fetaures during pega implementation
Sure thats a good plan. Let me make the content
plz make more videos on integration and advanced topics
Hey Santosh. Please follow my playlist and other videos. You have one entirely series for integration. Let me know how u go
Thank you so much🙏
You welcome satya :)
thanks pega god
Hey thanks a lot for the appreciation. Not sure I am justifying that title. Bit trying my best to get the best content with easy explanation so you would understand
Can you pls make a video on this.
Class also is a container of rules..
Rules set also container of rules.. How both are linked.? Can't find answer for it..
Rules are associated with classes, and stored in a ruleset. When you create an application, it will create a class and the application ruleset will store all the rules you create for the class
Hi bro, its really helpful, when i do private edit ,make the change,then test its working but once i check in and test it is not working but if i check out then its working Very strange, could you help
Hai bro, a small doubt. Why did we create branch seperately and merged it to new ruleset version 01.01.02. Can't we create this same process by save as from the previous 01.01.01 to 01.01.02 without creating branch?
Hey there,
Yes, you can do that. But there are many reasons why you shouldn't do that.
First let's say you have 4 developers are working in different user stories. and the same rule needs to be edited by 2 person for their respective changes, by keeping them in branch gives you a privilege for each developers to checkout and change to the same rule in respective branches. Else if it's in the same ruleset, until you checkin- the other person can't do the changes to the same ruleset
Second, when you write a code it must be reviewed before we merge into a ruleset version as we take the ruleset version to higher environment and we consider that a properly reviewed code. and in Branch your lead can review the compliance score and guardrail score so you can correct everything before merging.
Lastly - let's say you have worked on something which is no more required and another person worked on the same rule which we need to deploy to higher environment, then keeping them branch is so easy that we just need to delete the branch. But if you have already put that in ruleset version it's very hard to delete the changes that you have done as it's not more needed. if you delete something wrongly it would break others functionality.
Hope this clarifies your query.
@@pegahut Thank you so much for the detailed explanation brother and now I am completely cleared about it..