Abstract: Techniques are disclosed for using a multi-tenant framework for microservices in a microservices-based application to handle tenant-specific circuit breaking. The microservices-based application can include at least one microservice that incorporates the multi-tenant framework. The multi-tenant framework includes software components configured to provide multi-tenant functionality for the microservice. A first microservice may receive an indication associated with a tenant that a second microservice is overloaded. The first microservice can then receive a request containing tenant context data at an interface. A first software component of the multi-tenant framework can extract the tenant context data from the request. The first microservice may determine whether the tenant context data corresponds to the tenant. The first microservice can then trigger a circuit breaker for the second microservice.

Abstract: Permissions on a resource hierarchy of a process are propagated. The resource hierarchy of the process is accessed. The resource hierarchy includes multiple nodes arranged in level and each of the nodes is associated with a separate resource from a plurality of resources. A permission for a user is propagate from a first node to one or more lower nodes arranged below the first node in the resource hierarchy. The user is enabled to interact with each resource associated with the first node and the one or more of the lower nodes based on the propagated permission.

Abstract: Techniques are disclosed for implementing a multi-tenant framework for microservices in a microservices-based application. A distributed computing system can execute a cluster on which the microservices-based application is hosted. The microservices-based application can include at least one microservice that incorporates the multi-tenant framework. The multi-tenant framework includes modules configured to provide multi-tenant functionality for the microservice. The microservice may receive a request containing tenant context data at an interface. A first module of the multi-tenant framework can extract the tenant context data from the request. In response to the request, the microservice may generate microservice data. A second module of the multi-tenant framework can use the extracted tenant context data to obtain a data store connection for the tenant. The microservice can use the data store connection to access the tenant's data store and store the microservice data.

Abstract: Techniques are disclosed for implementing a multi-tenant framework for microservices in a microservices-based application. A distributed computing system can execute a cluster on which the microservices-based application is hosted. The microservices-based application can include at least one microservice that incorporates the multi-tenant framework. The multi-tenant framework includes modules configured to provide multi-tenant functionality for the microservice. The microservice may receive a request containing tenant context data at an interface. A first module of the multi-tenant framework can extract the tenant context data from the request. In response to the request, the microservice may generate microservice data. A second module of the multi-tenant framework can use the extracted tenant context data to obtain a data store connection for the tenant. The microservice can use the data store connection to access the tenant's data store and store the microservice data.

Abstract: In accordance with an embodiment, described herein is a system and method for use with a cloud computing environment, for creating or updating tenant artifacts using microservices. A multi-tenant cloud service provides a loosely-coupled and distributed approach for consistently creating or updating tenant artifacts through the use of multiple independent microservice's lifecycle containers, each having their own requirements during the creation or update of a tenant instance. The development and packaging of lifecycle containers is simplified by managing the software code responsible for artifact creation or update within a microservice code repository. The system can use a deployment approach of loosely-coupled microservice lifecycle containers together with an infrastructure lifecycle service that coordinates tenant artifact creation/update across multiple microservices.

Abstract: In accordance with an embodiment, described herein is a system and method for use with a cloud computing environment, for creating or updating tenant artifacts using microservices. A multi-tenant cloud service provides a loosely-coupled and distributed approach for consistently creating or updating tenant artifacts through the use of multiple independent microservice's lifecycle containers, each having their own requirements during the creation or update of a tenant instance. The development and packaging of lifecycle containers is simplified by managing the software code responsible for artifact creation or update within a microservice code repository. The system can use a deployment approach of loosely-coupled microservice lifecycle containers together with an infrastructure lifecycle service that coordinates tenant artifact creation/update across multiple microservices.

Abstract: A process cloud services (PCS) system is integrated with an intelligence cloud service (ICS) based on converted PCS analytics data. The PCS system converts PCS analytics data into a format for the ICS resulting on converted PCS analytics data. The converted PCS analytics data is transferred from the PCS system to the ICS. The PCS system is integrated with the ICS based on the converted PCS analytics data received at the ICS.

Abstract: Permissions on a resource hierarchy of a process are propagated. The resource hierarchy of the process is accessed. The resource hierarchy includes multiple nodes arranged in level and each of the nodes is associated with a separate resource from a plurality of resources. A permission for a user is propagate from a first node to one or more lower nodes arranged below the first node in the resource hierarchy. The user is enabled to interact with each resource associated with the first node and the one or more of the lower nodes based on the propagated permission.

Abstract: An embodiment provides data driven role permissions. Computer executable instructions are received. The computer executable instructions define a role behavior with respect to a process based on a data condition. A role member user is provided different types of interactions with different instances of the process based on execution of the computer executable instructions defining the role behavior.

Abstract: A bridge is created between the process cloud services (PCS) and a target intelligence system that is outside of the PCS at least by: publishing Representational State Transfer (REST) Application Programming Interfaces (APIs) for use in a user interface of the target intelligence system that a user interacts with, wherein the user is a customer of the PCS; providing intelligence cloud service (ICS) tables for designing customer dash boards; and creating converted PCS analytics data that the target intelligence system is capable of processing by converting PCS analytics data from the PCS into a target intelligence system format. The bridge is used for communications between the PCS and the target intelligence system at least by: retrieving the converted PCS analytics data using the published REST APIs of the user interface of the target intelligence system; and creating the customer dash boards based on the ICS tables and the converted PCS analytics data.

Abstract: A bridge is created between the process cloud services (PCS) and a target intelligence system that is outside of the PCS at least by: publishing Representational State Transfer (REST) Application Programming Interfaces (APIs) for use in a user interface of the target intelligence system that a user interacts with, wherein the user is a customer of the PCS; providing intelligence cloud service (ICS) tables for designing customer dash boards; and creating converted PCS analytics data that the target intelligence system is capable of processing by converting PCS analytics data from the PCS into a target intelligence system format. The bridge is used for communications between the PCS and the target intelligence system at least by: retrieving the converted PCS analytics data using the published REST APIs of the user interface of the target intelligence system; and creating the customer dash boards based on the ICS tables and the converted PCS analytics data.

Abstract: Various embodiments provide for integrating process cloud services (PCS) with intelligence cloud service (ICS). PCS analytics data is obtained using one or more PCS analytics data export application programming interfaces (APIs). A semantic model is provided to a predefined ICS system. The PCS analytics data is transferred to an ICS integration service. The PCS analytics data is converted into a format for a target intelligence system. The converted PCS analytics data is transferred to a service for later distribution as star schema data, for use by Representational State Transfer (REST) Application Programming Interfaces (APIs). The PCS analytics data is transferred from the ICS integration service to the predefined ICS system, for use by the ICS integration service to integrate PCS with the ICS system.

Abstract: An embodiment provides data driven role permissions. Computer executable instructions are received. The computer executable instructions define a role behavior with respect to a process based on a data condition. A role member user is provided different types of interactions with different instances of the process based on execution of the computer executable instructions defining the role behavior.

Abstract: Various embodiments provide for integrating process cloud services (PCS) with intelligence cloud service (ICS). PCS analytics data is obtained using one or more PCS analytics data export application programming interfaces (APIs). A semantic model is provided to a predefined ICS system. The PCS analytics data is transferred to an ICS integration service. The PCS analytics data is converted into a format for a target intelligence system. The converted PCS analytics data is transferred to a service for later distribution as star schema data, for use by Representational State Transfer (REST) Application Programming Interfaces (APIs). The PCS analytics data is transferred from the ICS integration service to the predefined ICS system, for use by the ICS integration service to integrate PCS with the ICS system.

Abstract: Systems and methods are disclosed to receive an indication that a buyer has placed an item in a virtual shopping cart. One or more conversion shipping options associated with shipping options used to ship one or more previously purchased items purchased by the buyer may be determined. One or more non-conversion shipping options associated with shipping options presented to the buyer with one or more unpurchased items previously placed in a virtual shopping cart by the buyer but not purchased by the buyer may be determined. A plurality of conversion probabilities may be determined for a plurality of different shipping options for the item in the virtual shopping cart based at least in part on the conversion shipping options and the non-conversion shipping options. In some embodiments, a shipping option may be selected based on the plurality of different shipping options and the plurality of conversion probabilities.

Abstract: Computer-readable media, computer systems, and computing devices for facilitating presentation of search result items having varying prominence is provided. The method includes referencing a search result item to be presented within a search results page in response to a search query. Thereafter, a determination is made that a size prominence of the search result item is to be modified. Such a determination can be based on a result attribute(s) associated with the search result item and a result attribute(s) associated with other search result items within the search results page. The size of the search result item is adjusted in accordance with the determination that the size prominence of the search result item is to be modified.

Abstract: A first delivery estimate prediction model and a second delivery estimate prediction model are generated using historical data from an online marketplace. Transaction information related to an item listed in the online marketplace is determined. A first time estimate is calculated by applying the transaction information to the first delivery estimate prediction model. A second time estimate is calculated by applying the transaction information to the second delivery estimate prediction model. A delivery time estimate is generated based on the lowest of the first time estimate and the second time estimate.

Abstract: Computer-readable media, computer systems, and computing devices for facilitating presentation of search result items having varying prominence is provided. The method includes referencing a search result item to be presented within a search results page in response to a search query. Thereafter, a determination is made that a size prominence of the search result item is to be modified. Such a determination can be based on a result attribute(s) associated with the search result item and a result attribute(s) associated with other search result items within the search results page. The size of the search result item is adjusted in accordance with the determination that the size prominence of the search result item is to be modified.