Mastership policies

You need to take mastership policies into consideration when planning your change management processes. Mastership adds another layer of control within your process.

For example, as a record moves from one state to another, different replicas can be assigned mastership of the record. Or, you may choose to have all records of a certain type, regardless of state, mastered by a specific replica, which means that all modification of those records must take place at the master replica.

Mastership can affect different aspects of your process. For example, consider the following guidelines:
  • Hooks that modify records or field values can run only if the current replica masters the record.
  • You must modify users and groups at the replica that masters the user or group.
  • You must edit Workspace items (queries, reports and report formats) at the master replica.
  • You can modify or customize schemas only at the working schema repository.