is Internal. This is the only option displayed for a site that has no Service
Link integrations defined with external systems and no Service Item tasks.
if the task is executed within Service Catalog.
option if the task is executed in an external application (not within Service
Catalog). For external tasks only, an ellipsis (...) button appears next to the
Workflow Type after you have saved the task. See the
Configuring an External Task
for more information.
you are using Service Item Manager module to design service items and track
these items. More information on service item tasks is given in the
Defining Service Item Task in a Delivery Plan
Managing the Services and Attributes.
Service Request to publish the Service Request data to a rabbitmq message
broker server. An external system subscribed to rabbitmq broker and the
specific exchange will receive the message and can execute its own work flow.
Task to grant or revoke permissions for a service item or multiple service
items that are created using grid dictionaries within the service delivery
plan. For more information, see
Creating Service Delivery Tasks for Granting and Revoking Permissions for a Service Item.
Directory Task if the operation is for adding or updating Organization Designer
entities (organizational units, people, queues) or Service Link agents.
Defining Delivery Tasks
for more information.
A brief title
for the task. This appears as the subject of the task in Service Manager. The
delivery task name may include the service name, using the #Name# namespace.
Service data (#Service.Data....#) can also be used.
data for a task name allows task performers to more easily differentiate tasks
in Service Manager. However, it presents challenges in the reporting modules,
since the task would no longer be automatically groupable by the task name;
report designers would need to use “Custom Groups” to aggregate by such tasks.
It may also require administrators to configure Service Manager to allow
“contains” searches, which may adversely affect performance. Service designers
should think carefully before including form data namespaces as part of a task
have saved the task, a Create Agent button appears. Click this button to use
the Integration Wizard. See the
Cisco Prime Service Catalog
Adapter Integration Guide for complete details.
Integration Wizard is available only to those service designers who have been
granted a role that allows creation of Service Link agents and transformations.
Integration Wizard automates many of the steps involved in implementing an
integration. It is available only for creating integrations between Service
Catalog and web services.
Integration Wizard works by retrieving the Web Services Description Language
(WSDL) and operation to be invoked by the web service integration. Based on
that definition of the integration, the Integration Wizard creates:
- The Service Link agent that
can be used in an external task to perform the integration
- A transformation to
transform nsXML into the SOAP message required by the web service
- Agent parameters for all
data required both in the initial web service request and the response
- A dictionary containing
fields mapped to the agent parameters
- An active form component
containing the dictionary created to hold agent parameter values
drop-down menu to choose the order in which any “child” tasks of this task
execute: one after the other (sequentially) or at the same time (concurrently).
(subtasks) become active (ongoing) in the delivery plan, and must be completed
before their parent task becomes active.
tasks are executed sequentially, the service duration includes the durations of
all such tasks. If tasks are executed concurrently, the service duration
includes the maximum duration of any child task.
length of time between when the system says the task is active (begins) and
when the task is completed, rounded to two decimal places.
if installing a software program only takes one hour, you might give the
performer a duration of 16 hours to finish the task, as the performer's
workload and priorities may vary throughout the course of two workdays.
value is not visible to the customer or performer, but is used to calculate the
due date for the task.
length of time it should take the performer to complete the task, rounded to
two decimal places. For example, it might take one hour to install a software
program. While Duration is “total elapsed time”, Effort is “time on task”.
value is not displayed to any users or used in due date calculations; it is
used instead as an Internal Productivity Target.
Set the task
priority to low, normal, or high. No system behavior is tied to the priority
for a task, other than a flag which is visible in Service Manager.
- If the priority is set to
system sets a red exclamation point in the Service Manager view where the task
- If the priority is set to
low, the system
sets a blue down-arrow in the Service Manager view where the task is displayed.
- If the priority is set to
normal, no flag
is displayed in Service Manager.
statement allows tasks to be initiated or skipped based on the whether the
expression used in the condition evaluates to true (include this task) or false
(skip the task). The expressions are formulated using the namespaces and
operators documented in
enter an expression, click
to make sure that the expression is correct.
- Namespace specified is valid
for the current scope (the specific level of review/authorization or task),
with the exception of dictionary fields (Data.DictionaryName.FieldName
). However, it may cause a runtime error: if the specified namespace, for
example, Data.EUIT_ACCESS.Access_Type, does not exist.
- Correct relational and
arithmetic operators are used.
“unexpected token” indicates that the namespace used is not valid in this
context or, perhaps, that you have forgotten to enclose an alphanumeric literal
condition has been entered, you must decide when that statement will be
evaluated. The condition for each task (approval, review, or delivery) can be
- At the beginning of a phase
(Authorization or Delivery moment), or
- When the activity becomes
condition that always evaluates to false (for example, “1=2”) in a conditional
statement to specify a task that will automatically be skipped.
common use cases for this are:
- When a service needs to
“auto-complete” without having any tasks completed. The skipped task is the
only task in the delivery plan. When it is skipped, the requisition is marked
- When an email needs to be
sent without having to complete a task or when multiple emails are needed
during a given moment in the following ways:
- Create a parent task. On
the Email subtab, choose an email to be sent out at completion. (You may also
configure a notification to go out when the activity becomes active.) For more
Defining Email Notifications for Delivery Tasks.
- Create a child task with
the condition 1=2. Set the condition to evaluate when the activity becomes
scheduled start date
To make the
task a delayed task, check
scheduled start date .Then,in the Form data for start date field, do one of
- Enter a date and time in
the following format: “YYYY-MM-DD HH:MM” such as “2006-12-23 13:30” (The quotes
- Or, enter the name of the
dictionary field you want to use to hold the date and time of the
starting-point for the task. Use the following syntax:
Data.DictionaryName.FieldName for a field from a dictionary in one of the
service’s active form components.
for a field from one of the parent service’s dictionaries (in the case of a
information about delayed tasks, see
Behavior for Scheduled Start Tasks.
for start date
If you have
checked the “Allow a scheduled start date” option, you may enter form data for
the start date and click
condition when delivery phase starts
If you have
specified a condition, click the option button to indicate when the condition
will be evaluated. Choose this if you want the condition to be evaluated when
the delivery moment starts for this service. This means that the information
required to correctly evaluate the expression must be available before the
delivery moment begins. Each authorization or review has its own moment; all
delivery tasks are performed within the Service Delivery moment.
Authorization tasks are always serial. You could put one conditional on one
task saying if field = “x” and a conditional on another saying field < >
“x”. That way, you know one authorization task will always be executed, and if
you choose “when authorization phase starts” only one authorization task will
appear in the process view. If you choose “when task becomes active” both tasks
would be displayed, but one would be skipped.
zero” statement means that Service Catalog will
evaluate the conditions at the beginning of the phase. If these conditions are
false, then the corresponding tasks will not be executed, and the
Date for the service will be calculated without
including the duration of these tasks.
condition when task becomes active
If you have
specified a condition, click the option button to indicate that the condition
must be evaluated only when the delivery process has reached this task in the
Catalog evaluates the condition at the beginning of each task. If the condition
is false, the corresponding task will not be executed. Durations for any task
configured with this option will be used to calculate the due date upon
expressions as plan advances
feature enables you to dynamically change the performer assignment for a task,
as well as the name of the task, based upon form data. This is useful if you
have designated that a task name or a performer assignment should be derived
from a namespace expression using form data, and when the form data will be
changed during the delivery process.
this flag specifies that the expression should be evaluated when the task
becomes active (not when the entire delivery plan is initiated). If this option
is not checked, all information used in expressions in the authorization task
must be present during the Ordering moment.
Re-evaluate Expressions feature is useful for designs in which there are
multiple sequential authorizations or tasks. It enables the person performing a
task to enter information in the service form that is used to recompute the
expression used to assign the performer for a subsequent task.
feature allows dynamic assignment of a task to a user (person or queue) and
dynamic adjustment of the task title. Once the task becomes active, the
expression is evaluated and the task is assigned appropriately.
re-evaluation of the performer for a task does not affect the due date for the
task. Due dates are not recomputed after the delivery moment begins.
allow cancellation of service after task starts
select this check box, the customer will no longer be able to cancel the
service after this task becomes active.
example, check this if the task will cause the delivery team to incur
substantial costs or take an action that is not easily reversible.
“Cancel” option in My Services is deactivated once the delivery team begins
Effort subpage on a delivery task
check this box, an “Effort” subtab for a delivery task is shown in Service