I'm trying to create a report that shows Service Name (with a filter showing specific services), Requisition ID, StartDate, Due Date, Close Date, Task Name (with a filter for specific tasks), Task Status, and Performer. Seems simple right? Not so far. Unfortunately, I can't combine the report using Service Name and Task Name. What am I doing wrong or is it that its not possible?
Do you need authorization tasks to show in this report as well? If so do you use departmental authorizations, service authorizaitons and financial or just one of the three?
Lastly, what I'm sure you've found is the difficulty getting the specific tasks that were routed for a specific service that was requested on a specific requisition. To do this you'll need to make use of the RequisitionEntryID. This is the only key between those three areas.<
both....they need the status of the service and the status of the task.
fields needed: service name, requisition id, service status, service start date, service due date, service closed date, task name, task status, performer first and last name, task due date, task completed date, task actual duration.
Alternatively, you can use ReportDesigner (Report Studio) with 2 lists, one at the Service Request level and another at the Service Task level. These 2 lists can be driven by a list of Requisition Entry IDs.
The design that I am thinking about is to use cascading prompt - User is prompted to choose one or more Service Name to report on, which then generate a list of Requisition Entry IDs in the system. Simply select all on the Requisition Entry IDs, and
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...