-
Notifications
You must be signed in to change notification settings - Fork 17
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
Improve/expand FRSL configuration #11
Comments
|
@tlstoffs yes, the explanation was confusing. Rephrasing: For the configuration example below, It's the same principle as REDCap's Drag-N-Drop Logic Builder: |
The "one control field" limitation has been fixed by PR #19. |
Indeed, the new version introduces a few features:
The only limitation left is the case in where multiple conditions are required to display a given form at the same time (not just one of them). Not sure how to solve this yet, maybe in a next major release. |
Another interesting feature that @pbchase and I discussed a few days ago is having a grade of checkboxes (instruments x events) in which we can pick individual forms to be displayed. Something like:
That would bring an extra flexibility, plus it's way more user friendly. |
All of the desires discussed in this issue can be addressed in the current release of FRSL, version 3.3.3. To get a multi-valued control field used the Advanced Control field feature. |
Currently, FRSL configuration form is limited:
The ideal solution for this is hijacking REDCap's branching logic form, which would be powerful and user friendly. But since this approach would take a considerable amount of time to implement, I would like to brainstorm middle ground solutions for this.
We could start, for instance, by hijacking the "Advanced Branching Logic Syntax" only - which is a simple text area field - alongside with a popup helper. Later on we could build on top of it.
@pbchase @tlstoffs any thoughts?
The text was updated successfully, but these errors were encountered: