Ironclad Salesforce Managed Package Update v3.71

This article goes over the features included in Salesforce Managed Package Update v3.71:

• Workflow Signature Management Support

• Turn Tracking History Component

• Workflow Launch Group API Name Metadata Decoupling

• Ironclad ID Field Addition

Permissions

What's Included in v3.71

The v3.71 release adds four core improvements to the managed package:

• Workflow Signature Management Support: Manage e‑signatures for Ironclad workflows directly from Salesforce.

• Turn Tracking History Component: Displays negotiation “turns” as a timeline on the Ironclad Workflow record.

• Workflow Launch Group API Name Metadata Decoupling: Make Workflow Launch Group configuration more stable across environments.

• Ironclad ID Field Addition: Introduces a durable ID that strengthens sync and deduplication between Ironclad and Salesforce.

Manage Signatures Directly in Salesforce

Workflow Signature Management extends the existing Ironclad Next Steps Lightning Web Component so users can manage the signature phase of an Ironclad workflow without leaving Salesforce.

Previously, Salesforce exposed Ironclad approvals and workflow status, but users still had to switch back to Ironclad to:

• Kick off signatures.

• Remind signers.

• Update signer information.

• Remove or cancel signers.

See Turn History on the Workflow Record Page

The Turn Tracking History Component is a new Lightning Web component added to the Ironclad Workflow record page. This component renders a date-based timeline that highlights:

• Time in each party's hands

• Total time taken per company

• Total number of turns.

You can use this turn data to inform follow-ups, escalation, and coaching without having to open the workflow in Ironclad. 

Workflow Launch Groups (WLGs) API Name Decoupling

With v3.71, Ironclad components now store the WLG API Name (DeveloperName) instead of the record ID. This change decouples configuration from org‑specific IDs, which ensures that embedded launch and workflow‑selection behavior remains stable as you move configuration across orgs, which is important when rolling out these features to multiple environments.

This update:

• Reduces the risk that a page breaks after a sandbox refresh, migration, or package upgrade.

• Makes it safer to promote Lightning pages between environments (e.g., Dev → QA → Prod).

• Aligns Ironclad with Salesforce best practices for using DeveloperName as a stable identifier in metadata instead of record IDs.

Use Ironclad ID as a Sync Key

v3.71 introduces a new Ironclad ID field on:

• Ironclad Contract

• Ironclad Workflow

This field stores the unique ironcladId value that Ironclad uses internally for workflows and contracts. It becomes a canonical ID that both systems can agree on. Any workflow or contract you interact with via Next Steps, Turn History, or Record Sync can always be traced back to its unique Ironclad counterpart.