---
# System prepended metadata

title: 'Feature: Lock a Record For Central Syncing.'

---

# Feature: Lock a Record For Central Syncing.


### 1. Clent's Problem :bug: 

1. Wellness benfits should not be added to a plan once a pateint has started using it. 
2. But wellness plan benefits get changed in the child site due to the central syncing which breaks the patinet benefits in child sites.


### 2. Solution :tada: 

To over come the situation , we have implmented an option where a wellness plan can be put in to a in draft version in the parent site until it is ready for syncing down. Once the record is marked as ready ,it will sync down then plan cannot be modified in the parent site. 


### 3. How it works ? :hammer_and_wrench: 

- In central structure sites , user see a "Lock Plan" Button on the wellness plan Record. 
- The record won't be syncing down until user lock the plan for central Syncing by pressing the button.
- In the child site this record shows as "Ignore" (along with a tooltip info) in the central syncing grid view until user locks the Plan.
- Once plan is locked then it gets synced down and User cannot modify the follwing items of the plan in the parent site. 

    1. Subscription Cycle
    2. Subscription Fee Product
    3. Fee Charged Per Cycle
    4. Term Length
    5. Pause extends membership end date
    6. Enrollment Fee
    7. Adding New Benefits



### 4. What Else ? :thinking_face: 

- A locked wellness plan in a central site can be copied, edited and saved.
- In central strcuture sites (Parent Site) the permission for wellnesplan shows as Add/edit/Lock
- If user does not have the lock permission then the "Lock Plan" button will be grayed out.
- All the wellness plan in the parent site will be set as "Locked" at start.