---
title: "Attachments Table"
canonical: "https://help.agiloft.com/space/SDA2603/521276555/Attachments+Table"
format: markdown
---
The Attachments table stores all of the documents, and metadata about those documents, that are attached to Contract and Sourcing Event records. Features like contract analysis with AI, document comparison against previous versions, optical character recognition rules, and version control are implemented for the table.

# Record Creation

By default, users in the following groups can create Attachment records: ACA and AI Add-on Group, admin, Admin Import, Approver, Business Admin, Contract Admin, Contract Creator, Contract Manager, Contract Requester, Internal Supplier Manager, Legal, Project Manager, Response Evaluator, Sourcing Event Creator, Sourcing Event Manager, and Sourcing Event Requester. 

Attachments are typically created the following ways:

- By generating a document from a template or uploading a document in a Contract record
- By generating a document from a template or uploading a document in a Sourcing Event record
- By sending an attachment to that table via email, if inbound email is enabled for the table

The types of attachments that can be created for these records is controlled by records in the [Attachment Types Table](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521278442).

When a user uploads or generates a file and saves the record, an Attachment record is created to store that attachment. Users can open an Attachment record by selecting an attachment on the Attachments tab in a Sourcing Event or Contract record. If a user edits an attachment using Checkout to Edit, the edited document generates another Attachment record that is linked to the original record. When an attachment is a PDF, the file undergoes optical character recognition (OCR) through one of the default [rules](https://agiloft-public.atlassian.net/wiki/spaces/SSDRAFT/pages/44736333), and the OCR version of the file gets attached to the OCR File field under Background Fields on the History tab of the Attachment record. The sections below further describe the features of the Attachments table.

Attachment records are owned by the user who creates them. Specifically, Creator Login is set to the Login of the user who creates the record. For more information on record ownership, see [Record Ownership](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718158) in the Help Guide.

# Record Layout

This section gives a high-level overview of the out-of-the-box power user record layout. Each tab is listed below, with descriptions of the main features, action buttons, and fields included in the layout by default. For information on working with record layouts, see [Layouts](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43715914) in the Help Guide.

## Common Area and Contract Analysis

When you view the Attachment record for a contract, you have the option to analyze the attachment with AI. Analyzing a contract is useful when the document is from a third party or is a legacy document that was uploaded and wasn't generated from a document template. The feature uses AI to extract clauses from the file and add them to the [Contract Clauses Table](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521276953) as well as extract key terms that update the Contract record.

First, if the attachment is a PDF, you can click Predict Document Type to run an OCR action that creates a searchable version of the PDF for analyzing. Then, to analyze the document, click Analyze Contract. 

![Common area showing the Analyze Contract and Predict Document Type](media://4a3273ab-bf32-44be-b4ad-590e0bc00e50)

The system runs a rule that analyzes the contract, extracts key terms and clauses, and pushes the extracted data back to the parent record. You can view the results of the analysis on the Attachment Details tab. The list below describes the Document Analysis fields.

![Attachment Details tab showing Document Analysis](media://e1968582-69ac-4c84-b783-040c79232fa8)

- **DA Status**: Displays the status of the analysis.
  - Queued means contract analysis was initiated and the process is pending.
  - Failed means contract analysis failed with an error. The Error is displayed in the DA Error field.
  - Processed means contract analysis completed successfully. Any errors are captured in the DA Error field, and annotations are displayed in the Annotations JSON field.
  - Processing means contract analysis is in progress.
- **DA Error**: Displays any errors that were encountered as well as informational messages like which labels were excluded. By default, the rule analyzes the contract against all labels in the [Label Library Table](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521279384), and some labels may not apply based on the document's contents.
- **Annotations JSON**: Displays the annotations for the document so you can review the extracted key terms and clauses.

## Document Comparison

If the "Attachment Type can be used in comparisons" field in the [Attachment Type](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521278442) record is set to Yes for the attachment, the Attachment record includes the Document Comparison tab. The document comparison feature enables you to compare the current version of the attachment against the most recent previous version or compare the current version of the attachment against the original or baseline version.

![Document Comparison tab](media://bc9e61ed-f436-4b6e-a47d-c1b70f1ade06)

### Compare Against a Previous Version

With this option, you can compare the current version of the attachment with any previous version of the document. This feature is extremely helpful since users can edit attachments directly. When a user does edit a document, a new Attachment record for the edited version is created automatically by a rule. This new Attachment record contains the previous version in the Previous Attachment field and the newly edited version of the document in the Attached File field.

Selecting an attachment in the Previous Attachment field populates the Previous Attached File field with the version of the document that was selected. To run the comparison, click Compare to Previous Version. If there aren't any changes, the File Changed? field is set to No. If there are changes, a marked-up version of the file is created and attached in the Markup File field. The markup file shows all of the edits between the compared versions.

### Compare Against Baseline

The baseline file is the original version of the document. For example, it is the first file that was generated from a document template or attached to a Sourcing Event or Contract record. The Baseline File filed is automatically populated when an attachment is edited. Clicking Compare to Baseline and Update Contract Clauses compares the version of the attachment in the record you have open to the baseline version of the document. A marked-up file is generated and stored in the Markup Against Baseline File field. This file shows redlines between the current version and the baseline.

## Version Control

The Version Control tab presents options that allow users to supersede previous versions of an attachment or re-activate a previous version to make it the current version. For example, a revised version of a supporting document for a Contract is sent via email. That revision is intended to replace the current version of the document attached to the Contract record. A user can open the Contract record, go to the Attachments tab, and select the new attachment to open its Attachment record. From the Version Control tab in the Attachment record, the user selects the previous attachment in the Select File to Supersede drop-down list then clicks Supersede File. The previous version is now superseded by the new version as shown on the Attachments tab for the Contract. In addition, flags like Include in Approval Packet are automatically set to No for the superseded file.

![Attachments tab in a Contract record showing a superseded attachment](media://7eaffee5-43ca-4278-baee-482d6715e382)

If a contract document is regenerated in the Contract record, the newest version automatically supersedes the previous version.

For superseded attachments, the Version Control tab displays the current version of the attachment and presents an option to make this attachment the current version. 

![Version Control tab for a superseded attachment](media://d8fdc13a-7e3c-43ad-90a5-7d01a0ffad82)

## History and Docusign Signatures Page

For Docusign users, there’s is a Merged File field and a Merge Signature Block button under the Background Fields section on the History Tab. Clicking Merge Signature Block appends a signature page to the file in the Attached File field and the merged file is added to the Merged File field. The action button uses an attached file action and an MS Word template signature page. The signature page is specially formatted to include DocuSign tags. A rule then converts the file in the Merged File field into a new Attachment record and resets the Merged File field to empty.

# Views

The Default View for the out-of-the-box Attachments table shows the Edit icon, ID, Attachment Type, Status, and Attached File fields.

![Default View for the Attachments table](media://571f7691-8ca8-43d7-9230-0d058b527666)

In addition to the Default View and other [standard views](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718574), the Attachments table includes several views for displaying the linked attachments table in Contract and Sourcing Event records:

- **Default Tree View**: This view contains the same columns as the Default View but displays the Attached File in a tree view if there are multiple versions of the attachment. For example:
- **Detail View**: This view presents details that include the same columns as the Default View plus the Date Created, Created By, Status, Related To, Contract ID, Sourcing Event ID, Previous Attachment ID, and Document Template ID fields.
- **Report View - Insurance Certificates**: The default view for the linked attachments table in the Active Insurance Certificates Expiring Within 60 Days report.
- **Report View - Performance Bonds**: The default view for the linked attachments table in the Active Performance Bonds Expiring Within 60 Days report.
- **View in Approvals - Contract**: The default view for the linked attachments table on the Contract Details tab in Approval records for Contracts.
- **View in Approvals - Sourcing Events**: The default view for the linked attachments table on the Sourcing Event Details tab in Approval records for Sourcing Events.
- **View in Attachments - Superseded Attachments**: The default view for the linked attachments table under Previous Documents on the Version Control tab in Attachment records with superseded files.
- **View in Contract**: The default view for the linked attachments table on the Attachments tab in Contract records.
- **View in Contract Signature**: Default view for the linked attachments table on the Signature tab in Contract records.
- **View in Sourcing Events**: The default view for the linked attachments table on the Attachments tab in Sourcing Event records.

# Saved Searches

The out-of-the-box Attachments table includes some saved searches that are used by rules. The following saved searches are available in the table menu by default:

- **My Active Attachments**: Finds records with a Status of Active that are created by the user who runs the search.
- **My Attachments**: Finds all records that are created by the user who runs the search regardless of the record's status.

# Fields

In addition to the [standard fields](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521273545/Table+Concepts#standard_fields), the out-of-the-box Attachments table includes the following fields.

| **Field Label** | **Data Type** | **Description** |
| --- | --- | --- |
| 1st Party Signer Name  
1st Party Signer Title  
2nd Party Signer Name  
2nd Party Signer Title  
Attachment Types Required for Contract Approval  
Attachment Types Required for Contract Review  
Company Fingerprint  
Contract Party ID  
Contract Party Name  
Contract is Confidential  
Contract Amount  
Contract Description  
Contract End Date  
Contract Manager  
Contract Manager ID  
Contract Start Date  
Contract Title  
Contract Type  
Contract Type AI Document Type  
Contract Department ID  
Document Source  
Contract Document Template ID  
Contract Department  
Contract ID  
Internal Signer  
Internal Signer Title  
People who can view Contract  
Contract Requester ID  
Contract Requester Name  
Roles that can view Contract  
Contract Status | Link to selected fields from other table: Contracts | For records related to Contracts, these fields store information about the contract. Some of these fields are displayed under Contract Information on the Related Info tab in the Attachment. |
| ACA Update | Choice:<br>- Yes
- No | This flag is used as a conditional filter for triggering certain rules. It's set to Yes when an attachment is edited with an Agiloft Contract Assistant application. Defaults to No. |
| Add to Approval Packet | Action button | Adds the document to the Approval Packet by changing Include in Approval Packet to Yes. |
| Add to DS Packet | Action button | Adds the attachment to the DocuSign Packet by setting To be eSigned to Yes and updating DocuSign Files to Sign in the Contract record. |
| AI Document Type  
AI Document Type ID | Link to selected fields from other table:  
AI Document Type | Identifies the AI document type of the attachment. |
| Adobe Sign Envelope ID | Short Text | The envelope ID mapped from the Adobe Sign conversion of the signed document. |
| Annotations JSON | Text | Stores the annotations generated by AI when a contract is analyzed. |
| Attached File | File with Versioning | The file attached to the record. If the file is a PDF, a rule runs OCR on the file and adds the OCR version of the document to the OCR File field. |
| Attachment Title - Date Created - Created By | Text | The title of the attachment with the date created and created by values appended to it. This field is used to differentiate attachments that have the same title. You can modify the formula to output any text string. |
| Attachment Type  
Attachment Type can be used in comparisons  
Default Publication Level  
Attachment Type Fields to Show  
Attachment Type ID  
Default Include in Approval Packet  
Default Include in Merge  
Default Show in Supplier Responses  
Default Include in DocuSign Envelope | Link to selected fields from other table: Attachment Types | These fields identify the attachment type and default settings for the type. |
| Baseline Contract File  
Baseline Contract File ID | Link to selected fields from other table: Attachments | Stores the original output of the document template, which is used for comparisons against subsequent versions of the document. |
| Button: Analyze Contract | Action button | Sets Trigger Extraction to Yes, which triggers a rule that runs document analysis with AI. The AI extracts key terms and clauses from the contract and adds the clauses to the [Contract Clauses Table](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521276953) . Annotations are stored in the Annotations JSON field. |
| Button: Compare to Baseline and Update Contract Clauses | Action button | Compares the attached file to the baseline version. A marked-up file is generated and stored in the Markup Against Baseline File field. The file shows redlines between the current version and the baseline. |
| Button: Compare to Previous Version | Action button | Compares the previous version of the file to the current version. If there are changes, a marked-up version of the file is created and attached in the Markup File field. The markup file shows all of the edits between the compared versions |
| Button: Convert to PDF | Action button | Converts the attachment to a PDF. |
| Button: Convert to Word | Action button | Converts the attached PDF to a Word document. |
| Button: Create Revision | Action button | Sets Trigger Creation of Revision to True. Used as a backup in case the system fails to create a revision record after a user opened the file in Word and possibly didn't save or close it. This option performs the same actions that would be performed if the user opened a file for editing, changed and saved the file, and then closed the file. |
| Button: Document to KB | Action button | Syncs the key terms from the attached contract document to the linked Contract record. |
| Button: Generate Candidate Clauses | Action button | Uses AI to extract clauses from the attached contract document. The extracted clauses in JSON format are added to the Candidate Clauses JSON field. |
| Button KB to Document | Action button | Syncs the key terms from the linked Contract record to the attached contract document. |
| Button: Make This Attachment Current Version | Action button | Makes the attachment the current version and marks other versions Superseded. |
| Button: Predict Document Type | Action button | Uses an AI model to predict the type of contract the attachment is. The action first checks the file type of the attachment. If it's a PDF and OCR hasn't been run, OCR is performed. |
| Button: Publish | Action button | Publishes extracted data in Annotations JSON to the contract document. |
| Button: Select For Signature | Action button | Sets the To Be eSigned flag to Yes. |
| Button: Set as Baseline | Action button | Sets the current version of the file as the baseline. |
| Button: Supersede File | Action button | Supersedes the attachment and clears the replacement fields. |
| Button: Update Data in Contract Record | Action button | Visible when Meta Data Synced Back to Contract is No. Sets the field to Yes to trigger a rule to update the Contract record. |
| Candidate Clauses JSON | Text | Stores the extracted clauses from the Generate Candidate Clauses action. |
| Clause Pushback Log | Text | Logs information about the extracted clauses that are added to the Contract Clauses table during document analysis. |
| Clauses Synced Back to Contract | Choice:<br>- Yes
- No | This field is for future use. |
| Compare 1st version to previous version | Action button | Compares the current attachment to the preceding version. |
| Contract Request ID | Link to selected fields from other table: My Contract Requests | For attachments that originate from Contract Requests. All conversions are performed from the Contracts table, and Contract Request ID is mapped as part of that conversion. There are no direct conversions from Contract Request to Attachment. |
| Coverage Amount | Currency | Visible if Attachment Type Fields to Show is Insurance Certificate. |
| Current Version  
Current Version ID  
Current Version Title | Link to selected fields from other table: Attachments | For Contracts and Sourcing Events, these fields are used for attachments that have a Status of Superseded. |
| DA Error | Text | Displays any errors that were encountered during document analysis. Also includes informational messages, such as labels that were excluded. |
| DA Status | Choice:<br>- Queued
- Failed
- Processed
- Processing | The system-managed status of the AI document analysis.<br>- Queued means contract analysis has been initiated for the attachment and the process is pending.
- Failed means contract analysis failed with an error. The Error is displayed in the DA Error field.
- Processed means contract analysis completed successfully. Any errors are captured in the DA Error field, and annotations are displayed in the Annotations JSON field.
- Processing means contract analysis is in progress. |
| Data Pushback Log | Text | This field is used to store log information when metadata is pushed back to a contract. |
| Document Template ID  
Document Template Title  
Document Template Uses Clauses | Link to selected fields from other table: Document Templates | For attachments generated from a document template, these fields identify the template. |
| DocuSign Envelope ID | Link to selected fields from other table: DocuSign Envelopes | The envelope ID mapped from the DocuSign conversion of the signed document. |
| Expiration Date | Date | The expiration date for the attachment. Visible if the Attachment Type Fields to Show contains Expiration Date. |
| Extracted Clauses | Related Table: Contract Clauses | Lists the clauses that were extracted from the contract after contract analysis is performed. |
| Extracted Company Fingerprint | Long integer field | If the document source is a third party, this field stores the company fingerprint. |
| File Changed? | Choice:<br>- Yes
- No | Flag set by the document comparison action documents are compared. |
| File is OCRd | Choice:<br>- Yes
- No | Flag that indicates whether OCR was run on the file. Set to Yes when the OCR action runs. Used to prevent the action from running again. |
| File Name Compound | Compound | This field is used to set a document title if it is blank. |
| File to Supersede  
Select File to Supersede  
File to Supersede ID | Link to selected fields from other table: Attachments | Specifies the file to be superseded by the current file. |
| Ignore Next Edit | Choice:<br>- Yes
- No | If the Attachment record is created without an Attached File, this flag prevents rules from running until a file is attached to the record. This scenario typically occurs when a file is created through the Word app. |
| Include in Approval Packet | Choice:<br>- Yes
- No | For Contract record attachments, this field Indicates whether the attachment should be added to an Approval Packet. Default is Yes. |
| Include in Merge | Choice:<br>- Yes
- No | Flag for Contract and Sourcing Event records that indicates whether an attachment should be included in a merged package. If an attachment is superseded, this flag is automatically set to No on the superseded attachment. |
| Latest AI Project ID | Link to single field from other table: AI Projects | The AI Project ID for files that were imported with AI. |
| Markup Against Baseline Contract File | File with Versioning | Stores the marked-up version of the file that shows the differences between the current version and the baseline version. |
| Markup File | File with Versioning | Stores the results of the document comparison action that is initiated by the Compare Documents action button. |
| Merge Signature Block | Action button | Merges in the signature block to the attached file, creating a new file in the Merged File field. |
| Merged File | File with Versioning |  |
| Meta Data Synced Back to Contract | Choice:<br>- Yes
- No | Flag that indicates when data needs to be synced back to the Contract record. |
| OCR Evaluation Result | Choice:<br>- No Language Detected
- Grammar Check Failed
- Multilanguage Document
- Check Passed
- OCR Needed
- Unsupported Language
- Bad Document | Stores the result from the OCR action. |
| OCR File | File with Versioning | Stores the OCR version of the PDF after the OCR action completes. |
| PDF Version | File with Versioning | Stores the PDF version of the file after the conversion from .docx to PDF. |
| Previous Attached File  
Previous Attachment  
Previous Attachment ID  
Previous Attachment Title | Link to selected fields from other table: Attachments | These fields identify the previous version of the attachment. |
| Previous Versions | Related Table: Attachments | For Contracts and Sourcing Events, this field displays the list of attachments superseded by the current version. |
| Publication Level | Choice:<br>- Public
- Contract Managers Only
- Internal | Used in permission filters to define which groups have access to the attachment record. Defaults to Internal.<br>- When Public, all groups have access.
- When Contract Managers Only, only the Contract Manager group has access.
- When Internal, all internal groups have access. |
| Related Approvals | Related Table: Approvals | This field is used to apply permissions to attachments for the approvers group based on whether the attachment is in an approval the user is assigned to. |
| Related To | Choice:<br>- Contracts
- Sourcing Events | Designates the type of record the attachment is linked to. |
| Remove from Approval Packet | Action button | Removes the attachment from the Approval Packet by setting Include in Approval Packet to No. |
| Remove from DS Packet | Action button | Removes the attachment from the DocuSign Packet by setting To be eSigned to No and updating the DocuSign Files to Sign in the Contract record. |
| Replaced File? | Choice:<br>- Yes
- No | This flag indicates whether the current file replaces a previous version of the file.<br>- When Yes, the current file is flagged as a replacement for the previous version.
- When No, the current file is not flagged as a replacement. |
| Roles that can view Attachment | Link to single field from other table: Roles | This field is used for confidentiality-related access restrictions. Values are set by the rules when confidentiality settings change in the source contract. Created as a separate field to enable "overlaps with" operator when creating saved searches. |
| Set Status to Superseded | Action button | This is an option under File Actions in the related table view of attachments in the parent record. It sets the attachment status to Superseded for the selected documents. |
| Show in Supplier Responses | Choice:<br>- Yes
- No | For Sourcing Events, this field determines if this attachment appears in the list of Published Documents from the Supplier Response. |
| Similarity between extracted company and similar company | Floating Point | Stores the calculated similarity value for third party contracts that are analyzed by AI. |
| Sort Order | Floating Point | Used to define the order of attachments when merging contract and sourcing event documents. Also used to define the order of documents in an AdobeSign envelope for contracts. |
| Source Attachment Type ID  
Source Attachment ID for Revision | Link to selected fields from other table: Attachments | Mapped in conversion when a revision is created. |
| Sourcing Event Department ID  
Sourcing Event Department  
Sourcing Event ID  
Sourcing Event Publicity Level  
Sourcing Event Facilitator  
Sourcing Event Facilitator ID  
Sourcing Event Title  
Sourcing Event Type  
Sourcing Event Status | Link to selected fields from other table: Sourcing Events | Links an attachment to a Sourcing Event record. Visible if Related To is Sourcing Events. |
| Status | Choice:<br>- Active
- Superseded
- Expired
- Contract Inactive
- Sourcing Event Canceled | The status of the attachment. Defaults to Active. |
| Superseded by Attachment ID | Link to selected fields from other table: Attachments | Lists the Attachment ID for the attachment that supersedes this record. |
| Supersede Old Versions | Choice:<br>- Yes
- No | Flag that indicates whether to set the Status of previous versions of the same attachment to Superseded. |
| Test Clause Pushback | Action button | Admin-only action button that can be used to sync clauses marked as changed from the attached document to the Contract record. Key terms are not synced. |
| Title | Short Text | The title of the Attachment record. |
| Title for Merged File | Short Text | The title to use for the file that is generated by merging files. |
| To Be eSigned | Choice:<br>- Yes
- No | This field is used to flag attachments that should be included in the DocuSign envelope. Default is No. |
| Trigger Creation of Revision | Choice:<br>- Yes
- No | Flag that is set to trigger the creation of a revision if it fails the first time. |
| Trigger Extraction | Choice:<br>- Yes
- No | Set when the Analyze Contract button is clicked. Triggers the rule that runs document analysis. |
| Trigger Import Action | Choice:<br>- Yes
- No |  |
| Trigger Pushback to Contract | Choice:<br>- Yes
- No | Flag that triggers syncing extracted data from document analysis back to the contract. |
| Type of Certificate | Choice:<br>- Other
- Excess Liability
- Employer's Liability
- Auto
- Worker's Comp
- Professional Liability
- Pollution Liability
- General Liability | Visible if Attachment Type Fields to Show is Insurance Certificate. |
| Version 1 markup against baseline | File with Versioning | Stores the first revision of the attachment. |
| Word Version | File with Versioning | Stores the Word version of the attachment after conversion from PDF to Word. |

# > Macro (anchor)

Automation

This section describes the rules that are implemented for the out-of-the-box Attachments table. For details about rule configuration options, see [Rules](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714473) in the Help Guide. The following rules automate attachment processing:

- **Edit: Create new revision document (web)**: For Contract and Sourcing Event attachments, this rule runs to create a new record when a .docx attachment is edited.
- **Create/Edit: Analyze Document and Publish Data to Contract (web, API)**: This rule runs when an attachment is created or edited. For records where the Trigger Extraction field is set to Yes, which is the case for records where the Analyze Contract button was clicked, the rule performs the following actions:
  - If the attachment is a PDF and optical character recognition (OCR) hasn't already been performed, it runs OCR and adds the file to the OCR File field.
  - If the attachment is a .docx file, it adds the file to the Attached File field.
  - Performs document analysis on the OCR File or Attached File, extracting key terms and clauses. Extracted clauses are added to the [Contract Clauses Table](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521276953) and annotations from the latest analysis are added to the Annotations JSON field.
  - Unlinks the existing contract clauses and publishes the newly extracted data to the contract.
- **Create: Identify Document: (web, API, email)**: This rule runs when a record is created. For .pdf, .xlsx, and .docx attachments, the rule runs an Identify Document action that checks whether the new record is an update to an existing attachment. If it is, it changes the Status of the previous version to Superseded.
- **Create: All create actions except OCR (web, API)**: This rule runs when an attachment is created, edited, or deleted. It updates various flags that trigger other actions:
  - If Title contains "with Signature Block," it sets the To Be E-signed field to Yes.
  - For any records where To Be E-signed is set to Yes, the Contract Update DS Files flag is set to Yes, which runs a separate rule in Contracts.
  - If Supersede Old Versions is Yes, it changes its status to Superseded.
  - Updates the Attachment type and Title of signed contracts.
  - Creates Contract Clause records on first revision.
- **Create: Add identification tag (web, API, email)**: This rule runs when a record is created. For .docx, .xslx, and .pptx attachments, it adds the Source UUID value if it’s blank.
- **Edit: Handle To Be Signed changes and Superseding (web, API)**: This rule updates the Include in Approval Packet file and To Be E-signed fields to No when an attachment's status is changed to superseded. It also updates Contract Update DS Files Flag to Yes.
- **Edit: Convert Merged File (web, API)**: This rule runs when an attachment is edited. It converts any merged files into new attachment records.
- **TB: (DISABLED) Notify Internal Contract Owner 30 days in advance of expiration**: This time-based rule is disabled by default and is configured to find attachments that expire within 30 days. For records that meet the criteria, it emails the Contract Manager to notify them of the upcoming expiration.
- **TB: (DISABLED) Handle Attachment Expiration**: This time-based rule is disabled by default and is configured to find attachments that expire today. For records that meet the criteria:
  - It sets the attachment Status to Expired.
  - Emails the Contract Manager about the expired attachment.
  - Sets the linked Contract Status to Inactive.
- **TB: (DISABLED) Daily - If Contract Status is not inactive and Status is Contract Inactive, reset Status of Attachment**: This time-based rule is disabled by default and is configured to find Attachment records with a Status of Contract Inactive where the linked Contract is not Expired, Canceled, or Terminated. For records that meet the criteria, it sets the Attachment Status to Expired and emails the Contract Manager to notify them of the expiration.
- **Edit: Run OCR action (web, API) if file changes**: This rule finds PDF and image attachments that were edited and runs an OCR action to convert the file into a searchable PDF document.
- **Create: OCR file (web, API)**: When PDF and image attachments are created, this rule runs an OCR action to convert the file into a searchable PDF document and appends _ocr to the filename.
- **Edit: When marked up baseline changes, Document template Uses Clauses not no, contract related, and not already done by addin, update contract clauses (web, API)**: This rule finds contract attachments that include clauses that are marked up against the baseline version. It syncs the modified clauses to the KB.
- **Edit: If Attached File has a value, set Ignore Next Edit to No (web, API, email)**: This rule runs when an attachment is edited. It finds records that include an attachment but have the Ignore Next Edit flag is set to Yes, which can happen if an Attachment record was originally created without an attachment and the attachment was added later. It sets Ignore Next Edit to No so the attachment will not be ignored by other rules.