Difference between revisions of "Data Partitions"
From SDU
m |
m |
||
| Line 10: | Line 10: | ||
{ "0" ,"Change Activity Log tables" ,"chgalg" ,"Change_Act_Log" } | { "0" ,"Change Activity Log tables" ,"chgalg" ,"Change_Act_Log" } | ||
{ "0" ,"Issue Activity Log tables" ,"issalg" ,"Issue_Act_Log" }</source> | { "0" ,"Issue Activity Log tables" ,"issalg" ,"Issue_Act_Log" }</source> | ||
| − | |||
== Constraint Types == | == Constraint Types == | ||
| Line 20: | Line 19: | ||
* '''Update''' - Updated records must satisfy this constraint in order to be saved. | * '''Update''' - Updated records must satisfy this constraint in order to be saved. | ||
* '''View''' - Identifies the records that can be viewed. | * '''View''' - Identifies the records that can be viewed. | ||
| + | |||
== Example Constraints == | == Example Constraints == | ||
Revision as of 15:11, 17 June 2008
Data Partitions are subsets of the database with restricted access based on their content. A Data Partition restricts access with a defined set of constraints. The Data Partitions are associated with Contacts via their Access Type. For legacy purposes Data Partitions can also be associated with a Contact Record directly, however this is not a recommended method.
Controlled Tables
Constraints can only be created for tables in the Controlled Tables list. There is no GUI supported method of adding tables to the Controlled Tables list, but the process can be achieved via a data load.
Example load:<source lang="text">TABLE Controlled_Table
del desc obj_name sym
{ "0" ,"Activity Log tables" ,"alg" ,"Act_Log" }
{ "0" ,"Change Activity Log tables" ,"chgalg" ,"Change_Act_Log" }
{ "0" ,"Issue Activity Log tables" ,"issalg" ,"Issue_Act_Log" }</source>
Constraint Types
- Create - New records must satisfy this constraint before a save can be completed.
- Defaults - Sets default values to be set on an empty field of a new record.
- Delete - Specifies what records can be deleted by the user.
- Pre_update - Identifies the records that can be updated by the user. Records not satisfying this constraint can only be view as read-only.
- Update - Updated records must satisfy this constraint in order to be saved.
- View - Identifies the records that can be viewed.
Example Constraints
| Table | Type | Syntax | Description |
|---|---|---|---|
| ca_contact | Pre-Update | id = @root.id | Only permit update of your own Contact Record. |
| ca_contact | Pre-Update | id = U'00' | Prevent updating of any Contact. |
| ca_contact | View | last_name NOT LIKE 'KT%' | Prevent display of any Groups beginning with the letters 'KT' |
| Call_Req | Create | customer = @root.id | Allowing only the creation of tickets where you are the End User |
| Call_Req | Default | type = 'I' | Create an Incident |
| Call_Req | Default | category = 'pcat:400001' | Set a default Request/Incident/Problem Area |
| Call_Req | Delete | id = 1 | Prevent the deletion of any tickets |
| Call_Req | Pre-Update | customer = @root.id | Allowing only the updating of tickets where you are the End User |
| Call_Req | View | customer = @root.id | Allowing only the viewing of tickets where you are the End User |
| Cr_Status | View | code IN ('ACK','OP','RE','WIP') | Display a set list of Status Options |
| Workflow_Task | Delete | task != 'APP' | Prevents the deletion of the Approval task. |
To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.
To discuss or ask questions about this article, select the discussion tab above.
