Activities Database Tables

To create and maintain activities list, you use the following database tables:

The RDC_ACTIVITIES database table, which contains the setup information for all the activities defined for the RDC application
The RDC_ACTIVITIES_TAGS database table, which contains the tags that call the functions that provide values for a text string, a display expression, or a URL

The following sections provide more information about each table:

Parent topic: Customizing Activities

RDC_ACTIVITIES Database Table

The Oracle Clinical RDC_ACTIVITIES database table contains the setup information for all the activities defined for the RDC application. You can add new activities, modify existing activities, and delete activities.

Each record (that is, row) in the RDC_ACTIVITIES database table defines the setup information for one activity.

Note:

The database table includes the default activities listed in activities-database-tables.html#GUID-B941737D-2B7E-4558-95D1-A085F2951277__CIHHDAIC.

Each field (that is, column) defines the values for an activity. activities-database-tables.html#GUID-B941737D-2B7E-4558-95D1-A085F2951277__CIHHDAIC describes each column in the RDC_ACTIVITIES database table.

Table 10-1 RDC_ACTIVITIES Database Table

Column Name	Description	Type (Max Length)
`USER_ROLE`	Specifies for which user roles RDC displays the activity. Each user logging in to RDC is associated with only one role. You can use the user role to control which activities RDC displays when the user logs in to the application. You can specify: One role Multiple roles (use a comma to separate roles) All roles (use the % wildcard character) For example, assume you define the following activities and user roles: Activity 1: `USER_ROLE` = % Activity 2: `USER_ROLE` = DM Activity 3: `USER_ROLE` = DM, CRA, SITE For this example, RDC displays: All three activities when the data manager (DM) logs in Only Activity 1 and Activity 3 when the CRA logs in Only Activity 1 when the investigator (INV) logs in The user role is not the only value that controls when RDC displays an activity. The value defined in the DISPLAY_EXPR column defines the condition that must be meet for RDC to display the activity. See the DISPLAY_EXPR description later in this table for more information.	VARCHAR2 (50)
`TEXT`	Specifies the title of the activity. This is the title the user sees in the RDC application. Examples of title text: Show All My Open Discrepancies Review All Investigator Comments Go to the Oracle Web Site You must specify the TEXT value in English. RDC currently only supports English. The TEXT value can contain one or more tags. A tag provides variable information, such as the site name, a count of records, or a refer function. You use % signs to enclose a tag. For example, `%OPEN_DISCREPS%`. When you specify a tag in the TEXT column, RDC processes the tag as follows: Locates the tag in the `RDC_ACTIVITY_TAGS` table Calls the function specified in the `FUNCTION_NAME` column in that table Replaces the tag with the value returned by the called function For example, assume the TEXT column has the following line: `Show` `%OPEN_DISCREPS%` `Active Discrepancies for Site` `%CURR_SITE%` For this example, the resulting title in the RDC application might be: `Show 3 Active Discrepancies for Site ACME DRUG CO` You can also customize the return value of the function to take into account the applicable site.	VARCHAR2 (200)
`ACTIVITY_ID`	Provides a unique key for the activity.	Number (10)
`ACTIVITY_TYPE`	Defines the type of activity. P — Indicates that this is a procedure activity. Recall that a procedure activity executes the defined query, navigates to the appropriate RDC page, and displays only those patients/CRFs that meet your defined search criteria. You use this type of activity for procedure-based tasks. U — Indicates that this is a URL activity. Recall that a URL activity launches a browser instance, opens a new browser window, and automatically navigates to the Web page associated with the URL. You use this type of activity for URL-based tasks.	VARCHAR2 (15)
`ACTIVITY_SCOPE`	Defines the scope in which the activity is eligible for display. The possible values for `ACTIVITY_SCOPE` depend on your version of the RDC application. For RDC (4.5.3 and later), `ACTIVITY_SCOPE` determines the page navigation. Because all activities in RDC are always processed for the current site, you do not need to define whether the activity is applicable to a specific study, site, or patient. RDC_ZF_CRF — Navigates to the Review CRFs page. RDC_ZF_DISCREP — Navigates to the Review Discrepancies page. RDC_ZF_INV — Navigates to the Review Investigator Comments page. RDC_ZF_LINK — Navigates to the Web page defined by the URL.	VARCHAR2 (15)
`ACTIVITY_EXEC`	Defines what task RDC executes when the user clicks the activity link. The value you specify depends on the type of activity you are creating. If the `ACTIVITY_TYPE` is P, then the value in the ACTIVITY_EXEC column: Is the name of the procedure to call when the activity is executed. Procedures use standard variables to determine the current study, site, or patients. Therefore, tags are not necessary with procedures. Examples of procedures: `rdc_activity_std.process_open_discreps` `RDC_ZF_surround_activity.LoadInvComments('All')` If the `ACTIVITY_TYPE` is U, then the value in the ACTIVITY_EXEC column is the URL. As shown in the following examples, you can use tags to make the URL sensitive to the context: U = https://company.com/v_rsdir/study%CURR_STUDY%.htm U = https://opa.apps.company.com/v_rsdir/rdcservlet?study=%CURR_STUDY%&site=%CURR_SITE% For these URL examples, you must create the study specific Web pages or a servlet that accepts study and site as parameters. See Creating and Maintaining Customized Activities for more information.	VARCHAR2 (200)
`DISPLAY_EXPR`	Defines the condition that determines whether RDC displays the activity link. You can enter no value (null) or you can specify a conditional display expression associated with the activity. The expression can include tags. The expression must return a true or false value. Based on the value in the column, RDC determines whether to display the activity. If the value is null, RDC always displays the activity. If the value of the specified expression evaluates to true, RDC displays the activity. If the value of the specified expression evaluates to false, RDC does not display the activity. You use the `DISPLAY_EXPR` column to suppress activities if no records match a specific condition. For example, you can define that RDC display a link to view all active discrepancies only if the number of open discrepancies is greater than zero (`%OPEN_DISCREPS%` > `0`). %BLANK_COUNT%>0 %OPEN_DISCREPS%>0 %ZF_OTHER_DISC%>0 %ZF_OPEN_DISC%>0	VARCHAR2 (200)

