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

staging area

khyati

When I upload files from workarea, it goes to staging area.
Is this staging area , a part of content store ?
I can select files from workarea and push them to the production and I can submit files to production from staging area as well. If workarea does not contain real files but pointers to the files (as mentioned in manual). How can these files be put in the workflow, without real copies of files being there ?
Same thing applies to Staging.

Pls explain.

Find more posts tagged with

Comments

Jcse

Is this staging area , a part of content store ?

No,Staging Area is not a part of content store.Staging Area is the area where documents on the branch are integrated, conflicts are identified there and different versions of the same file can be merged, rather than overwritten(as per the manual),whereas content store is the physical area where actually contents are stored.

I can select files from workarea and push them to the production and I can submit files to production from staging area as well. If workarea does not contain real files but pointers to the files (as mentioned in manual). How can these files be put in the workflow, without real copies of files being there ?

its very correct that workarea does not contain real files but pointers to the files,whenever you submit a file it goes to STAGING ,then when you publish file a new edition is created for that file and finally the real file was then updated by that new edition ,then a workflow picked up that file further.
So,in this way it works.

i am not sure for this,its just my understanding.

Adam Stoller

The staging area is a read-only view of the latest version of each file within the branch in the content store.
Files are submitted from the workarea to staging and thus to the content store.

The files in the workarea are virtual copies IFF they represent the same version of the file that exist in the TeamSite Staging area or an edition. As soon as the file in the workarea is modified - it becomes a physical copy. When the modified file gets submitted, it becomes a virtual copy again.

khyati

[quote] Files are submitted from the workarea to staging and thus to the content store[/qoute]

So you mean, when a file is submitted from workarea, it goes to content store and STAGING is readonlyview of the content store. That means, STAGING does not contain any physical copies of files, but just drivers to see latest version in content store.
So workflow picks up files from content store, right ? If so, then always there is a physical copy of a file available for workflow. When I select a file from workarea and put it in the workflow, I get an error "file is not available in STAGING." How can that be ? In content store , copy of file is always available. So if latest version of file is not uploaded, still previous version is available.

If above understanding is not correct, then if file is submitted to STAGING and its not content store, then how is a file submitted to content store ? Does a physical copy of a file stay in STAGING ?
From where does workflow pick up the physical copy of a file to send it to production ?

Can workflow pick up files from workarea ?

thanks

Migrateduser

Yes, workflows can pick up files from the workarea. The workarea/staging is just a virtual representation of the files. The actual files are stored in the iw-store. It is there so that you can see the file system similar to the ones on unix or windows.

Amit_LnT

Khyati,
Do not get confused by the different areas given for the contents in TS.
Those are given for different purposes.
The content store is one where all your contents, versions and editions are kept.
As mentioned above, workarea and staging are pointers to the files.
And a workarea will allow you to create/modify/delete the files, whereas staging area is used as the merging/integration point for the branch contents.

File will only be available to the STAGING area, when you submit the file from workarea.

I am not sure,how you are referring the files from staging area in to the workflow for deployment.
But, Workflow can definitely take file from workarea. We used it in all workflows. We have put code in the WFT file to explicitly insert selected files in the workflow from workarea.