Submit Workflow

We came across something interesting, and only as of recently, something that's a little baffling...

We have one workflow configured for a particular branch, for all commands (except the TFO ones, don't have TFO installed). So when a user is done generating from FormsPublisher in CCPro, they will get prompted with options for this one workflow. But instead, they are seeing the default submit workflow (which is setup only for submit command). And it's only for certain category/data-types, and certain files, why would that be? We have verified that there is not already another job with those files attached.

Any thoughts on this oddity?
We are on TS 6.5 on Solaris, using CCPro.

Raf Winterpacht
HSBC Technology Services
TS 6.5

Find more posts tagged with

Comments

jkm

Can you post your available_templates.cfg file?

shanon

Raf,

Yes, please post your available_templates.cfg, but so you know, when you are done generating from FormsPub, it does trigger a "submit" command. So, you may be seeing what you're supposed to.

Try removing the "submit" from the default submit, and adding the "submit" to your custom workflow and see what happens. If this works properly, then just change the branch regexp to exclude the spots that you want to default to the custom workflow.

Also, you can play around with the "tt_data" options as well. Consult the WF docs on this.

HTH,

Shanon

rwinterpacht

Hi,
I will post the relevant workflows, and I do appreciate the second pair of eys on this.
The workflow that's giving us the problem is the last template listed, the microsite workflow.

Thanks!

Raf Winterpacht
HSBC Technology Services
TS 6.5

jkm

Hey I just tried you config file on my test system and it comes fine .. Can you check the branch names if any change on those or rename

<branch value="default/main/intranet_content" include="yes"/> to <branch value="default/main" include="yes"/> something and try after that

rwinterpacht

Hi,
It doesn't work exactly as expected. We have the same user, same role, same branch (regex in cfg file), same command, and depending on the category/data-type, it will show the ONE configured microsite workflow, or just the default submit workflow.
What would be good is to figure out how to troubleshoot this, or have some kind of a way to call available_templates.ipl with the appropriate arguments, and have it return the list of workflows.

Raf Winterpacht
HSBC Technology Services
TS 6.5

LegendIssue.rptdesign

Adam Stoller

I'm not sure whether this would be causing any problems - but you have a number of entries in your available_templates.cfg file that look like this: <branch value="all" include="yes"></branch>which should really look like this: <branch value="all" include="yes"/> as these are "empty" elements.

Also - you have some entries like: <branch_list>
<branch value="all" include="yes"/>
<branch value="default/main/content_management_projects/hsbc/hsbcusa.com" include="no"/>
<branch value="default/main/intranet_content" include="no"/>

</branch_list>which I believe should really be like this: <branch_list>
<branch value="default/main/content_management_projects/hsbc/hsbcusa.com" include="no"/>
<branch value="default/main/intranet_content" include="no"/>

<branch value="all" include="yes"/>
</branch_list>as I believe the directives are processed in a top-down fashion, so the declaration for 'all' should always appear last in the list.

I'm not sure that either of these explain the behavior you're seeing - but I'd recommend fixing the config file as per the above and then seeing if you can still replciate the problem.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rwinterpacht

Hi,
Thanks for the tips there, it didn't make a difference. As far as the way the tags are closed, that really shouldn't matter, at least functionally it shouldn't.
I think we should get some kind of a way to troubleshoot this, by getting all the right arguments to available_templates.ipl, and see what it returns. Start playing with those arguments, and print some debug info.
My next step is to open a case...it's pretty low priority, however, because the workaround is to submit the content, then select New Job and pick the microsite workflow.
Thanks again!

Raf Winterpacht
HSBC Technology Services
TS 6.5

jbonifaci

Did you try what Adam suggested and re-ordering your branch elements in your branch list? Adam was correct in saying that the first element matched will be used. So if your all is first, the remaining branch elements will be ignored.

~Jeff