User programmatic interface for supporting data access control in a database system

Patent metadata

Field	Value
Publication number	US-11222133-B1
Application number	US-202016863956-A
Country	US
Kind code	B1
Filing date	Apr 30, 2020
Priority date	Nov 13, 2017
Publication date	Jan 11, 2022
Grant date	Jan 11, 2022

Abstract

Systems and methods for providing an API for a database system. The API may be provided to enable external application developers to build applications that can support the dynamic security model of the content management system and describe the runtime properties of records in data objects. The API of may provide a record property object and/or a query describe object when returning data set in response to a query by providing information about actions an end user can take on the data records, and to provide metadata required to understand a data response.

First claim

What is claimed is:

1. A method for managing a case in a content management system, comprising:
receiving configuration metadata of a first data record and a second data record in the content management system;
receiving a first query for data objects in the content management system;
obtaining the first data record in response to the first query;
displaying a first user interface for receiving a selection of an existing case or a new case;
receiving a selection of a new case on the first user interface;
displaying a data entry user interface for receiving data of an initial version of an object of the new case;
receiving a request for a first review;
generating a first minor version of the object of the new case and saving the first minor version of the object of the new case in the content management system;
receiving an input which indicates that the first minor version of the object of the new case is not approved;
displaying a copy of the first minor version of the object of the new case, receiving a first update to it, and saving the first minor version of the object of the new case with the first update as a second minor version of the object of the new case while keeping the first minor version of the object of the new case in the content management system;
receiving a request for a second review;
receiving an input which indicates that the second minor version of the object of the new case is approved; and
saving the second minor version of the object of the new case as a first major version of the object of the new case to the content management system.

2. The method of claim 1 , wherein the new case is for managing an adverse medical event.

3. The method of claim 1 , further comprising: changing a status of the new case to closed after saving the second minor version of the object of the new case as the first major version of the object of the new case.

4. The method of claim 3 , further comprising: receiving a selection of an existing case on the first user interface.

5. The method of claim 4 , further comprising: receiving a selection for creating a first follow-up of the new case after the first major version of the object of the new case is saved.

6. The method of claim 5 , further comprising: displaying a copy of the first major version of the object of the new case, receiving a second update to it, and saving the first major version of the object of the new case with the second update as a first minor version of an object of the first follow-up case while keeping the first major version of the object of the new case in the content management system.

7. The method of claim 6 , further comprising: receiving a request for a third review.

8. The method of claim 7 , further comprising: receiving an input which indicates that the first minor version of the object of the first follow-up case is approved.

9. The method of claim 8 , further comprising: saving the first minor version of the object of the first follow-up case as a second major version of the object of the new case.

10. The method of claim 9 , further comprising: changing a status of the first follow-up case to closed after saving the first minor version of the object of the first follow-up case as the second major version of the object of new case.

11. The method of claim 10 , further comprising: receiving a selection for creating a second follow-up of the new case before the first major version of the object of the new case is saved.

12. The method of claim 11 , further comprising: displaying a copy of the first major version of the object of the new case, receiving a third update to it, and saving the first major version of the object of the new case with the third update as a first minor version of an object of a second follow-up case while keeping the first major version of the object of the new case in the content management system.

13. The method of claim 12 , further comprising: receiving a request for a fourth review.

14. The method of claim 13 , further comprising: receiving an input which indicates that the first minor version of the object of the second follow-up case is approved.

15. The method of claim 14 , further comprising: saving the first minor version of the object of the second follow-up case as a third major version of the object of the new case.

16. The method of claim 15 , further comprising: changing a status of the second follow-up case to closed after saving the first minor version of the object of the second follow-up case as a first major version of the object of the second follow-up case.

17. A content management system, comprising:
a plurality of repositories for storing data; and
a case management controller for:
displaying a first user interface for receiving a selection of an existing case or a new case;
receiving a selection of a new case on the first user interface;
displaying a data entry user interface for receiving data of an initial version of an object of the new case;
receiving a request for a first review;
generating a first minor version of the object of the new case and saving the first minor version of the object of the new case in the content management system;
receiving an input which indicates that the first minor version of the object of the new case is not approved;
displaying a copy of the first minor version of the object of the new case, receiving a first update to it, and saving the first minor version of the object of the new case with the first update as a second minor version of the object of the new case while keeping the first minor version of the object of the new case in the content management system;
receiving a request for a second review;
receiving an input which indicates that the second minor version of the object of the new case is approved; and
saving the second minor version of the object of the new case as a first major version of the object of the new case.

18. The system of claim 17 , wherein the case management controller further receives a selection for creating a first follow-up of the new case after the first major version of the object of the new case is saved.

19. The system of claim 18 , wherein the case management controller further receives a selection for creating a second follow-up of the new case before the first major version of the object of the new case is saved.

20. The system of claim 19 , wherein the case management controller further displays a copy of the first major version of the object of the new case, receives a third update to it, and saves the first major version of the object of the new case with the third update as a first minor version of an object of a second follow-up case while keeping the first major version of the object of the new case in the content management system.

Assignees

• Veeva Systems Inc

Inventors

• Gassner Peter
• Han Andrew
• Tsives Igor
• Stone Jon
• Mortensen Marius K
• Immel Scott
• Kuchnio Piotr
• Mitchell Andrew James
• Roll Asaf
• Tan Zhen

Classifications

• G06F21/604

  Tools and structures for managing or administering access control systems · CPC title

• G06F2221/2113

  Multi-level security, e.g. mandatory access control · CPC title

• G06F21/6227 Primary

  where protection concerns the structure of data, e.g. records, types, queries · CPC title

• G06F16/9035

  Filtering based on additional data, e.g. user or group profiles · CPC title

• G06F16/9038

  Presentation of query results · CPC title