Policies describe the individual pieces of information that MCS needs to render pages that match the devices used by a range of users.
Policies describe the individual pieces of information that MCS needs to render pages that match the devices used by a range of users.
By applying different policies, you can distinguish between 'device-specific' and 'device-independent' information. This policy based separation enables quicker, easier maintenance as well as rapid implementation.
You can target visual presentation elements such as page layouts and style sheets at particular devices, and reuse them easily. You can administer a single source, rather than having to programmatically generate a piece of logic for each and every device, layout or mark-up combination. This also means that your application can more easily support new devices and changes in visual presentation.
You describe a set of policies for your application by creating a workbench project, and using the MCS policy editors to define combinations of:
Policies that bind different types of resource to devices
Variants and their attributes
Graphical layouts for different devices
Stylistic themes for different devices
New devices and custom device policies, and standard policy values and identification patterns to suit any special requirements in your organization
In addition to the policy editors there are a number of supporting workbench views.
You can configure MCS projects to enable different users to work simultaneously on policies, layouts and themes, by locking resources while they are edited. Enabling collaboration takes place when a project is first created, or by editing the project properties.
Collaborative working requires the use of a JDBC policy repository.
Policy names can contain any characters except:
| (space) | |
|---|---|
| . | full stop |
| () | parentheses |
| [] | brackets |
| {} | braces |
| " | double quotes |
| ' | single quotes |
| \ | backslash |
| / | forward slash |
| + | plus |
| - | minus |
| * | asterisk |
| ÷ | divide |