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

Access files across workareas

Shilpax

Hi,

I have different workareas under different branches -

Branch1
workarea1
templatedata
SiteContent

Branch2
workarea2
templatedata
SiteContent

Folder SiteContent has all the assets inside like pdf,css,html etc.
I need to map/browse a file from /branch1/workarea1/SiteContent/pdf into the DCR field inside branch2 - /branch2/workarea2/templatedata/category/datatype/data/DCR2.xml

in this way can we access the files from another branch into a DCR Browse field?
This is required to avoid the multiple copies which will be created if we keep all the documents in both the branches. While deployment I need to deploy this pdf along with the html file for that DCR.

At the time of deployment how can we handle this?

Please let me know if we can do this mapping and deploy the content to web server.

Find more posts tagged with

Comments

Shilpax

Got help from some of the posts on DevNet for cross branch browsing.

Now want to know how do I deploy these files from different branches in a workflow task.
Please suggest some solution.

Snap 2016-02-17 at 15.46.48.png

jagadesh

Got help from some of the posts on DevNet for cross branch browsing.

Now want to know how do I deploy these files from different branches in a workflow task.
Please suggest some solution.

Workflow is workarea based approach. The workflow wont allow to attach the different workarea files to the workflow task. you have to write some script parse the DCR/output file and append those values in file list(two different) before the deployment starts and you can achieve this.

Adam Stoller

Workflow is workarea based approach. The workflow wont allow to attach the different workarea files to the workflow task. you have to write some script parse the DCR/output file and append those values in file list(two different) before the deployment starts and you can achieve this.

Or add a process to the browse-functionality that copies the selected file(s) from branch1/workarea1 to branch2/workarea2, so that the files will be there when the workflow runs and all the files can be deployed together in a logical manner.