17. Know the developer actions in a rule form - Check out, check in and private edit
Вставка
- Опубліковано 13 вер 2024
- 👉 Pega Masterclass knowledge sharing- 57+ hours of video tutorials covering different pega topics (both beginner and advanced)
👉 Pega Constellation knowledge sharing - 12.5+ hours of video tutorials covering the topics around Pega UI evolution primarily focussed on Constellation
Course landing page - www.myknowacad...
For any questions, please drop an email 📧 to pegaknowledgesharing@gmail.com
#myknowpega
Detailed explanation on the three common developer action during pega development - Check out, check in and private edit. Detailed explanation my myknowpega author - Premkumar Ganesan
------------------------------ Connect with me --------------------------------------
LinkedIn - / premkumar-g-a5633a64
Facebook profile - www.facebook.c...
Facebook page - / myknowpega
Pega blog - myknowpega.com
---------------------------------------------------------------------------------------------------------
Developer actions
check out in pega
check in pega
private edit in pega
enable check out option in pega
check in approval in pega
check in comments in pega
check out to branch in Pega
Pega developer
pega development
Learn Pega
Pega videos
Pega senior system architect
Pega for beginnners
Pega step by step tutorial
myknowpega
-----------------------------------------------------------------------------------
#myknowpega #pega #techridewithpk
Now I am obsolutely cleared with this topic after watching this video a Big Thanks to you.
You are welcome Hemanth 😊
Thank you soo much Prem for your detailed explanation on each topic!! So so helpful are these!! 😊😊
Thanks Divya!
Now i got super clarity ...nice explanation pk
very nice explanation
Thanks and welcome
Thanks Prem for your efforts and KT :)
Thanks Dinesh 😊
How check in and check out concept work, when we are making changes using app studio?
Hi Suresh, with App studio Pega takes care of the check out, check in processes and will not be shown to users developing from app studio. Citizen developers may find it difficult to under this checkin check out and hence pega didn't expose these options in the low code app studio platform
Hi guys, please clarify the following:
If a UserA checks-out a rule then a rule copy is created for them. Another UserB does a private edit on the same rule. This private edit of a rule can be saved onto a branch or another ruleset you said, if so can these changes be merged after a user checks in and the rule is available? Or do we need to do a save-as for the same rule again and then check-out, do our edits and then check-in ?
In one operator they do changes their branch after he checkin. Then I run and execute, in the above branch rule is impact on my execution or it is take on the highest version of main rule.
hey Prem , what is release lock in Actions Menu?
Hi, usually when the lock timeout is reached the lock can go into soft lock mode. Using the actions menu, you can easily release those soft locks and then you can acquire lock
@@myknowpega okay. Thanks for the reply. Is it possible to have video on that ? 🙂 Sorry for asking.
@@thriver5664 yes sure.. I will cover it in locking mechanism video 😊
If a rule is checked out in latest version and some other user wants to unit test that rule, which rule will be picked by the other user,will the rule in latest version available to that other user?
Hi Deepika, Let's say rule is in rulesetA in latest version on 01-01-34. User A checked out the rule from 01-01-34, so there will be two versions on a rule. One the Unchecked out rule which is 01-01-34 and the other checked out version of rule in the user private copy. Now for other user, say User B, latest version 01-01-34 will always be available and it will be picked up during rule execution.