Edit a data configuration

When editing a data configuration, you can modify the data configuration as a whole, or add, modify, or delete variables in the data configuration. Certain information about data configurations can be specified only during editing and not when creating the data configuration. This information includes fields related to third-party links from case details, database groups, and permissions.

1. In the left navigation pane, click the Settings icon ().
2. In the Configure System section, click Manage Configurations.
3. Click the Row Action menu () for the configuration, and then click Edit.
4. To modify the data configuration as a whole, next to the data configuration name in the top portion of the page, click Edit.
5. Modify fields as necessary. For descriptions of fields, except those related to third-party links, database group, and permissions, see Add a data configuration. The type of all configurations will be Local after configuration details have been edited and saved.

   Note:

   If you modify the name of an existing data configuration, all references to that name by existing runs, case series, and saved lists are updated automatically.
6. Optionally, select the drug hierarchy value from the Drug Hierarchy Account field.

   See drug and event hierarchies for more information.

7. Optionally, select the event hierarchy value from the Event Hierarchy Account field.
8. You can specify a link to appear on the Case Details page. For example, you can provide a link to a third-party application page providing further information about the case.
   1. In the Third Party Link Text field, enter the name of the link to appear on the Case Details page. If you do not specify a name, the link name is External Link.
   2. In the Third Party Link URL field, enter the URL for the third-party application page. You can use the following substitution variables:
      • $REPORT_ID$—Will be replaced by the value of the variable specified as the Report ID Col for the LIST section of the drilldown map table for the configuration.
      • $EXTERNAL_REPORT_ID$—Will be replaced by the value of the external report ID for the case. If you use this substitution variable, the configuration must include a variable of the type, External Report ID.

      For example: https://Signal/caseinfo.asp?caseid=$REPORT_ID$

9. To assign the configuration to a Database Group, you can select an existing group from the drop-down list, or select Add to new group and enter a name for the new group. Results reviewers can use this information when finding and selecting a data mining run. The application also uses the database group when determining color changes for case ID links that are visited by users.
10. Assign group permissions.
    1. To grant permissions to your login group, in the Group Permissions, Login Group section, next to the Login Group, click Read or Edit.
    2. To grant permissions to individual users in your login group, in the Individual Permissions, User section, next to the username, click Read or Edit.

       Users with Read permission for a configuration can select the data configuration for tasks such as creating a run or case series. Users with Edit permission can edit, copy, and delete the data configuration, as well as use it for tasks such as creating a run or case series.

       A user's permissions for a data configuration are determined by settings for both the individual user and the user's login group. For example, if the individual user has Read access but that user's login group has Edit access, the user has Edit access.

11. Click Save.
12. Optionally, add or edit data configuration variables. For more information, see Add or edit a data configuration variable.

    Note:

    Editing configuration variables will change the configuration type.
13. Validate the data configuration. Even if the only change was to assign permissions, you must validate the data configuration again.

    Certain attributes of a data configuration or its variables require you to log out of the application and log back in before they take effect. For this reason, Oracle suggests that you always log out and back in if you want to see the effect of your changes.