@@xwhyz9757 yes you need to add a hardstop using a when condition if thats happening you can figure it our from the tracer

Thanks Raj

Yes Ravi

Sure, Working On It Will Upload by This Week

@@pegaforlife3154 Thank you

@@Vijay_Tummapala kzbin.info/www/bejne/gqOwZH2vaaqqlas

You are Right Lets Say we have a Frontend Application in React and backend Flow is Using Pega Workflow , Dx Api will Provide The Meta data of the UI and the Case Details Along With The Action to The React Developer who will encorporate the forntend with data from DX API From Pega.

Thank you For Your Valuable Feeback i will Take that into Account for Sure 🙂

In Pega, sub-reports allow you to include results from any report definition (including a report definition defined on a different Applies To class) in another report definition. However, it seems like you’re having trouble including everything from a sub-report into the main report without specifying a join condition. Here are some things you might want to consider: Sub-report Configuration: Each sub-report should be configured properly before you can refer them to your main report. This includes setting up the sub-report result count, column inclusion, join condition, column alias, and parameters. Join Condition: While it might seem counter-intuitive, a join condition is often necessary to establish a relationship between the main report and the sub-report. This is similar to how a sub-query works in SQL, where the sub-query is used to return data that will be used in the main query as a condition to further restrict the data to be retrieved. Alternative Approach: If there’s no common column to join on, one workaround could be to create a calculated field that extracts the common values from the columns you want to establish a match on, and then use those calculated fields to join together. Remember, the configuration of your sub-report and the relationship between your main report and sub-report can greatly affect the results of your report. If you’re still having trouble, I would recommend checking the Pega community forums or reaching out to Pega Support for more specific guidance. Hope this helps! 😊

@@pegaforlife3154 Actually Sub-Reports do not quite work as generic subqueries. In other words Select * From (Select * from SubReport) is not possible in Pega. Pega often makes "Reuse" a 4 letter word like "Pega" itself. Totally not worth the time. Copy Paste Modify works.

Please Keep Supporting

Have To check but i think co pilot is powered by Open APi which is paid now earlier it was free

Try free api of open ai from rapidapi

Yes i dint Add It as Mostly Everyone configure their email accounts

Yes

kzbin.info/www/bejne/fZ7Je2OHpbuVfNU

Please Check the Description where Steps are there with a Video Link on the Implementation

@@pegaforlife3154 thank you

Thank You For Your Comments pyWorkCover.pxCoverInsKey in clipboard pyWorkPage.pyBreadcrumbs(2).pyCaseBreadCrumbID Declare_pzRecentsCache.pyRecentListItems(3).pyRecordID pyWorkPage.pyBreadcrumbs(2).pyID

Thank You For Your Valuable Comment, Will Take Care of the it.

kzbin.info/www/bejne/gXWUfGWJoa9jh6M

i am Creating a Document For The Same Will Upload soon

wandermindset.com/creating-and-using-pega-component-from-scratch/ Go Ahead Best Of Luck👍🏻👍🏻👍🏻👍🏻 If Still You are having Some Issues let me know in Linkedin Bro Happy to Help

please Mute it and watch will add some binaural beats next time

updated in the Blogpost in description please have a look Thanks for Commenting🙂

what is not working ?

@@pegaforlife3154 while applying save data page to life cycle, it's asking for primary key. And in activity also page copy method got error 😕

@@Puzzle__Planet Debug and See and recheck the video you should get it

@@pegaforlife3154 actually I am fresher , that's why these many questions 😅

@@Puzzle__Planet No Prob 80% debugging 20% development always ☺

Thanks For Commenting Sir , i have some upcoming plans in which i would start recording with Voice If you have any doubt in understanding or need any more info you can very well reach out to me. 🙂

yes ☺, no nonsense direct action to the point.

@@pegaforlife3154 exactly 😁.

Yes , you can further verify from the blog Link in description

Yes , best would be to find some use case and fit the Ai to that use case 🙂

Help me to solve this error

@@nikhilgubbala104 the error has your answer

@@nikhilgubbala104 This Link will help you kzbin.info-m6ACi5sr_I

I already contacted you in Linkedin right. If you are new to pega pls learn circumstancing topic, then you will come to know about this scenario. but i will Keep your Request do check the description by Eod

wandermindset.com/scenario-based-single-variant-circumstancing-in-pega/

Create an Activity Step 1 : Page-New for tempage STep 2: For Each EMBD loop for the pagelist Step2.1 : Property -set (All the Properties in Pagelist Map to Temp Page) Step2.2 : obj-Save (Tempage) Add this activity in Submit Buttton

@@pegaforlife3154 let me try it 😁

For this you need to have a custom logic for case id generation you can put the logic in pydefault dt where case id logic is present

If we reset it to 1, will it not create any issue with old case which has already created with same 1? Will the data in old case be replaced with new data

@@javvajisatish hi Satish the question is not about how i am goin to mantain the old cases which i am sure there has to be an appeoach to handle it, the question is what config i will do to reset to 1 this is just one way there might be many solutions .What if the start case counter starts with 10001 or 101 or 1001 thats upto the business(APBR) i am just showing if you have to reset, this way you can reset

ASBR - As per Business Requirement

Yes

Subreport is again a separate query and that results are given to the main query for further condition applied to the main query. Subreport is used when there is no direct relation or in some complex requirements. Whereas Join condition is used when we have the direct relationship with the table.

Sure Will Take it Up Next

Thank you for reaching out