Skip to content

Conversation

@labkey-bpatel
Copy link
Contributor

@labkey-bpatel labkey-bpatel commented Oct 12, 2020

Copy link
Contributor

@labkey-jeckels labkey-jeckels left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall code is looking pretty good.

- Add matching postgres script for EHR_ComplianceDB-12.39-12.40.sql
- Add Treatment_Frequencies_Active.sql
- Other minor cleanup
Copy link
Contributor

@labkey-jeckels labkey-jeckels left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One Postgres syntax issue, otherwise all set

// The Animal group search is working fine now after this change.
if (groupName)
config.removeableFilters = [LABKEY.Filter.create('groupId/name', groupName, LABKEY.Filter.Types.EQUAL)];
//config.removeableFilters = [LABKEY.Filter.create('groupId/name', groupName, LABKEY.Filter.Types.EQUAL)];
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isnt userFilters the new name for removeableFilters? this change prevents the user from removing the group name filter, doesnt it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that is the intention given that user enters filter criteria in a form, which then results in a filtered grid in a different panel, having removable filters on this resultant grid would be confusing.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's clear that if there was a bug preventing the filter from being applied, that's a problem.

I can see the argument on there being a filter panel above, but by that same logic then shouldnt start/end date also be immutable? It is possible for the top filter fields and DR to get out of sync.

This is a small enough change that it's probably not a big deal, but in general I would tend toward preserving capabilities for the user. For example, what is they want to do another filter type? More than one group? Contains? etc.

-Remove broken query study.currentBloodAvailable.
-Add module property DCM_NHP_Resources_Container.
-Update automated tests.
…filter that will get applied during insert and update.
…ey is not managing the calculations & validations, it is now done by a third party tool.
Use existing & functional utility code to get ehr_lookups.labwork_services store.
Replace 'onprc-snomedtreatmentcombo' with 'ehr-snomedtreatmentcombo' (since the onprc one is not defined).
Some cleanup.
…tore is not loading when servicerequested is selected)
… and not been run successfully by the client.
Copy link
Contributor

@labkey-jeckels labkey-jeckels left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One question but looks good.

@Override
protected boolean skipStudyImportQueryValidation()
{
return true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still needed?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this for test length / performance reasons? Is at least one of the ONPRC EHR tests doing a query validation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was added temporarily for query validation to pass so i could fix actual test failures but had missed to removed it after. Now removed, and query failures are fixed as well.

@labkey-bpatel labkey-bpatel merged commit 4270a0d into release20.7-SNAPSHOT Oct 30, 2020
@labkey-bpatel labkey-bpatel deleted the 20.7_fb_merge_from_onprc19.1 branch October 30, 2020 17:38
labkey-tchad pushed a commit that referenced this pull request Feb 24, 2025
Change DATE_TIME_FORMAT in AttributeData and Event to use 0-23 for hours format
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants