| 
Role based Access Control:
Example: Mr. Smith belongs to the sales team. He can log on to the
application and access the purchase order window. But as a salesperson,
he cannot enter the Human Resources windows.
Visual Guard will first verify the user's login. Then, it will
disable some menu options to restrict access to authorized windows
only.
Secure the data:
You can define which user can modify or view any particular data.
Example: Salaries are confidential. Only the director can modify
them, some managers can review them and most of employees won’t
see them.
Visual Guard will hide this field or disable modifications depending
on the user's permissions.
For security or confidentiality reasons, you may also want to filter
data that users can see and modify.
Example: A salesperson in charge of the USA can only access the
deals made with American customers whereas the person in charge
of Canada will access Canadian deals.
Visual Guard will dynamically filter the deals the user can see
or modify.
Adapt the graphical interface to the User Profile:
You may need to change the application’s GUI to reflect the
user's permissions.
Example: The customer window contains a button called “new”
to create a new customer.
Visual Guard can hide or disable this button if the user is not
allowed to create customers.
This feature is available for any item of the user interface (button,
tab, menu, fields, etc…).
Parameter business logic:
Business rules may vary from one user to another.
Example: Employees can create purchase orders up to $500 and managers
up to $10,000.
Visual Guard will apply this limitation according to the value
defined for the user profile.
Top
Resources:
 See
a demo for PowerBuilder
Getting
started
Visual Guard Architecture
How does it work?
Receive an evaluation version
Visual
Guard for .NET
|
