Package 'rapbase'

Description

Provide explicit reference to function for do.call

Usage

.getFun(x)

Arguments

Value

value of the exported 'function' in 'package'

Description

Simple test of automated reporting from definitions provided in a yaml config file

Usage

.testAutoReport(aNum = 1, aChar = "a", anExp = Sys.Date(), bulletin = 0)

Arguments

Value

A simple message listing the contents of the arguments

Examples

.testAutoReport()

Description

A dataset containing test entries for the application log.

Usage

appLog

Format

A data frame with 20 rows and 8 variables:

id

character id

time

character timestamp

user

user name

name

user full name

group

users group/registry

role

users role

resh_id

users organization

message

log message

Description

Provides a widget-like information and utility block to be applied to all registry apps at Rapporteket. Contains the user name, organization and logout/exit as hyperlinked text.

Usage

appNavbarUserWidget(
  user = "Undefined person",
  organization = "Undefined organization",
  addUserInfo = FALSE,
  selectOrganization = FALSE,
  namespace = NULL
)

Arguments

Details

Normally, user information will be be provided through the session parameter and hence this will have to be provided from the server. The "rendering" of this info must hence be done within a layout element at the client such as a tabPanel. Selecting any one of them should be fine... At the client, both uiOutput and textOutput will be fine "rendering the information provided by the server.

Example of use in shiny (pseudo code):

server <- function(input, output, session) {
  ...
  output$appUserName <- renderText(getUserName(session))
  output$appUserOrg <- renderText(getUserReshId(session))
  ...
}

ui <- tagList(
  navbarPage(
    ...,
    tabPanel(...,
    appNavbarUserWidget(user = uiOutput(appUserName),
    organization = textOutput(appUserOrg))
    ),
    ...
  )
)

Value

Ready made html script

Examples

appNavbarUserWidget()

Description

These shiny modules may be used to set up auto reporting from registries at Rapporteket.

Usage

autoReportUI(id)

autoReportOrgInput(id)

autoReportOrgServer(id, orgs)

autoReportFormatInput(id)

autoReportFormatServer(id)

autoReportInput(id)

autoReportServer(
  id,
  registryName,
  type,
  org = NULL,
  paramNames = shiny::reactiveVal(c("")),
  paramValues = shiny::reactiveVal(c("")),
  reports = NULL,
  orgs = NULL,
  eligible = shiny::reactiveVal(TRUE),
  freq = "month",
  user,
  runAutoReportButton = FALSE
)

autoReportServer2(...)

Arguments

Details

The reports argument must be a list where each entry represents one report and its name will be used in the auto report user interface for selecting reports, e.g. reports = list(MagicReport = ...) will produce the entry "MagicReport" in the GUI list of reports to select from. The value of each entry must be another list with the following names and values:

synopsis

character string describing the report

fun

report function base name (without"()")

paramNames

character vector naming all arguments of fun

paramValues

vector with values corresponding to paramNames

These named values will be used to run reports none-interactively on a given schedule and must therefore represent existing and exported functions from the registry R package. For subscriptions the reports list can be used as is, more specifically that the values provided in paramValues can go unchanged. It is likely that parameter values must be set dynamically at runtime in which case paramValues must be a reactive part of the application. See Examples on how function arguments may be used as reactives in an application.

Value

In general, shiny objects. In particular, autoreportOrgServer returns a list with names "name" and "value" with corresponding reactive values for the selected organization name and id. This may be used when parameter values of auto report functions needs to be altered at application run time.

Examples

## make a list for report metadata
reports <- list(
  FirstReport = list(
    synopsis = "First example report",
    fun = "fun1",
    paramNames = c("organization", "topic", "outputFormat"),
    paramValues = c(111111, "work", "html")
  ),
  SecondReport = list(
    synopsis = "Second example report",
    fun = "fun2",
    paramNames = c("organization", "topic", "outputFormat"),
    paramValues = c(111111, "leisure", "pdf")
  )
)

## make a list of organization names and numbers
orgs <- list(
  OrgOne = 111111,
  OrgTwo = 222222
)

## client user interface function
ui <- shiny::fluidPage(
  shiny::sidebarLayout(
    shiny::sidebarPanel(
      autoReportFormatInput("test"),
      autoReportOrgInput("test"),
      autoReportInput("test")
    ),
    shiny::mainPanel(
      autoReportUI("test")
    )
  )
)

## server function
server <- function(input, output, session) {
  org <- autoReportOrgServer("test", orgs)
  format <- autoReportFormatServer("test")

  # set reactive parameters overriding those in the reports list
  paramNames <- shiny::reactive(c("organization", "outputFormat"))
  paramValues <- shiny::reactive(c(org$value(), format()))

  autoReportServer2(
    id = "test", registryName = "rapbase", type = "dispatchment",
    org = org$value, paramNames = paramNames, paramValues = paramValues,
    reports = reports, orgs = orgs, eligible = TRUE, freq = "month", user
  )
}

# run the shiny app in an interactive environment
if (interactive()) {
  shiny::shinyApp(ui, server)
}

Description

Adds an entry to the system configuration of reports to run at given intervals. After generating the configuration from the new entry the function load the current system configuration, adds the new entry and saves the updated system configuration.

Usage

createAutoReport(
  synopsis,
  package,
  type = "subscription",
  fun,
  paramNames,
  paramValues,
  owner,
  ownerName = "",
  email,
  organization,
  runDayOfYear,
  startDate = as.character(Sys.Date()),
  terminateDate = NULL,
  interval = "",
  intervalName = "",
  dryRun = FALSE
)

Arguments

Value

Nothing unless dryRun is set TRUE in which case a list of all config will be returned

See Also

deleteAutoReport

Description

Delete existing report from config/db

Usage

deleteAutoReport(autoReportId)

Arguments

See Also

createAutoReport

Description

Functions for registries that wants to implement exporting of registry databases, e.g. for local development purposes. Also includes relevant helper functions

Usage

exportUCInput(id)

exportUCServer(
  id,
  dbName,
  teamName = NULL,
  eligible = shiny::reactiveVal(TRUE)
)

exportUCApp(dbName = "rapbase")

selectListPubkey(pubkey)

exportDb(dbName, dropTabs = NULL, tableNames = "", compress = FALSE, session)

queryToFile(
  dbName,
  tableName = "",
  query,
  format = "RDS",
  compress = FALSE,
  session
)

Arguments

Value

Shiny objects, mostly. Helper functions may return other stuff too.

Examples

## client user interface function
ui <- shiny::fluidPage(
  shiny::sidebarLayout(
    shiny::sidebarPanel(
      exportUCInput("test"),
    ),
    shiny::mainPanel(
      NULL
    )
  )
)

## server function
server <- function(input, output, session) {
  exportUCServer("test", dbName = "rapbase")
}

## run the shiny app in an interactive environment
if (interactive()) {
  shiny::shinyApp(ui, server)
}

Description

Shiny app with database export functionality

Usage

exportApp(teamName = "", dbName = "data", logAsJson = TRUE)

Arguments

Description

Shiny modules providing the Export Guide

Usage

exportGuideUI(id)

exportGuideServer(id, dbName)

exportGuideServer2(id, dbName)

exportGuideApp()

Arguments

Value

Functions ui and server representing the (module) app

Examples

ui <- shiny::fluidPage(
  exportGuideUI("exportGuide")
)

server <- function(input, output, session) {
  exportGuideServer("exportGuide", "test")
}

if (interactive()) {
  shiny::shinyApp(ui, server)
}

Description

Generic function to filter various entities from auto report data

Usage

filterAutoRep(data, by, pass)

Arguments

Value

List of auto reports matching the filtering criteria

Examples

ar <- data.frame(type = c("A", "B"))
filterAutoRep(ar, "type", "B") # ar2

Description

Find the next date that an automated report is supposed to be run. Likely, this function will only be relevant for shiny apps when this date is to be printed

Usage

findNextRunDate(
  runDayOfYear,
  baseDayNum = as.POSIXlt(Sys.Date())$yday + 1,
  startDate,
  terminateDate,
  interval = NULL,
  returnFormat = "%A %e. %B %Y"
)

Arguments

Value

String date for printing

Examples

# Will return Jan 30 in the current year and locale with default formatting
findNextRunDate(runDayOfYear = c(10, 20, 30),
 baseDayNum = 20, startDate = 1, terminateDate = 50)

Description

Try to obtain yaml-formatted configuration placed either as given by the environment variable R_RAP_CONFIG_PATH or as provided by the package itself. If none can be found the function exits with an error

Usage

getConfig(fileName, packageName = "rapbase")

Arguments

Value

A list of (yaml) configuration

Description

Collect various data from the GitHub API

Usage

getGithub(what, value, .token = NULL)

Arguments

Value

Character vector with results from the GitHub api request

Description

To be used for testing purposes

Usage

halloRapporteket()

Value

message A test message

Description

Render text on how Rapporteket deals with personal data

Usage

howWeDealWithPersonalData(..., callerPkg = NULL)

Arguments

Value

fragment html info text

Description

Call to this function will return TRUE when run on a system where the environment variable R_RAP_INSTANCE is set to either "DEV", "TEST", "QA" or "PRODUCTION" and FALSE otherwise

Usage

isRapContext()

Value

Logical if system has a defined Rapporteket context

Examples

isRapContext()

Description

Generic to registries, provide reporting data obtained from sql databases Underlying this function is rapbase::RapporteketDbConnection

Usage

loadRegData(registryName = "data", query, dbType = "mysql")

describeRegistryDb(registryName, tabs = c())

nlinesRegistryDb(registryName, tab = "")

Arguments

Value

data frame containing registry data or a list with table names and corresponding fields with attributes

Description

To be used for logging at application level (i.e. when a shiny session is started) or at report level (i.e. each time a report is run). Logging of single report events should be made from reactive environments within the shiny server function or from within the (report) functions used by the same reactive environments.

Usage

appLogger(
  session,
  msg = "No message provided",
  .topcall = sys.call(-1),
  .topenv = parent.frame()
)

userLogger(user, msg = "No message provided")

repLogger(
  session,
  msg = "No message provided",
  .topcall = sys.call(-1),
  .topenv = parent.frame()
)

autLogger(
  user,
  name,
  registryName,
  reshId,
  type,
  pkg,
  fun,
  param,
  msg = "No message provided",
  .topenv = parent.frame()
)

Arguments

Details

The below fields will be appended to the log, in the following order:

1. time: date-time as event is logged as format(time, "%Y-%m-%d %H:%M:%S")

2. user: username as found in the shiny session object or as provided by function argument

3. name: full name of user as found in the shiny session object

4. group: users group membership as provided by the shiny session object. Normally, this will correspond to the registry the user belongs to

5. role: users role as provided by the shiny session object. Its value will depend on whatever is delivered by the authorization provider, but for OpenQReg registries 'LU' (local user) and 'SC' (system coordinator) are typical values

6. resh_id: the organization id of the current user as provided by the shiny session object, OR, when source of logging is auto reports, the organization ID of the data source used to make the report

7. environment: environment from where the logger function was called (only provided by repLogger())

8. call: function (with arguments) from where the logger was called (only provided by repLogger())

9. message: an optional message defined as argument to the function

The autLogger() function is a special case to be used for automated reports. Since such reports are run outside a reactive (shiny) context shiny session data are not available to the logger. Hence, logging data must be provided as arguments directly. As of rapbase version 1.12.0 logging of automated reports are already taken care of. Hence, this function should not be applied per registry application.

Value

Returns nothing but calls a logging appender

Note

Pseudo code of how appLogger() may be implemented:

library(shiny)
library(raplog)

server <- function(input, output, session) {
  raplog::appLogger(session, msg = "Smerteregisteret: starting shiny app")
  ...
}

Pseudo code on how repLogger() can be implemented as part of a function in a reactive (shiny) context. First, this is an example of the shiny server function with the (reactive) function renderPlot() calling a function that provides a histogram:

library(shiny)
library(raplog)

server <- function(input, output, session) {
  ...
  output$hist <- renderPlot({
    makeHist(data, var = input$var, bins = input$bins, session = session)
  })
  ...
}

Then, logging is called within the function makeHist():

makeHist <- function(data, var, bins, ...) {

  if ("session" %in% names(list(...))) {
    raplog::repLogger(session = list(...)[["session"]],
                      msg = "Providing histogram")
  }
  ...
}

Examples

# Depend on the environment variable R_RAP_CONFIG_PATH being set
try(appLogger(list()))



# Depend on the environment variable R_RAP_CONFIG_PATH being set
try(repLogger(list()))



# Depend on the environment variable R_RAP_CONFIG_PATH being set
try(autLogger(user = "ttester", registryName = "rapbase", reshId = "999999"))

Description

Every info, warning and error will be logged in json format.

Usage

loggerSetup(
  usernameEnv = "SHINYPROXY_USERNAME",
  appidEnv = "SHINYPROXY_APPID",
  hooks = TRUE
)

Arguments

Description

Wrapper around logger::log_shiny_input_changes

Usage

logShinyInputChanges(...)

Arguments

Description

Make a table to be rendered in a shiny app providing automated reports from a given user or registry as obtained from the environmental variables.

Usage

makeAutoReportTab(
  namespace = character(),
  user = getUserName(),
  group = getUserGroups(),
  orgId = getUserReshId(),
  type = "subscription",
  mapOrgId = NULL,
  includeReportId = FALSE
)

Arguments

Details

Each table record (line) represents a uniquely defined automated report. For each line two shiny action buttons are provided to allow for editing and deleting of each entry. For applications implementing this table observing events on these action buttons may be used to allow users to manage automated reports by GUI. The action buttons for editing and deleting are provided with the static input ids edit_button and del_button and upon clicking the button part of their ids will change to the unique id of the report. Hence, a GUI call for editing a report can be caught by shiny::observeEvent("edit_button") and within this event the report id is obtained by collecting the string after the double underscore, e.g. strsplit(input$edit_button, "__")[[1]][2].

Optionally, report id may be provided as the last column in the table to allow further development for registry specific purposes. Regardless, this column should normally be hidden in the GUI.

Take a look at the example shiny server function in rapRegTemplate on how this function may be implemented.

Value

Matrix providing a table to be rendered in a shiny app

Description

This function provides an even sequence of day numbers spanning 365/366 days from the start date and interval provided. Mainly to be used in setting up automated reports at Rapporteket

Usage

makeRunDayOfYearSequence(startDay = Sys.Date(), interval)

Arguments

Value

Integer vector of day numbers

Examples

makeRunDayOfYearSequence(interval = "month")

Description

Function that will return tables used in reports.

Usage

mst(
  tab,
  col_names = colnames(tab),
  type = "pdf",
  cap = "",
  label = knitr::opts_current$get("label"),
  digs = 0,
  align = NULL,
  fs = 8,
  lsd = FALSE
)

Arguments

Details

mst() creates RMarkdown code for creating standard tables.

Value

Character string containing RMarkdown table code

Examples

mst(tab = mtcars[1:10, ])

Description

Shiny modules for making a user information widget in registry shiny apps at Rapporteket. One benefit using these modules will be reduced complexity and number of code lines for each registry.

Usage

navbarWidgetInput(id, addUserInfo = TRUE, selectOrganization = FALSE)

navbarWidgetServer2(id, orgName, map_orgname = NULL, caller = NULL)

navbarWidgetApp(orgName = "Org Name")

Arguments

Details

These modules take use of the shiny session object to obtain data for the widget. Hence, a Rapporteket like context will be needed for these modules to function properly. For deployment of (shiny) application as containers make sure to migrate to navbarWidgetServer2(). In addition to serving the user information widget, this function provides a list of reactive user attributes. Hence, when using navbarWidgetServer2() the source of (static) user attributes is no longer the shiny session object but rather the list object (of reactive user attributes) returned by this function.

Value

Shiny objects, mostly. navbarWidgetServer2() invisibly returns a list of reactive values representing user metadata and privileges. See userAttribute for further details on these values.

Examples

## client user interface function
ui <- shiny::tagList(
  shiny::navbarPage(
    "Testpage",
    shiny::tabPanel(
      "Testpanel",
      shiny::mainPanel(
        navbarWidgetInput("testWidget")
      )
    )
  )
)

## server function
server <- function(input, output, session) {
  navbarWidgetServer2("testWidget", orgName = "Test org")
}

## run the app in an interactive session and a Rapporteket like environment
if (interactive() && isRapContext()) {
  shiny::shinyApp(ui, server)
}

Description

To be applied for user input when there is actually no choice :-)

Usage

noOptOutOk()

Value

String with possible state of mind (in Norwegian) once left with no options

Examples

noOptOutOk()

Description

Provide common functions and resources for registry specific R-packages at Rapporteket. This packages is relevant for developers of packages/registries at Rapporteket

Description

Close down data connection handle

Usage

rapCloseDbConnection(con)

Arguments

Description

Generic to registries, handle the data source connections, including usernames and passwords needed to open these connections

Usage

rapOpenDbConnection(dbName, dbType = "mysql")

Arguments

Value

A named list of con and drv representing the db connection handle and driver, respectively.

Description

This is a wrapper around bslib::bs_theme

Usage

