The class naming conventions are incorrect, service-related classes should be grouped under a single dedicated class(in pega int classes), and having request and response properties within a business logic (work class) is a poor practice that violates separation of concerns.
Hi Nikita, Thank you for providing very useful information. I have a humble request for more detailed explanations about pages & classes, and parameters.
If there is a column added in the db table associated with the work class and that change needs to be added in the product file but the instances of the work class should not be included. What to do for that?
when I try to create a new product rule I get an error message "Quick CreateERROR: Save failed.pyRuleSet: Your Operator ID does not allow Rule Check Out making it impossible to save a record belonging to a RuleSet that requires Check Out." - but my Operator ID has "allow rule checkout" enabled. Is there something else I need to do before creating the product rule?
But what's wrong in that? Companies also don't drop in message or call when rejecting the candidate.They just stop contacting them.Also do they think before when they lay off..