We have been struggling with making service forms "obsolete" when using the catalog deployer. For example, we have customers who like to fill out requisitions and save them in an unsubmitted state. Whenever they need to submit the a requisition, they simply copy the unsubmitted request, fill out a few fields, and submit it. The problem is whenever something on the form changes, they lose the ability to copy the requisition because the form becomes "obsolete". In order to reclaim their templates, they have to remake the items from scratch.
Is it possible to change the service forms and also update their unsubmitted requsitions with the new form information so that the customer does not have to recreate the form? Do your customers save requisitions so that they can be copied? If so, how do you work around the changing forms?
We've struggled with this; also, when you mark a service as inactive and someone has it book marked, RequestCenter throws an error saying it can't find the 'orderinactiveservice.jsp' page, so even if it's inactive it throws an app error. We've put in a blank JSP page in the path ($AppPath$\comps\dictionary\) to mask this issue as the case has been open for a while.
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...