Create a project publish event

post

http://{PublishServerHost}/api/productCatalogManagment/v1/projectPublishEvent

Example of a client listener for receiving the notification ProjectPublishEvent

Request

There are no request parameters for this operation.

Supported Media Types
Request Body - application/json ()
Root Schema : ProjectPublishEvent
Type: object
Title: ProjectPublishEvent
The notification data structure
Show Source
Nested Schema : ProjectPublishEventPayload
Type: object
Title: ProjectPublishEventPayload
The event data structure
Show Source
  • Publish_Job
    Title: Publish_Job
    Is a detailed description of a publish Project available externally in the form of a list of Project Items.
Nested Schema : Publish_Job
Type: object
Title: Publish_Job
Is a detailed description of a publish Project available externally in the form of a list of Project Items.
Show Source
Nested Schema : projectItems
Type: array
Contains the list of Project Items that are part of the publish
Show Source
  • ProjectItemRef
    Title: ProjectItemRef
    Project Item reference. A project Item ref represents entities that can be ProductOffering or ProductOfferingSpecification or ProductOfferingPrice etc..
Nested Schema : ProjectItemRef
Type: object
Title: ProjectItemRef
Project Item reference. A project Item ref represents entities that can be ProductOffering or ProductOfferingSpecification or ProductOfferingPrice etc..
Show Source
  • The TMF base type of the target instance when needed for disambiguation.
  • The actual type of the target instance when needed for disambiguation.
  • context
  • Allowed Values: [ "ENTITLEMENT_PRICING", "ENTITLEMENT_SERVICE" ]
    entitlememt type
  • Reference of the related entity.
  • Unique identifier of a related entity.
  • The lifecycleStatus of the related entity.
  • Name of the related entity.
  • Allowed Values: [ "RECURRING", "ONE_TIME", "USAGE", "ALTERATION", "ALLOWANCE", "OVERAGE", "PENALTY", "ONE_TIME_PRICE_PLAN", "RECURRING_PRICE_PLAN", "USAGE_PRICE_PLAN", "ALTERATION_PRICE_PLAN", "OVERAGE_PRICE_PLAN", "COUNTER" ]
    Describes the price, such as recurring, discount, allowance, penalty, and so forth
  • Allowed Values: [ "PACKAGE", "COMMERCIAL_BUNDLE", "SERVICE_BUNDLE", "SERVICE", "DEVICE", "ACCESSORY", "CHOICE", "AGGREGATION", "SYSTEM_OFFER" ]
    Used to indicate the type of product.
  • Allowed Values: [ "DEVICE_SPEC", "BUSINESS_CONFIG", "TRADE_IN", "CHARGING_TERM", "SUSPENSION_TERM", "RETURN_CHECKLIST", "ENTITY_PROFILE", "RENEWAL_TERM", "FINANCE_PLAN", "ZONE_VALUE_MAP" ]
    type of the profile
  • Allowed Values: [ "AWARD", "DISCOUNT", "TRADE_IN", "CROSS_PRODUCT_DISCOUNT" ]
    Comma seperated promotion tags/type
  • Allowed Values: [ "COMPATIBILITY", "ELIGIBILITY", "MIGRATION", "RECOMMENDATION", "CONSTRAINT" ]
  • Version of the object
Nested Schema : context
Type: array
Show Source
Nested Schema : ProjectItemContextsOracle
Type: object
Title: ProjectItemContextsOracle
Project item context objects which holds the KPI parameters
Show Source
Nested Schema : params
Type: array
Show Source
Nested Schema : ProjectItemContextParamsOracle
Type: object
Title: ProjectItemContextParamsOracle
Project item context KPI parameters
Show Source
Back to Top

Response

201 Response

Your request is processed successfully.

400 Response

Your request couldn't be processed because it contains missing or invalid information, such as a validation error on an input field, a missing required value, and so forth.
Body ()
Root Schema : Error
Type: object
Title: Error
Show Source

401 Response

Your request isn't authorized. The authentication credentials included with this request are missing or invalid.
Body ()
Root Schema : Error
Type: object
Title: Error
Show Source

404 Response

Your request includes a resource URI that doesn't exist.
Body ()
Root Schema : Error
Type: object
Title: Error
Show Source

405 Response

HTTP action specified in the request (DELETE, GET, POST, PUT) isn't supported for this request URI.
Body ()
Root Schema : Error
Type: object
Title: Error
Show Source

409 Response

The request can't be completed due to a conflict with the current state of the resource.
Body ()
Root Schema : Error
Type: object
Title: Error
Show Source

500 Response

The server encountered something unexpected that prevented it from completing the request.
Body ()
Root Schema : Error
Type: object
Title: Error
Show Source
Back to Top

Examples

The following example shows how to create a project publish event by submitting a POST request on the REST resource using cURL.

cURL Command

curl -u username:password -X POST https://{FusionAppsHost}/crmRestApi/atcProductCatalog/11.13.18.05/tmf-api/productCatalogManagement/v4/project/ -D @create_projectPublishEvent.json | json_pp

Example of Request Body

The following shows the contents of the request body in JSON format.

{
  "@type": "ProjectOracle",
  "@baseType": "Project",
  "name": "Delta Projects",
  "version": "7.0",
  "description": "Delta project publish event.",
  "lifecycleStatus": "In design"
}

Example of Response Body

The following shows the contents of the response body in JSON format.

{
    "@type": "ProjectOracle",
    "@baseType": "Project",
    "href": "https://{FusionAppsHost}/crmRestApi/atcProductCatalog/11.13.18.05/tmf-api/productCatalogManagement/v4/project/PJT300100192427135",
    "lastUpdate": "2020-12-16T10:46:13.000Z",
    "lastUpdatedBy": "booth",
    "createdBy": "booth",
    "created": "2020-12-16T10:46:13.000Z",
    "lifecycleStatus": "In design",
    "lifecycleConfiguration": {
        "id": "DEFAULT_LC_STATUS_CONFIG_ID",
        "name": "Default Lifecycle Status Configuration",
        "href": "https://{FusionAppsHost}/crmRestApi/atcProductCatalog/11.13.18.05/v1/lifecycleConfiguration/DEFAULT_LC_STATUS_CONFIG_ID",
        "version": "26.0",
        "@referredType": "LifecycleConfigurationOracle"
    },
    "description": "Delta project publish event.",
    "version": "7.0",
    "action": "CREATE_OBJECT",
    "name": "Delta Projects",
    "id": "PJT300100192427135"
}
Back to Top