Go back to the Release Notes Hub
Welcome to Ironclad's Release Notes! This article highlights Ironclad’s new feature releases and existing feature updates. We update release notes the Monday of each release. Generally, each week's features are available to test in your demo environment by end-of-day Monday. The features are then added to your production environment by end-of-day Wednesday.
If you are interested in Ironclad CLM API updates, refer to the Ironclad API Changelog. Want to be updated about the latest and greatest changes to Ironclad's APIs? In your favorite RSS reader, add this link to subscribe for updates.
If you have questions about any of these features, submit a request with our Support Team.
September 25, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Error Messages in Smart Import |
Product Area |
CLM
Repository
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Smart Import will now show descriptive errors if the file type is unsupported, the file is encrypted, or if the import was cancelled by a user. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Ironclad Signature Non-Latin Font Support |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Ironclad Signature now supports additional fonts for Chinese, Japanese and Korean characters. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Workflow Designer “Reverted to Review” Formula Field Support |
Product Area |
CLM
Workflow Designer
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins |
Description |
Workflow Designer now features a new Workflow Metadata formula field called ‘Reverted to Review’ which indicates whether at any point during the workflow, a user returned to the Review step from the Sign step. |
Use Case |
Reverted to Review Fallback Approver (commonly used with Public Workflows and NDAs) Consider a workflow with no configured approvers that goes directly out for signature after launch. Previously, if the workflow returned to the review step (e.g., the signer declined to sign), the ‘fallback’ approver would automatically be the Workflow Owner. Now, you can set a conditional approver using the Reverted to Review formula field. This approver would not be triggered at initial launch, but would be the ‘fallback’ approver if the workflow ever returns to the Review step. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
Feature Name |
Delete Workflows |
Product Area |
CLM
Workflows
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
If you are a company administrator, you can permanently delete a workflow, removing the workflow, its metadata, and Repository record from Ironclad. The workflow must be canceled before you delete it. This action cannot be undone. You cannot recover a deleted workflow. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
September 18, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Reassign Workflows Upon User Deletion in SCIM |
Product Area |
CLM
Workflows
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
When an Ironclad user is deleted via SCIM, we now automatically reassign all of their associated workflows to your default company admin. This prevents workflows from getting stuck or lost. Your admin can then reassign and delegate workflow tasks to other team members in Ironclad. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name | |
Product Area |
CLM
eSignature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Users with access to Workflow Designer can assign a signer to text properties. Once assigned, the information provided by the signer will be captured as metadata and used in Ironclad Repository, Insights, and more. This is available for Ironclad Signature, and supported 3rd party eSignature providers. |
Use Case |
An Ironclad admin is building a workflow and wants to capture their signers’ addresses and sync them back to their CRM where they maintain their contract's record. To optimize the signer's experience, the admin wants to capture the address when the signer is signing rather than in the launch form. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
September 11, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Upload Signature |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Using Ironclad Signature, signers can now upload an image of their signature. This image will be used in place of a manually entered signature throughout the document. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name |
Sync Null Values from Salesforce |
Product Area |
CLM
Integrations
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
The Ironclad Salesforce integration now syncs empty/missing field values from Salesforce to the mapped fields in Ironclad. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
September 4, 2024
Feature Name |
Copy Signing Links |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
You can now copy a recipient's unique signature packet signing link. This is the same link Ironclad automatically emails to signers and viewers. This enables you to send the signature packet to signers through methods outside of Ironclad such as text or chat. |
Use Case |
An Ironclad user has a workflow move into the Sign step. They want to send the first signer the signing link via text message. They copy the signer’s unique signing link and texts it to them. |
|
|
How to Enable |
An admin must enable this feature. To enable this functionality, navigate to Company Settings > Settings and toggle on Allow users to copy signer links. Once enabled, you can configure access on a per-workflow basis in the Workflow Configuration’s Sign step settings. |
Relevant Resources |
|
August 21, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Automatic Renewal Opt-Out Dates |
Product Area |
CLM
Workflows
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
In addition to maintaining the Expiration Date in the lifecycle preset, Ironclad will also maintain the Renewal Opt Out Date by using the Renewal Opt-Out Period. When the expiration date in the Repository is changed as a result of an auto-renewal, optional extension, or metadata edit, the renewal opt-out date will be recalculated using the opt-out period. If a Renewal Opt-Out Period is not provided but an Opt-Out Date is, then the renewal term length will be used to move the Opt-Out Date forward when the contract Auto-Renews or is Extended. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
Feature Name |
AI Playbooks & Smart Import Clause Data Improvements |
Product Area |
CLM
AI
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
We've updated AI Clauses’ search to prioritize clause names, followed by relevant hits in descriptions. Previously, searches only covered descriptions. We also visually improved the AI Clauses page. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
Feature Name |
Workflow Designer Duration Format with Both Text and Numeral |
Product Area |
CLM
Workflow Designer
|
Impact of Change |
Additional Functionality |
Roles Impacted | Admins |
Description |
Previously Duration tags in Workflow Designer could be formatted as either Text (“two years”) or Number (“2 years”). Duration tags now support a third option: Both. This allows for the common contract convention of the number written as text followed by the numeral in parentheses. For example, “two (2) years”. |
Use Case |
Format the Initial Term Length lifecycle property on the document template as both to print it as “twelve (12) months” on the contract. |
Notes |
• This format is available as the “Both” option for Duration field tags on templates in Workflow Designer. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
Feature Name |
Workflow Designer In() Formula Support for Boolean (Yes/No) and Number Lists |
Product Area |
CLM
Workflow Designer
|
Impact of Change |
Additional Functionality |
Roles Impacted | Workflow Design Admins |
Description |
Workflow Designer features an In() formula function that can determine whether a certain value exists within a list. This is commonly used alongside the GetColumn() function to determine whether a specific Text value exists within a Text column of a Table.
|
Use Case |
For example, when a workflow has a Products Table, one common Column field is the Product SKU. If you want to check whether a specific product is included in this contract, you would use the In() formula to check whether “SKU-123” is in the Product SKU column of the Products table. In(GetColumn([Products Table], [Product SKU]), “SKU-123”) This might be used as a condition to show an applicable clause in the contract when that particular product is included. Similarly, if there is a Column field for “Requires Additional Signature” that is of type Yes/No, you can now use the In() formula to check whether that value is true for any of the rows in your Table and include an additional signer if so. |
Notes |
• The In() formula now supports Text lists, Yes/No lists, and Number lists. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
August 14, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Improved AI Clauses UI and Search |
Product Area |
CLM
AI
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
We've updated AI Clauses’ search to prioritize clause names, followed by relevant hits in descriptions. Previously, searches only covered descriptions. We also visually improved the AI Clauses page. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
Feature Name |
Bug Fix: Clickwrap Records with Address Now Sync To Repository |
Product Area |
CLM
eSignature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Previously, Clickwrap records did not sync to the CLM Repository if the address was part of the record sync. We have resolved this, and records with addresses will now be added to the Repository as intended. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources | No relevant resources at this time. |
Feature Name |
Users Without Send Directly for Signature Permissions Can Access and Edit Groups |
Product Area |
CLM
Permissions
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Previously, users with Users & Groups Administration permissions, but without Send directly for Signature permissions could not access or edit groups. We have resolved this so users with Users & Groups Administration permissions, but without Send directly for Signature permissions can now view and edit groups. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
August 7, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Improved Coupa Error Text |
Product Area |
CLM
Integrations
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
We have improved Coupa errors to be clear and actionable. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources | No relevant resources at this time. |
Feature Name |
RunAI Beta - Update Repository with Custom Clauses |
Product Area |
CLM
AI
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
If you are enrolled in the RunAI beta program, you can now refresh your Repository using AI custom clauses. If you add, delete, or modify samples in your custom clauses, you can then use RunAI to update your Repository clause records. |
How to Enable |
This feature is automatically enabled for customers enrolled in the RunAI Beta program. If you are interested in this functionality, reach out to your Ironclad representative. |
Relevant Resources |
No relevant resources at this time. |
July 31, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Contract Statuses and Auto Renewals |
Product Area |
CLM
Workflows
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
We are excited to announce the release of contract statuses and auto renewals! Contract statuses indicate whether a contract is Active or Inactive in addition to more detailed sub-statuses such as Evergreen, Auto-Renewing, or Expiring. The contract status information is presented in a status pill, which is visible across Ironclad wherever contracts are visible. This includes the Dashboard, reminders, and contract relationships search. The contract status is automatically populated and updated based on the effective date, expiration date, and auto-renewal type. Contracts that are marked as auto-renewing are truly auto-renewing in the Ironclad system. The renewal type for an agreement will govern what happens on its expiration date if it has one. For records where the Renewal Type property has a value of Auto-Renew, their expiration date will automatically be moved forward by their renewal term, up to the maximum number of allowed auto-renewals set in the contract. |
Use Case |
An Ironclad user has added the Lifecycle Preset to all of their existing workflow configurations. They want to know if a specific contract is Auto-Renewing. They locate the contract’s corresponding record in the Repository and can see that the record is Auto-Renewing at 180 days. They hover over the contract status pill to see the date it will auto-renew. |
Notes |
|
How to Enable |
If you were an Ironclad customer prior to September 13, 2023, an admin must enable this feature. To enable this functionality, navigate to Company Settings > Settings and toggle on Contract lifecycle. You must add the Lifecycle Preset to your workflow configurations before turning on this feature to ensure the statuses are accurate. |
Relevant Resources |
|
Feature Name |
Contract Status Actions |
Product Area |
CLM
Workflows
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
With the launch of the contract statuses and lifecycle features, all contracts in Ironclad reflect their current status across the product. |
Use Case | An Ironclad user processes an account termination. They locate the corresponding account’s record in the Repository. They click the contract status pill and select Terminate contract. They relate the record that contains the associated termination notice letter. |
Notes |
|
How to Enable |
While this functionality is automatically available for all users, you must manually enable contract statuses to use status actions. |
Relevant Resources |
|
July 24, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Add Weak Examples to AI Custom Clauses / Add Up to 20 Examples to Each AI Custom Clause |
Product Area |
CLM
AI
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
You can now add examples with a ‘weak’ training impact to AI custom clauses. You can add up to 20 total examples per AI custom clause. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name | |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
When you are sending a document out for signature from the Dashboard, you can share a copy of the signature request and completed signature packet to any email, Ironclad user, or Ironclad group. |
Use Case | An Ironclad Signature user is sending a document straight for signature. The user selects individuals or groups with whom to share a view-only version of the signature packet. The user could add an internal group like Legal, a counterparty point-of-contact, or any other internal or external party that needs to know about the signature packet, but is not a signer themself. During the Add Signers step, they toggle on ‘Share a copy’ and add the relevant users. A copy is sent to the added recipients. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
July 17, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Separate Upload Step When Sending Directly for Signature |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
UI/UX Change |
Roles Impacted | Admins and End Users |
Description |
When you send a document directly for signature from the Dashboard, the Upload step is now split from the Add Signers step. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Clear Signature Inputs in Ironclad Signature |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
When using Ironclad Signature to sign a contract, if a signature or initial signer tag is populated, you can clear it by deleting the text field and applying your signature in the modal, or by selecting the trash icon. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name |
Click-to-Accept Upgrade |
Product Area |
CLM
Click to Accept
|
Impact of Change |
Process Change |
Roles Impacted | Admins and End Users |
Description |
We’re upgrading Click-to-Accept! This release brings the classic Click-to-accept experience into Ironclad Signature, introducing new functionality to simplify administration and improve the signing experience. These features include:
|
Notes |
|
How to Enable |
No action required. If you are currently using custom email branding, your account will not be upgraded. |
Relevant Resources |
|
Feature Name |
Security and Data Pro |
Product Area |
CLM
API
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins |
Description |
Ironclad is offering a new add-on to the CLM platform. The Security & Data Pro add-on provides advanced security and data solutions, enabling you to add extra layers of trust, compliance, and governance to your mission-critical apps. The Security and Data Pro package includes the following features:
|
Notes |
This package requires a technical admin to implement it. |
How to Enable |
Reach out to your Ironclad representative to learn more about enabling this functionality. |
Relevant Resources |
|
Feature Name |
Enable API User to Use POST/Workflow in Multipart Format |
Product Area |
CLM
API
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins |
Description |
Developers using the API can now use the 'data' field to include existing JSON data and use 'form-data' to include file information in the POST /workflow API request. |
How to Enable |
No action required. Automatically enabled for all API users. |
Relevant Resources |
|
July 10, 2024
At a Glance
This week's release includes the following features:
- Autosave Activity Feed Comments
- Clause Approvers Display in the Approvals Section of a Workflow
- Lifecycle Preset
- Data Manager
- Connected Properties
- Signature Tag Size Rendering Consistently
- Remove Ironclad Signature (Legacy) from Integrations Options
- Send for Signature in Sandbox Mode Requires Ironclad Signature
Feature Name |
Autosave Activity Feed Comments |
Product Area |
CLM
Workflows
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
When you are drafting a comment in the Activity Feed, it will periodically be saved to ensure that you do not lose the entire message if you accidentally close your tab. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No related resources at this time. |
Feature Name |
Clause Approvers Display in the Approvals Section of a Workflow |
Product Area |
CLM
AI Playbooks
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
When you request exceptions for non standard terms, you can now check the approval status at any time in the Approvals section of the workflow. This includes ad-hoc clause approvals and clause approver configurations at the Playbook position level. Similar to document approvers, you can modify the approver and send reminders. To view the specific clause assigned to the approver, click Go to Clause. This feature is being rolled out incrementally. It will be available to all users early August. If you would like to enable this feature prior to it being generally available, please reach out to your Ironclad contact. |
Use Case | A workflow owner reviews their document and finds a clause that they would like to replace. They click Request an exception and assign the exception to an approver. To check on the status of the approval and send a reminder, they navigate to the workflow page and locate the approver under Approvals. |
|
|
How to Enable |
This feature is being rolled out incrementally. It will be available to all users early August. If you would like to enable this feature prior to it being generally available, please reach out to our Support team. |
Relevant Resources |
|
Feature Name |
Lifecycle Preset |
Product Area |
CLM
Workflows
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
The Lifecycle Preset is a collection of properties, conditions, and launch form questions to help you easily track key contract lifecycle data in your workflows, such as effective date, expiration date, and auto-renewal information. The library of properties, conditions, and launch form questions in the Lifecycle Preset can be added to any workflow configuration with a single click. We highly recommend that you use the Lifecycle Preset in most, if not all, of your workflow configurations. To learn more, refer to the Restructure Your Data article and Manage Your Data Academy course. |
Use Case |
An admin wants to create a standard data model for all of their workflow configurations. They want to ensure that they collect the most important information from their contracts. They apply the lifecycle preset to all of their existing workflow configurations, published and unpublished, and follow the steps outlined in the Manage Your Data course and Restructure Your Data article to restructure their data. Moving forward, their workflows collect consistent and detailed information as defined by the lifecycle preset and their custom properties. |
Notes |
|
How to Enable |
While this functionality is automatically available for all users, you must manually add the preset to any existing workflow configurations, published and unpublished. |
Relevant Resources |
|
Feature Name |
Data Manager |
Product Area |
CLM
Data
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Data Manager serves as a central location to view and manage all of your contract properties and record types across workflows and records. Admins can create, merge, rename, and delete properties, and create and delete record types in Company Settings. Ironclad Data Manager provides the following tools to help you manage and optimize your data:
|
Use Case |
An admin wants to create a standard data model for all of their workflow configurations. They want to ensure that they collect the most important information from their contracts. They apply the lifecycle preset to all of their existing workflow configurations, published and unpublished, and follow the steps outlined in the Manage Your Data course and Restructure Your Data article to restructure their data using Data Manager. Moving forward, their workflows collect consistent and detailed information as defined by the lifecycle preset and their custom properties. If they want to edit their properties or record types in the future, they use Data Manager to do so in a central location. |
Notes |
We highly recommend taking the Manage Data Academy course and then walking through the Restructure Your Data article. These resources will help you understand the big picture of how data is now structure within Ironclad, and how to use Data Manger to support this new model. |
How to Enable |
This functionality is automatically enabled for all admins. To access Data Manager, navigate to Company Settings > Data Manager. |
Relevant Resources |
|
Feature Name |
Connected Properties |
Product Area |
CLM
Workflows
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Properties now span your workflow configurations, workflows, and records (hence, “Connected Properties”). If you edit the property in one location of the product, that change will be reflected in all other places where that property is present. Additional safeguards in Workflow Designer now prevent duplicate properties, and changes to property names and descriptions are limited to Administrators. |
Use Case | An admin wants to update an existing property. They update the property’s name and description in the Properties and Conditions panel in Workflow Designer. Every instance of the property is updated, including any other workflow configurations, inflight workflows, records it is used in, along with filters and columns on the Dashboard, Repository, and Insights. |
Notes |
|
How to Enable |
This functionality is automatically enabled for all admins. To access Data Manager, navigate to Company Settings > Data Manager. |
Relevant Resources |
|
Feature Name | |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Previously, signature tags would occasionally render at a smaller size than intended. This has been resolved, and signature tags now appear at a consistent medium size. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Remove Ironclad Signature (Legacy) from Integrations Options |
Product Area |
CLM
eSignature
|
Impact of Change |
Process Change |
Roles Impacted | Admins |
Description |
“Ironclad Signature (Legacy)” is no longer an available signature provider integration to link under “Other eSignature Providers” on the Integrations tab in Company Settings. It will only appear under Integrations if you are already linked to Ironclad Signature (Legacy). |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name |
Send for Signature in Sandbox Mode Requires Ironclad Signature |
Product Area |
CLM
eSignature
|
Impact of Change |
Process Change |
Roles Impacted | Admins |
Description |
Sending a workflow for signature in Sandbox Mode requires having "Ironclad Signature" enabled in your instance. If you use Sandbox Mode without Ironclad Signature enabled, the contract will fail to send for signature, and the end user will see an error at the Sign Step. |
How to Enable |
No action is required for this change. However, if this update blocks your necessary actions, reach out to your Ironclad contact. |
Relevant Resources |
|
July 3, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Configure Send for Signature in Company Settings |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
If you are an administrator, you can now control whether or not anyone at your company can send contracts directly for signature, including other administrators. This provides you with greater control over Send for Signature functionality. |
How to Enable |
An admin must enable this feature. To enable this functionality, navigate to Company Settings > Settings and toggle on Allow users to upload contracts directly for signature. |
Relevant Resources |
|
Feature Name |
Signature Tag Size Rendering Consistently |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Previously, signature tags would occasionally render at a smaller size than intended. This has been resolved, and signature tags now appear at a consistent medium size. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No related resources at this time. |
Feature Name |
Customize Signer Date Format |
Product Area |
CLM
eSignature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Wf you are an admin, you can configure the signer date format for your company and your counterparty to best meet your needs. The following formats are available:
|
Use Case |
Your company prefers international date formats or a different date format for clarity. |
Notes |
Translations are not supported for “Day” or “Month” for these formats:
|
How to Enable |
An admin must enable this feature. To enable this functionality, navigate to Company Settings > Settings and select a date format. |
Relevant Resources |
|
Feature Name |
Alphabetically Sort Salesforce String Fields |
Product Area |
CLM
Integrations
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Currently, only numeric fields (int and double) are supported for sorting array data in the Salesforce integration mapping. This update will introduce support for alphabetical or lexicographic sorting of string fields. |
Use Case |
A seller using Ironclad presents a table of subscriptions in their Order Form contract template. These subscriptions appear on the Salesforce Quote as individual Quote Lines and each have a specific start date. The seller might leverage Ironclad’s enhanced sorting ability to ensure that the subscriptions appear in the table in order of when they are scheduled to begin. Similarly, if the agreement involves shipping products and we want product line items going to the same destination city to appear together in the product table, the seller might sort the Quote Lines by the name of the destination city. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Microsoft Teams Integration |
Product Area |
CLM
Integrations
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Ironclad’s Microsoft Teams integration allows users to launch workflows, review workflow details, and be notified when an approval is needed. Threads and replies will be synced between the two systems, allowing for seamless conversations, helping you close contracts faster - all without leaving teams. |
Notes |
For a list of frequently asked questions, please refer to Integration with Microsoft Teams. |
How to Enable |
An admin must enable this feature. To enable this feature, navigate to Company Settings > Integrations and connect Microsoft Teams. |
Relevant Resources |
|