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

emailNotification showing success but no files listed.

System

I an running a email results with emailNotification_textbody.tpl and there is not file list showing up. I can creat a list from the deploy callout but the default email template is not getting the list of files.

If I look in the task_outputxxxxx.xml there is no files listed. they are infact deployed.

Find more posts tagged with

Comments

BlueWhale

Are you sure you're looking at the right task_output file?

The Email tpls look for the task_outputXXX.xml file. If the files aren't listed out there, you're not going to get them in your email.

For more information, could you post your task_output.xml file and the tpl?

Migrateduser

that is correct they are not listed in the task output file. My question is why arn't they. and how do I get the template to work and show all the files.

The deployment is done by doing a submit of the workarea and then an area diff if the staging to that last edition.

Adam Stoller

that is correct they are not listed in the task output file. My question is why arn't they. and how do I get the template to work and show all the files.

The deployment is done by doing a submit of the workarea and then an area diff if the staging to that last edition.

If you're doing an area diff - the list of files associated with the job is somewhat irrelevant, however, without seeing the actual code that generates the job XML and the PT/XSLT file that's composing the email - it is difficult to figure out what is / is not working as designed.

Also - what are you using here?

This also plays a big role in trying to figure out whether you are looking in the right place for the information.

Migrateduser

Ok sorry. I am using the solutions email and default templates.

The other difference is that I am using the command iwsubmit instead of the WorkFlow function. Does the $IWHOME/bin/iwsubmit command not load the task output file info the same as the WF submit?
Thanks

Adam Stoller

Ok sorry. I am using the solutions email and default templates.

The other difference is that I am using the command iwsubmit instead of the WorkFlow function. Does the $IWHOME/bin/iwsubmit command not load the task output file info the same as the WF submit?
Thanks

What do you mean by that last sentence?
Neither iwsubmit nor submittask load a task output file.
The submittask knows to get the list of files from the workflow.
iwsubmit needs to be provided the list of files to submit (usually in the form a temporary file of a specific format using the '-f' flag - RTFM for more details)
Neither should cause the list of files associated with the workflow to change.

Migrateduser

I am using $iwhome/bin/iwsubmit -r -w -u $workArea to submit the files. $workArea is a point to the work area that contains the files to deploy. In our case we always deploy all of the files in the work area

They do get deployed but don't show up in the task_outputxxxx.xml file. Do I need to do something else to get them in the task file so the email template will work. It turns out we can not use the submit in the worklflow because of 2 issues. 1. to submit all the files to the WF in 1 command could exhaust the cmd line limit and break. and doing them 1 at a time takes to long.

So we opted to use the command lime submit in a script. But as stated the emails don't sow the files.

thanks for the help.

Adam Stoller

I am using $iwhome/bin/iwsubmit -r -w -u $workArea to submit the files. $workArea is a point to the work area that contains the files to deploy. In our case we always deploy all of the files in the work area

They do get deployed but don't show up in the task_outputxxxx.xml file. Do I need to do something else to get them in the task file so the email template will work. It turns out we can not use the submit in the worklflow because of 2 issues. 1. to submit all the files to the WF in 1 command could exhaust the cmd line limit and break. and doing them 1 at a time takes to long.

So we opted to use the command lime submit in a script. But as stated the emails don't sow the files.

thanks for the help.

I'm not sure, but I think you have apples and oranges here.

You can disable having all files attached to the command line on external tasks via a setting in iw.cfg - though I've never heard of this being an issue with submittask

The email issue is separate - since you're using iw_solution_email.ipl - you can edit the script and enable debugging - which will make it dump the job XML output to a file in IWHOME/tmp that you can examine to see if the information is there. The information will appear, I believe, towards the top - in the "workflow" section, as opposed to within the individual task sections lower down.

If the file information isn't there - you may have to open a case with Support, though they might not take it on as it's a "custom implementation".

If the file information is there, but isn't showing up in the emails - you need to look at the PT and verify that it is intending to show that information.

Migrateduser

ok thanks the files are not listing in the debug output. If I use the iwsubmit. But If I use the submittask and $task->addFile then it shows up in the debug file and the email.

Adam Stoller

ok thanks the files are not listing in the debug output. If I use the iwsubmit. But If I use the submittask and $task->addFile then it shows up in the debug file and the email.

Okay - the fog is starting to clear here.

Does your workflow attempt to add pre-selected files to the job during instantiation?

If you add pre-selected files to the job and you don't select any files before initiating the job, the workflow engine should identify all the modified files within the workarea and attach them to the job for you - and then they should show up in the email debugging file (and subsequently the email)

If you add pre-selected files to the job and you do select some files before initiating the job, the workflow will only know about those pre-selected files and not about any other files that were submitted via iwsubmit.

If you do not add pre-selected files to the job and you don't select any files before initiating the workflow - then the workflow will not have any knowledge of the files being submitted (via iwsubmit) and thus the files will not appear in the email debug log nor in the email.

Frankly - I question the design of the workflow and its implementation - but its' yours so you can do as you see fit.

Migrateduser

Thanks that is kinda what I suspected.

The WF is as designed by Interwoven Services based on our implementation the have the workarea feed by external processes and have to "Lock" out any changes as the updates are occuring. also we have the likely hood of 2-300,000 files updates during a deployment. Any suggestions would be greatfully accepted.

Also the workarea is going to contain all the files to be delivered and maybe some that are unchanged. So for every deployment all the files in the work area are submitted to staging and then diffed to the last edition. The files are not predefined for delivery and we don'e want files that are in the work area and unchanged to be delivered. So they deployment is done with an area diff of staging to last edition.

Thanks.

Adam Stoller

Thanks that is kinda what I suspected.

The WF is as designed by Interwoven Services based on our implementation the have the workarea feed by external processes and have to "Lock" out any changes as the updates are occuring. also we have the likely hood of 2-300,000 files updates during a deployment. Any suggestions would be greatfully accepted.

Also the workarea is going to contain all the files to be delivered and maybe some that are unchanged. So for every deployment all the files in the work area are submitted to staging and then diffed to the last edition. The files are not predefined for delivery and we don'e want files that are in the work area and unchanged to be delivered. So they deployment is done with an area diff of staging to last edition.

Thanks.

I'm not sure I understand the "external processes and have to Lock out any changes as updates are occurring" part - and how that affects the choice between using a submittask or using an externaltask that runs iwsubmit - nor how that affects the identification of pre-selected files and such. There are a number of options available - the person who developed the workflow chose one. Whether it was the best choice ... I'm not sure.

However - since the thread was about trying to understand why you weren't seeing a list of files in your workflow email - I think that has already been figured out.

Now it's a question of what, if anything, you're going to do about it.

Migrateduser

My thoughts are to run a dnr in the deployment process that will grab the list of files from and create a manifest file. Then in the email process read that file and put the info into a mail message and send it.

To answer the other question we are intagrating Control Hub into an existing environment replaceing the current Content Delivery system. Then over time integrate more of the teamsite product into the enviroement. But right now CuntrolHub is going to be receiving files into the workarea and process them to the targets.