Cisco Cisco Process Orchestrator 3.0 Release Notes
2
2
New Features and Enhancements
The following topics describe the new features and enhancements introduced in Cisco Process Orchestrator:
•
Service Catalog Adapter—enhancements to the existing Cisco Prime Service Catalog Adapter. It includes the integration
with the Queue Service Request, a new feature in Cisco Prime Service Catalog 10.1 release and shifts to use nsAPI for Service
Item related activities rather than the prior Service Link API.
with the Queue Service Request, a new feature in Cisco Prime Service Catalog 10.1 release and shifts to use nsAPI for Service
Item related activities rather than the prior Service Link API.
•
Integrate Hidden Variables with Service Catalog Secure Data Type—Encrypted data is now allowed in standard payloads
to be pushed to hidden variables within the Cisco Process Orchestrator layer.
to be pushed to hidden variables within the Cisco Process Orchestrator layer.
•
Self-Signed SSL Certificate for NorthBound Web Services—allows for the install of a self-signed certificate for use in
securing communication with the Northbound Web Services in Cisco Process Orchestrator 3.0.2.
securing communication with the Northbound Web Services in Cisco Process Orchestrator 3.0.2.
•
External String Encryption—Cisco Process Orchestrator's encryption and “hidden string” features can be exposed for use
to external callers to improve security of the data passed between different products.
to external callers to improve security of the data passed between different products.
•
Email adapter enhancement—allows users to modify polling frequency used by the Email Adapter.
•
String Length enhancements—provides the capability to return the length of a string within a workflow reference.
Service Catalog Adapter
In Cisco Prime Service Catalog 10.1, the Service Designer can define a Queue Service Request. The Queue Service Request
enables publication of the Service Request data to a message broker. Cisco Process Orchestrator subscribes to the specified queue
of the message broker. Upon receiving the Queued Service Request message, Cisco Process Orchestrator will trigger a workflow
to act on the service request; and update the status of service request contained within the Queued Service Request via Cisco
Prime Service Catalog REST nsAPI. Cisco Prime Service Catalog Server also provides REST nsAPI for Cisco Process
Orchestrator to obtain the detail of the AMQP message broker for each service request. The enhanced Service Catalog Adapter
also uses nsAPI instead of Service Link API to perform Service Item related activities starting this release. This removes the
requirement of using Channel ID as in the prior releases.
enables publication of the Service Request data to a message broker. Cisco Process Orchestrator subscribes to the specified queue
of the message broker. Upon receiving the Queued Service Request message, Cisco Process Orchestrator will trigger a workflow
to act on the service request; and update the status of service request contained within the Queued Service Request via Cisco
Prime Service Catalog REST nsAPI. Cisco Prime Service Catalog Server also provides REST nsAPI for Cisco Process
Orchestrator to obtain the detail of the AMQP message broker for each service request. The enhanced Service Catalog Adapter
also uses nsAPI instead of Service Link API to perform Service Item related activities starting this release. This removes the
requirement of using Channel ID as in the prior releases.
Note
Version 10 and higher are supported. Versions earlier than 10 (i.e. 9.x and prior) are no longer supported.
Integrate Hidden Variables with SC Secure Data Type
Encrypted data is now allowed in standard payloads to be pushed to hidden variables within the Cisco Process Orchestrator
layer. If this data is encrypted using the public key provided from Cisco Process Orchestrator, Cisco Process Orchestrator
recognizes the encrypted string and processes it.
layer. If this data is encrypted using the public key provided from Cisco Process Orchestrator, Cisco Process Orchestrator
recognizes the encrypted string and processes it.
Self-Signed SSL Certificate for NorthBound Web Services
By installing a self-signed certificate for use in communicating with the NBWS, all traffic to orchestrator servers are encrypted
and therefore secure by default. Optionally, you can override the default certificate with a certificate from a trusted authority
using the “Web Service” tab of the “Environment Properties” configuration page. For further information, see your NorthBound
Web Services Guide.
and therefore secure by default. Optionally, you can override the default certificate with a certificate from a trusted authority
using the “Web Service” tab of the “Environment Properties” configuration page. For further information, see your NorthBound
Web Services Guide.
Note
If upgrading from a previous version of Cisco Process Orchestrator with a certificate configured for use with the secure
NBWS, reconfigure the certificate on the Web Service tab in the Environment Properties dialog. The Cisco Process
Orchestrator server now actively manages the certificate for this port and will assign a self-signed certificate by default.
In the event that a custom certificate is being used in a prior release, override the default certificate created by the
Orchestrator server.
NBWS, reconfigure the certificate on the Web Service tab in the Environment Properties dialog. The Cisco Process
Orchestrator server now actively manages the certificate for this port and will assign a self-signed certificate by default.
In the event that a custom certificate is being used in a prior release, override the default certificate created by the
Orchestrator server.