---
title: Asset Group Properties
slug: ryze/asset-group-properties
description: Learn how to access and edit properties for Medidata Rave Asset Group Level, including Locale, Annotation, Use Alias For OID, and more. Customize your workflows and configurations with this comprehensive guide for Medidata Rave system users.
createdAt: 2023-09-29T10:43:23.404Z
---

 To access Medidata Rave Asset Group Level properties, select the Asset Group and click the **edit properties** icon. Click the pencil icon next to the Medidata Rave plugin.

### Locale

Locale dictates which language to display on the eCRF visualization, or to export. This attribute works with other ‘Locale’ fields.

### Annotation

Used to display Annotations on the Medidata Rave eCRF Preview and iMedidata Rave EDC eCRF Preview Visualizations. Se&#x65;**&#x20;Annotation Properties**

### Use Alias For OID

Used to specify whether Alias values that have been added within elements should be used instead of OIDs. The Alias that is used is the one that matches the context specified in the Alias OID Remapping Context Properties.

### Alias OID Remapping Context

Used to specify the context of the Alias values to use in place of the element’s OID during export.

### Use Alias For Coded Value

Used to specify Alias values that have been added within Code List Items/Enumerated Items to use in place of the Code List Item/Enumerated Item’s Coded Value. The Alias that is used is the one that matches the context specified in the Alias Coded Value Remapping Context.

### Alias Coded Value Remapping Context

Used to specify the context of the Alias values to use in place of the Code List Item/Enumerated Item’s Coded Value during export.

### Matrix View Sort Options

Used to specify how Forms are sorted in the Matrix View. Sort options are: 

- Sort Key: Forms can be sorted by Name, OID or Ordinal. 
- Sort Order: Sort key can be in Ascending or Descending order.

### Master Marking Group

Used to specify which Marking Group values are allowed for the Study or Standard. properties that use Marking Groups will refer to this property for the list. For example, Method Level properties.

