I think it would be better to abstract the role into a group, so that the work-effort could be published to a group. The group will have roles and the roles will have persons. When a workeffort has been started it will not be visible to others.
This means that the group will have a responsibility to have the work done, and the group manager can manage the work. Then the group could have a calendar, with skill and other functionality defined in party. How about Timesheet-management (those persons that forgot to fill it in, and those that has filled in too many hours by mistake, or has used wrong workeffort in the timesheet)? I have not seen this functionality in OFBiz, but this will be added by the work you are doing? Torstein -----Opprinnelig melding----- Fra: Adrian Crum [mailto:[email protected]] Sendt: 24. juni 2009 19:29 Til: [email protected] Emne: Re: Discussion: iCalendar Integration The improved iCalendar integration has been committed, and there is a Wiki page: http://docs.ofbiz.org/x/piE. I still haven't resolved the party assignment role issue, but it will be an easy change to make once a decision is made. -Adrian Adrian Crum wrote: > I'm almost ready to commit the work I have been doing on the iCalendar > integration. Before I do, I would like some feedback on a particular > function. > > Background: One work effort serves as an iCalendar "publish point" - > it's not a work effort that anyone interacts with, it just contains > settings that tell the iCalendar servlet what to do. In the current > implementation, all public work efforts of all parties assigned to the > publish point will be included in the calendar. The party's assignment > role is ignored. The publish point's scope (public, confidential, > private) is ignored. These are things I would like to change. > > In the new implementation, if the publish point work effort has a public > scope, then anyone can view work efforts that are related to it. If the > scope isn't public, then access to the related work efforts is > restricted to only the parties who are assigned to the publish point. > Oops, now I have a conflict with the previous implementation - where a > party assignment meant to include that party's public work efforts in > the calendar. > > Here's where I need the feedback. I need to use the publish point work > effort to party assignment ROLE to control what the servlet does. A > party related to the publish point in role "A" is a party whose public > work efforts are included in the calendar. A party assigned to the > publish point in role "B" is a party whose access to the calendar is > controlled by the publish point. > > Looking at the current calendar roles, we have Attendee, Delegate, Host, > Organizer, and Owner. The Delegate role might be appropriate for the > party in role "B". I don't know what to do about the party in role "A" - > should I create a new role? Something like "Calendar Participant" or > "Calendar Member"? > > Any feedback would be appreciated! > > -Adrian >
