Cisco Process Orchestrator 3.5.1 Release Notes
Cisco Process Orchestrator Support
Unable to Upgrade Cisco Process Orchestrator 3.5.1 Using Pre–Created Database Using qsaq Account
Obtain Documentation and Submit a Service Request
This document describes key features, product requirements, enhancements, and known issues in this release of Cisco Process Orchestrator. For more information about this release, refer to the appropriate product guides.
To access the most current Process Orchestrator documentation, including these release notes, see http://www.cisco.com/c/en/us/support/cloud-systems-management/process-orchestrator/tsd-products-support-series-home.html.
Cisco Process Orchestrator is the foundation on which to standardize, unify, and automate best practices for IT processes in complex, heterogeneous environments. Through its unique ability to automate the end-to-end service delivery process across the entire IT landscape, Cisco Process Orchestrator allows organizations to improve business alignment and adaptability, rapidly provision new services, achieve vendor interoperability, and reduce risk. Automating tasks that IT staff would otherwise perform manually improves alignment to best practice and improves security, quality, and productivity.
For the complete list of inter-operable components and version/release information, see the Cisco Process Orchestrator 3.5.1 Compatibility Matrix located here: http://www.cisco.com/c/en/us/support/cloud-systems-management/process-orchestrator/products-device-support-tables-list.html.
Cisco Process Orchestrator is primarily purchased as a part of various solutions. The packaged automation packs in these solutions specialize Process Orchestrator to a particular domain and provides the solution’s value.
The solution compatibility matrix governs which Process Orchestrator versions are supported with each solution version (such as Cisco Intelligent Automation for Cloud). For example, although separate solution downloads will typically not require any updates to the Process Orchestrator release, customers should check the solution’s compatibility matrix for specifics because on occasion a specific Process Orchestrator patch level might be required.
When an order is placed, the customer receives their Claim Certificate. The Claim Certificate provides the Product Authorization Keys (PAK) and a link to the Cisco Product License Registration Portal where the PAK keys are registered.
The licensing team will then issue the customer their keys. Customers should contact Cisco Technical Support and will be referred to the Global Licensing Organization (GLO) to request a new license code.
After you receive the new license code, enter the license into the Cisco Process Orchestrator Update Product License dialog.
Along with general user experience improvements and bug fixes, the following are additions and enhancements to Cisco Process Orchestrator for this release.
■CLI to apply an automation pack patch
■Create Approval Request from Table
■Run Start Process REST API without web service trigger
■Enhanced Read Table from Text Activity
The following are some of the known issues with Cisco Process Orchestrator 3.5.1, with solutions and workarounds, if available.
Upgrade fails removing process database that was pre–created manually. This applies to only sql server that used 'sa' account to create the database while using windows account from installer to connect to process database.
Upgrade process database using the same windows account that was used in the original install.
When the existing process schema is selected first and then changed to System user after traversing Back in the installer UI, the error message pops up and the installer does not allow you to progress. This issue applies only to manually created process database schema.
Cancel the install and restart. Enter proper process database schema and avoid traversing back.
Swagger API is missing a field to allow users to specify a Name or ID of the task to create or update.
Many APIs append “––XXXX” to the name of the object created or updated. This cause the name of the created object to have a different name than the intended name. Which sometimes causes the API to update the wrong object if there is an object with such name or fail to update the object if there is an object with the specified name plus the appended portion. This is only an issue with Swagger. It's not an API issue.
Use the “Bug Search” tool to search for a specific bug or to search for all bugs in a release.
1. Go to http://tools.cisco.com/bugsearch.
2. At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Search page opens.
If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.
3. To search for a specific bug, enter the bug ID in the Search For field and press Enter.
4. To search for bugs in the current release, click the Search Bugs tab and specify the following criteria:
a. In the Search For field, enter Process Orchestrator 3.5.1 and press Enter. (Leave the other fields empty.)
b. When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can search for bugs by modified date, status, severity, and so on.
Note: To export the results to a spreadsheet, click the Export All to Spreadsheet link.
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.