What is one way to specify properties to propagate from a parent to a subcase?

Specifying properties to propagate from a parent case to a subcase typically involves defining those properties directly within the case type definition. This method allows for a clear and controlled way to manage which properties are inherited by the subcase. When properties are defined in this manner, it becomes straightforward for developers to identify each property that needs to be passed down, ensuring that the subcase has access to the necessary information from the parent case.

In contrast, other methods such as triggers do not inherently relate to the propagation of properties and instead are focused on events or actions that occur within the application. Automatic propagation by the system lacks the granularity and specificity that a defined approach offers, which might lead to unintended properties being carried over that are not needed. Creating a workflow, while useful for defining the process and order of operations, does not directly address the mechanism for transferring property values. Each of these methods has its own purpose but does not provide the structured and explicit approach that defining properties directly offers for subcase property propagation.