Good morning,
I am trying to analyse how a previous A.I. install developer managed to make conditional folder security. There is nothing obvious in the folder properties or organization controls. There are two Custom Actions that appear to just check if the folder already exists or not, CheckforScreens and CheckforScreensdeferred. These have appropriate sections in an external visual basic script file. I'll attach these but i'm not sure what part if any in deciding whether folder permissoins for a user are set.
So the crux of the matter:
1. During installation, the install user chooses frontend or backend install.
2. Both of these on a later dialogue accept/take USER_NAME and DOMAIN_NAME variables which populate the folder Permissoins (Edit Folder)
3. If the frontend is chosen then the folder permissions 'are not' set for the variables in 2.
4. If the backend is chosen then the folder permissoins 'are' set for the variables in 2.
Can't find any conditional logic to support 1 through 4.
Thanks for any insight.