Seems the role-based profiles are a good way toward what I need, but I see a useability problem: Rules change. When there are policy changes for some organizational role, these could affect what can and what must appear on the desktop for those members, but in the current "generate at create" model, the only way to propagate those changes to all current members in the affected role is to delete the members and re-create the accounts, and this would lose any of the member customizations.
Here's my proposed work-around, and please tell me if there is an easier way ;) ... if the links are resolved at login time, then role-merge templates should only include link references to other psml files where the actual portlets for that role are set out. I haven't tried it yet, but I'm expecting that this will work, only this may mean that the members themselves will be unable to customize any of the role-based portlet configurations (or will they be allowed to make changes global across all members?) That's a bit of a pain, but if its the only way to let them keep personal configurations across role psml updates, then we'll have to live with it. Is there a better way? -- Gary Lawrence Murphy - [EMAIL PROTECTED] - TeleDynamics Communications - blog: http://www.teledyn.com/mt/ - biz: http://teledyn.com/ - "Computers are useless. They can only give you answers." (Picasso) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
