You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an RS developer, I would like to be able to generate an empty report so that lineages work correctly
Description/Use Case
Currently, the code only support generating an empty report as part of sending something to receiver (i.e. they're on batch schedule and always want a report even if there are no items). However, the convert step also needs to be able to generate an empty report in situations, i.e. none of the items are valid. The empty report must be generated because otherwise the report lineage doesn't work and the action logs from the convert step are not visible
Risks/Impacts/Considerations
Dev Notes
ActionHistory.trackGeneratedEmptyReport already exists and overload likely can get created to support this.
Acceptance Criteria
The FHIR convert step generates an empty report in the situation where no items will get passed to the next step
The FHIR route step generates an empty report in the situation where no items will get passed to the next step
The text was updated successfully, but these errors were encountered:
User Story
As an RS developer, I would like to be able to generate an empty report so that lineages work correctly
Description/Use Case
Currently, the code only support generating an empty report as part of sending something to receiver (i.e. they're on batch schedule and always want a report even if there are no items). However, the convert step also needs to be able to generate an empty report in situations, i.e. none of the items are valid. The empty report must be generated because otherwise the report lineage doesn't work and the action logs from the convert step are not visible
Risks/Impacts/Considerations
Dev Notes
ActionHistory.trackGeneratedEmptyReport
already exists and overload likely can get created to support this.Acceptance Criteria
The text was updated successfully, but these errors were encountered: