All,
I'm currently working with the new ITSM Data Management suite
and have run into a conceptual issue that I thought I saw discussed on here
before but I can't seem to find the right search terms to unearth it.
The former data load process, the foundation data load, had two
spreadsheets that specified application permissions (i.e. Incident User,
Asset viewer, etc..) and support group memberships for specific users. The
new data management suite goes a different route and uses templates instead.
Thus, a given set of application permissions and group memberships are
attached to a template and that template is used to create a user.
This is all well and good when you have a "simple" environment
in which, for example, there are a limited number of application permission
combinations (i.e. everyone is going to get one of three "sets" of
permissions) and everyone belongs to a limited number of support groups.
But what if an environment is more complicated? What if, for
example, there are about 75 support users. Of these 75, about 50 could be
classified into two application permissions groups (either IM Floating or
IM/PM/CM Fixed) but the rest are all unique combinations of permissions. To
make it more complex, each user belongs to one or more groups and there are
many possible combinations.
Unless I am completely misunderstanding how this is designed
this would necessitate the creation of a separate template for each
application permission/support group combination and then a template would
have to be used to create the user with that combination.
Other than creating a few generic templates and doing the rest
by hand, assuming the above is correct, is there a more efficient manner in
which to import this information?
Thanks!
--- J.T. Shyman
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"