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

Submitting Multiple Files

smarchetti

I have a challenging task and I need some help. Here is the current situation. Using Content Center Standard, a user creates or edits a dcr, saves it, and generates a page. The presentation template that is used calls two additional presentation templates, one for generating or re-generating a printable version of the page, and one for re-generating an index page. Everything up to this point works perfectly, but I now need to take advantage of a workflow that will automatically deploy these files. I am currently using the solutions/configurable_default_submit.wft file that came standard with TeamSite, and it is kicked off via a submit or a tt_data command. This works fine, but it will only submit the dcr and the main page created via the first presentation template. I am looking for a way to have this workflow or a similar workflow automatically include the print version of the page as well as the newly re-generated index page. Any suggestions? Thanks.

--
Sean Marchetti
smarchetti@hess.com

Find more posts tagged with

Comments

Dwayne

I don't think that you'll be able to find any configuration settings for the solutions workflow that will "automatically" pick up these additional files. You might be able to make a copy of it, and find the block of code that generates the <files> </files> section. If you can programmatically figure out the path to the auto-generated files based on the filenames that ARE provided, then you should be able to just explicitly add them to the <files> </files> section, and be good to go.

--

Current project: TS 5.5.2/6.1 W2K

Migrateduser

I don't know much about the configurable workflows, but for a custom workflow I would probably go with ExternalTask logic to add any related files before each read-only user or group task. That way, if a user adds a DCR during the workflow process the output files get attached. I would have your generation logic set attributes on the DCR indicating what files were generated, then have your ExternalTask logic check that and attach any missing references.

gzevin

John,

it's not that obvious - files that are generated from component presentation templates DO NOT have extended attributes that make them look like generated (templated) files

I'd reccomend to use the following technique - in fact, iwpt_compile if invoked with appropriate options, can produce an XML manifest, that will include all the files that got generated by a presentation template. Then this file needs to be parsed in order to retrieve all the file names, and these files could be attached to the workflow.

and, naturally, this is not a trivial task.. but doable...

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

smarchetti

Thanks for the response. I am pretty sure that I will be able to determine the names of the files that will need to be submitted based on the name of the file that is automatically getting attached to the workflow. Do you suggest that I add this logic to the configurable workflows as an external task or to a new workflow that I should write? Thanks.

--
Sean Marchetti
smarchetti@hess.com

Adam Stoller

Probably a combination. Make a copy of the configurable workflow (since you will be changing a product deliverable) and then add your customizations to the copy. Unless you find more aspects of the workflow that doesn't do what you want, there's no need to re-invent the entire wheel if all you want to do is add a hub-cap ;-)

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