Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support generating an empty report during steps #14349

Open
2 tasks
mkalish opened this issue May 9, 2024 · 3 comments
Open
2 tasks

Support generating an empty report during steps #14349

mkalish opened this issue May 9, 2024 · 3 comments
Labels
platform Platform Team tech-debt Anything that is purely a technical issue and does not affect functionality

Comments

@mkalish
Copy link
Collaborator

mkalish commented May 9, 2024

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 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
@mkalish mkalish added platform Platform Team tech-debt Anything that is purely a technical issue and does not affect functionality labels May 9, 2024
@arnejduranovic arnejduranovic added the ready-for-grooming Ticket is a point where we can productively discuss it label May 13, 2024
@Andrey-Glazkv
Copy link
Collaborator

@Andrey-Glazkv
Copy link
Collaborator

Please add your planning poker estimate with Zenhub @JFisk42

@Andrey-Glazkv
Copy link
Collaborator

Please add your planning poker estimate with Zenhub @david-navapbc

@Andrey-Glazkv Andrey-Glazkv removed the ready-for-grooming Ticket is a point where we can productively discuss it label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform Platform Team tech-debt Anything that is purely a technical issue and does not affect functionality
Projects
Development

No branches or pull requests

3 participants