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 subfolders

prof_brazen_guff

TeamSite 6.5.0 SP 2

Submitting a top-level folder doesn't automatically submit subfolders. Has anyone else experienced this? Is it addressed in a newer version of TS as we're planning to upgrade in the new year.

Find more posts tagged with

Comments

nipper

How are you submitting ? If you submit via commandline it should. However if you are submitting via GUI, the it is up to the workflow.

Also, are these directories empty (new dirs) or do they have content ? New dirs do not typically get acted upon until they contain new data.

prof_brazen_guff

How are you submitting ? If you submit via commandline it should. However if you are submitting via GUI, the it is up to the workflow.

Also, are these directories empty (new dirs) or do they have content ? New dirs do not typically get acted upon until they contain new data.

We are submitting via the GUI, so I'll have a look at the workflow to see if it isn't working as it should - the folders which aren't submitting all contain data.

Thanks for the response

Adam Stoller

We are submitting via the GUI, so I'll have a look at the workflow to see if it isn't working as it should - the folders which aren't submitting all contain data.

Thanks for the response

Is this a custom workflow or an OOTB submit workflow?
If custom - are you sure your workflow attaches pre-selected files?

nipper

Is this a custom workflow or an OOTB submit workflow?
If custom - are you sure your workflow attaches pre-selected files?

This is most likely the issue. I almost never submit dirs, rather, I do a view modified from the point I want to submit and then select the files.

That being said, changing the WFT to, for each dir selected, attach all modified files underneath that directory is not difficult.

prof_brazen_guff

Thanks for the responses - I'm still finding my way around this system, but looks like I need to look at our wft and see what's happening there. It was implemented by an IW consultant, so I just assumed it was OOTB ...

Adam Stoller

Thanks for the responses - I'm still finding my way around this system, but looks like I need to look at our wft and see what's happening there. It was implemented by an IW consultant, so I just assumed it was OOTB ...

implemented by a consultant does not mean OOTB - as many consultants implement custom workflows.

Migrateduser

This is most likely the issue. I almost never submit dirs, rather, I do a view modified from the point I want to submit and then select the files.

I concur with Andy about the best way to go about this. In fact, when coding custom workflows, I generally disallow submissions of directories by anyone other than an administrator or master, because it's impossible to predict what the end user's expectation of the behaviour is going to be. If you don't disallow it, I would recommend adding some text to the pre_tagtable_html to tell the user exactly what to expect if they attach a directory.

Adam Stoller

I concur with Andy about the best way to go about this. In fact, when coding custom workflows, I generally disallow submissions of directories by anyone other than an administrator or master, because it's impossible to predict what the end user's expectation of the behaviour is going to be. If you don't disallow it, I would recommend adding some text to the pre_tagtable_html to tell the user exactly what to expect if they attach a directory.

In WFT code (not sure how to do this in WFM - haven't tried yet) - I parse the preselected file list and if any of the entries are directories I replace it with the file contents of that directory (recursively) - assuming your submit workflow has a comment prompt for each file attached to the workflow - when they see the instantiation screen they'll know what files are going to be submitted ....

Migrateduser

I've (so far) never had a case where the client wanted to keep the behaviour of the default submit workflow of having individual file comment textboxes. They usually want to strip the instantiation page down as far as possible. I do typically add a list of attached files to the workflow just so they know what they are doing, especially in cases where any files other than what they explicitly selected are being added to the list (e.g. DCRs or multiple different output renderings of the same content).

Adam Stoller

I've (so far) never had a case where the client wanted to keep the behaviour of the default submit workflow of having individual file comment textboxes. They usually want to strip the instantiation page down as far as possible. I do typically add a list of attached files to the workflow just so they know what they are doing, especially in cases where any files other than what they explicitly selected are being added to the list (e.g. DCRs or multiple different output renderings of the same content).

Either way - either separate comment boxes for each file, or just a list of all files - you can do that programmatically within the WFT so it shows up on the instantiation form and give the user the chance to abort before instantiating the job if - if the file list doesn't look right.