Cisco Cisco Prime Service Catalog 10.0 技术参考
1-41
Cisco Prime Service Catalog Designer Guide
OL-31033-01
Chapter 1 Service Design Fundamentals
Configuring the Delivery Plan
Condition
A conditional 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
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
After you enter an expression, click Validate to make sure that the expression is
correct.
correct.
Validation checks if:
•
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.
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.
The message “unexpected token” indicates that the namespace used is not valid in
this context or, perhaps, that you have forgotten to enclose an alphanumeric literal
in quotes.
this context or, perhaps, that you have forgotten to enclose an alphanumeric literal
in quotes.
If a condition has been entered, you must decide when that statement will be
evaluated. The condition for each task (approval, review, or delivery) can be
evaluated either:
evaluated. The condition for each task (approval, review, or delivery) can be
evaluated either:
•
At the beginning of a phase (Authorization or Delivery moment), or
•
When the activity becomes active.
Allow a scheduled
start date
start date
To make the task a delayed task, check Allow a scheduled start date. Then, in the
Form data for start date field, do one of the following:
Form data for start date field, do one of the following:
•
Enter a date and time in the following format: “YYYY-MM-DD HH:MM”
such as “2006-12-23 13:30” (The quotes are required.)
such as “2006-12-23 13:30” (The quotes are required.)
•
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:
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.
the service’s active form components.
–
ParentData.DictionaryName.FieldName for a field from one of the parent
service’s dictionaries (in the case of a bundled service).
service’s dictionaries (in the case of a bundled service).
For more information about delayed tasks, see
Form data for start
date
date
If you have checked the “Allow a scheduled start date” option, you may enter form
data for the start date and click Validate.
data for the start date and click Validate.
Field
Description