Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
13 replies
Subscribers
9 subscribers
Views
7291 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Deployment of first solution on-premise
sudhak
over 8 years ago
Hello,
Could someone throw some light on best practices for deployment of a first solution on an on-premise installation? I saw the link on Application Deployment Guidelines here:
ppdtpoc.appiancloud.com/.../Application_Deployment_Guidelines.html
but these are only for 16.1 or are applicable for all versions? We run 7.9 on-premise.
Thanks,
Sudha
OriginalPostID-232684
Discussion posts and replies are publicly visible
Parents
0
sikhivahans
over 8 years ago
@sudhak Absolutely there isn't a need to worry about dynamic groups. Just make sure that dynamic groups aren't included in the Export. These dynamic groups should be associated with the environment in which they are created and they should stay in the same environment for a lifetime or handled in the same environment for deletion/modification purposes as long as they are meant for handling environment specific objects such as process instances. Also, make sure that you are not carrying any development activities where the dynamically created groups aren't directly referred by any objects that you export across the environment. For instance, a dynamcially created group can be used in the security of process instance, or a record which queries the dynamically created group by checking the group id in database or a PV in a process but it shouldn't be directly referred in the security of the Process Model\\Record Type etc.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sikhivahans
over 8 years ago
@sudhak Absolutely there isn't a need to worry about dynamic groups. Just make sure that dynamic groups aren't included in the Export. These dynamic groups should be associated with the environment in which they are created and they should stay in the same environment for a lifetime or handled in the same environment for deletion/modification purposes as long as they are meant for handling environment specific objects such as process instances. Also, make sure that you are not carrying any development activities where the dynamically created groups aren't directly referred by any objects that you export across the environment. For instance, a dynamcially created group can be used in the security of process instance, or a record which queries the dynamically created group by checking the group id in database or a PV in a process but it shouldn't be directly referred in the security of the Process Model\\Record Type etc.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data