Contract Document Generation Enhancements

You can now generate contract documents using a generic API invoked by a calling application that can be against any entity, including Shopping cart or Order.

These contract documents are PDFs. They are initially created in Draft status and subsequently, based on customer acceptance, would move to Accepted. Once the order is completed, the document life cycle status can be updated to Active. Similarly, if the order is cancelled, the document status can be updated to Inactive. Contract documents that remain in Draft status and do not progress in the customer journey can be later updated to Obsolete.

There are two specific design-time considerations in place:

• There is a Business configuration that decides if the Contract document is generated only based on order completion or not. To support this feature, this configuration is set to False.

• There is an additional flag to categorize the templates that can be used to generate the contract document. For this feature, the templates are defined with the new specificationBased flag set to No, in combination with the properties "type": "ContractTemplate", "domain": "Consumer" and "contentType": "Dynamic".

The templates and contract documents can be stored in any document management system through the Document management adaptor. The CXIF document management adaptor has to be configured to work with the desired Document Management System.

The business benefit of this feature is that it provides great flexibility in generating contract documents through the invocation of a generic API.

Steps to Enable

You don't need to do anything to enable this feature.

Access Requirements

Use the Contract Administrator role privilege for updating specific contract document statuses such as Active, Obsolete and Inactive and to define contract templates.

Use the Back Office Specialist role privilege for setting up the Business configuration.