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; } } }

Cant get a solution wf to work

nico

As the Author submits in ccs the Error I'm getting is "Invalid workflow: ERROR: Bad task name Author Work in activation ERROR: 00001: Failure in operation"

Trying to get the "Configurable Author Submit" workflow going. Using TS 6.5 sp1 win. Thoughts?

Thanks,
Nico

Find more posts tagged with

Comments

Adam Stoller

As the Author submits in ccs the Error I'm getting is "Invalid workflow: ERROR: Bad task name Author Work in activation ERROR: 00001: Failure in operation"

Trying to get the "Configurable Author Submit" workflow going. Using TS 6.5 sp1 win. Thoughts?

Thanks,
Nico

Sounds like you broke something in the wft code - without seeing the actual code it's difficult to tell you where you (or someone else) went wrong.

nico

I've attached the solution wft file however I was under the impression that one did not even have to edit that file but rather one simply edits the xml file that associates with it, is this assumption incorrect?

And yes I did read the manual in case anyone is wondering.

Adam Stoller

I've attached the solution wft file however I was under the impression that one did not even have to edit that file but rather one simply edits the xml file that associates with it, is this assumption incorrect?

And yes I did read the manual in case anyone is wondering.

It looks like you have workflow debugging enabled - is it possible to see the output job description file? Or is this erroring out before it can get to that point?

'author_work' appears to be getting defined and appears to be linked from 'email_author' and linked to 'metadata', both of which also appear to be defined.

What associated XML file did you edit?
Did you keep a copy of the original so that you can easily determine the changes that were made?
Can you post the XML file you changes (I'm assuming we're not talking about available_templates.cfg)

nico

configurable_author_submit.cfg was the only file that was edited, besides available templates too of course.

I've attached the wftdebugmode output and the .cfg file mentioned above.

nipper

If you look at the XML that is created, it is a 2 step WF, submit and end.

However the submit step has a pred. step defined, loking for the Author Work.

So, if you really only modified the config file and did not change the WFT, then this WF will not work with only 1 step. You could try to remove that statement (the pred entry in the submit task) and see what happens.

Andy

Adam Stoller

configurable_author_submit.cfg was the only file that was edited, besides available templates too of course.

I've attached the wftdebugmode output and the .cfg file mentioned above.

Okay - clearly something is going on here - perhaps I missed a conditional in the original posting (I'll have to go back and look after I look at the config file you posted) - but the generated job description file looks like:

<workflow name="Author Submit" owner="fhlbsf\forondaa" creator="FHLBSF\forondaa" description="x">

    <!-- This job was created using solutions/configurable_author_submit.wft -->

    <submittask name="Submit" owner="fhlbsf\forondaa" description="Content Submission" start="t" unlock="t" savecomments="t">
        <areavpath v="/default/main/www/public/WORKAREA/mktg"/>
        <successorset>
            <succ v="End"/>
        </successorset>
        <files>
            <file path="about/resources/default.asp" comment=""/>
            <file path="templatedata/public/AU_resources/data/resources" comment=""/>
        </files>
        <activation>
<pred v="Author Work"/>
        </activation>
        <variables>
            <variable key="submit_cmt" value="x"/>
        </variables>
    </submittask>

    <endtask name="End">
        <activation>
            <pred v="Submit"/>
        </activation>
    </endtask>
</workflow>

Note that there is a predecessor specification for "Author Work" but there is no such task defined.

The high-degree of configurability in this wft makes it hard to debug visually. I'd suggest trying to debug this a bit more, perhaps get Support involved (there might be a bug in the declaration of tasks as being dormant and properly determining the full transition path (I don't see anywhere that author_work is declared dormant - so it *should* be in the resultant job description file, but apparently it isn't).

Maybe someone else who has an available environment to play in could try using your version of the config file and see if they can reporduce the problem. That's about all I can offer.

nico

Issue resolved thanks to IW support, they noticed in my wft file that there were 2 spaces in front of one line. Can you believe that? 2 freakin spaces made the darn thing fail, nutty.