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

Changing sharing option for Workarea

asalim

Hello,

I created a workarea with the option sharing=private. Is it possible to change the sharing option to sharing=group after that workarea is created?

Thanks,
Alexander

Find more posts tagged with

Comments

kajjubee

You can click on properties against the workarea and change it.

K

asalim

You can click on properties against the workarea and change it.
K

That would be to easy (-: If I click on properties for that workarea I want to change, I got only the information that the sharing option is set to "private", but this option is not editable.

Alexander

ISCBorisB

That would be to easy (-: If I click on properties for that workarea I want to change, I got only the information that the sharing option is set to "private", but this option is not editable.

Alexander

Workareas are(should be?) disposable commodities. Submit, delete, re-create with the desired properties,
get latest. What's the big deal?

asalim

Hello,
I want to change the sharing option of an existing workarea, which sharing option was set to "private", to "group". Instead of copying the complete content to a different workarea, I thought of changing the Workarea by clicking on the "Properties" button.
After clicking on "Properties" for a selected workarea, I got an overview of the workarea settings (name, location, sharing, group, ...). Now I want to change the sharing option to "group", but that field in the overview is not editable, so I cannot change its settings on this way.

Alexander

ISCBorisB

1. Submit your Workarea assets to STAGING.
2. Delete Workarea.
3. Create Workarea with the same name and a sharing Property that you want.
4. Get in it and Execute "Get Latest" - that'll take all from STAGING.

There are other scenarios like publishing an Edition and use it as WA "Base Edition" upon WA (re)creation, etc...
The method suggested above is IMO the simplest. I do not beleive you have too many other options in 6.5

asalim

Thanks a lot,
Alexander

simple cube.rptdesign

kajjubee

Sorry, I was speaking from a TS 6.7.x perspective. What Boris said should work if you can submit all your content to STAGING which may not be desirable if you have multiple workareas and your changes cannot be propogated to other workareas.

I would :
-Create a new workarea with the desired group sharing
-Do a "copy to area" to the new workarea from your original workarea
-Delete the original workarea.
-Rename the new workarea to the original workarea name.

Cheers,
K

ISCBorisB

Sorry, I was speaking from a TS 6.7.x perspective. What Boris said should work if you can submit all your content to STAGING which may not be desirable if you have multiple workareas and your changes cannot be propogated to other workareas

*if you have multiple workareas and your changes cannot be propogated to other workareas* you should execute your TS Architect before the next dawn

kajjubee

Why, Because of the multiple workareas?

Thanks,

nipper

Why, Because of the multiple workareas?

Thanks,

He meant that is if some idiot set up TS where changes in 1 workarea are never to be pushed to another workarea on the same branch, the architect should be fired/shot/etc. I have seen this set up before and invariably every time has created huge problems.

kajjubee

I never said "never" Smiley Happy

The scenario I was referring to was if there are multiple workareas and if there are certain changes in one workarea that cannot go to staging/production yet. Makes sense?

ISCBorisB

Why, Because of the multiple workareas?

Thanks,

No. In many design cases multiple Workareas provide reliable parallel Development mechanism.

In IWOV TS Architecture WAs are virtual Views of the single STAGING with (possibly) some Files
modified. Same Branch WAs with unique non-private components are not supported. I saw such
designs time and again though, they are disasters just waiting to happen

ChangeSeriesVisibilityOnReloadFromForm.rptdesign