rapTheme(theme = "flatly", version = 3)

Arguments

Value

a Bootstrap theme object

Description

Read automated report metadata

Usage

readAutoReportData()

Value

a table of autoreport data

Examples

try(readAutoReportData())

Description

Title on the top left of the app, including the logo

Usage

regTitle(regTitle = "rapbase")

Arguments

Value

a div containing the logo and the title

Description

Function that renders documents at Rapporteket from rmarkdown source files. Output formats may be (vanilla) HTML or PDF based on our own pandoc latex template or fragments of html when the result is to be embedded in existing web pages. Rmarkdown allow parameters to be part of report processing. Thus, parameters that are specific to reports must be provided (as a named list) when calling renderRmd().

Usage

renderRmd(
  sourceFile,
  outputType = "html",
  logoFile = NULL,
  params = list(),
  template = "default"
)

Arguments

Value

Character string with path to the rendered file or, if outputType is set to "html_fragment", a character string providing an html fragment. Files are named according to tempfile() with an empty pattern and with the extension according to outputType ("pdf" or "html").

Description

Updated version of repLogger() to be used in reactive contexts where user data is provided as reactive values. This is the case for the when user <- navbarWidgetServer2 which the way of providing user data in shiny applications at Rapporteket. The use of the original repLogger() should be changed to repLogger2 as repLogger() doesn't handle change of user roles during a session, which can happen in the shiny applications at Rapporteket.

Usage

repLogger2(
  user,
  msg = "No message provided",
  .topcall = sys.call(-1),
  .topenv = parent.frame()
)

Arguments

Note

If you are in the main shiny server, you can call user without passing it as an argument to the server function, as user is available in the main server environment. However, if you are in a module server function, you need to pass user as an argument to the module server function before you call repLogger2(user).

Examples

## Not run: 
# Inside a reactive context, for example within a
# downloadHandler() function, you can call:
rapbase::repLogger2(user, msg = "This is a test")
# make sure user exists inside server modules
# by passing it as an argument to the module server function:
module_server <- function(id, user) { ... }

## End(Not run)

Description

Usually to be called by a scheduler, e.g. cron. If the provided day of year matches those of the config the report is run as otherwise specified in config. Functions called upon are expected to return a character string providing a path to a file that can be attached to an email or, in case of a bulletin, the email body itself. For bulletins, files cannot be attached. The email itself is prepared and sent to recipients defined in the config

Usage

runAutoReport(
  dayNumber = as.POSIXlt(Sys.Date())$yday + 1,
  dato = Sys.Date(),
  group = NULL,
  type = c("subscription", "dispatchment"),
  dryRun = FALSE
)

Arguments

Value

Emails with corresponding file attachment. If dryRun == TRUE just a message

Examples

# Example depend on environment variable R_RAP_CONFIG_PATH being set
try(runAutoReport())

Description

This is a wrapper for runAutoReport() to issue bulletins.

Usage

runBulletin()

Value

Whatever runAutoReport() might provide

Description

Function that removes log entries older than a given number of days.

Usage

sanitizeLog(eolDays = 730)

Arguments

Value

NULL on success

Description

This function can be used to send email from within R at Rapporteket. It relies on (and must hence be provided) specific settings through local configuration to work properly.

Usage

sendEmail(conf, to, subject, text, attFile = NULL)

Arguments

Value

Invisible sending of email

Description

Low level functions for handling registry staging data at Rapporteket. As such, these functions does not provide staging data management per se. Proper management, e.g. staging data updates and fallback logic must therefore be established within each registry that take staging data into use.

Usage

listStagingData(registryName, dbTable = "data")

mtimeStagingData(registryName, dbTable = "data")

saveStagingData(registryName, dataName, data, dbTable = "data")

loadStagingData(registryName, dataName, dbTable = "data")

deleteStagingData(registryName, dataName, dbTable = "data")

cleanStagingData(eolAge, dryRun = TRUE, dbTable = "data")

Arguments

Details

Staging data is stored as binary large objects in a database. A per registry symmetric encryption of storage content is enforced. Keys used for encryption are generated from existing database credentials. Therefore, please note that removing or changing such credentials will render any historic staging data inaccessible.

cleanStagingData() globally removes all staging data with store date prior to the end-of-life age provided. This is a vastly destructive function that should be used with great care.

Value

• listStagingData() returns a character vector of staging data sets for the given registry (registryName).

