I am a new Pega developer, and I've completed several of the training modules in PegaAcademy. However, I am unable to find any real documentation for the actual Pega syntax. So, despite having a bit of training, I am struggling to write my own rules without help.
Are there any good documentation resources for learning syntax?
As a start, I would suggest the internal help in a PRPC installation, the Mesh, and PDN as sources of documentation. A good way to learn is to look at the existing rules in your PRPC installation as they are working examples.
From a typical use and generation standpoint, I suggest initially avoiding syntax completely. As a first exploration, navigate to the application explorer from the developer portal and try running the NewWork flow from class PegaSample-CustomerRequest. Supply only some summary text on the first screen and click the "create" button. One you see a work ID, you've successfully created a work object and an assignment, which involved using many of the out-of-box rules.
If you want to see what rules are used during that exercise, start the Pega tracer before clicking the "create" button, and then by clicking on the ruleset shown in the right-hand column of the tracer output, you will see the ruleform for the chosen rule appear in a tab on your developer portal.
Most rules are stored as standard db records, with many of the fields mapped to exposed db columns.
You can also peek at an xml representation of the rule by choosing the "rule data" option on the ruleform.
When you are ready to try modifying a rule, you'll first need your own operator record, access group, rule-application record and ruleset. Hopefully your Pega Academy training modules show how to create those.
Once you are logged in as your own operator, you may want to choose one of the section rules that the NewWork flow referred to, as revealed either by the tracer or the UI inspector, and use "save-as" to copy it into your own ruleset. Start by changing some visible text and run NewWork once more to demonstrate that your modified text appears.
Thank you! Your solutions have been most helpful. John, that's exactly what I meant. Eric, that is incredibly useful advice, and Matthew, peeking at the code my peers have already written has been a great resource.