I cannot speak to when the official guidance will be released - hopefully soon. What i can say is that the 3-day "app build" will not be a singular application built from scratch. If you think about it, 3 days is far too short to develop an single application that tests LSA-level proficiency among the topics covered in the 7.3.1 LSA course. As with the 7.1 LSA course there will be a written design component, Certain exam requirements only need to be designed as opposed to being 100% functional.
I was studying the LSA architect course and then I found so many things which were never a part of earlier versions.
For general, OOD concepts. I wanted to know if Liskov Subsitution and things of that sort are needed to be an LSA? I thought it would be completely technical and then we have more theory than practical knowledge as part of 7.3 LSA learning. Also, composite applications, I didn't understand it. I just wanted a clarification in terms of whether it is going to remain like the way it is. Are these things relevant to become an LSA?
OOP is absolutely essential to the creation of a long-lasting foundation for developing multiple types of applications. The course says that amongst the SOLID principles you mostly focus on the Open-Closed Priniple in Pega. The optimal way to maximize reuse is to organize rulesets as components. Components that involve extendable case types are configured as applications. Such applications would be flagged as a potential Built-On Application when running the New Application Wizard.
FYI - the course will very soon become non-beta. Substantial effort was invested to improve exercise step detail and clarity. Once you go through these exercises, building them out yourself, you will see the benefit of component oriented development. One regret is not having time to include an exercise involving the Template Pattern and DCR. An exercise of that type will be added in the future.
Thanks for clarifying. I have been working on Pega for sometime now, but have never heard about terms like Solid principles in Pega and also component applications. And to be honest, if more examples and exercises are provided with help, it would make things clear.
The Template Pattern is the same as when you see extension points in Pega, e.g., NewDefaults, OpenDefaults, PerformDefaults. The bulk of the logic is Final. In a few "safe" places within the logic's "algorithm", developer customization is allowed. To customize, the developer must override the extension point rule.
No update on when a DCR-incorporating Template Pattern exercise will be added to the course.
I was also curious when the sample application for 3 day app build will be released, it will give us a fair idea what to expect in CLSA 7.3 app build, as we already are aware that it won't be an app build from scratch, but with this sample application we will get a more precise idea what to expect here and hands on experience to handle it.
Actually in 7.1 CLSA course, one sample application was used during the entire course for exercises. Another was available at the last for App build practice in pretty much the same format as one will expect during CLSA part2 i.e with requirement doc and design questions etc.
I was wondering if we have something similar for CLSA 7.3 course as well, but from what you mentioned I guess we have a sample application for exercises but not the another one for app build practice.
No. The 7.3 course is shorter than it was in 7.1 as is the duration of the "Architect" exam (a.k.a., "Part 2").
In 7.1 the built-in sample application (HR Services) was a continuation of the same application that was used for 7.1 CSA and CSSA courses.
A decision was made for the 7.3 course to break from this convention and use a Practice Build-like, Part 2 exam-like scenario as the course's sample application. '
Note how a lesson named "Introducing the Business Scenario" appears at the beginning of the 7.3 course. There was no such lesson at the beginning of the 7.1 course.
Having additional 7.3 applications to learn from, as opposed to exercises, is an excellent idea but this would need to be done outside the course, perhaps as a group effort within this LSA Community forum?