Veeva Systems Inc.

Jon Stone

Peter Gassner

Igor Tsives

Andrew Han

Eric Z Batzdorff

Eric David Bezar

Derek Allwardt

George C Lee

Rich Mayfield

Arno Sosna

Timothy S Murphy

Ian Wong

Graham Gelwicks

Chatham Reed

Patrick Ota

Stephen Paul Harper

Shu-Shang Sam Wei

Piotr Kuchnio

Marius K Mortensen

Zhen Tan

Asaf Roll

Peter Thorson

Jean-Christophe Meriaux

Arvind Talari

Richard Mayfield

Bobby Ng

Andrew James Mitchell

Scott Immel

Tyler James Jensen

Jeremy House

Mark Arnold

Tanay Nagjee

Joshua Andrew Lim

Leah Avalon Weitz

Sindhusha Reddy Jensen

Bailey Chen

Sandeep Chopra

Zhanye Tong

Tao Wang

Jason Methia

Todd Tullis

Systems and methods for re-using content in a content management system. The content management system may have two or more repositories. A link document may be generated in a link repository for a source document in a source repository. The link document may be a copy of the source document, and synchronized to the source document in a number of different ways, dynamically or statically. When the source document is updated, the source repository may notify the link repository about the change, receive a pull request from the link repository for the change, and generate an updated link document. A static copy of the link document may be created to prevent further changes to the link document for business or compliance purposes.

System and method for content sharing in enterprise content management

Systems and methods for processing emails in a content management system. The content management system may have two or more repositories. Users associated with a customer of a content management system, e.g., a pharmaceutical company, may send emails to a master email address, or email processor username, specifically created for an email processor in the content management system. The email processor may automatically create documents, records and attachments from the emails.

System and method for processing emails in enterprise content management

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.

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

Systems and methods for generating a multi-view report in a content management system. A number of report views may be defined and a report type may be configured. The report type configuration may define the report views to be included, the field the report views match on, and how the report views should be joined. The multi-view report is generated according to the report type configuration.

Displaying reports in a content management system

Systems and methods for exchanging clinical data among parties involved in a clinical trial. The system comprises a clinical data exchange controller, a first repository and a second repository. Repository configuration information comprises: a connection to a target repository, scope of capacities, and a rule set. Repository configuration information for the first repository is received at the first repository, and repository configuration information for the second repository is received at the second repository. When there is a change defined in the rule set happened in the first repository, a request for data transfer is sent to the clinical data exchange controller, and the clinical data exchange controller then transfers the data to the target repository based on the rule set.

System and method for exchanging clinical data

Systems and methods for controlling document access in a content management system. A user setup record may be saved for each user, and user groups may be generated based on attributes of user setup records. When a user group is stamped to a document in the content management system, all users in that user group get access to the document.

Dynamic document access control in a content management system

Systems and methods for re-using content in a content management system. The content management system may have two or more repositories. A link document may be generated in a link repository for a source document in a source repository. The link document may be a copy of the source document, and synchronized to the source document in a number of different ways, dynamically or statically. When the source document is updated, the source repository may notify the link repository about the change, receive a pull request from the link repository for the change, and generate an updated link document.

Systems and methods for controlling object/document access in a content management system. The content management system may have several layers of access controls, which may include a layer of access control at the object level, a layer of access control at the row level and a layer of access control at the field level. Access may be controlled at the object level by a user's security profile, at the object record level (or row level) by the user's role, and/or at the object field level by the user's role or a state in a document lifecycle. In other words, the object level access control may grant access (e.g., Create, Read, Edit and Delete) on objects, the object record level access control may grant access (e.g., Read, Edit and Delete) on object records, and field level access control may grant access (e.g., Read, Edit and Hidden) on object field level.

Access control in a content management system

Systems and methods for uploading tenant code to a multi-tenant system. Tenant Java source code is sent to the multi-tenant system over an MDL interface, and stored in a repository of the multi-tenant system as source code metadata. The tenant code may be extracted and executed when a predetermined event occurs.

Uploading tenant code to a multi-tenant system

Growing community of inventors

Manteca, CA, United States of America

Jon Stone