Cloud Service Console for Batch Feed Publishing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Organizations face challenges with installing and maintaining software on their computer systems, including time-consuming installation processes, resource-intensive updates, compatibility issues, and the need to protect against viruses, leading to outdated software and compatibility problems.

Innovation Solution

The development of a cloud-based service console that provides an on-demand, web-based system for accessing data and applications, allowing agents to interact with object record information stored in a multitenant database, reducing the need for local software installations and enhancing compatibility through a user-friendly interface that streamlines workflows and reduces click counts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software is installed on organization's computer systems, then the organization can use the software to meet computing needs, but the installation and maintenance process requires significant time commitments and resources

Engineering Contradiction:
Improvesoftware functionalityVSAvoidinstallation and maintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces a cloud-based service console as an intermediary between the organization and the software functionality. Instead of installing software locally on multiple computers, the console provides access to software capabilities through a centralized web-based interface, eliminating the need for local installation and maintenance while preserving full functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a virtual copy of the software environment in the cloud, accessible through a web browser. This allows users to access software functionality without having the actual software installed on their local machines, effectively copying the software experience to a remote location that can be accessed from any device.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If software is installed on multiple computer systems, then the organization can access the software across different devices, but each installation needs to be separately monitored, upgraded, and maintained

Engineering Contradiction:
Improvesoftware accessibilityVSAvoidsoftware management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service console provides a universal access point that works across all devices and operating systems. Instead of installing device-specific software on each computer, the console offers a single web-based interface that can be accessed from any device with a browser, eliminating the need for separate installations and simplifying management.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The console acts as a centralized intermediary that manages all software operations in one location. Administrators can monitor, upgrade, and maintain software through the console without needing to access individual computer systems, reducing management complexity from multiple distributed installations to a single centralized system.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If software is frequently upgraded to meet organizational needs, then the organization can use updated features and improvements, but compatibility problems arise with different versions across computer systems

Engineering Contradiction:
Improvesoftware update capabilityVSAvoidsoftware compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The console serves as a controlled intermediary environment where software updates are first tested and validated before being made available to users. This centralized control ensures that all users access the same verified version of the software, eliminating compatibility issues that arise from having different versions distributed across multiple local installations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary testing and validation of software updates within the console environment before deploying them to users. This advance verification ensures that updates are compatible and functional before widespread distribution, preventing the compatibility problems that would otherwise arise from deploying untested versions across multiple systems.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If software is installed on in-house computer systems, then the organization has control over the software, but significant resources are required for protection against viruses and other malevolent code

Engineering Contradiction:
Improvesoftware controlVSAvoidmaintenance resources
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The console acts as a secure intermediary between users and software, providing a controlled environment that inherently protects against viruses and malevolent code. Users access software through the console's security framework rather than having it installed locally, eliminating the need for separate antivirus protection on each machine while maintaining full control over software distribution and security policies.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10606436B2Computer implemented methods and apparatus for composing and batch publishing feed items in a feed-based interaction context
Publication Date: 2020.03.31 SALESFORCE INC
  • US10606436B2 patent drawing
  • US10606436B2 patent drawing
  • US10606436B2 patent drawing

AI summary

Disclosed are methods, apparatus, systems, and computer-readable storage media for composing and batch publishing feed items in a user interface in a feed-based interaction context. In some implementations, a computing device provides a first prompt for display in a first user interface component, which is configured to display unpublished feed items. The computing device receives, at the first prompt, first feed item data for a first feed item. Responsive to a request to compose a second feed item, the computing device displays in the first user interface component a second prompt for second feed item data without publishing the first feed item. The computing device receives, at the second prompt, second feed item data for a second feed item of a first record, the first and second feed items being related to the first record.