The recommended practice is to set the Access time-out value for the child case to be greater than the parent case time-out value. This ensures that the child case does not become inaccessible due to a time-out while the parent case is still active, which could happen if it had the same or a shorter time-out value. References: Pega official documentation on locking strategies and time-out values.

In Pega's Enterprise Class Structure (ECS), standard functionalities that are shared across multiple applications within an organization, such as sending a confirmation email, should be placed at the Organization layer. This allows for reusability and standardization across various implementations within the organization. Reference: Pega best practices for class design and ECS.

To ensure that patients can read but not edit cases in the hospital's ER case management system, two steps need to be taken. First, configure an Access Role to Object rule with the open case action set to 1 (B), which grants read-only access. This ensures that patients can view their cases without the ability to make any modifications. Secondly, create an access group unique to patients (D). This access group would include the Access Role to Object rule configured in the previous step. By associating patients with this access group, it ensures that they are granted the appropriate level of access to their cases, fulfilling the security requirements specified by the stakeholders.References: Pega Community documentation on Access of Role to Object and access groups.

Branched rulesets are used when multiple teams need to work on the same application version simultaneously.
Each team can work in their own branch, allowing for concurrent development without affecting the main application until the branches are merged. References: Pega Platform Help - Branched Rulesets.