The security keys will be right on StandardForm... no templating required.  Just set the permission key on the form to define the permission that is required to view/edit the form and then define the permission within the database (same functionality on the field-level, too).

Hmm..how about the ability to allow users to change roles, permissions, etc.?

Absolutely.  There is a dialog form that you can display to the end-user to manage all of the roles, users, and permissions associated with the roles and users.  It is very flexible and gives you complete control without actually having to write the end-user interface yourself.

In the same approach we have taken throughout the framework, we have implemented features that give you as much or as little control over the security that you would need. 

Perfect!

I really think the security will "float your boat"  .  It is going to be a spectacular addition to the framework!

Hi,
I can remeber if i saw this in the documentation somewhere. StrataFrame currently does support field level access, is this correct, and if it is how would this be affected or implemented with the additions you are doing to the security of forms right now.

Wayne

StrataFrame does currently support field level security but it is not data driven.  Without the security module you would have to manually capture the CheckFieldSecurity event and program your logic.  With the security module it is data driven allowing a permission to be associated with the field level access.  For example, one type of role (or a specific user) may be able read the address information but not write to it.  So the role or user account will either be assigned a field level permission with an action assigned.  An action determines the type of access.  For example: write, readonly, blank, blank with message, replacement characters, and regex replacement.  So the field level security can be data driven and will respect the users permissions.

In fact, we used the CheckFieldSecurity hook that was already in place to check the field level security, we just made it data-driven, like Trent said.

Hi,

"You'll be happy to know that the security will be in the next release.  Probably when 1.4.1 switches from pre-release to full release. "

How close are we to the 1.4.1 full release and would it be possible to get a video sample of how these new security features can be used.

Kari

Kari,

It will be July before the 1.4.1 release is official and the security module becomes available for use.  When we release the security module, there will be samples to help you along the way.  And yes, we will more than likely create a video to post on the forum showing how to use the security features.