Design Note: Policies

A configuration policy allows you to create a set of requirements that should apply for a given set of conditions. Typically this means settings or security rights. Using a policy, you can automatically grant the "end of day" security right to all users between 4pm and 6pm, or perhaps change a group of settings on a subset of lanes under specific conditions.

Overview

1. A policy is created and given a name, eg "All Sites" or "Customer 6"
2. The specific settings or security rights are added to this policy.
3. A condition map is created to outline when the policy is applied.
4. A policy can be optionally merged into another at a future date. This means that over time there won't be a build up of thousands of policies

Conceptually, it is similar to the following (example only, may show ideas that aren't implemented)

Policy   EOD
	between 4pm and 6pm
	grant right EOD

Apply EOD
	to all lanes


Policy NewServers
	setting A = ?
	setting B = ?
	setting C = ?
	grant right xyz
	revoke right ghj

Apply NewServers
	require version >= 1995
	to location 6 when teller=23
	to location 5 after 3rd May
	to all progressively by 20th May
	merge to AllLanes after 20th June

Apply NewServers
	when teller=test
	or customer=test