---
title: "Metadata Types Table"
canonical: "https://help.agiloft.com/space/SD/511148050/Metadata+Types+Table"
format: markdown
---
The Metadata Types table defines how Agiloft processes data in [Obligation](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/570163248) records. Each Metadata Type record represents one question in an [Obligation Management](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/237240328) screen. The records control which types of fields to map standard plain text answers to and which fields to display in Obligation records.

# Creating Records

By default, users in the admin, Admin Import, Business Admin, and Obligations Management groups can create and edit Metadata Type records. You can create a record by 

- Clicking the Convert to Metadata Type button in a Screen Result record.
- Clicking the Update/Create Subtopic button if it’s available in an Obligation record.
- Clicking New in the table view action bar.

The sections below describe the fields in Metadata Type records.

## Topic and Metadata Type

The Topic and Metadata Type fields are required. Topic describes the type of obligation, and Metadata Type defines the category of the obligation. Metadata Type maps to Subtopic in an Obligation record, Question Title in an Obligation Management screen, and Element Name in a Screen Result record.

## Standard Fields Visibility

This field controls which of the standard fields to display in Obligation records for the metadata type. In addition to Obligation Type, which is always populated from a preconfigured set of values, each question in the Agiloft Obligation Management screens return these fields:

- **Responsible Party**: Lists the company name or description of the party responsible for the obligation.
- **Summary**: The answer to the Question Text in the question configuration. Maps to Answer in Obligation records.
- **Summary Standardized**: The meaningful value from the full answer in the Summary field. This is the key value that you might want to use for filtering, reporting, and automation.
- **Consequence**: A summary of the penalty or remedy for failing to meet the terms of the obligation.
- **Consequence Standardized**: The specific consequence, such as a fixed amount, percentage, or penalty/remedy. Like Summary Standardized, this field holds the key value that can be useful for filtering, reporting, and automation.
- **Trigger**:** **The specific event or condition that triggers the obligation.
- **Trigger Type**: The type of trigger: Event-based, Time-based, or Ongoing.

All fields are selected by default in new Metadata Type records. To hide fields in Obligation records for a metadata type, clear the checkbox next to the fields you want to hide. Select the checkboxes for fields you want to display. 

> ℹ️ **Example**
> ℹ️ 
> ℹ️ In the Obligation Management screens, the responses for some structured data fields are always blank. For example, some questions return null for Consequence, so there’s no need to display the Consequence field in the Obligation record for that question.
> ℹ️ 
> ℹ️ The SaaS Maintenance & Support question in the Obligations – SaaS Agreements screen returns only the Summary, Trigger Type, and Responsible Party. The other fields return null. To hide the null fields on Obligation records for SaaS Maintenance & Support, only the Summary, Trigger Type, and Responsible Party fields are selected in Standard Fields Visibility.

## > Macro (anchor)

Processing Target Fields

This field tells the system which types of fields to process the Summary Standardized and Consequence Standardized values to in an Obligation record. Since responses from Astra are in plain text format, they’re human readable but not interpretable by the system. That means they can’t be used for operations like filtering, automation, or reporting. To use the values in operations, they need to be processed to a typed field. The table below lists the options and describes the target data type, the structured data field the value is pulled from, and the format to prompt for.

