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

Get Latest functionality

brocktune

Sorry if this is basic, but I'm trying to get a thorough understanding of how the IW architecture is setup.

When a workarea is submitted it goes into STAGING. If you then do a get latest on another workarea, selecting update and override manually, everything from STAGING will be moved to the workarea? If this is the case, you'll end up with files from other workareas that you might not necessarily want.

My question is, how can you put controls on users selecting get latest and just how does the get latest should work?

Again, I apologize for the basic question. I'm just trying to get everything figured out.

Find more posts tagged with

Comments

nipper

Yes you are mostly correct on how GL works.

Yes you do understand the problems, esp as we get more non techical users.

A couple of points. TS tries very hard to prevent you from causing conflicts (big warning if I edit an old
version of the file, are you really sure you want to do this type questions, etc). TS tries to prevent you
from overwriting a file you have modified (but it is allowed since it is a good way to get rid of unwanted edits).

Get Latest is also specific to your location and can be restricted if you select a file.

Finally, write workflows with the update task. Makes WF more complex, but will prevent a number of issues.
If I change foo & push it to WF, update can push it to one or all WAs on the system.

HTH

Andy

Adam Stoller

One point Nipper didn't fully address:

If this is the case, you'll end up with files from other workareas that you might not necessarily want.In general, any file that is submitted to staging should be able to exist in all workareas on that branch. Do NOT try to make your workareas look different for different users - that's the road paved with good intentions that leads to ****.
An exception to this rule is for transient workareas that are created for a specific purpose (like pulling in the versions of files referenced by a previous edition in order to do a bug fix without also pulling in newer changes).

A workarea is intended as a virtual view of the branch - unlike many other version management systems - any file in your workarea that is the same as the file in staging is a *virtual* file (not a copy - no additional disk space is utilized) any files that you have modified in your workarea are not accessible by other workareas unless someone in the other workarea has specifically copied your file into their workarea - or until your file is submitted to staging and they perform a Get Latest.

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

brocktune

Thanks for the reply.

I'm still having some trouble understanding how this works, exactly. If you want to split a website up by business units. How do you keep them seperate. Say you don't want the content from the toys dept. Workarea being displayed in the weapons dept. Workarea. So it looks like this:

someCompany (Branch)

---Toys (Workarea)

------ promotions (folder)

---Weapons (Workarea)

------nuclear (folder)

Now, after submitting everything to Staging, if you do a get latest on the Weapons Workarea you'll see promotions in there.

---Weapons (Workarea)

------nuclear (folder)
------promotions (folder)

Is that how you're saying it's going to work? Why would you want the promotions folder to appear in a Workarea that's totally unrelated to that content?

Thanks for your help on this. I'm just confused on how everything should be setup.

nipper

Yes you are confused

Use branches in that example

Weapons & Toys are the higher branches (under company)

Weapons/Nuclur (in honor of Pres. Bush

) Toys/promotions are subbranches.

Workareas for users or small groups.

I certainly hope you have a consultant in to help design this. You can really shoot yourself in the foot
(and higher) by trying to hide things in different workareas.

I did not read into the post your original intent, as fish did. Good thing he did.

Andy

Migrateduser

You are on the right track. The answer is that you want to put things in different branches. Where this begins to get complicated is that many times, the stuff in your child branches will need to be able to reference stuff (forms, images, css, whatever) in other branches. That's where you have to begin making use of proxy remapping. In the example you gave, what you would want would be something like this:


someCompany (Branch)
|
---Toys (Subbranch)
|
------ workarea1
------ workarea2
--------- promotions (folder)
|
---Weapons (Subbranch)
------workarea1
---------nuclear (folder)

nipper

My answer is different from Rob's in that I used branches for Promotions, assuming that
you have other sections under Toys that you want to keep seperate. May not be an issue
then use directories.

HTH

Andy

brocktune

NIpper,

There are consultants taking care of the implementation. I'm just trying to get up to speed on everything.