ea(start|stop)op

I'm trying to use eastartop in my workflow. According to the documentation I can use pre-defined variables to set such things as workflow name, id etc

Here is what I have on one of the tasks:

Everything is fine, BUT.

the workflow_id EA on the files is in hex format, looks like %workflowid; does not convert the value to the decimal value.

Is it a bug or a feature?

Find more posts tagged with

Comments

Migrateduser

Umm, what command are you referring to and where did you see this in the documentation and in which document? I don't think there *is* an "eastartop" CLT.

Dave

Migrateduser

Dave - It's not a CLT. It's an option in the wft that sets extended attributes on files when the task either activates or deactivates.

As for the behaviour, the documentation isn't clear on what the format should be, so I would guess it's a feature.

hideColumnBasedOnParameter.rptdesign

Valentine

Yes.
It's in a workflow jobspec.

The documentation is "the workflow developers guide" (ts.650a.wf.pdf), p141

Adam Stoller

I'm trying to use eastartop in my workflow. According to the documentation I can use pre-defined variables to set such things as workflow name, id etc

Here is what I have on one of the tasks:

Everything is fine, BUT.

the workflow_id EA on the files is in hex format, looks like %workflowid; does not convert the value to the decimal value.

Is it a bug or a feature?

You should report this as being either a documentation bug or product bug - my guess is documentation, although it would be nice if the value was provided in decimal format, the hex format is consistant with the values provide to iwat triggers from the event [sub]system - you can use perl's built-in functions to decode it where needed (I'm assuming that somewhere along the line you're referencing this EA via perl - though perhaps not)