Master properties may be added with data integrations. See also [Data Integrations](https://docs.formedix.com/ryze/data-integrations).

### Master Roles

Used to specify which Role values are allowed for the Study or Standard. properties that use Roles will refer to this Property for the list. For example, View Restrictions and Entry Restrictions properties

### Master Review Group

Used to specify which Review Groups are allowed for the Study or Standard. properties that use Review Groups will refer to this property for the list: 

- Requires Manual Reviews property at Field level 
- Requires Manual Reviews property at Item level 
- Require Review in Check Actions

### Master Coding Dictionary

Used to specify which Coding Dictionary values are allowed to be used in the Standard or Study. The Coding Dictionary property at Item level will refer to this property for the list. See **Coder Configuration**.

### Master Lab Analyte

Used to specify which Lab Analyte values are allowed to be used in the Standard or Study, The Lab Analyte property at Item level and the Lab Analyte property at Field level will refer to this property for the list

### Master User Group

Used to specify which User Group values are allowed for the Study or Standard. properties that use User Groups will refer to this property for the list. For example, Method Level properties

### Master User

Used to specify which User values are allowed within the file

Note: You can upload Rave URL configurations files for the following properties (see Data Integrations):

- Master Marking Group
- Master Roles
- Master Review Group
- Master Coding Dictionary
- Master Lab Analyte
- Master User Group

### Delete Existing

Used to specify whether an existing draft is deleted before the content of the new draft is uploaded when you import an Architect Loader Spreadsheet (ALS) into Rave.

### Project Type

Used to specify the Project Type.

### Primary Form

Used to specify the Primary Form. This appears when a new subject is added in Rave. Unless specified, this defaults to the first Form in the Forms tab

### Default Matrix

Used to specify the primary Matrix. Defaults to the first defined Matrix. If no Matrices are defined, this defaults to the OID of the hard coded default Matrix (‘BASE’)

### Confirmation Message

Used to specify a message to display to end users when forms are submitted in Rave

### Signature Prompt

Used to specify a message to display to the Investigator when a signature is entered.

### Standard Units

Used to specify the name of the group that defines Standard Units. See **Lab Module Configuration**

### Reference Labs

Used to specify a Reference Labs name. See Lab Module Configuration

### Alert Labs

Used to specify an Alert Labs name. See Lab Module Configuration

### Matrix

Allows matrices to be defined. See Matrices

### Lab Variable Mappings

Allows Lab Variables to be mapped. You can define more than one Lab Variable Mapping. See Lab Module Configuration

## Annotation property

The Annotation property lets you customize the annotations displayed on the Medidata Rave Previews and Visualizations. Annotation properties are added at the asset group level from Plugin properties.

### Annotation Type

Used to specify the type of annotation that should be displayed on the visualization. The following Annotation types can be displayed: 

- OID: displays the OIDs of the relevant objects (for example, Question OID 
- SAS: displays the following: “SASDatasetName” for Sections, “SASFieldName” for Questions, “SASFormatName” for Terminologies 
- SDS: displays the following: “Domain” for Sections, “SDSVarName” for Questions 
- Alias: displays the “Alias” for Questions. The ‘Annotation Alias Type’ property must also be used in order to specify the type of Alias annotation. See Aliases

### Annotation Alias Type

Used to specify which alias types are displayed. This allows multiple annotations to be added

### Visibility

Used to specify whether the Annotation will be shown on the visualization or not.

### Display Format

Specifies what the Annotation will display by using the following special parameter values:

- %name%: shows the Alias Name (for example, VSORRES)
- %context-base%: shows the text before the “:” in the Alias Context (for example, SDTM)
- %context-qualifier%: shows the text after the “:” in the Alias Context (for example, Decode) 

The default value is ‘%name%’ when only one Alias Annotation is used. This will change to ‘%context-base%: %name%’ when more than one Alias Annotation is used

### Background Color

Used to specify the background color of the Annotation.

### Font Color

Used to specify the font color of the Annotation.

### Font Family

Used to specify the font family of the Annotation.

### Font Size

Used to specify the font size of the Annotation.

### Font Style

Used to specify the font style of the Annotation.

### Font Weight

Used to specify the font weight of the Annotation.

## Aliases

Aliases consist of the Name and the Context attributes. The Name field contains the text displayed as the annotation. The Context attribute associates the “Annotation Alias Type” property with the Alias and defines where the annotation is displayed on the visualization.

The Alias context consists of three parts:

- Alias Type: specified in the “Annotation Alias Type” property. This can be any text string. For example “SDTM”, “CDASH”
- Delimiter: must be “:”

## Matrix

The Medidata Rave system supports multiple workflows. These serve several purposes:

- Provide different eCRF lists for groups of subjects
- Enables dynamic switching of workflow, dependent on data entered into the eCRFs and controlled by Edit Check programming
- Provides a mechanism to Add or Remove certain eCRFs from a subjects workflow

 

The Matrix property allows one or more Matrices (Study Events) to be defined.  If no Matrices are defined, a default Matrix is created using the Form references within the Study Events to populate the Matrix. Only the Study Events that have been added to the Visit Schedule screen have their Form references populated.

The order of Study Events within the Matrix is dictated by their order in the Visit Schedule screen. Any Study Events which are not in the Visit Schedule should be placed at the bottom. If no Visit Schedule is defined, the order of the Study Events will be the order in which they appear in the Visits tab.

**Note**: The order of the Forms in the Matrix is dictated by the order they appear in the Forms tab. The Ordinal property at Form level can be used to change this order. If Ordinals are not set, they are assigned an Ordinal based on their order in the Forms tab.

### Name

Used to specify the name of the Matrix. For example, ‘Screen’

### OID

Used to specify the OID of the Matrix

### Allow Add

Used to specify whether the Matrix is available on the ‘Add Event’ drop-down list on a Subject’s homepage.

### Max

Used to specify the maximum number of times a Matrix can be added to a Subject via the ‘Add Event’ drop-down list

### Default Folder Forms group

Used to specify Forms are shown in the ‘Subject Name’ column in the Matrix. The Primary Form is always shown in this column

### Folders group

- Folder: this property is used to specify which Forms to include in the Matrix. All Forms referenced by the Visit specified in the ‘Folder’ property, are included. 
- Exclude Form: used to specify if any Forms in this Matrix should not be included


