Ironclad Setup
Ironclad Setup
You’ll need an appropriate contract workflow defined in Ironclad. Our example uses an Order Form use case, but the only details we depend on here are some of the standard fields that exist on almost all Ironclad workflows (Agreement Date, Counterparty Signer Email, Counterparty Signer Name), as well as the following custom attributes that you will need to add to the workflow:
| Attribute | Attribute ID | Type | Notes |
|---|---|---|---|
| Dynamics MSA ID | dynamicsMsaId | Text | This will be used to store the ID of the Dynamics Agreement record that triggered the workflow launch. |
| Dynamics MSA Number | dynamicsMsaNumber | Text | This will store the human-readable Agreement Number of the Agreement that triggered the workflow. |
| Total Contract Value | totalContractValue | Monetary | This will store the Agreement Value from the Agreement in Dynamics. |
| Product Line Items | productLineItems | Table | This table will store the Opportunity Product line items from the Opportunity in Dynamics. The columns in the table are described in the rows below. |
| Product Name | productName | String (Table Column) | This table column will store the product name from the product line item. |
| Product Quantity | productQuantity | Number (Table Column) | This table column will store the quantity from the product line item. |
| Product Unit Price | productUnitPrice | Monetary (Table Column) | This table column will store unit price from the product line item. |
| Product Line Total Price | productLineTotalPrice | Monetary (Table Column) | This table column will store the total price from the product line item. |
Updated about 2 hours ago
