Tokens

Mit der Standard- oder Advanced-Lizenz verfügbar.

Mit der Workflow Manager-Lizenz verfügbar.

Tokens are placeholder text for dynamic properties that will be placed at run time. For example, if you want to define an email message that will be sent automatically at certain times and you want to date-stamp the message, you can add a placeholder token that will be swapped out at run time with the value of date. ArcGIS Workflow Manager provides a mechanism for defining messages and strings using tokens, and they will automatically be parsed and updated before being used. Some of the elements in Workflow Manager that use tokens are the following:

• Job naming schemes (job name, version name, and so on)
• Queries (current user or groups)
• Job history messages (see activity types)
• Notification messages
• Step locations, arguments, descriptions

The Workflow Manager application has a token expression builder that is accessible in the parts listed above. For example, on the Naming tab on the Job Types dialog box, you can click the Token Expression Builder button to view available tokens.

Tokens are categorized into specific parsers. There are six parsers included in Workflow Manager:

1. Job parser—Responsible for swapping out job properties
2. Extended parser—Responsible for swapping out extended job properties (1-1 only)
3. System parser—Responsible for swapping out system properties, such as current date or user
4. Function parser—Responsible for carrying out certain functions on specified text, such as getting the email address of a user
5. Spatial Notification parser—Responsible for swapping out properties related to spatial notifications
6. Environment Variable parser—Responsible for swapping out environment variables, such as the TEMP folder

These parsers are, by default, parsed in the above order. This is important because some parsers may rely on the output of previous parsing to work correctly. For example, the following string contains two tokens.

Please contact the current user at

[EMAILOF([SYS:CUR_LOGIN])]

The first is a function parser token and the second is a system parser token. The EMAILOF token requires an input parameter that is the result of another parsing; therefore, the system parser must run first.

Hinweis:

Some job tokens, like [JOB:ID], are not applicable in queries and report an SQL WHERE clause. The queries and reports generate output based on all jobs in the database and cannot be filtered on a specific job's ID.

Each parser may contain any number of tokens. The following table lists the currently supported tokens and the parser to which each belongs.

Parser	Token	Description	Example input	Example output
Job	[JOB:ID]	Job ID	[JOB:ID]	1642
	[JOB:PARENT_VERSION]	Parent version for the job version	[JOB:PARENT_VERSION]	SDE.Default
	[JOB:VERSION]	Version name	[JOB:VERSION]	Workflow Manager_1642
	[JOB:TYPE_ID]	Job type ID	[JOB:TYPE_ID]	4
	[JOB:TYPE_NAME]	Job type name	[JOB:TYPE_NAME]	TRANS
	[JOB:OWNED_BY]	Job owner	[JOB:OWNED_BY]	jbloggs
	[JOB:CREATED_BY]	User who created the job	[JOB:CREATED_BY]	fjones
	[JOB:NAME]	Name of the job	[JOB:NAME]	JOB_TRANS_1642
	[JOB:STATUS_ID]	Job status ID	[JOB:STATUS_ID]	12
	[JOB:STATUS_NAME]	Job status name	[JOB:STATUS_NAME]	Created
	[JOB:STAGE_ABBRV]	Job stage name (short)	[JOB:STAGE_ABBRV]	W
	[JOB:STAGE_NAME]	Job stage name (long)	[JOB:STAGE_NAME]	Working
	[JOB:ASSIGNED_TO]	Who the job is assigned to	[JOB:ASSIGNED_TO]	fjones
	[JOB:ASSIGNED_TYPE]	Assigned to group or user	[JOB:ASSIGNED_TYPE]	User
	[JOB:ATTACHMENTS]	List of attachments	[JOB:ATTACHMENTS]	manifest.txt input_map.pdf
	[JOB:STARTED_DATE]	Date the job was started	[JOB:STARTED_DATE]	12/8/04
	[JOB:END_DATE]	Date the job was completed	[JOB:END_DATE]	12/20/04
	[JOB:START_DATE]	Dat