nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Additional Tokens?

FraserHand

Hi There,

Upon looking at the activity types in wmx, I saw that there is a whole heap of tokens that seem able to be used. Examples of these are [CUR_USER],[CUR_NT_USER],[STEP],[HOLD],[VERSION] - you get the idea.

These aren't described on http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Using_Tokens/00380000002m000000/ - getting hold of a IJTXParserTokenParser(2) and requesting GetSupportedTokens(2)() returns the list we see in the doc - but get this:

t = ps.Item[2] as IJTXTokenParser2;
{System.__ComObject}
    [System.__ComObject]: {System.__ComObject}
    Caption: "System"
    Name: "esriJTX.JTXSystemParser.1"
t.Parse("[CUR_NT_USER]",pJTXDB,job,null);
"handf"

So I'm guessing what I'm looking at is this on IJTXActivityType.Message - "The message that will be added to the job's history when this activity is performed. Tokens contained in the message will be parsed at runtime."

ah - but which parser is used and what tokens are accepted?

so there appears a whole heap of tokens available for configuring activities which would be useful. Has anyone got a list of these? Or what object will return them?

Many thanks,

Fraser

Vind meer berichten getagd met

Accepted answers

KevinBedel

Yes, you are correct. The [Version], etc items cannot be reused in any new activity types.

DEAF_PROBERT_68_0-1785852378550.png

All comments

KevinBedel

Yes, you are correct. The [Version], etc items cannot be reused in any new activity types.

DEAF_PROBERT_68_0-1785852378550.png

FraserHand

Hi Fraser,

The first two tokens that you list in your example ([CUR_USER],[CUR_NT_USER]) are old tokens that are still supported for backwards compatibility.

Hi Kevin,
Thanks for that. This was slightly confusing as you are still using these older tokens in the OOTB activities etc, and use the other tokens in some tasks without explaining the use etc. So we cannot reuse any of the [VERSION] etc in any activities we create?
Thanks,
Fraser

KevinBedel

Hi Fraser,

The first two tokens that you list in your example ([CUR_USER],[CUR_NT_USER]) are old tokens that are still supported for backwards compatibility. These are the equivalent of [SYS:CUR_LOGIN], which can be used instead.

The other items you list ([STEP],[HOLD], etc.) are special values that are not parsed by the token parsers. Instead, these are specific to the activity types they are used in, and are just substituted by the Workflow Manager application. These are not supported in other cases beyond the out of the box activity types.

The list of documented tokens is the complete list of supported tokens that can be utilized in any aspect of Workflow Manager that supports tokens.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.