	US 12,192,044 B1
	System and method for sharing updates between repositories in enterprise content management
Scott Edward Mitreuter, Brick, NJ (US); Andrew Han, Needham, MA (US); Bobby Ng, San Ramon, CA (US); and Katharyn A. Wilber, Philadelphia, PA (US)
Assigned to Veeva Systems Inc., Pleasanton, CA (US)
Filed by Veeva Systems Inc., Pleasanton, CA (US)
Filed on Jan. 23, 2020, as Appl. No. 16/751,205.
Int. Cl. H04L 41/02 (2022.01); G06F 16/25 (2019.01); H04L 41/0806 (2022.01); H04L 41/5003 (2022.01); H04L 43/06 (2022.01)

CPC H04L 41/02 (2013.01) [G06F 16/25 (2019.01); H04L 41/0806 (2013.01); H04L 41/5003 (2013.01); H04L 43/06 (2013.01)]

17 Claims

1. A computer-implemented method for sharing updates between a first repository and a second repository in a content management system, wherein the content management system comprises a content management server, the method comprising:

receiving integration point configuration information at the content management server for integrating the first repository and the second repository, wherein the first repository is associated with a first group of multiple user accounts, a first application and data of the first application, and the second repository is associated with a second group of multiple user accounts, a second application and data of the second application, and wherein updates in the second repository are visible to the first group of multiple user accounts associated with the first repository, and wherein the first application is a quality management application;

creating a first record in the first repository for a first change, wherein the first record comprises information about the first change;

generating a plurality of impact assessments in the first repository for the first change;

assigning one impact assessment of the plurality of impact assessments relating to the second repository to the second repository;

generating a second record for the impact assessment relating to the second repository in the first repository, wherein the second record for the impact assessment relating to the second repository comprises information about a type of the impact assessment and a link to the one impact assessment;

sending the second record for the impact assessment relating to the second repository from the first repository to the second repository via a first integration point message; and

providing, in response to a selection of the link by a user account of the second group of multiple user accounts, the impact assessment of the first repository to the user account of the second group of multiple user accounts associated with the second repository.