Ve Opening LLC v. Salesforce Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: VE Opening LLC (Texas)
  • Defendant: Salesforce, Inc. (Delaware)
  • Plaintiff's Counsel: Direction IP Law
• Case Identification: 7:25-cv-00539, W.D. Tex., 02/05/2026
• Venue Allegations: Venue is alleged to be proper based on Defendant having a place of business in Austin, Texas, within the district, and committing alleged acts of infringement there.
• Core Dispute: Plaintiff alleges that Defendant's Slack Enterprise Search product infringes a patent related to methods for sharing information between different applications on a computing device.
• Technical Context: The technology addresses the challenge of siloed software applications by enabling a user to initiate a search from a primary application that can find, display, and link to information within separate, secondary applications.
• Key Procedural History: The complaint is a First Amended Complaint, superseding an Original Complaint. The complaint contrasts the patented invention with prior art systems like Android's "Intents" and Apple's iOS 7 to argue for the invention's novelty and non-obviousness.

Case Timeline

Date	Event
2014-06-05	'079 Patent Priority Date
2018-03-13	'079 Patent Issue Date
2026-02-05	First Amended Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

• Patent Identification: U.S. Patent No. 9,916,079 ("Method and System for Enabling the Sharing of Information Between Applications on a Computing Device"), issued March 13, 2018.

The Invention Explained

• Problem Addressed: The patent addresses the problem of software applications on computing devices typically operating independently, making it "difficult and confusing" for a user to perform tasks that require information from multiple applications without tedious manual steps Compl. ¶14 '079 Patent, col. 1:36-46
• The Patented Solution: The invention provides a method where a user, from within a "first application," can initiate a "global search" that covers both the first application and a separate "second application." The system automatically finds and presents "candidate elements" (e.g., files, emails, contacts) from the second application. A user can then select a candidate element to create a selectable link within the first application, which then allows the user to access the information from the second application directly through the first, breaking down the traditional application silos '079 Patent, abstract '079 Patent, col. 2:50-63
• Technical Importance: The technology provided a method for seamless cross-application search and data integration at a time when major mobile and desktop operating systems were characterized by "siloed environments" that limited inter-app communication Compl. ¶15

Key Claims at a Glance

• The complaint asserts independent claim 1 and dependent claims 4, 5, and 6 Compl. ¶21
• Independent Claim 1: A method for sharing information between a first and second application, which includes the essential steps of:
  • From a first application, initiating a global search covering both applications, which involves receiving a global search request, prompting for, and receiving a search term.
  • Based on the search term, automatically determining and presenting corresponding "candidate elements" from the second application for the user to select.
  • Receiving the user's selection of a candidate element.
  • Linking the selected candidate element with the first application by generating a "selectable link" within the first application.
  • Upon selection of this link, presenting information related to the selected element through the first application.
• The complaint asserts dependent claims 4, 5, and 6, which add limitations regarding the active/non-active state of the applications, their inclusion in a "personal information manager," and their status as "secure applications" Compl. ¶¶30-32

III. The Accused Instrumentality

Product Identification

• The Accused Instrumentality is Salesforce's Slack Enterprise Search product Compl. ¶22

Functionality and Market Context

• Slack Enterprise Search is described as an AI-powered feature that allows users to search for information "across all connected tools and systems, without leaving Slack" Compl. p. 8 It integrates with numerous third-party applications (e.g., Asana, Google Drive, Salesforce, GitHub), treating Slack as the central "first application" and the connected tools as "second applications" Compl. ¶22 Compl. p. 8 A screenshot in the complaint shows a user initiating a search from within the Slack interface, which then surfaces content from connected applications like Google Drive Compl. p. 10 The stated purpose is to "break down information silos and streamline productivity" by allowing users to find information from different sources in a "single pane of glass" Compl. p. 9 Compl. p. 21

IV. Analysis of Infringement Allegations

'079 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
A method of enabling the sharing of information between a first application and a second application on a computing device, ... from the first application, initiating a global search covering the first application and the second application by performing steps comprising:	Slack Enterprise Search enables sharing of information between Slack (the first application) and connected apps like Asana or Salesforce (the second application) by initiating a search from the Slack interface Compl. ¶22	¶22	col. 13:36-40
receiving a global search request through the first application, wherein the global search request requests information across the first application and the second application;	A user initiates a global search by using the search bar within the Slack application, which is configured to search both Slack and connected applications Compl. ¶23 A complaint screenshot depicts a search bar within the Slack UI above a list of searchable connected apps Compl. p. 10	¶23	col. 13:41-44
in response to the reception of the global search request, prompting for a search term from a user;	The Slack Enterprise Search interface provides a search bar that prompts the user to enter a search term Compl. ¶24	¶24	col. 13:45-46
receiving the search term;	A user enters a search query, such as "What's the status of the Hawksdale Group deal?", into the search bar Compl. ¶24	¶24	col. 13:47
based on the received search term, automatically determining one or more corresponding candidate elements associated with the second application and presenting the determined one or more corresponding candidate elements associated with the second application for selection by the user;	Slack processes and indexes content from connected second applications. Based on the search term, it automatically identifies and presents relevant content (candidate elements), such as documents from Google Drive or tickets from Jira, in the search results Compl. ¶25	¶25	col. 13:48-54
receiving the selection of at least one of the candidate elements;	The user selects a candidate element from the search results, such as a "Hawksdale Group Proposal" document Compl. ¶26 The complaint includes a screenshot showing a cursor selecting a search result Compl. p. 15	¶26	col. 13:55-56
linking information between the first application and the second application by performing steps comprising: responsive to receiving the selection of the candidate element, linking the selected candidate element with the first application such that a user may access the selected candidate element from the first application;	The complaint alleges that upon selection, the candidate element is linked with Slack, allowing the user to access it from within the Slack application Compl. ¶27	¶27	col. 14:1-5
generating for the first application a selectable link that, when selected, is operable to enable access to information related to the second application;	The search results themselves are presented as selectable links within Slack that, when selected, enable access to the underlying information from the second application Compl. ¶28	¶28	col. 14:6-9
receiving the selection of the linked selected candidate element through the first application; and	The user selects the linked candidate element (the search result) from within the Slack interface Compl. ¶29	¶29	col. 14:10-12
responsive to the reception of the selection of the linked selected candidate element, presenting information related to the linked selected candidate element through the first application.	Upon selection, Slack Enterprise Search displays information related to the linked element, such as pulling information from a third-party app to provide a comprehensive update, "all without requiring you to visit each system separately" Compl. ¶29 Compl. p. 21	¶29	col. 14:13-16

