Domain NOVA Customer

Capabilities:

Diagrams

NOVA Customer Data Types NOVA Customer Service Model NOVA Customer Master Data NOVA Customer Master Data
- Customer Data Types Domain
- Customer Data Types OpenAPI 		- Customer Address Validation Service
- Customer Service Model Domain
- Customer Service Model OpenAPI
- Customer Service Model Roles
- Customer Service Partner Write Requests
- Customer Service Responses
- Customer Service Security Roles 		- Customer Data Unit
- Customer Master Data Domain
- Customer Master Data OpenAPI

Artifacts

Artifact Icon Maturity Level since
NOVA Customer Data Types 🐔 Crazy Chicken
NOVA Customer Service Model 🐔 Crazy Chicken
NOVA Customer Master Data 🐔 Crazy Chicken
NOVA Customer Events 🐔 Crazy Chicken

Dependencies

Artifact Outgoing Dependencies Incoming Dependencies
NOVA Customer Data Types - NOVA Common Data Types
- NOVA Common Data Types 		- NOVA Customer Master Data
- NOVA Customer Service Model
- NOVA Booking Service Model
- NOVA Offer Store Service Model
- NOVA Checkout Service Model
- NOVA Token Service Model
- NOVA Fulfillment Service Model
- NOVA Travel Authorization Control Service Model
- NOVA Transaction Approval Service Model
- NOVA Transaction Approval Events
- NOVA Coupon Service Model
- NOVA Payment Service Model
- NOVA Contract Service Model
- NOVA Offer Service Model
- NOVA Offer Master Data
NOVA Customer Service Model - NOVA Common Data Types
- NOVA Customer Data Types
- NOVA Master Data Data Types
- NOVA System Problem
NOVA Customer Master Data - NOVA Common Data Types
- NOVA Customer Data Types
- NOVA Master Data Data Types
NOVA Customer Events

Provided REST Endpoints / Services

AddressValidationService

Service provides the endpoints / operations to validate customer address data. Depending on the type of address different operations are available. Also the validation rules highly depend on the type of address.


REST Path / Operation Description
/customers:validateCommunicationAddress [POST]

validateCommunicationAddress(CommunicationAddress, NOVAContext) 		Operation can be used to check if a communication address is valid for usage on NOVA.


CustomerService

Service provides the endpoints / operations to access and update NOVA customer data.


REST Path / Operation Description
/customers [GET]

getPartner(PartnerRequest, NOVAContext) 		Method returns the partner with the passed customer reference (TKID or CKM).
/customers:preparePartner [POST]

preparePartner(PreparePartnerRequest, NOVAContext)
/customers/{customerID}:confirm [POST]

confirmPartner(PartnerRequestContext, NOVAContext)
/customers/{customerID}:update [POST]

updatePartner(UpdatePartnerRequest, PartnerRequestContext, NOVAContext)


Planned Breaking Changes

No breaking changes planned.

Deprecations

Package ch.voev.nova.customer.datatypes

No deprecations published.


Package ch.voev.nova.customer.servicemodel

No deprecations published.


Package ch.voev.nova.customer.masterdata


Classes with Deprecations


Type Attribute Description Deprecated since Planned to be removed
CustomerDataElementQualityLevelsMasterData Type will be removed completely without a successor. 2.0 PI 22
CustomerDataQualityProfileMasterData Type will be removed completely without a successor. 2.0 PI 22
CustomerDataUnit
customerRoleDefinitionMasterData Please use direct association customerRoleDefinitions to versioned object CustomerRoleDefinition instead. 2.0 PI 22
customerDataQualityProfileMasterData Please use direct association customerDataQualityProfiles to versioned object CustomerDataQualityProfile instead. 2.0 PI 22
customerDataElementQualityLevelsMasterData Please use direct association customerDataQualityLevels to versioned object CustomerDataQualityLevel instead. 2.0 PI 22
CustomerRoleDefinitionMasterData Type will be removed completely without a successor. 2.0 PI 22


Package ch.voev.nova.customer.events

No deprecations published.