Hello Listers,
ARS 7.1 patch 4
MS SQL 2005
MS 2003 Enterprise SP2
I am trying to nail down a method to using functional groupings for
users.
We have 4 functional groups for an application.
CustService (CS), Tech, Logistics(Log) and Maintainer
The first three deal with handling customer requests.
CS and Log can create and change Customer Requests.
Techs cannot create but can change requests.
Maintainers can create and change requests. They must also maintain data
driven menus via workflow.
CS Tech Log Maintainer
-----------------------------------------
Create X X X
Change X X X X
Maintain X
I was going to make 4 entries in the Group form but the Maintainers need
to move users in and out of the four functional groups. I can't give the
Maintainers access to the Group and User form because the ARServer has
multiple tenants using other applications. I would not be able to
restrict them to this application's users because as new people are
added we do not know if they will eventually work this application. Plus
if the Maintainer removes someone from all of the groups they would not
be able to get them back if we setup row-level access restrictions.
I thought a data driven form could be used as a pseudo-group form to
control who can create, change or maintain the primary form's data and
menus.
I'm just having a hard time getting my mind wrapped around structure of
this idea.
I need a table to track what I tried to display above. The "Permissions"
form would be extensible if they added a new functional group.
Then I think I would need to use a join to the People_Info form so I
could flag a global field on the Request form to restrict the current
$USER$ to their functional group permissions. Set flag = CS and the
workflow would prevent them from seeing the Menu Maintenance button, or
Flag = Tech and they get warned when they open the form in "New" mode.
Of course that means I have to hard code information into the Workflow
to make the proper restrictions/allowances.
Does this sound like the right course of action?
Thanks for being a sounding board.
---
John J. Reiser
Senior Software Development Analyst
Remedy Administrator/Developer
Lockheed Martin - MS2
The star that burns twice as bright burns half as long.
Pay close attention and be illuminated by its brilliance. - paraphrased
by me
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
