You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would you provide some guidance on implemeting the following:
Immediately after the Data Upload option, there will be a list of pre-uploaded mapping yaml files so that the user just selects the yaml and run the app.
To elaborate, suppose there are two mapping config files and depending on the source data, the uses would select the one that is appropriate for the input data.
I see that the mapping paramter in the safetyGraphicsApp() function but wondering where should the input-file-selector should be placed.
Thank you
The text was updated successfully, but these errors were encountered:
Hi @raheems - there are a few ways you could approach this:
Create a "wrapper app" that lets the user load a mapping file before calling the safetyGraphics with a custom mapping. See these lines in safetyGraphicsInit().
You could also create custom metadata files with new mapping values built in and then the app would auto-select the best match. You'd just need to add your new default values in columns to the metadata saved here - similar to standard_adam and standard_sdtm in the current files
I was trying to find a way to pass user-selectable parameters when deploying the app using the following line:
safetyGraphics::safetyGraphicsApp(runNow = FALSE) # add parameters here (if any)
Since shiny app cannot be called from another shinyApp, how to include selectInput style parameters that users can select and click a button that calls
Would you provide some guidance on implemeting the following:
To elaborate, suppose there are two mapping config files and depending on the source data, the uses would select the one that is appropriate for the input data.
I see that the mapping paramter in the
safetyGraphicsApp()
function but wondering where should the input-file-selector should be placed.Thank you
The text was updated successfully, but these errors were encountered: