JSON

Example

{
    "id": 710,
    "name": "jPetStore",
    "archived": false,
    "owner": {
        "id": 205,
        "name": "100/AUTOMIC/AUTOMIC",
        "type": "User"
    },
    "folder": {
        "id": 706,
        "name": "JPETSTORE"
    },
    "custom_type": {
        "id": 409,
        "name": "Generic",
        "version": "1.0.0 PCK.AUTOMIC_BOND"
    },
    "components": {
        "has_more": false,
        "total": 2,
        "data": [
            {
                "id": 712,
                "name": "jPetStore DB"
            },
            {
                "id": 872,
                "name": "jPetStore Webserver"
            }
        ]
    },
    "description": null
}

Description

Element / Attribute	Description
id	Application Pack ID
name	Application Pack name
archived	Defines if the Application is archived or not. Possible values: true/false
owner	Id, name, and type of owner (user/user group)
folder	Id and name of folder
custom_type	Id, name, and version of Custom Type
components	has_more=false. No more components are available. Number, id and name of Components
description (optional)	Description of the Application Pack

Property type serialization

Property type	Serialization
Single line text	string
Short text	string
Long Text	string
Single Choice	string
Multi Choice	The selected choices are separated by " , "
Integer	Integer type must be used: {"type": "integer"}: Important! The treatment of the Integer type depends on the implementation of the JSON Schema validator
Float	JSON does not have distinct types for integers and floating-point values:
Date	ISO 8601
Time	ISO 8601
Checkbox	Boolean type must be used: {"type": "boolean"} Possible values:"true" or "false"
E-Mail	Space separated (for example "example@example.org My Mail")
URL	Space separated (for example "http://example.com My URL")
File	string
Identity	string