What must match when a Call Behavior Action invokes another activity?

When a Call Behavior Action invokes another activity, it is crucial that the pins of the action and the activity parameter's behavior type match. This requirement ensures that the data being passed between the caller and the invoked activity is compatible.

When invoking an activity, it typically involves specifying inputs and outputs that align with the expected types of the parameters defined in the called activity. If the types do not match, it could lead to issues in data handling, resulting in runtime errors or incorrect behavior during the execution. Therefore, it ensures that the calling action communicates effectively with the invoked activity, maintaining the integrity of the data flow and the overall system functionality.

In this context, matching the behavior type is essential for the successful execution of the activity and for upholding the principles of type safety in modeling practices.