top of page

Version 1.8.9 🦖

  • Writer: Leslie Leahy
    Leslie Leahy
  • Sep 27
  • 2 min read

Today's update we've totally overhauled the special conditions feature, added more settlement date options, further enhanced our API's and added a number of other things you've been asking for.


Keep reading for all the details. 😄


📄 Special Conditions

We've done a major overhaul of the "special conditions" feature in OPEX, giving you better formatting options AND merge fields.


  • Improvements to the special conditions templating system

  • Ability to "archive" old special conditions templates

  • Insert merge fields in special conditions, just like in email campaigns

  • Improved text formatting options for special conditions including

    • Bold, italics, underline

    • Bullet list

    • Numbered list; and

    • Support for tables

  • Ability to change the heading of the special conditions page that's inserted in the contract

Special conditions with merge fields and text formatting
Special conditions with merge fields and text formatting

📅 Settlement Date Options

Especially useful for post registration projects, our enhanced settlement date options allow you to have a contract with options for the settlement date to be:


  • X days from date of contract; or

  • A fixed date


Via project settings you can allow either, or both options to be available when creating a contract. When using "X days from date of contract" you can optionally add a "suffix" to the merged data. Meaning you can tell OPEX to merge in the number (eg: "30") or the number plus a string (eg: "30 days") giving you lots of flexibility.


More options for your settlement dates.
More options for your settlement dates.
When creating a contract the options change depending on the project settings.
When creating a contract the options change depending on the project settings.

🔤 Mandatory Input Fields

Sometimes it can be hard to find "mandatory input fields" in a contract, not any longer! Where a contract has mandatory input fields (that are required to be populated before you can issue a contract) the system will guide you through populating them before issuing your contract.


Contracts with 'mandatory inputs' are now much easier to work with.
Contracts with 'mandatory inputs' are now much easier to work with.

🖊️ Sign In-Person

When signing contracts "in-person" (and a project launch for example) the signature panels now auto-populate with the purchaser details.


🤖 API

We've further enhanced our REST API by adding more data to payloads and introducing a new endpoint. Updated documentation is available in our developer portal.


  • A new Contract POST request has been implemented so that you can created contracts in OPEX from 3rd party systems (such as Salesforce)

  • Our Event payloads have been enriched with additional parameters so that a subsequent Contract GET isn't required for basic contract information, the additional parameters are:

    • projectId

    • projectName

    • lotNumber; and

    • flowStep


The OPEX developer portal
The OPEX developer portal

 
 
bottom of page