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

Trouble with Data Access Group #82

Open
ebmalone opened this issue Sep 23, 2020 · 2 comments
Open

Trouble with Data Access Group #82

ebmalone opened this issue Sep 23, 2020 · 2 comments
Labels

Comments

@ebmalone
Copy link

Hi,

We are suddenly experiencing an error that I think* may be related to the Form Render Skip Logic but not 100% sure. It suddenly stopped working last week but seems to only be affecting users assigned to 1 (out of 3) data user groups on our project. I am not assigned to a DAG so my view looks fine/normal.

Here's a screenshot below of the Dashboard view. It starts at Record ID 264-69, where, based on a response in the "Patient Initial Screening Chart Review" form, the "Patient Approach" form should or should not appear. But, now, as you can see, all forms are showing up. If you think this may be a fix I can make to the Form Render Skip Logic set-up, I will greatly appreciate any suggestions!

image

@ChemiKyle
Copy link
Contributor

Hi @ebmalone,

What version of form render skip logic (FRSL) are you using? I altered behavior regarding DAGs in late 2019, this may be related to a bug that was introduced in 3.3.8 and corrected in 3.3.9. See issue #58 for more information.

If you're using a later version, could you please provide your project XML (metadata is fine if there is PHI in the records) and a screenshot of your FRSL configuration? GitHub won't allow you to attach .xml files in a comment, but you can work around this by putting it in a .zip file.

@ebmalone
Copy link
Author

Hi @ChemiKyle,

Thanks for your response! Yes, our University has version 3.3.11. I'm no longer actively working on that project but reached out to the team and the issue is still only affecting uses in one particular DAG, not all users and not users assigned to other DAGs. I'll work on getting the metadata and screenshots too if your able to look through those to see where the issue may be.

Thanks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants