IP Library Granted Patent US 11,803,370
Granted Patent B2
US 11,803,370 · App. 17/644,032 · Granted Oct 31, 2023

Configurable transaction status interface

Inventors: Tarundeep Batra (Fremont, CA); Lopa Mukherjee (San Mateo, CA); Himanshu Kapoor (Bangalore, IN)
Assignee: Salesforce, Inc.
G06F8/71G06F16/2379G06Q20/027
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,803,370
App. No.
17/644,032
Granted
Oct 31, 2023
Kind
B2
Abstract

In a cloud computing environment, a configurable transaction status interface of an enterprise computing platform enables application developers to customize applications efficiently. The configurable transaction status interface includes a global variable that is populated using a method for implementing a configurable status map that maps a transaction result to the global variable without having to customize the application. The configurable transaction status interface allows third party vendors of transaction gateways to use the configurable status map to map one or more of their gateway-specific transaction results to a generic status defined in the global variable. The vendors manage the configurable status map in their own namespace independently of the application with which they are interfacing.

Claims (41)

1. A method for configuring a status of a transaction processed in an enterprise computing platform, the method comprising:

defining a status variable for a transaction in an application namespace;

exposing an interface to enable a transaction entity, in a gateway namespace separate from the application namespace, to populate the status variable with a first status representing a result of processing the transaction in the gateway namespace; and

accessing the status variable populated with the first status in the application namespace, the first status based on a map of statuses defined in the application namespace to transaction results defined in the gateway namespace.

2. The method of claim 1 , wherein the enterprise computing platform is a multi-tenant database system, and wherein the transaction entity is a tenant of the multi-tenant database system.

3. The method of claim 1 , wherein the populating the status variable with the first status comprises defining a configurable status map to connect the status variable to the first status.

4. The method of claim 3 , wherein the map is stored within the gateway namespace.

5. The method of claim 4 , wherein the gateway namespace is specific to the transaction entity.

6. The method of claim 1 , wherein the gateway namespace is a first gateway namespace, and wherein the application namespace is associated with a plurality of gateway namespaces.

7. The method of claim 6 , wherein the first status is a gateway status of the transaction entity, and wherein the status variable is populated with a plurality of gateway statuses, each of the plurality of gateway statuses associated with one of the plurality of gateway namespaces.

8. The method of claim 7 , further comprising:

processing a transaction through a gateway process, the gateway process operating in the gateway namespace; and

storing a result code based on the processing the transaction.

9. The method of claim 8 , wherein the result code is the first status.

10. The method of claim 9 , further comprising:

providing a call containing the result code to the map; and

receiving, based on the call, the status variable populated with the first status.

11. The method of claim 10 , further comprising:

setting a transaction status of the transaction to the status variable; and

providing the transaction status to the application namespace.

12. A system for a computing platform having a configurable transaction status interface, the system comprising:

a processor capable of executing instructions in multiple namespaces of a computing platform; and

a memory storing instructions to cause the processor to perform operations comprising:

defining a status variable for a transaction in an application namespace;

exposing an interface to enable a transaction entity, in a gateway namespace separate from the application namespace, to populate the status variable with a first status representing a result of processing the transaction in the gateway namespace; and

accessing the status variable populated with the first status in the application namespace, the first status based on a map of statuses defined in the application namespace to transaction results defined in the gateway namespace.

13. The system of claim 12 , further comprising:

a multi-tenant database system, wherein the transaction entity is a tenant of the multi-tenant database system.

14. The system of claim 12 , wherein the populating the status variable with the first status comprises defining a configurable status map to connect the status variable to the first status.

15. The system of claim 14 , wherein the map is stored within the gateway namespace.

16. The system of claim 15 , wherein the gateway namespace is specific to the transaction entity.

17. The system of claim 12 , wherein the gateway namespace is a first gateway namespace, and wherein the application namespace is associated with a plurality of gateway namespaces.

18. The system of claim 17 , wherein the first status is a gateway status of the transaction entity, and wherein the status variable is populated with a plurality of gateway statuses, each of the plurality of gateway statuses associated with one of the plurality of gateway namespaces.

19. The system of claim 18 , wherein the operations further comprise:

processing a transaction through a gateway process, the gateway process operating in the gateway namespace; and

storing a result code based on the processing the transaction.

20. The system of claim 19 , wherein the result code is the first status, and wherein the operations further comprise:

providing a call containing the result code to the map;

receiving, based on the call, the status variable populated with the first status;

setting a transaction status of the transaction to the status variable; and

providing the transaction status to the application namespace.

Assignments (2)
CHANGE OF NAME Recorded Dec 18, 2024
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 069717/0638 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 23, 2022
From: BATRA, TARUNDEEP; MUKHERJEE, LOPA; KAPOOR, HIMANSHU
To: SALESFORCE.COM, INC.
Reel/Frame 059978/0518 →
Continuity (3)
Continuation 16856902 · Apr 23, 2020
Provisional Application 62922246 · Apr 26, 2019
Related Publication 20220276861A1 · Sep 1, 2022