Repository Synchronization allows changes made to the LANSA for i Repository to be propagated to Visual Repositories. Repository synchronization includes updates to task tracking and other partition information.
When a change is made to an object, it is automatically propagated by LANSA for i sending read-only version of the transaction to the Visual LANSA Slave Repositories. If an object is currently checked out for update in a Visual LANSA Slave Repository, the propagation overwrites this object and the Visual LANSA Slave Repository user will need to check the object out for update again before they can perform any modifications. This situation can be avoided by ensuring the developer who has checked out the object for update is the only developer authorized to the task they are using and hence the only developer modifying the object.