Jump to: navigation, search

Create Package

Method

POST

Syntax

 
/grs/v1/tenant/{tenantId}/businessnode/{nodeId}/package

Request Body

 
{   
   "name":"XYZ",
   "type":"samples",
   "businessName":"XYZ",
   "description":"SamplePackage 
Note: Must enable wildcards for this to 
work decision-table-enable-wildcards=true",
   "templates":[   
      {   
         "name":"Existing Template",
         "version":7
      },
  {   
         "name":"A new template",
         "version":2
      }
   ]
}

Response Body

 
{   
"packageId", "f44268af-dd9e-4035-ba1f-acd53d78fc89",   
  "name":"XYZ",
   "type":"samples",
   "businessName":"XYZ",
   "description":"SamplePackage",
   "templates":[   
      {   
         "name":"Existing Template",
         "version":7
      },
  {   
         "name":"A new template",
         "version":2
      }
   ]
}

HTTP Status Codes

  • 201 Created—Response body provided
  • 401 Unauthorized—APIToken not valid
  • 403 Forbidden—User does not have permission for the specified tenant or business node, or does not have proper permission to perform this operation.
  • 422 Unprocessable Entity—Field Validation Error
 
{
  "message": "Validation Failed",
  "errors": [
    {
       "code" : "1000",
       "field" : "name",
       "message": "package name must be specified"
    }
  ]
}

Other possible return values:

  • 1001—name—package name contains invalid character(s)
  • 1002—name—package name cannot contain java keyword(s)
  • 1003—name—package name already in use
  • 1004—type—package type must be specified
  • 1005—templates—specified template: {templatename} version: {version} not found
  • 1006—businessName—business name already in use
  • 503—Service Unavailable
This page was last edited on May 16, 2017, at 08:20.
Comments or questions about this documentation? Contact us for support!