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

Moving Files

rsearle

Peridically, I have users who want to move files from one branch to another. What's the best way of doing this? Is there are pre-built workflow for this?

Find more posts tagged with

Comments

nipper

The short answer is no, there is not a WF to do this.

The long answer is why ? This is not very common, though it does happen and is seldom a recurring task.

The reason I bring this up, is that many times people copy files, move them around because of a limitation of the tool they use, not because it is the proper business strategy.

So, you need to really consider what theya re trying to do and see what the best way to do this in TeamSite is. Is it branching & proxy settings ? Is it archival ? Is it that users are a pain in the **** ? Inquiring minds want to know.

Get a little more info before you start coding.

#SOAPBOX_OFF

Andy

MattP

Aside from the soap_box questions....

You can select *a* file and use File->copy to area to move it to another area.

Matt

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

mogoo

I don't know all of rsearle's needs, but we also have the need for branch copying, and in answer to your soapboxing, here's a couple reasons WE need a copy-to-another-branch workflow...

1. Certain things cannot be reliably viewed/tested in the teamsite environment. Things like some cgi scripts, DHTML, embedded flash, frames.
2. Things are best deployed to a "real" server to QA in different platforms, different browsers.
3. Outside approvers need to review the work, but on a password protected production server. Yes, this review could be done on teamsite, but then the Smart Context Edit toolbar appears on the pages. True, it could be removed on a workarea basis, but the developers that use those workareas want it there. It is unprofessional to send high-level reviewers a page with a teamsite bar across it.

...in order to accomplish these goals, we need to deploy some review files out to a server without submitting them to staging of our main branch, which would set them on the path to going live. Bad business practice or not, nipper, these are our needs. If you can come up with any other alternative than copying to a different branch, I'd love to hear it.

There, that's my soapboxing Smiley Wink

...

As for rsearle, Matt was right... File-->Copy to Area will allow you to copy to another branch. There are no OOTB workflows that accomplish this. Our idea was to have either a custom menu item or a submit workflow that would kick this process off. I'm *guessing* iwupdate is the CLT that needs to be referenced in the workflow, but I'm not sure, haven't played around with it yet. Good luck!

maureen

nipper

I never meant to imply that you should not move files. There are valid reasons to do so. However I have also seen people, who do not understand how TeamSite usually works, implement some really screwy policies when there is basic functionality to solve the original problem.

In my current implementation, a lot of people were clamoring for the ability to copy lots of files. Instead, we used subbranches and proxy settings, allowing them to do multiple languages, which was their business concern and fit much better to a normal TeamSite implementation.

Andy

mogoo

Good points, nipper. I agree, you need to make sure you "know the teamsite beast" first, before you make decisions on how to set up your processes... unless you want to spend a LOT of time reorganizing.
maureen