Email Namespace for Ad Hoc Task's Expected Duration & Due On fields?
How do I Question: How does one reference Expected Duration and Due Date Namespace for an Ad Hoc Task to an email template?
I'm new to service design...period. I'm trying to include the Expected Duration and the Due Date of an Ad Hoc task in an email template. But I can't tell from looking at my training material what the Namespace is supposed to be. Can anybody help? (Thanks in advance from a RC newbie.)
Email Namespace for Ad Hoc Task's Expected Duration & Due On fie
I'll jump in here. All of the namespace variables that are listed for Tasks and Service Group Authorizations/Reviews (starting on page 30 of the Namespace Guide) will work. Some of the more commonly used for task-related emails:
#Subject# -- name of the task #DueOn# -- due date/time (***in GMT***) #ExpectedDuration# -- duration in hours #Requisition.RequisitionID# -- requisition number #Service.ServiceDefinition.Name# -- service name #Instructions# -- instructions entered by the creator of the ad hoc task #Customer.FirstName# #Customer.LastName# -- person who created the ad hoc task #URL# -- use this to link directly to the ad hoc task
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...