Identified Points of Contention

• Scope Questions: A central question may be whether the integrated "search-and-display" function of the accused product maps to the discrete, sequential steps recited in claim 1. Specifically, the claim recites both "linking the selected candidate element with the first application" and "generating for the first application a selectable link." The defense may argue that the accused product performs a single action of displaying a hyperlink, which does not equate to the two distinct linking and generating steps as claimed.
• Technical Questions: What is the nature of the "linking" performed by the accused product? The patent specification includes an embodiment where a link is embedded into a persistent information field of the first application (e.g., a link to an email is added to the "Notes" field of a task) '079 Patent, col. 12:48-53 '079 Patent, Fig. 4 This raises the question of whether the temporary display of a search result in the accused product constitutes "linking... with the first application" in the manner required by the claim, or if a more permanent integration is required.

V. Key Claim Terms for Construction

• The Term: "linking information between the first application and the second application"

• Context and Importance: This phrase appears to be the core of the claimed invention, describing the action that bridges the two separate applications. The construction of "linking" will be critical to determining whether presenting a hyperlink in a search result list meets this limitation. Practitioners may focus on this term because the patent's specific embodiment shows a more integrated form of linking than what is alleged in the complaint.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The claim language itself is functional: "linking... such that a user may access the selected candidate element from the first application" '079 Patent, col. 14:3-5 Plaintiff may argue that any mechanism that achieves this functional result, including displaying a selectable hyperlink in the first application's UI, satisfies the claim.
  • Evidence for a Narrower Interpretation: The specification provides an example where a link is generated and presented "as part of the notes information field of the first application" '079 Patent, col. 12:48-53 Defendant may argue this example limits the term "linking" to an act of embedding or integrating the link into a data field within the first application, rather than merely displaying it in a transient list of search results.

• The Term: "personal information manager (PIM) application"

• Context and Importance: This term appears in dependent claim 5, and its construction will determine infringement of that claim. The dispute will likely center on whether a modern collaboration platform like Slack qualifies as a "PIM."

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The patent describes a PIM as potentially being comprised of other applications, including "an email application..., a calendar application..., a contacts application..., a notes application... and/or a tasks application" '079 Patent, col. 10:26-31 Plaintiff alleges that Slack, by integrating with such tools, functions as a modern PIM Compl. ¶31
  • Evidence for a Narrower Interpretation: Defendant may argue that a PIM is a historically understood category of software (e.g., Microsoft Outlook) and that the patent's examples limit the term to that traditional definition. They may contend that a general-purpose collaboration platform is technically distinct and does not fall within the scope of a "PIM" as understood by one skilled in the art at the time of the invention.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement, stating that Salesforce provides marketing materials, videos, and user guides that instruct and encourage customers to use Slack Enterprise Search in a manner that directly infringes the '079 Patent Compl. ¶35 Knowledge is alleged to have begun "at least as early as the filing and service of the Original Complaint" Compl. ¶35
• Willful Infringement: While not pleaded as a separate count, the complaint establishes a basis for willfulness by alleging that Defendant had knowledge of the '079 Patent and its infringement from the date of the original complaint and "continued and continues to encourage and induce its customers to use the Accused Instrumentality to infringe" Compl. ¶35

VII. Analyst's Conclusion: Key Questions for the Case

• A core issue will be one of claim construction and scope: Does the multi-step method of Claim 1, which distinguishes between "linking" an element with the first application and "generating" a selectable link for the first application, read on the accused product's integrated function of displaying a list of hyperlinks as search results? The case may turn on whether these are viewed as distinct, required steps or as a redundant description of a single action.
• A second key issue will be one of definitional scope: Can the term "personal information manager (PIM) application," rooted in the context of applications like calendars and contacts as described in the patent, be construed to cover a modern, extensible collaboration platform like Slack? The outcome of this question will determine the viability of infringement allegations for dependent claim 5.
• A central evidentiary question will be one of technical operation: Does the interaction between Slack and its connected applications meet the "active state" versus "non-active state" limitation of dependent claim 4? Proving this will require detailed evidence about the background processes and data-sharing architecture of the accused system.