Abstract: Systems and methods are disclosed to implement a machine learned system to determine the comparative relationship between item package quantity (IPQ) information indicated in two item descriptions. In embodiments, the system employs a neural network that includes a token encoding layer, an attribute summarizing layer, and a comparison layer. The token encoding layer accepts an item description as a token sequence and encodes the tokens with token attributes that are relevant to IPQ extraction. The attribute summarizing layer uses a convolutional neural network to generate a set of fixed-size feature vectors for each encoded token sequence. All feature vectors for both item descriptions are then provided to the comparison layer to generate the IPQ comparison result. Advantageously, the disclosed neural network model can be trained to make accurate predictions about the IPQ relationship of the two item descriptions using a small set of token-level attributes as input signals.

Abstract: Methods, systems, and computer-storage media having computer-usable instructions embodied thereon for identifying related entities are provided. One or more entities may be identified from a search query. The one or more entities may include any identifiable term having related information associated therewith. An entity store may be referenced to identify one or more related entities related to the entity. The one or more related entities, along with their relationship(s) to the entity (and one another, perhaps) may then be ranked and displayed to a user.

Abstract: Methods, systems, and computer-storage media having computer-usable instructions embodied thereon for identifying related entities are provided. One or more entities may be identified from a search query. The one or more entities may include any identifiable term having related information associated therewith. An entity store may be referenced to identify one or more related entities related to the entity. The one or more related entities, along with their relationship(s) to the entity (and one another, perhaps) may then be ranked and displayed to a user.

Abstract: Methods, systems, and computer-storage media having computer-usable instructions embodied thereon for identifying related entities are provided. One or more entities may be identified from a search query. The one or more entities may include any identifiable term having related information associated therewith. An entity store may be referenced to identify one or more related entities related to the entity. The one or more related entities, along with their relationship(s) to the entity (and one another, perhaps) may then be ranked and displayed to a user.

Abstract: Methods and systems authenticate and authorize an extranet client to a secure intranet business application with a perimeter network topology, where connections to the secure intranet business application from outside the secure intranet are not permitted. A perimeter network proxy is authenticated within the secure intranet. The perimeter network proxy corresponds to an authenticated extranet client. If the perimeter network proxy is authenticated, information on an intranet business application client is acquired and used to create a session with the intranet business application. The intranet business application client corresponds to the extranet client, and the extranet client uses the session to submit requests to the intranet business application.

Abstract: Managed application programming interfaces (APIs), schemas and procedures receives a managed API call from an application, and maps the managed API call to an unmanaged API call. Managed data types and managed data objects of the managed API call are mapped to corresponding unmanaged data types and data objects. A request resulting from the unmanaged API call is dispatched to and interpreted by an unmanaged programming language interpreter, which executes the request in an unmanaged programming language. An unmanaged response to the request is mapped to a corresponding managed response, which is provided to the managed application.

Abstract: Methods and systems access managed Internet protocol context information by receiving an unmanaged Internet protocol context class call from an Internet application written in an unmanaged programming language. An unmanaged Internet protocol context class, which is written in an unmanaged programming language, is instantiated in response to the call. Interaction with a managed Internet protocol context class results in receiving Internet protocol context information. The managed Internet protocol context class corresponds to the unmanaged Internet protocol context class.

Abstract: Methods and systems authenticate and authorize an extranet client to a secure intranet business application with a perimeter network topology, where connections to the secure intranet business application from outside the secure intranet are not permitted. A perimeter network proxy is authenticated within the secure intranet. The perimeter network proxy corresponds to an authenticated extranet client. If the perimeter network proxy is authenticated, information on an intranet business application client is acquired and used to create a session with the intranet business application. The intranet business application client corresponds to the extranet client, and the extranet client uses the session to submit requests to the intranet business application.

Abstract: Managed application programming interfaces (APIs), schemas and procedures receives a managed API call from an application, and maps the managed API call to an unmanaged API call. Managed data types and managed data objects of the managed API call are mapped to corresponding unmanaged data types and data objects. A request resulting from the unmanaged API call is dispatched to and interpreted by an unmanaged programming language interpreter, which executes the request in an unmanaged programming language. An unmanaged response to the request is mapped to a corresponding managed response, which is provided to the managed application.

Abstract: Methods and systems access managed Internet protocol context information by receiving an unmanaged Internet protocol context class call from an Internet application written in an unmanaged programming language. An unmanaged Internet protocol context class, which is written in an unmanaged programming language, is instantiated in response to the call. Interaction with a managed Internet protocol context class results in receiving Internet protocol context information. The managed Internet protocol context class corresponds to the unmanaged Internet protocol context class.

Abstract: Creating a web site using a site definition application and an additional application is disclosed. Metadata in the additional application may store page definitions and the site definition application may be configured such that the page definitions are supplied by the additional application.

Abstract: In a method of customizing a software-implemented business process on a mobile computing device, subscriptions are defined to business solutions entities that are defined by metadata. Next, the entities identified by the subscriptions are uploaded to the mobile computing device.

Abstract: In a method of managing a synch operation during which business solutions entities are loaded into a mobile data store of a mobile computing device from a central data storage system, subscriptions are defined that identify entities to be loaded into the mobile data store during a synch operation. Next, a remaining data storage capacity of the mobile data store and a subscriptions data quantity corresponding to an amount of data space required to store the entities identified by the subscriptions are estimated. Finally, the subscriptions data quantity is compared to the remaining data storage capacity.

Abstract: In a method of customizing a software-implemented business process on a mobile computing device, customized metadata defining customizations of the business process are provided. Next, the metadata is deployed to the mobile computing device and stored in a data store of the mobile computing device. The customizations defined by the metadata are then applied to the software-implemented business process.