-
Notifications
You must be signed in to change notification settings - Fork 26
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
Would be nice to be able to delete simulator log messages individually #543
Comments
It seems like the delete transaction feature should be only available to user-created test sessions or the admin user. This way, users with their private test session Id will have control over their own transactions but not the "default" or "cat" test sessions. |
There are couple of approaches to deleting a simulator transaction log:
On a related topic, does archiving simulator log messages mean the metadata is kept intact in the simulator but move Message items from the "Messages" list box to a new "Archived Messages" list box? |
I am removing this issue from Milestone 7.8.0 because there is insufficient information to complete this task. |
This is a "Nice to Have". When going through transaction logs, I sometimes want to delete individual records that I no longer need. I would be happy to click on a record and then click on a delete button. Bonus points for being able to select 5 records with check boxes and then delete with one click. If you went to that effort, you could also support download of those 5 records.
Specific use case is for the Document Source metadata tests that we are extending. A customer is going to submit 5 transactions to a simulator for evaluation. Of those 5, only 1 is correct. I want to delete the 4 incorrect ones and keep the good one.
Another wrinkle to consider is an Archive or Hide button that does not delete the record but moves it to a place where it is not shown to the user.
As I said, Nice to Have but not required. I know new development is going to the FHIR tools.
.
The text was updated successfully, but these errors were encountered: