What make Worksets better?

[Former Member]

Hi,

i'am student, i work at the moment and i have the job to find out how worksets work.

My question is, what make worksets on the server? How merge they the page?

Why are Worksets better then when you give the user direct the role?

For example:

Now we have

User => the User have Roles => in the role are Pages => in the Page are iViews

with Worksets

User => Worksets => in the Worksetes are Page Role and iView

What make the Workset version better/faster?

Thanks for your answers

Cheers

Simon

[Former Member]

Hi Simon,

Portal follows hierarchy as :

Users are assigned Roles,

Roles contians Worksets,

Worksets contains Pages,

Pages contains iViews.

where cardinality can be LHS to RHS as 1..*

One user can have many roles, one role can have many worksets etc.

This a deep nesting structure, which helps in better security, better navigation, better organization of content (you can put different worksets in one role etc).

Once you created a structure (everything under a role). Then you can assign that role to N number of users..that's reusability...

Overall it looks pretty organized when you follow such structure, so it is a nice practice to adapt it.

Hope you get now more better understanding....

Regards,

Yogesh...

[Former Member]

Hi,

thank you for your answer, i hope my problem is now solved.

I will give you response when i need more information.

Cheers

Simon

[Former Member]

Hi,

i know about that file but thats just for what worksets are.

And that don't answer my questions.

I need the system behind the worksets and give us worksets a better performance

But thank you

Cheers Simon

Edited by: Simon Gasser on Jul 15, 2008 1:29 PM

Edited by: Simon Gasser on Jul 15, 2008 2:34 PM

[benjamin_houttuin]

Simon,

It is not possible to assign a workset directly to a user but it always have to be via a role.

Anyway I will try to answer your question therefore I split them in 2:

Q1. "What is the 'system' behind worksets?"

A1. The main Pro of a workset is the possibility to reuse it. When content is created in modular worksets then reusability is high and maintenance effort is low. For example within a portal initiative there is a workset called "Management Reports" this workset is assigned to 5 roles. When you want to add a new reporting iView/Page then you only have to do it once in the workset. When the worksets where assigned as delta links to the roles then the 5 roles automatically get the new content.

If you didn't implement it with a workset but by adding content directly then you had to do it 5 times.

Q2. "does it give better performance"

A2. deep nested hierarchies with allot of delta link need allot of DB queries... therefore flat navigation structures tend to be faster.

BUT.... in my oppinion when setting up a hierarchy/navigation structure you should first focus on usability, possibility of reuse, maintenance before you give in to performance. Why? Performance can be taken care of by caching or by better hardware... hardware now a days is cheaper then maintenance cost on software by consultants.

Cheers,

Benjamin Houttuin

[srinivas_sistu]

Hi,

Have a look at this....

http://help.sap.com/saphelp_nw04s/helpdata/en/4f/bceaffeb8c114ebef8255b63079c7c/frameset.htm

Regards,

Srinivas.