There is some confusion on how you run or "convert" a V7 application to a V8 application and run on a V8 server that has the Security Framework turned on. Here are some notes on the subject based on my testing. Everything below would be done with the application open in version V8:
1) As recent as release 3081, Grids have what I believe to be a bug - the Security Model defaults to Group Based, even if you had applied Levels to your V7 application. Presently, for any Grid where you used Levels, you need to open the Grid, go to Properties and toggle the Security Model from Group Based to Levels. All of your original Levels will immediately be corrected back to their original values.
If you don't do this, the Level settings on your Grid will not apply at all (i.e.: no security) and there won't be any error message to tell you they failed.
You have to make this fix even if you have Security Framework turned OFF at the server.
2) This above issue does not appear on Navigation Components. If you set any Levels on a Nav Component, they are properly reflected when you open or just publish them in V8.
Dialogs are not affected because they did not have any security settings in v7.
3) Even if you leave the settings under Web Security > Web Security Settings turned OFF, you can still run that application on a V8 server that has the Security Framework turned ON. You just have to create placeholder security files using the undocumented function a5ws_createsecurityfiles(c full path to project files). If later you do toggle the security features on, whatever security settings you define overwrite the placeholder files.
The reverse is not true, a5ws_createsecurityfiles() will NOT overwrite existing security files. This is a good thing.
4) You do have to open your V7 app in V8 and republish all files from V8 to the V8 server. There probably are other reasons, but I do know the way components are represented in the A5W pages has changed.
5) Final note, I don't really know how this would work in practicality, but you can toggle the Security Model to Group Security for one Grid and Level Security for another Grid. Same story for Nav Components. Dialogs only allow Group Security.
1) As recent as release 3081, Grids have what I believe to be a bug - the Security Model defaults to Group Based, even if you had applied Levels to your V7 application. Presently, for any Grid where you used Levels, you need to open the Grid, go to Properties and toggle the Security Model from Group Based to Levels. All of your original Levels will immediately be corrected back to their original values.
If you don't do this, the Level settings on your Grid will not apply at all (i.e.: no security) and there won't be any error message to tell you they failed.
You have to make this fix even if you have Security Framework turned OFF at the server.
2) This above issue does not appear on Navigation Components. If you set any Levels on a Nav Component, they are properly reflected when you open or just publish them in V8.
Dialogs are not affected because they did not have any security settings in v7.
3) Even if you leave the settings under Web Security > Web Security Settings turned OFF, you can still run that application on a V8 server that has the Security Framework turned ON. You just have to create placeholder security files using the undocumented function a5ws_createsecurityfiles(c full path to project files). If later you do toggle the security features on, whatever security settings you define overwrite the placeholder files.
The reverse is not true, a5ws_createsecurityfiles() will NOT overwrite existing security files. This is a good thing.
4) You do have to open your V7 app in V8 and republish all files from V8 to the V8 server. There probably are other reasons, but I do know the way components are represented in the A5W pages has changed.
5) Final note, I don't really know how this would work in practicality, but you can toggle the Security Model to Group Security for one Grid and Level Security for another Grid. Same story for Nav Components. Dialogs only allow Group Security.
Comment