• mtimeStagingData() returns a staging data set named POSIXct vector of modification times for the given registry (registryName).

• saveStagingData() when successful returns the data object (data), invisibly. If saving fails a warning is issued and the function returns FALSE.

• loadStagingData() returns the data object corresponding to the name given upon saving (dataName). If the requested data set for loading does not exist the function returns FALSE.

• deleteStagingData() returns TRUE if the data set was deleted and FALSE if not.

• cleanStagingData() returns a list of data sets (to be) removed.

Examples

## Prep test data
registryName <- "rapbase"
dataName <- "testData"
data <- mtcars

## Save data for staging
try(saveStagingData(registryName, dataName, data))

## List data currently in staging
try(listStagingData(registryName))

## Retrieve data set from staging and compare to outset
try(stagedData <- loadStagingData(registryName, dataName))
try(identical(data, stagedData))

## Get modification time for staging file(s)
try(mtimeStagingData(registryName))

Description

These modules may be used by registries for easy setup of usage reports. The intended purpose is to provide registry staff access to when and by whom the resources at Rapporteket were used, i.e. application start-up and single report usage. As such, this will be a tool to provide useful statistics. However, it might also serve as a formal monitor utility but only if logging is carefully implemented throughout the relevant functions that make up the registry application at Rapporteket.

Usage

statsInput(id)

statsUI(id)

statsServer(id, registryName, app_id = NULL, eligible = TRUE)

statsServer2(
  id,
  registryName,
  app_id = NULL,
  eligible = shiny::reactiveVal(TRUE)
)

statsApp()

logFormat(log)

logTimeFrame(log, startDate, endDate)

Arguments

Value

Shiny objects, mostly. Helper functions may return other stuff too.

Examples

# client user interface function
ui <- shiny::fluidPage(
  shiny::sidebarLayout(
    shiny::sidebarPanel(statsInput("test")),
    shiny::mainPanel(statsUI("test"))
  )
)

# server function
server <- function(input, output, session) {
  statsServer("test", registryName = "rapbase", eligible = TRUE)
}

# run the shiny app in an interactive environment
if (interactive()) {
  shiny::shinyApp(ui, server)
}

Description

Shiny modules providing the Stats Guide

Usage

statsGuideUI(id)

statsGuideServer(id, registryName)

statsGuideApp()

Arguments

Value

Functions ui and server representing the (module) app

Examples

ui <- shiny::fluidPage(
  statsGuideUI("statsGuide")
)

server <- function(input, output, session) {
  statsGuideServer("statsGuide", "test")
}

if (interactive()) {
  shiny::shinyApp(ui, server)
}

Description

A dataset containing test entries.

Usage

testdata

Format

A data frame with 10 rows and 6 variables:

id

int id

someText

char text

someInt

int integer

someBigInt

int big integer

someFloat

num float number

someTime

time date

Description

For apps running as containers particular environment variables must be defined for an orderly handling of dynamic user privileges. This function makes use of environmental variables defined by shinyproxy to provide available privileges for the shiny application.

These are helper function for userInfo. When used without a shiny session object calls to these functions is made without any arguments. If redefining contexts is needed, please use userInfo instead.

Usage

userAttribute(unit = NULL, map_orgname = NULL)

getUserEmail(...)

getUserFullName(...)

getUserGroups(...)

getUserName(...)

getUserPhone(...)

getUserReshId(...)

getUserRole(...)

Arguments

Value

Invisibly a list of user metadata and privileges:

name

The username for whom the privileges apply.

fullName

User full name

phone

User phone number

email

User email

unit

Unit id under which the privileges are defined.

org

Organization id for the user.

role

Role of the user.

orgName

Name of the organization as defined under the unit id.

String with user attribute

Examples

try(getUserEmail())

Description

Extracts elements from either config, url (shiny), shiny session or environmental variables relevant for user data such as name, group, role and org id (e.g. resh id). Source of info is based on environment context and can be controlled by altering the default settings for which contexts that will apply for the various sources of user data. This function will normally be used via its helper functions (see below).

Usage

userInfo(entity)

Arguments

Value

String of single user data element

See Also

getUserName, getUserGroups, getUserReshId, getUserRole

Description

Write automated report metadata

Usage

writeAutoReportData(config)

Arguments

Examples

# Example depend on environment variable R_RAP_CONFIG_PATH being set
try(config <- readAutoReportData())
try(writeAutoReportData(config = config))