Naming conventions

This topic lists the requirements for naming various workflow-related items.

Workflow definitions

The name of a workflow definition must conform to the following rules:

TIP Workflow names that begin or end with spaces may be difficult to find when performing a search.

Attachments, data fields, event logs, indexes, operations, queues, rosters, rulesets, and workflow groups

Ensure that all names:

In addition, you cannot use any of the following reserved words for a name:

abs
adddays
addhours
addminutes
addmonths
addseconds
addyears
alt_field_defined
and
attachment
arraystring
bitand
bitnot
bitor
blue
boolean
color
convert
currency
date
datetostring
days_between
decode
dist_bernoulli
dist_beta
dist_binomial
dist_exponential
dist_gamma
dist_geometric
dist_lognormal
dist_normal
dist_poisson
dist_uniform
dist_weibull
document
elementcount
encode

envfield
err_encode
false
field_defined
float
folder
green
hex
if
in_set
int
is_date
is_null
is_number
is_time
is_valid
is_validxml
is_wellformed
len
integer
lower
ltrim
max
min
mod
nextelement
not
null
number
numbertostring
or
random
red
repeat
rtrim
seconds_between
selection

sizeof
stringtodate
stringtotime
string
strins
strloc
substitute
substr
systemdate
systemenvfield
systemtime
time
timetostring
translate
trim
true
unsigned
upper
userenvfield
userid
weekday
xmlinsertbefore
xmlinsertafter
xmlinsertchildfirst
xmlinsertchildlast
xmlremove
xmlrename
xmlbooleanexpr
xmlintegerexpr
xmlfloatexpr
xmlstringexpr
xmlstringarray
xmltransform
xmlemcode
xmldecode

Servers, database instances, databases, and tablespaces

On Windows-based systems, the following characters are not allowed:

* \ # [ ] ! < > - " (space)