[Index]
View to augment CUC Callhandler device-models in the relation
Model ref.: view/HF_CallHandlerVIEW
The full URL would include the host-proxy name: https://[host-proxy].
Variables are enclosed in square brackets.
{ "$schema": "http://json-schema.org/draft-03/schema", "type": "object", "properties": { "cuc_info": { "type": "string", "description": "Informative (non-input) field. Indicates the target CUCx host/IP, which is automatically derived from the input NDL.", "title": "Cisco Unity Connection" }, "target_ndl": { "type": "string", "description": "Mandatory input-field for the Add use-case (if hierarchy is at Site-node, however, this value is derived automatically). The workflow (and GUIRules) will target the UC devices that is linked to this Network Device List (NDL). In the Mod use-case, this should also be derived automatically and can thus be omitted from Updates.", "title": "Network Device List" }, "greetings_tab_message": { "type": "string", "description": "Greetings", "title": "Message" }, "route_list": { "type": "string", "description": "The Cisco Unified CM Route List to use. (The valid options are dependent on the selected NDL / CUCM)", "title": "Route List" }, "owners_message": { "type": "string", "description": "(fields will become available after new item has been saved)", "title": "Message" }, "callerInput_tab_message": { "type": "string", "description": "Caller Input", "title": "Message" }, "hierarchy_type": { "type": "string", "description": "Hidden (internal-only) helper field to store hierarchy type string (e.g. 'Site' or 'Customer')", "title": "Hierarchy Type" }, "cuc_template": { "type": "string", "description": "Select the Cisco Unity Connection Call Handler Template. (The valid options are dependent on the selected NDL / CUCx)", "title": "Call Handler Template" }, "cucm_info": { "type": "string", "description": "Informative (non-input) field. Indicates the target CUCM host/IP, which is automatically derived from the input NDL.", "title": "Cisco Unified CM" }, "transfer_rules_message": { "type": "string", "description": "(fields will become available after new item has been saved)", "title": "Message" } }, "schema_version": "3.2.0" }
Task | Call | URL | Parameters | Response |
---|---|---|---|---|
Get the GUI Add form. | GET | /api/view/HF_CallHandlerVIEW/add/ |
|
The GUI Add form of view/HF_CallHandlerVIEW as JSON |
The API call to the /add/ URL can only be made from a hierarchy that allows the model type to be added. The actions in the response shows the url for the POST API call to create an instance.
Task | Call | URL | Parameters | Payload |
---|---|---|---|---|
Create | POST | /api/view/HF_CallHandlerVIEW/ | hierarchy=[hierarchy] |
|
tool/Transaction/[trans pkid]shows the View resource has no instance pkid, because a view model stores no instances.
Task | Call | URL | Parameters | Payload |
---|---|---|---|---|
Get a selected [export_format] of the schema and instances [pkid1], [pkid2],... of view/HF_CallHandlerVIEW; optionally with tag_version at [version] and Configuration Template as [configtemplate]. | POST | /api/view/HF_CallHandlerVIEW/export/ |
|
{ "hrefs":["/api/view/HF_CallHandlerVIEW/[pkid1]", "/api/view/HF_CallHandlerVIEW/[pkid2]",...]}} |
For export_format=json, the response is a time stamped zip file of data in JSON as in the system database. Item properties such as strings that are empty or Boolean values that are not set, are not included. The filename in the response is of the format as the example:
Content-Disposition: attachment; filename=export_2013-05-17_14:20:19.186444.json.zip Content-Language:en Content-Type:application/x-zip
For export_format=raw_xlsx, the response is a MS Excel spreadsheet with columns corresponding to the JSON format export and a response filename format:
Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_CCYY-MM-DD_HH-MM-SS.xlsx Content-Language:en Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
For export_format=xlsx, the response is a MS Excel spreadsheet, arranged by any Field Display Policies that apply. The columns correspond with those of a Bulk Load Template export sheet. The response filename format is:
Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_formatted_CCYY-MM-DD_HH-MM-SS.xlsx Content-Language:en Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
The XLSX format can be used to bulk load instances of view/HF_CallHandlerVIEW and the JSON format can be used to import instances of view/HF_CallHandlerVIEW.
GET http://[host-proxy]/api/view/HF_CallHandlerVIEW/?hierarchy=[hierarchy]
Task | Call | URL | Parameters | Response |
---|---|---|---|---|
Get a compressed format of the Bulk Load spreadsheet template for view/HF_CallHandlerVIEW | POST | /api/view/HF_CallHandlerVIEW/export_bulkload_template/ |
|
The response is an attachment of the format: filetype_bulkloadsheet.xlsx.gz |
Task | Call | URL | Parameters | Response |
---|---|---|---|---|
List | GET | /api/view/HF_CallHandlerVIEW/ |
|
The view/HF_CallHandlerVIEW schema and all instances as JSON. |
(The list will return 0 to 3 view/HF_CallHandlerVIEW instances)
{ "operations": [ "add", "help", "configuration_template", "field_display_policy", "export_bulkload_template", "transform" ], "pagination": { "direction": "asc", "order_by": null, "maximum_limit": 2000, "skip": 0, "current": "/api/view/HF_CallHandlerVIEW/?skip=0&limit=3&order_by=None&direction=asc&traversal=default", "limit": 3, "total_limit": null, "total": 0 }, "meta": { "tags": [], "cached": true, "title": "", "business_key": {}, "schema_version": "3.2.0", "references": { "device": [ { "pkid": "", "href": "" } ], "children": [], "parent": [ { "pkid": "6t0ggef2c0deab00hb595101", "href": "/api/data/HierarchyNode/6t0ggef2c0deab00hb595101" } ], "foreign_key": [] }, "actions": [ { "add": { "support_async": false, "class": "add", "href": "/api/view/HF_CallHandlerVIEW/add/?hierarchy=[hierarchy]", "method": "GET", "title": "Add" } }, { "export": { "title": "Export", "support_async": false, "submit": "payload", "class": "export", "href": "/api/view/HF_CallHandlerVIEW/export/?hierarchy=[hierarchy]", "method": "POST", "view": "/api/view/ExportData/add/?auth_token=[authtoken] } }, { "export_bulkload_template": { "support_async": false, "class": "bulkload_template", "href": "/api/view/HF_CallHandlerVIEW/export_bulkload_template/?hierarchy=[hierarchy]", "method": "POST", "title": "Export Bulk Load Template" } }, { "list": { "support_async": false, "class": "list", "href": "/api/view/HF_CallHandlerVIEW/?hierarchy=[hierarchy]", "method": "GET", "title": "List" } }, { "help": { "support_async": false, "class": "help", "href": "/api/view/HF_CallHandlerVIEW/help?hierarchy=[hierarchy]", "method": "GET", "title": "Help" } } ], "model_type": "view/HF_CallHandlerVIEW", "model_specific_actions": [ "add" ], "summary_attrs": [ { "allow_filtering": true, "name": "hierarchy_friendly_name", "title": "Located At" } ], "api_version": "20.1.1", "tagged_versions": [] }, "resources": [] }
Task | Call | URL | Parameters | Response |
---|---|---|---|---|
Get the on-line Help for view/HF_CallHandlerVIEW. | GET | /api/view/HF_CallHandlerVIEW/help | hierarchy=[hierarchy] | On-line help of Model ref.: view/HF_CallHandlerVIEW as HTML |
Task | Call | URL | Parameters | Response |
---|---|---|---|---|
Get a selected [export_format] of the schema and a single instance with [pkid] of view/HF_CallHandlerVIEW; optionally with tag_version at [version] and Configuration Template as [configtemplate]. | GET | /api/view/HF_CallHandlerVIEW/[pkid]/export/ |
|
The response is an attachment. Refer to the list below. |
For export_format=raw_xlsx, the response is a "raw" MS Excel spreadsheet with columns corresponding to the JSON format export and a response format:
Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_CCYY-MM-DD_HH-MM-SS.xlsx Content-Language:en Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
For export_format=xlsx, the response is a MS Excel spreadsheet, formatted to show all columns and a response format:
Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_formatted_CCYY-MM-DD_HH-MM-SS.xlsx Content-Language:en Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
For export_format=json, the response is a time stamped zip file of data in JSON and a response format:
Content-Disposition: attachment; filename=export_2013-05-17_14:20:19.186444.json.zip Content-Language:en Content-Type:application/x-zip
The XLSX format can be used to bulk load instances of view/HF_CallHandlerVIEW and the JSON format can be used to import instances of view/HF_CallHandlerVIEW.
For Bulk Export, refer to the Bulk Export section.
Task | Call | URL | Parameters | Response |
---|---|---|---|---|
Get | GET | /api/view/HF_CallHandlerVIEW/[pkid]/ | hierarchy=[hierarchy] | The view/HF_CallHandlerVIEW instance with [pkid]. |
Task | Call | URL | Parameters | Response |
---|---|---|---|---|
Help | GET | /api/view/HF_CallHandlerVIEW/[pkid]/help | hierarchy=[hierarchy] | The on-line Help for view/HF_CallHandlerVIEW. |