Parent topic: Activities Database Tables

RDC_ACTIVITY_TAGS Database Table

The RDC_ACTIVITY_TAGS database table contains the tags that are defined in the system and the execution module (function name) that evaluates the tag.

The following list describes the columns in the RDC_ACTIVITY_TAGS table.

Column Name Description Type (Max Length)

Column Name	Description	Type (Max Length)
`ACTIVITY_TAG`	Defines the tag that you can then specify in the following columns in the RDC_ACTIVITIES database table: TEXT ACTIVITY_EXEC DISPLAY_EXPR When RDC finds a tag in a column, RDC then searches through the values in the ACTIVITY_TAG column looking for a match for the tag. Locates the tag in the `RDC_ACTIVITY_TAGS` table Calls the function specified in the `FUNCTION_NAME` column in that table Replaces the tag with the value returned by the called function When each of these columns is parsed, if a TAG is found, the process searches this column to find the TAG match so that it can identify the code or substitution variable to display in place of the TAG. If a match is found, it processes the expression found in the `FUNCTION_NAME` column.	VARCHAR2 (15)
`FUNCTION_TYPE`	Defines the type of function specified in the FUNCTION_NAME column. F — Indicates the function is a user-defined function. S — Indicates the function contains search parameters. You use this type as a place holder for the search parameters (if they need to be brought up as part of the URL link). P — Indicates the function contains one of the following parameters: SITE, STUDY, or PATIENT. RDC sets the tag to the name to apply to the site, study, or patient. You cannot define new tags as parameter tags. The valid values are restricted to the name of the site, study, or patient.	VARCHAR2 (15)
`FUNCTION_NAME`	Defines either the name of the substitution variable or the name of the function in the system. Depending on the FUNCTION_TYPE value, the value in this column can be one of several types. If the FUNCTION_TYPE is F, then this column holds a database function, for example rdc_activity_std.open_discreps. See Function Activity Tags for examples of activity tags with a function type of F. If the FUNCTION_TYPE is S, then, this column holds a database function, e. g. RDC_ZF_surround_crf.getCrfsCountReadyForVerify passing required values for the function execution internally. If the FUNCTION_TYPE is P, then the only valid value is SITE. The tag gets the value of the current site being processed. If the FUNCTION_TYPE is T, then this value refers to a trigger.	VARCHAR2 (61)

ACTIVITY_TAG

Defines the tag that you can then specify in the following columns in the RDC_ACTIVITIES database table:

TEXT
ACTIVITY_EXEC
DISPLAY_EXPR

When RDC finds a tag in a column, RDC then searches through the values in the ACTIVITY_TAG column looking for a match for the tag.

Locates the tag in the RDC_ACTIVITY_TAGS table
Calls the function specified in the FUNCTION_NAME column in that table
Replaces the tag with the value returned by the called function

When each of these columns is parsed, if a TAG is found, the process searches this column to find the TAG match so that it can identify the code or substitution variable to display in place of the TAG. If a match is found, it processes the expression found in the FUNCTION_NAME column.

VARCHAR2 (15)

FUNCTION_TYPE

Defines the type of function specified in the FUNCTION_NAME column.

F — Indicates the function is a user-defined function.
S — Indicates the function contains search parameters. You use this type as a place holder for the search parameters (if they need to be brought up as part of the URL link).
P — Indicates the function contains one of the following parameters: SITE, STUDY, or PATIENT. RDC sets the tag to the name to apply to the site, study, or patient. You cannot define new tags as parameter tags. The valid values are restricted to the name of the site, study, or patient.

VARCHAR2 (15)

FUNCTION_NAME

Defines either the name of the substitution variable or the name of the function in the system. Depending on the FUNCTION_TYPE value, the value in this column can be one of several types.

If the FUNCTION_TYPE is F, then this column holds a database function, for example rdc_activity_std.open_discreps. See Function Activity Tags for examples of activity tags with a function type of F.
If the FUNCTION_TYPE is S, then, this column holds a database function, e. g. RDC_ZF_surround_crf.getCrfsCountReadyForVerify passing required values for the function execution internally.
If the FUNCTION_TYPE is P, then the only valid value is SITE. The tag gets the value of the current site being processed.
If the FUNCTION_TYPE is T, then this value refers to a trigger.

VARCHAR2 (61)

Parent topic: Activities Database Tables