| **Target Field** | **Data Type** | **Structured Data** | **Prompt Format** | **Notes** |
| --- | --- | --- | --- | --- |
| Amount | Floating Point | Consequence Standardized | Number with a decimal point | A monetary value in any currency. |
| Currency | Link to selected fields from other table: Currency | Summary Standardized | 3-letter currency code | The currency code for the amount. |
| Data Processing | Choice: Lawful Basis, Data Minimization, Purpose Limitation | Summary Standardized | One of the Choice values | For privacy law and contract compliance, this is the category under which a company can process data with permission. |
| Date | Date (Due Date field in Obligation) or  
Integer (Due in Days field) | Summary Standardized | Specific date or number (without a decimal point) that represents the number of days in the future | Makes the Date Type field visible on the Obligation record. A rule sets Date Type to Fixed or Relative depending on whether there’s a specific Due Date or Due in Days value. |
| Incoterms Code | Multi-Choice: EXW, FCA, FAS, FOB, CFR, CIF, CPT, CIP, DPU, DAP, DDP, Other | Summary Standardized | A value from the Multi-Choice list or multiple values separated by semicolons | International Commercial Terms in the contract. |
| Law/Regulation | Link to single field from other table: Law/Regulation | Summary Standardized | A code from the Laws/Regulations table or multiple codes separated by semicolons | The codes must exist in the Laws/Regulations table. Before extracting new codes, add the codes as records in the table. |
| Minimum Coverage Amount | Floating Point | Summary Standardized | Number with a decimal point | A monetary value. |
| Penalty/Remedy | Link to selected fields from other table: Penalty/Remedy | Summary Standardized | Text describing the penalty or remedy for obligation breach | If the extracted value doesn’t match a record in the Penalties/Remedies table, the value will be displayed in the target field in the Obligation record, but it won’t be a link. You can manually add a record for the new value. |
| Recurrence Frequency | Choice: Weekly, Bi-Weekly, Monthly, Bi-Monthly, Quarterly, Annually | Summary Standardized | Text from the Choice list | Describes how often the obligation recurs. If you need additional options, change the prompt in the screen and edit the choice list for the Reporting Frequency field in the Obligations table. |
| Timeframe | Integer | Summary Standardized | Number without a decimal point | The number of units. The unit of time is configured in the [Timeframe Units](#) field. |

You only need to select target processing fields when you want to use the data in Summary Standardized or Consequence Standardized for filtering, reporting, or automation. When a value exists only in a standard text field, users can read it but the system can’t. 

> ℹ️ **Example**
> ℹ️ 
> ℹ️ Summary Standardized contains the value “30” to represent a number of days. It looks like a number, but since the field is a plain text type, the value can’t be used in a report on obligation deadlines. Selecting Timeframe as the Processing Target Field processes the text into an integer the system can interpret and use in reports.

Typically, you only need to select one target field because only one of the standardized prompts returns a value. If both standardized prompts generate responses that you might want to use in operations, you can select multiple target fields. For example, you may want to process an Amount from Consequence Standardized and law or regulation from Summary Standardized. You can also select multiple target fields if one prompt has a conditional response that varies in data type. When multiple processing fields are selected, the system populates the appropriate target field based on the extracted text.

### > Macro (anchor)

Timeframe Units

This field is displayed when Processing Target Fields includes Timeframe. It defines the unit of time, like days, weeks, or months, to use for the timeframe values extracted for this question. Any structured data field prompts for this question should instruct AI to output the timeframe values in the selected unit.

> ℹ️ **Example**
> ℹ️ 
> ℹ️ Below is a portion of the Summary Standardized prompt for the Recurring Payments question in the Obligations - SaaS Agreements screen. The prompts tells AI to return the value in number of days:
> ℹ️ 
> ℹ️ If the Summary field contains a specific time period for when the obligated party must make payment (e.g., "within 15 days from the end of each month", "30 days after annual invoice"), convert that period into a number of days and output only the integer. (e.g. within 15 days from the end of each month = 15).
> ℹ️ 
> ℹ️ In the Metadata Type record for Recurring Payments, Timeframe Unit is set to Days.

## > Macro (anchor)

Yes/No Obligations

For existence checks, or yes/no obligations, the Yes or No response in Summary Standardized or Consequence Standardized is processed to the Obligation Exists field in the Obligation record. If Summary Standardized returns No or Summary Standardized and Consequence Standardized are both blank, Obligation Exists is set to No. In all other cases, the field is set to Yes. 

> ℹ️ **Example**
> ℹ️ 
> ℹ️ The Early Termination Penalties question in the Obligations – Termination screen is an example of a yes/no obligation. In Question Details, the instructions are to output Yes if there are early termination penalties or No if there aren’t. The prompt for Summary Standardized is, “If the Summary field is Yes, output Yes. If the Summary field is No, output No.” When the screen is run, Obligation Exists is set to Yes or No, depending on the value in Summary Standardized.
> ℹ️ 
> ℹ️ The Early Termination Penalties question is also set up to use the Consequence field to provide a summary of the early termination penalties if Summary is Yes. From the response in Consequence, the Consequence Standardized field captures the explicit penalty amount if it exists. In the Metadata Type record for Early Termination Penalties, Amount is selected as a Processing Target Field so an amount from Consequence Standardized is processed to the amount-related fields in the Obligation record.

# Views

The out-of-the-box Metadata Types table includes the [standard views](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718574). The Default View shows the Edit icon, View icon, ID, Source, Related To, Topic, Metadata Type, Standard Fields Visibility, Processing Target Fields, and Status fields.

![Default View for the Metadata Types table](media://b973ed9a-d628-4258-ba0b-aa8cecdbd3d8)

# Fields

In addition to the [standard fields](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434023), the out-of-the-box Metadata Types table includes the following fields.

| **Field Label** | **Data Type** | **Description** |
| --- | --- | --- |
| Metadata Type | Short Text | The data category for obligations. This value maps to the Subtopic field in Obligation records, Element Name in Screen Result records, and Question Title in the Obligation Management screens. |
| Processing Target Fields | Multi-Choice: Amount, Currency, Data Processing, Date, Incoterms Code, Law/Regulation, Minimum Coverage Amount, Penalty/Remedy, Recurrence Frequency, Timeframe | Controls which fields/data types the extracted Summary Standardized and Consequence Standardized values are parsed to. |
| Related To | Choice: Obligations | The type of extraction this metadata type relates to. |
| Source | Choice: AI Platform, GenAI Action, Screen, Other | System-managed field that lists the source that created the record. Currently, the source is always Screen. |
| Standard Fields Visibility | Multi-Choice: Summary, Summary Standardized, Consequence, Consequence Standardized, Trigger Type, Trigger, Responsible Party | Controls which of the standard fields returned by Astra should be displayed in Obligation records for this Metadata Type. For example, if a question always returns null for Consequence, you can deselect Consequence so it won’t appear as an empty field in Obligation records of this type.<br>> ⚠️ Do not change the list of multi-choice values. They map to the structure of the Astra output. |
| Status | Choice: Active, Inactive | The status of the metadata type. Can be used for filtering records. |
| Timeframe Units | Choice: Hours, Days, Weeks, Months, Quarters, Years, Percentage | Visible when Processing Target Fields includes Timeframe. This field defines the unit of time for the timeframe values extracted for this question. The structured data field prompts for this question should instruct AI to output the timeframe values in the selected unit. |
| Topic | Choice: Confidentiality, Data, Delivery, Financial, Insurance, Performance, Regulatory, Termination | Describes the type of obligation. The values map to the Obligation Type in the structured data output from Astra.<br>> ⚠️ Do not rename the choice list values. If Astra returns a new value, you can add that value to the list. |