Introduction

Agreements (or Contracts) exist for two main reasons:

• Being able to have a history of the different versions an Asset had for a customer.
• Representing the contracted Asset in a way that it can be billed by the billing module or external billing system.

This is, that when we activate an Order, two things happens:

• The asset is generate with the same structure as the Order and Product Version with its components/relationships and attributes.
• The agreement is generated after evaluating the Agreement Term Rules defined in the Product Version.

This way, you could have actually different products that would generate the same billing concepts, or have a product that depending on the configuration of its attributes or component would generate different Agreement Terms.

This gives a lot of flexibility and avoid the need of having any kind of conversion of the Assets / Contracts when trying to process the billing or invoice.

 Agreement Terms Rules

At Product Version level you can create Agreement Term Rules which let you define rules to add an Agreement Term or not and with which value depending on the product Setup.

Rules Functions

Out of the Box CPQ Functions

Wattyo comes with different Functions that are useful for Agreement Term Rules.

Custom Function

You can add any custom Function that you need trough [ Custom Fucntions Libraries ]({{< relref “/docs/technical/rules/implementation/customfunctionslibraries” >}}).

It’s important to note that the Context passed to functions called by the Agreement Mapping Engine is a ConfigurationWrapper.Item object with the Item configuration details. So any function should expect the Context parameter to be of this type if it needs to use the Context.