Common Contract Technical Specifications
Contract Services
The contract generation logic is structured into two distinct layers to ensure efficient and accurate processing:
1. Contract Generation Request (CGR) Processing
This layer manages the initial handling of contract generation requests based on the client's profile and the current generation status. It ensures that requests are validated and routed correctly. The steps involved in this layer are:
Contract Generation Request Validation:
Client/Generation Status Specific Processing:
Route the request to appropriate processing flows based on the client type and generation status.
For CR Draft Requests:
For CR Final Requests:
For SSP (Special Service Package) Requests:
2. Document Generation
Upon successful processing of the contract generation request, the next layer focuses on the creation of the contract documents. This layer includes:
Generate Pricing Schedule Package:
Document Creation:
Key Features and Benefits
Automation: Automates the entire contract generation process, reducing manual effort and minimizing errors.
Customization: Tailors contract documents based on client-specific information and product requirements.
Efficiency: Streamlines the process, ensuring timely and accurate generation of contracts.
Scalability: Supports a wide range of contract types and can handle high volumes of requests.
Side Effects
List the downstream effects of using this API, such as spinning up a phone line or charging a credit card.
In the Standard Pricing API, an example of a side effect is to make prices available in client applications: SSP, Salesforce, BC, etc.
Dependencies
List other capabilities and services that this capability uses (as well as any backing systems).
In the Standard Pricing API, some examples of dependencies are:
- The Catalog Capability is needed for product and offer definitions.
- The PO&M System is needed to supply the list of approved prices from the pricing optimization and management