The provider and resellers can have their own contracts with various software vendors.
The VendorContract
APS type must be implemented by APS applications that allow the provider and resellers to
create and edit software vendor contract identifiers.
In this document:
The considered APS type (download
) looks as follows:
{
"name": "VendorContract",
"id": "http://odin.com/aps/types/oa/vendor-contract/1.0",
"apsVersion": "2.0",
"implements": [
"http://aps-standard.org/types/core/resource/1.0"
],
"properties": {
"vendorContract": {
"type": "string",
"title": "Vendor Contract",
"default": ""
}
}
}
In the current version of the platform, the only property in the above schema is vendorContract
. This is a
string representing a contract ID.
An APS package can implement the VendorContract
APS type on two levels:
Application instance: the root APS type that implements the Application APS type
implements the VendorContract
APS type as well. This enables the provider to set their own vendor
contract ID when installing the APS application instance.
Reseller profile: the APS type that implements the ResellerProfile APS type also
implements the VendorContract
APS type. This influences the provider and only those resellers whom the provider
delegates a service template based on the considered APS package. They can set and edit their own
vendor contract ID in the service template configuration.
An APS package considered here contains a custom ResellerCloud
APS type that implements
ResellerProfile and ExternalIdentifiers
APS types:
{
"apsVersion": "2.0",
"name": "ResellerCloud",
"id": "http://aps-standard.org/samples/vpsdemo/reseller-profile/1.0",
"implements": [
"http://aps-standard.org/types/core/profile/reseller/1.0",
"http://odin.com/aps/types/oa/vendor-contract/1.0"
],
/* Other parts */
}
For more details about the contract ID use, refer to Managing Software Vendor Contracts.