Salesforce, Inc. patent applications on June 13th, 2024
Patent Applications by Salesforce, Inc. on June 13th, 2024
Salesforce, Inc.: 14 patent applications
Salesforce, Inc. has applied for patents in the areas of G06F16/2457 (2), H04L12/18 (2), G06F16/28 (2), H04L51/216 (1), G06F40/169 (1) G06F9/48 (1), G06F11/3075 (1), G06F16/24 (1), G06F16/24573 (1), G06F16/254 (1)
With keywords such as: data, database, user, service, communication, computer, records, instance, based, and immutable in patent application abstracts.
Patent Applications by Salesforce, Inc.
Inventor(s): Federico Piagentini of Buenos Aires (AR) for salesforce, inc., Javier Dombronsky of Buenos Aires (AR) for salesforce, inc., Leonardo Rodriguez of Buenos Aires (AR) for salesforce, inc.
IPC Code(s): G06F9/48
CPC Code(s): G06F9/48
Abstract: methods, systems, and storage media are described for enabling the execution of design operations associated with service integrations. in particular, some implementations are directed to executing design operations using operation-specific processors. other implementations may be disclosed or claimed.
Inventor(s): Mark Wilding of San Francisco CA (US) for salesforce, inc.
IPC Code(s): G06F11/30, G06F11/07, G06F11/34
CPC Code(s): G06F11/3075
Abstract: techniques for providing application contextual information. one or more sets of database context identifiers corresponding to events that occur within the database are generated by the database. the one or more sets of database context identifiers have at least one application context field. a session identifier corresponding to a session to be monitored is sent from the application to the database. information to be stored in the database with the session identifier is sent to the database. database logs and application logs are correlated using at least the session identifier.
20240193154.Mechanisms for Deploying Database Clusters_simplified_abstract_(salesforce, inc.)
Inventor(s): Varun Jobanputra of New York City NY (US) for salesforce, inc., Joshua Gruenberg of Bozeman MT (US) for salesforce, inc.
IPC Code(s): G06F16/24, G06F16/21, G06F16/23, G06F16/27
CPC Code(s): G06F16/24
Abstract: techniques are disclosed that pertain to deploying immutable instances of a system. a computer system may maintain an active generation value that indicates an immutable instance of a database system that is permitted to write data to a database. the computer system may deploy a first immutable instance of the database system and update the active generation value to permit the first immutable instance to write data to the database. the computer system may receive a request to deploy a second immutable instance of the database system that includes an update not found in the first immutable instance. the computer system may deploy the second immutable instance and update the active generation value to cause the first immutable instance to cease writing data to the database and to permit the second immutable instance to write data to the database.
Inventor(s): Zachary Alexander of Berkeley CA (US) for salesforce, inc., Yixin Mao of San Francisco CA (US) for salesforce, inc.
IPC Code(s): G06F16/2457, G06F16/242, G06F16/28
CPC Code(s): G06F16/24573
Abstract: database systems and methods are provided for assigning structural metadata to records and creating automations using the structural metadata. one method of assigning structural metadata involves determining a candidate group of semantically similar conversations based on unassigned conversations, determining a clustering performance metric associated with the candidate group based on a relationship between the candidate group and a plurality of existing groups of semantically similar conversations, and when the clustering performance metric is greater than a threshold, automatically assigning one or more unassigned conversations to the candidate group based on the representative utterances associated therewith and automatically updating one or more associated records at a database system to include metadata identifying the candidate group.
20240193174.AUTOMATIC DATA LINTING RULES FOR ETL PIPELINES_simplified_abstract_(salesforce, inc.)
Inventor(s): Ignacio Agustin MANZANO of Buenos Aires (AR) for salesforce, inc., Subhash Periasamy of Newark CA (US) for salesforce, inc., Berkay Polat of Redwood City CA (US) for salesforce, inc., Vineeth Anand Nair of Mountain House CA (US) for salesforce, inc., Udayakumar Dhansingh of Dublin CA (US) for salesforce, inc., Vijay Gopalakrishnan of Seattle WA (US) for salesforce, inc., Saebom Kwon of San Francisco CA (US) for salesforce, inc.
IPC Code(s): G06F16/25
CPC Code(s): G06F16/254
Abstract: in the present disclosure, systems and methods are described for allowing a non-code user to create to transform a database in an etl pipleline. specifically, as disclosed herein, a user can take a database and receive a ruleset to apply to the database in an etl pipeline. the data linting system may take the database and extract a schema and a data sample from it. further, the data linting system may use the schema and data sample to create two rulesets. with these rulesets, the data linting system combines them to create a final ruleset which may be validated using the data sample. the data linting system then sends the final ruleset and the validation report to the user. with this system, the user only needs to give it a database and will receive a ruleset that is able to be immediately used in an etl pipeline.
20240193186.DATABASE LAYERED FILTERING_simplified_abstract_(salesforce, inc.)
Inventor(s): Patrick James Helland of San Rafael CA (US) for salesforce, inc., David Edward DeHaan of Burlington (CA) for salesforce, inc.
IPC Code(s): G06F16/28, G06F16/22, G06F16/2457
CPC Code(s): G06F16/282
Abstract: techniques are disclosed pertaining to layered filtering. a computer system may store records in a hierarchy of levels. the computer system may receive a request to perform a key range search to locate records that fall within a key range and satisfy selection criteria. the computer system may perform the key range search. as part of processing a particular level, the computer system may receive a first set of records associated with another level and select a second set of records from the particular level that fall within the key range and satisfy the selection criteria. the computer system may merge the first and second sets of records into a third set of records, which may include not inserting, into the third set, any record of the first set of records for which there is a newer version in the particular level that does not satisfy the selection criteria.
Inventor(s): Feifei Jiang of San Mateo CA (US) for salesforce, inc., Zachary Alexander of Berkeley CA (US) for salesforce, inc., Yuanxin Wang of Mountain View CA (US) for salesforce, inc., Yixin Mao of San Mateo CA (US) for salesforce, inc., Sitaram Asur of Newark CA (US) for salesforce, inc., Regunathan Radhakrishnan of Dublin CA (US) for salesforce, inc., Aron Kale of Huntington Beach CA (US) for salesforce, inc.
IPC Code(s): G06F16/9535, G06F16/9538
CPC Code(s): G06F16/9535
Abstract: a cloud platform establishes a communication session between an agent and a user. the communication session is over an electrical medium. the cloud platform generates an interface on a client device associated with the agent. a first portion of the interface is configured to exchange messages between the agent and the user for a conversation or otherwise transcribe a conversation between the agent and the user. the cloud platform obtains, at a first time, a set of utterances from a transcript of the conversation. the cloud platform accesses a database including a plurality of articles. the cloud platform generates relevance scores between the conversation and the plurality of articles. the cloud platform then selects a subset of articles having relevance scores above a threshold value or proportion. the identified articles are presented on a second portion of the interface.
Inventor(s): Zachary Alexander of Berkeley CA (US) for salesforce, inc., Yixin Mao of San Francisco CA (US) for salesforce, inc.
IPC Code(s): G06F40/35, G06F16/16
CPC Code(s): G06F40/35
Abstract: database systems and methods are provided for assigning structural metadata to records and creating automations using the structural metadata. one method of assigning structural metadata to a group of conversation records involves receiving a user input modification pertaining to a group of semantically similar conversations, automatically reassigning a conversation to a different group of semantically similar conversations based on its representative utterance in a manner that is influenced by the user input modification, and automatically updating, at a database system, a record associated with the conversation to include metadata identifying the different group of semantically similar conversations.
Inventor(s): Heather Phillips Stables of Woodstock GA (US) for salesforce, inc., Paul Joseph Nix of Indianapolis IN (US) for salesforce, inc., Tejas Sanghavi of Palo Alto CA (US) for salesforce, inc., Jonathan Daniel Showers Belkowitz of New York NY (US) for salesforce, inc., Amrutha Krishnan of San Francisco CA (US) for salesforce, inc.
IPC Code(s): G06N20/00, G06F18/40
CPC Code(s): G06N20/00
Abstract: methods, systems, apparatuses, devices, and computer program products are described. a data service may receive a first user input indicating a first set of entities for training an artificial intelligence (ai) model for propensity score-prediction. the data service may receive a second user input indicating a set of outcome conditions which define what a user would like to predict about a customer (e.g., propensity to purchase). the data service may generate the ai model accordingly, and based on executing the ai model, generate a set of prediction metrics (propensity scores) for a second set of entities. the data service may store an indication of the ai model for review by a user. when the user approves the ai model and publishes the ai model to the data service, the generated propensity scores may be used to generate a segment of entities of the second set of entities.
Inventor(s): Tyler Lewis of San Anselmo CA (US) for salesforce, inc., Joseph Michael McGarr of Mountain View CA (US) for salesforce, inc., Felix Rieseberg of San Francisco CA (US) for salesforce, inc., Issac Gerges of Austin TX (US) for salesforce, inc., Anuj Nair of Berkeley CA (US) for salesforce, inc.
IPC Code(s): H04L51/046, G06F3/04842, G06F40/169, H04L12/18, H04L51/08
CPC Code(s): H04L51/046
Abstract: draft message object collaboration in a group-based communication platform is described. a request to generate a message object can be received from a first client associated with a first entity of a group-based communication platform. a first instance of a composition user interface, configured to enable a draft of the message object to be generated, can be presented via the first client and a request to add a second entity as a collaborator can be received. a second instance of the composition user interface can be presented via a second client of the second entity. a modification to the draft of the message object can be received and, in response to receiving the modification, the message object can be updated as presented via respective instances of the composition user interface.
Inventor(s): Sri Vasamsetti of San Francisco CA (US) for salesforce, inc., Paul Matthew Jennings of Redwood City CA (US) for salesforce, inc., Paul Rosania of San Francisco CA (US) for salesforce, inc., Steven Gordon of San Francisco CA (US) for salesforce, inc., Michael Demmer of San Francisco CA (US) for salesforce, inc.
IPC Code(s): H04L51/42, G06F16/11, H04L12/18, H04L51/216
CPC Code(s): H04L51/42
Abstract: embodiments described herein include apparatuses, computer program products, and methods for data management in a group-based communication system. specifically, some embodiments address data management for group-based communication channel(s) accessible to any number of entities based on various data retention policies. in this regard, embodiments enable maintenance of data associated with multiple organizations accessing a group-based communication channel based on a single, shared data retention policy, or different data retention policies, for example based on authorship of the group-based communication message. in embodiments, a data retention policy may be assigned directly to an entity, or assigned to a higher-level or lower-level entity and function as a default data a retention policy for other entities associated therewith. a group-based communication system is configured to enable storage of data based on corresponding data retention policies for each organization identifier, and/or an agreed data retention policy for all organization identifiers.
Inventor(s): Serguei Mourachov of Vancouver (CA) for salesforce, inc., Sameera Thangudu of San Francisco CA (US) for salesforce, inc., Manju Vijayakumar of Fremont CA (US) for salesforce, inc., Gabriel Adomnicai of San Francisco CA (US) for salesforce, inc., Kimberly Van Anh Nguyen of Oakland CA (US) for salesforce, inc., Eric M. Halpern of San Francisco CA (US) for salesforce, inc., Dan Willhite of West Bath ME (US) for salesforce, inc., Brett Griffin Wines of Mountain View CA (US) for salesforce, inc.
IPC Code(s): H04L65/1093, H04L65/1069, H04L65/1073
CPC Code(s): H04L65/1093
Abstract: media, methods, and systems are provided for real-time updates of collaborative documents in a group-based communication system. collaborative documents may allow for multiple users to simultaneously modify and edit a document. when a collaborative document is created, a server may create an ephemeral channel and an identifier for the collaborative document. as users connect to the collaborative document, the users may be assigned a temporary subscription to the collaborative document. real-time events, such as indications that a user is typing, indications that a user is connected in the collaborative document, and changes to the collaborative document may be published to the user via the temporary subscription. when the user disconnects from the document, the real-time events may no longer be communicated.
Inventor(s): Alejandro Lopez of San Francisco CA (US) for salesforce, inc., William Robert Jennings, II of Indianapolis IN (US) for salesforce, inc., Penny Nicoletta Tselikis of Carmel IN (US) for salesforce, inc., Justin Louis Condren of San Francisco CA (US) for salesforce, inc.
IPC Code(s): H04L67/75, G06F3/0483
CPC Code(s): H04L67/75
Abstract: methods, systems, apparatuses, devices, and computer program products are described. a communication process flow management service may display a set of actions associated with a communication process flow configured to manage communications for a tenant. to update a segment of entities on which the communication process flow is to be executed, a user may navigate to a separate browser tab from that of the communication process flow management service, and may update the segment using an entity segmentation service. the communication process flow management service may receive an indication from an entity segmentation service that a segment of entities is updated and display a notification or a toast popup indicating the segment update to a user interface.
20240195908.MAINTAINING SERVICE AVAILABILITY_simplified_abstract_(salesforce, inc.)
Inventor(s): Kaushal Bansal of San Francisco CA (US) for salesforce, inc., Prabhat Signh of San Francisco CA (US) for salesforce, inc.
IPC Code(s): H04M3/22, G06F8/30
CPC Code(s): H04M3/2209
Abstract: systems, devices, and techniques are disclosed for maintaining service availability. files including code written using a domain specific language (dsl) for network security may be received. a knowledge graph including connections between services may be generated from the code written using the dsl in the files. a service that will have an availability issue may be determined based on the connections between services in the knowledge graph. the service that will have the availability issue may be replicated. the replication of the service that will have the availability issue may occur before the service has the availability issue.
- Salesforce, Inc.
- G06F9/48
- CPC G06F9/48
- Salesforce, inc.
- G06F11/30
- G06F11/07
- G06F11/34
- CPC G06F11/3075
- G06F16/24
- G06F16/21
- G06F16/23
- G06F16/27
- CPC G06F16/24
- G06F16/2457
- G06F16/242
- G06F16/28
- CPC G06F16/24573
- G06F16/25
- CPC G06F16/254
- G06F16/22
- CPC G06F16/282
- G06F16/9535
- G06F16/9538
- CPC G06F16/9535
- G06F40/35
- G06F16/16
- CPC G06F40/35
- G06N20/00
- G06F18/40
- CPC G06N20/00
- H04L51/046
- G06F3/04842
- G06F40/169
- H04L12/18
- H04L51/08
- CPC H04L51/046
- H04L51/42
- G06F16/11
- H04L51/216
- CPC H04L51/42
- H04L65/1093
- H04L65/1069
- H04L65/1073
- CPC H04L65/1093
- H04L67/75
- G06F3/0483
- CPC H04L67/75
- H04M3/22
- G06F8/30
- CPC H04M3/2209
