Project Entry or General Entry - limit Entry based on associated

Yahoo Archive
1
Do you really fear project managers would acidently (or intentially?!?!) mess up each others' work?

This seems to me to be computerization of what is really a management/trust (people) issue.

Why not just add critical fields in project management to be change logged and then have your managers act like managers (since you will then have an audit trail if any finger pointing occurs)?

Rob




________________________________
From: brychanwilliams <brychanwilliams@...>
To: vantage@yahoogroups.com
Sent: Thursday, May 21, 2009 8:24:58 AM
Subject: [Vantage] Project Entry or General Entry - limit Entry based on associated Person





Hi,

At the moment we use the project module but this scenario could be applied elsewhere.

Each project has a project manager associated to it(via the person table). There is a project administrator who setups the projects and all the related data such as orders etc.

The requirement is that project managers can only update project tasks on their own projects. At quite a high level my thinking was as follows;

1) Create a seperate menu for project entry for project managers.
2) Attach a seperate customisation.
3) When they enter the projectid(get by id), the customisation matches person against user id against the project manager.
4) Initially make all objects read only plus any processes.
5) If the user is the project manager then it makes the tasks related objects as not read only .

Does this make sense ???

Would anybody else be willing to share any experiences or suggestions on this?

Thanks in advance







[Non-text portions of this message have been removed]
2
Hi,

At the moment we use the project module but this scenario could be applied elsewhere.

Each project has a project manager associated to it(via the person table). There is a project administrator who setups the projects and all the related data such as orders etc.

The requirement is that project managers can only update project tasks on their own projects. At quite a high level my thinking was as follows;

1) Create a seperate menu for project entry for project managers.
2) Attach a seperate customisation.
3) When they enter the projectid(get by id), the customisation matches person against user id against the project manager.
4) Initially make all objects read only plus any processes.
5) If the user is the project manager then it makes the tasks related objects as not read only .

Does this make sense ???

Would anybody else be willing to share any experiences or suggestions on this?

Thanks in advance