Skip to content

$apply-generated CommunicationRequest.payload restricted to a single entry #627

@oyisre

Description

@oyisre

In resolveCommunicationRequest for ActivityDefinition $apply, the resulting request's payload is restricted to a single entry which does not appear to be necessary

Is this intentional behaviour? A similar restriction is there for Task.input here. I'm happy to create a PR if appending the payloads and inputs instead is fine

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions