Salesforce Com, Inc.

Salesforce, Inc.

Steven deRochemont

Michael Starukhin

Daryn Cox

Cassandra Funk

Richard Farah

Osvaldo Rene Canel Lopez

Susan S Levine

Michael Dandy

Vadim Shmah

Amanda Hatker

Aspects of the disclosure described herein provide for a streamlined system for developing an order fulfillment process. The system may include a stateless web resource application programming interface (API) supported by a server, which may be configured as an endpoint to receive order requests (e.g., via an e-commerce website) and generate an instance of a complex object based on the order request. The instance of the complex object may be generated according to an invocable action configured at the system and may include one or more nested data types corresponding to order parameters indicated by the order request. The instance of the complex object may be processed according to fulfillment rules to generate a response to the order request. The response to the order request may include an identification of an order fulfillment center, a fulfillment order, etc.

Processing fulfillment using stateless APIs and complex classes

Methods, systems, and devices supporting data storage are described. A database system may store order information for an organization. This order information may span multiple steps of an order lifecycle, including order creation, order changes, order fulfillment, etc. To efficiently store order information for low-latency querying and data consistency, the database system may implement order summaries. For example, a database server may receive a new order data object associated with an order identifier and may create a corresponding order summary data object. If the database system receives any additional data objects associated with the same order identifier, the database server may update the order summary data object based on the additional data objects. If the database system receives a query for information related to the order, the system may retrieve queried values directly from the order summary data object, rather than aggregating data on-the-fly across multiple underlying data objects.

Data object aggregation to manage an order summary

Disclosed herein are system, method, and device embodiments for implementing an order management graphical user interface (GUI). An application service may monitor completion of a workflow associated with a purchase order, generate a GUI layout associated with the purchase order, the GUI layout including a graphical workflow frame dimensioned to present a predicted amount of graphical representations associated with the workflow, and a detailed information frame. Further, the application service may generate a first graphical representation representing the purchase order and the order status, generate a graphical area corresponding to an operation of the plurality of operations for providing the product to the customer, determine performance of the operation based on the monitoring, generate a second graphical representation within the graphical area based on the performance of the operation, and generate a connection item between the first graphical representation and the second graphical representation.

Order management user interface

Display screen or portion thereof with icon

Display screen or portion thereof with a group of icons

Display screen or portion thereof with graphical user interface

Growing community of inventors

Lighthouse Point, FL, United States of America

Steven deRochemont