LJ, David: Thank you for you responses. Two more questions. So if I have
a field in one of the forms in appA with permissions for a group called
groupA. I export this application to another server.
1. What happens if the destination server doesnot have this group called
groupA? Does remedy automatically give access to groups which are
defined in the role at the destination server?
2. Role definition only provides ability to provide access to one group
for each state of the application. What if I want to give one group
just "View and "Change" to another group?
Thank you.
Ravi
LJ Longwing wrote:
Nope...that's why I specified that role ID's are specific to their
application...so role id -1234 in AppA does not conflict with role id -1234
in AppB...in fact I have a number of apps on my servers that have the same
role id because I map them to the same group...
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Ravi
Sent: Monday, June 02, 2008 2:54 PM
To: [email protected]
Subject: Re: Use of "Roles" in Deployable Application
LJ, David: thanks for your response. What if the role already exists in the
destination server? Wouldn't I run into the same issue.
For example:
Source Server has a deployable application (appA) and a role (roleA).
Let'z say this roleA has a group called Testers. I export this application.
Destination server already has a different application (appB) and a role
(roleA). If I import the application here, wouldn't that mess up appB?
TIA
Ravi
LJ Longwing wrote:
Additionally, Role ID's are specific to the application...which means
that a deployable application can be dropped onto a new server, and
have the roles mapped to existing groups on the new server without
breaking anything. If it's a local application then the permissions
are tied to a group id...if the group id that the application uses is
already in use on the destination server...you are screwed...I believe
that this architecture was setup so that Company A could sell an
application to Company B without regard for if the group ID's the
application was built on are already in use on the destination server
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Ravi
Sent: Monday, June 02, 2008 11:34 AM
To: [email protected]
Subject: Use of "Roles" in Deployable Application
Hi: I am trying to build a deployable application for the first time
so I can migrate the application between test, development and
production remedy servers. I read through the docs couple of times and
still can't seem to understand the usage of roles. I know users are
part of one or more group(s). A role can have one group when in Test
and another group when in Production. Is that all: All roles does is
provide access to the application to different set of users based on the
deployable application state?
So do the groups and roles have to exist on the destination arserver
before exporting an imported application from my test server to the
development arserver?
Also looks like the advantage of using deployable application instead
of local application is that it can be licensesed and tracked. Is that
the only reason why someone would use deployable?
TIA
Ravi
______________________________________________________________________
______
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
