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

Keeping a clean workarea

System

I have two workareas in a branch and w1 (workarea 1) contains file A and w2 contains file B and both files have been submitted. If I do a get latest in w1 and get file B and later decide that I don't want to see file B in workarea 1 is there a way to remove file B from my workarea 1? I know you can delete it but then it appears with a delete icon and could potentially be submitted.

Find more posts tagged with

Comments

reddyl

I have two workareas in a branch and w1 (workarea 1) contains file A and w2 contains file B and both files have been submitted. If I do a get latest in w1 and get file B and later decide that I don't want to see file B in workarea 1 is there a way to remove file B from my workarea 1? I know you can delete it but then it appears with a delete icon and could potentially be submitted.

Why not change the permission on file B in workarea 1 so that it does not show that file from the UI.

Migrateduser

I think you're talking about doing it in the filesystem. I just tried that and it's not possible since Teamsite_Web_Preview is the group that needs to be removed, but removing it is not allowed. When I try to remove the permissions for this group from that file it just puts it back. Part of the workings of Teamsite.

Adam Stoller

I have two workareas in a branch and w1 (workarea 1) contains file A and w2 contains file B and both files have been submitted. If I do a get latest in w1 and get file B and later decide that I don't want to see file B in workarea 1 is there a way to remove file B from my workarea 1? I know you can delete it but then it appears with a delete icon and could potentially be submitted.

This question seems to come up from time to time and is usually a symptom of lack-of-training / lack of understanding the basic, underlying concepts of TeamSite.

A workarea is a virtual view of the contents of a branch. You cannot have multiple [active] workareas having *different* virtual views of the same branch other than with respect to files currently undergoing modification in one workarea or another (or the complete lack of Get Latest) - period.

Branches and workareas can be hidden from users based on file system access lists and iw.cfg entries.

Folders and files can only be protected from access based on file system access lists - they cannot be hidden (a folder that is protected may not let a user to navigate within to see the contents - so in that respect the contents of the folder is hidden, but the folder itself is not)

Migrateduser

symptom of lack-of-training / lack of understanding the basic, underlying concepts of TeamSite

Uhmmmm, I understand, how it works. I was just hoping for a way to use Teamsite differently. Bend the rules, if you will.

Adam Stoller

Uhmmmm, I understand, how it works. I was just hoping for a way to use Teamsite differently. Bend the rules, if you will.

You can certainly try "bending the rules" - but chances are it will cause you problems somewhere down the line and it's basically unsupported - so any time you have a question or issue with the system you'll have to go through an extremely lenghty description of what you did / why you did it before you can really get to the actual issue you want to discuss.

IMO - you either use the tool in the way it was intended, work with the vendor to change it to work the way you want, or find a different tool.

Migrateduser

If we didn't bend the rules and ran it out of box, then why would we need consultants?

C'mon, let's start a flame war!!!!

Adam Stoller

If we didn't bend the rules and ran it out of box, then why would we need consultants?

C'mon, let's start a flame war!!!!

I'm not looking to start a flame war.

There's a difference between customization and misuse of a tool.

You're trying to use TeamSite as if it were ClearCase in which one can define custom views for a "workarea" by specifying layered configuration filters to determine which files show up in which view - when that's not the underlying model, and therefore is basically a misuse, of TeamSite.

deepakb

I completely agree with you...

Consultants are there to provide to solutions using API, Configurations using the underlying model of TeamSite. Not to provide solution by hacking the Product code (Bending rules) this will eventually cause problem in the scalability, maintainability in the long run.

Deepak