This article will walk you through what the Lifecycle Preset in Workflow Designer is and how to use it.
The Lifecycle Preset is a collection of fields, conditions, and launch form questions to help you easily track key contract lifecycle in your workflows, such as agreement date, expiration date, and auto-renewal information. The library of fields, 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.
The Lifecycle Preset fields is required for customers to be able to leverage contract status and auto-renewal features. These fields are used by Ironclad to automatically track the status of a contract over time. If the Lifecycle Preset fields are not populated in a workflow, the resulting records may not accurately reflect the correct Active/Expired status and automatically follow their auto-renewal terms.
Add the Lifecycle Preset to a Workflow Configuration
- On the Fields and Conditions panel located on the left, click the plus sign and select Lifecycle located under presets. Your workflow configurations is updated to include 11 fields, 7 conditions, and 9 launch form questions. The full list of fields, conditions, and launch form questions can be found below.
- The workflow configuration is now automatically set up to track key contract lifecycle information. The fields and associated launch form questions are used to collect contract lifecycle information from your users on the launch form, such as agreement date, expiration date, and auto-renewal information. These fields will populate the Record Status after the contract is executed.
- The conditions are used to conditionally show only the launch form questions that are relevant to the current workflow. For example, if the Renewal Type is Evergreen, the launch form questions that ask for the renewal term length and number of renewals allowed will not be shown.
Edit/Delete Fields and Conditions
You may find that you don’t need all of the fields, conditions, or launch form questions. You can always delete fields from the preset and choose to power them with formulas instead of a question.
- On the Fields and Conditions panel located on the left, locate the field or condition you want to delete. Click the three stacked dots located next to it and then click Delete field or Edit field.
-
If you selected Delete field, a confirmation modal displays informing you of the consequences of deleting the field, and any other related fields/conditions that will be affected by the deletion of the field.
View Image
- If you deleted a field from the preset by accident, you can easily re-add the field by clicking the three vertical dots to the right of an active preset field > View Preset. From there, click the three vertical dots next to the deleted preset and then click Add field back to preset.
Edit/Delete Launch Form Questions
You can remove or edit any launch form questions added with the Lifecycle Preset. This is important because it is the only part of the experience that your workflow users will see. For example, if you want to describe auto-renewals in a different way from the standard launch form question, you can edit the question. If your contracts never auto-renew, you can delete the question.
- Click on the Workflow Designer tab and select the workflow configuration you want to modify. Click on the Create tab.
- Locate the questions you want to modify. You can edit the Lifecycle Preset questions as you would any other existing questions.
- To delete a question, click Delete question located in the bottom right of the question.
View Example
If you know that all of your contracts from your template are evergreen, you won’t need the fields, conditions, and launch form questions to collect information on expiration date, initial term length, renewal term etc. You can just delete the renewal type question, the associated fields questions and conditions, and just power the Renewal Type field with a formula.
Finally, in cases where you would like to still have users fill out these details but they may not be available at launch, you can leverage sections, and our feature to only display questions in the Review step to get those details.
Deleting the question is another way of only filling out the fields during the Archive step. However, conditions and multi-choice questions don’t apply at the Archive step, so you’d want to review this closely.
Existing Workflow Configurations vs. New Workflow Configurations
The Lifecycle Preset is relatively simple to use in a new workflow configuration because you’re building it from nothing. You can add the Preset and then modify the fields, conditions, and launch form questions to suit your exact needs.
If you are updating an existing workflow configuration to use the Lifecycle Preset, your workflow configuration may already be tracking lifecycle concepts like agreement date, expiration date, and auto-renewal information. In this case, some of your existing fields and launch form questions will overlap with the new ones from the Lifecycle Preset. You will need to remove your existing fields and launch form questions so there is no overlap - the Lifecycle Preset should be the only set of fields, conditions, and launch form questions that track the following concepts:
- Agreement date
- Expiration date
- Agreement Term
- Auto-renewal
- True/false or type
- Opt-out date
- Auto-renewal term length
- Termination
List of Fields, Conditions, and Launch Form Questions in the Lifecycle Preset
Field Name | Data Type | Question/Formula | Description | Required for Status/Auto-Renewals |
---|---|---|---|---|
Contract Owner | Formula: Get workflow owner’s email | This field is useful for having a modifiable, contract owner email in the Repository that you can send reminders to. By default this is powered by a formula which is set to be the email of the Workflow Owner. |
No.
|
|
Expiration Date | date | What is the initial expiration date? | The expiration date is when this agreement will end or become inactive, if an expiration date isn’t present then the effective date plus the initial term length are used to determine the expiration date. |
One of Expiration Date or Initial Term Length are required in order to determine the expiration date of an agreement.
This is not required if the agreement is evergreen/perpetual or if it doesn’t have an explicit expiration date. The agreement will then stay active until the user manually marks the contract as expired.
|
Effective Date | date | What is the effective date? | Th effective date is when this agreement begins and is considered active. If the effective date is not defined then the executed date of the agreement is used as the effective date. |
Not required. If this is not present or left blank, the system will use the executed date (a system generated value which tracks the date when all signatures, or all approvals for contracts that don’t require a signature are collected).
|
Initial Term Length | duration | What is the initial term of the agreement? | The initial term length is the time from the effective date that the agreement will be effective for. If this is not defined, then the agreement will be active until the expiration date. If an expiration date is also not defined, then the agreement will be active indefinitely, until the agreement is manually marked as terminated or expired. |
One of Expiration date or Initial Term Length are required in order to determine the expiration date of an agreement.
Not required if the agreement is evergreen/perpetual or doesn’t have an explicit expiration date. The agreement will then stay active until the user manually marks the contract as expired.
|
Renewals Allowed | number | What are the maximum amount of times this agreement will auto-renew? (unlimited if left blank) | Agreements that have an auto-renewal, may have a maximum number of times they will auto-renew before expiring. If left blank, then the number of auto-renewals will be unlimited. |
Only required for auto-renewing contracts that have a maximum number of auto-renewals, if not present or left blank the contract will auto-renew perpetually until canceled/terminated.
|
Renewal Term Length | duration | What will be the term of the renewal for this agreement? | If an agreement auto-renews or has an optional extension, that renewal/extension will have a term (1 year, 6 months, etc). |
Required for agreements that are auto-renewing or have an optional extension and used to calculate the new expiration date when the agreement renews.
|
Renewal Opt-Out Period | duration | What is the opt-out period for this agreement? | An agreement may have an opt-out period that let’s you opt out of the upcoming auto-renewal before it renews. In the case of an opt period, the last day to opt out is the expiration date minus the opt-out period. |
No.
|
Renewal Opt-Out Date | Date | What is the opt-out date for this agreement? | An agreement may have an opt-out period that let’s you opt out of the upcoming auto-renewal before it renews. In the case of an opt period the opt-out date is the expiration date minus the opt-out period. |
No.
|
Renewal Type | text - multiple choice | What is the renewal type for this agreement? |
The renewal type for an agreement will govern what happens on its expiration date if it has one.
Auto-Renew: These agreements will automatically renew on their expiration date which means they will then have a new expiration date which would be the current date plus the renewal term length.
Optional Extension: These agreements have an optional extension which means that the party can choose to renew the agreement by the renewal term length without renegotiating the contract. There may be a notification requirement to exercise this option.
Evergreen: These are agreements that don’t have an expiration date, which means they are active forever. Also known as perpetual agreements.
None: This is for agreements that don’t have a renewal provision and will expire on their expiration date. If an agreement has no renewal provision but also doesn’t have an expiration date, it’ll be active forever.
Other: For renewal provisions that are not covered by these options.
|
Required if you would like to accurately track the full lifecycle of the agreement.
If this is not present or left blank, the contracts will either stay active forever or expire if an expiration date is present.
|
Termination Notice Period | duration | What is the notice period for this agreement? | This is the number of days of notice that needs to be given before this agreement can be terminated. |
No.
|
Other Renewal Type | text | If other, what is the renewal type for this agreement? | For renewal types not handled by the Ironclad platform. In this instance, Ironclad will treat these as contracts with no renewal provision. |
Yes, if you would like to account for renewals not captured by the renewal types listed above.
The Ironclad platform, however, will just expire these agreements on the expiration date if an expiration date is present.
|
Condition: Auto-Renew | condition | Renewal Term Length Number of Renewals Renewal Opt-Out Period Expiration Date |
This ensures that the questions relevant for auto-renewals only show up when required. | |
Condition: Optional Extension | condition | Renewal Term Length Number of Renewals Renewal Opt-Out Period Expiration Date |
This ensures that the questions relevant for optional-extensions only show up when required. | |
Condition: Renewal Type Other | condition | Other Renewal Type | This ensures that the questions relevant for other renewal types only show up when required. | |
Condition: Evergreen | condition | This ensures that the questions relevant for evergreen agreements only show up when required. | ||
Condition: None | condition | Expiration Date | This ensures that the questions relevant for agreements with no renewal provision only show up when required. |