Abstract: A remote network management platform may include a provider computing instance, a recipient computing instance, and a neutral computing instance including persistent storage that defines a table and fields therein, and where the neutral computing instance is configured to: (i) receive, by way of a first software interface, data from the provider computing instance, where the data is an update to a field within the table; (ii) validate that the provider computing instance is permitted to update the field; (iii) write a representation of the data to the field; (iv) receive, by way of a second software interface, a request from the recipient computing instance for the data; (v) validate that the recipient computing instance is permitted to access the field; and (vi) transmit the data as stored in the field to the recipient computing instance.

Abstract: In accordance with the present approach, an edition-managing software application may be provided to query registries of client devices for edition information associated with a target software package. When retrieved, the edition information may then be stored in a universal storage location from which the edition-managing software application may generate an edition report that provides an accurate representation of actual installations of each edition of the target software package on the client devices. Further, in accordance with the present approach, a usage-tracking software program may be provided to retrieve a last used date of a target software package on client devices. If the last used date is beyond a threshold time period for the client devices, the enterprise may determine that the target software package is underutilized compared to a desired usage. Then, the target software package may be uninstalled from the client devices and installed on other client devices.

Abstract: The present disclosure relates generally to outputting purchase outputs based on received voice input by a client device. The purchase outputs may include an invoice, a purchase order, a request for funds associated with a purchase of one or more items, and the like. In general, the voice input received by the client invoice is used to generate a purchase request input that includes at least one product that an employee wants to purchase. One or more candidate items are generated based on the purchase request input, which may be sent to a user and/or manager for approval before generating a purchase output based on the candidate items.

Abstract: A software model specification for a software package can be associated with representation of a software downgrade definition. The software model specification can include a publisher of the software package, an application title of the software package, and the version of the software package. One or more entitlements for the software package can be obtained. Based on the software downgrade definition being associated with the software model specification, the software downgrade definition can be associated with the entitlement(s). Compliance of the installations of the software package with the entitlement(s) can be calculated, where the software downgrade definition can cause each of the entitlement(s) to be applicable to the installations of the version of the software package or one or more earlier versions of the software package.

Abstract: An example embodiment may include a central computational instance, as well as a plurality of computational instances that are configured to execute a software module. The central instance may be configured to deliver updates to configuration data for the software module at a plurality of release times. The embodiment may involve a computing device disposed within a particular instance of the plurality of instances transmitting a request for an out-of-band delivery of the configuration data, where the out-of-band delivery is to be made during a time other than any of the release times, receiving the configuration data from source field(s) of a central database of the central instance, and writing the configuration data to destination field(s) of a local database of the particular instance. The embodiment may also involve executing the software module according to the configuration data stored in the destination field(s).

Abstract: A system may be configured to: provide, to a client device of a managed network, a representation of a graphical user interface (GUI) that displays a nominal configuration of a computing device on which a particular software application is deployed or is a candidate for deployment, where licensing information in a database of the system respectively indicates a first license rights consumption for the particular software application; receive, by way of the GUI and from the client device, an indication of a proposed configuration of the computing device; in response to receiving the indication of the proposed configuration, determine a second license rights consumption that results from deploying the particular software application in accordance with the proposed configuration; and provide, to the client device, an updated representation of the GUI that displays a graphical indication of the second license rights consumption.

Abstract: A system may include a database and server device(s) disposed within a remote network management platform. The database may contain established normalization information for a plurality of software applications installed on computing devices of a managed network.

Abstract: A software model specification for a software package can be associated with representation of a software downgrade definition. The software model specification can include a publisher of the software package, an application title of the software package, and the version of the software package. One or more entitlements for the software package can be obtained. Based on the software downgrade definition being associated with the software model specification, the software downgrade definition can be associated with the entitlement(s). Compliance of the installations of the software package with the entitlement(s) can be calculated, where the software downgrade definition can cause each of the entitlement(s) to be applicable to the installations of the version of the software package or one or more earlier versions of the software package.

Abstract: The present disclosure relates generally to outputting purchase outputs based on received voice input by a client device. The purchase outputs may include an invoice, a purchase order, a request for funds associated with a purchase of one or more items, and the like. In general, the voice input received by the client invoice is used to generate a purchase request input that includes at least one product that an employee wants to purchase. One or more candidate items are generated based on the purchase request input, which may be sent to a user and/or manager for approval before generating a purchase output based on the candidate items.

Abstract: An example embodiment may include a central computational instance, as well as a plurality of computational instances that are configured to execute a software module. The central instance may be configured to deliver updates to configuration data for the software module at a plurality of release times. The embodiment may involve a computing device disposed within a particular instance of the plurality of instances transmitting a request for an out-of-band delivery of the configuration data, where the out-of-band delivery is to be made during a time other than any of the release times, receiving the configuration data from source field(s) of a central database of the central instance, and writing the configuration data to destination field(s) of a local database of the particular instance. The embodiment may also involve executing the software module according to the configuration data stored in the destination field(s).

Abstract: A software model specification for a software package can be associated with representation of a software downgrade definition. The software model specification can include a publisher of the software package, an application title of the software package, and the version of the software package. One or more entitlements for the software package can be obtained. Based on the software downgrade definition being associated with the software model specification, the software downgrade definition can be associated with the entitlement(s). Compliance of the installations of the software package with the entitlement(s) can be calculated, where the software downgrade definition can cause each of the entitlement(s) to be applicable to the installations of the version of the software package or one or more earlier versions of the software package.

Abstract: A software model specification for a software package can be associated with representation of a software downgrade definition. The software model specification can include a publisher of the software package, an application title of the software package, and the version of the software package. One or more entitlements for the software package can be obtained. Based on the software downgrade definition being associated with the software model specification, the software downgrade definition can be associated with the entitlement(s). Compliance of the installations of the software package with the entitlement(s) can be calculated, where the software downgrade definition can cause each of the entitlement(s) to be applicable to the installations of the version of the software package or one or more earlier versions of the software package.

Abstract: A remote network management platform may include a provider computing instance, a recipient computing instance, and a neutral computing instance including persistent storage that defines a table and fields therein, and where the neutral computing instance is configured to: (i) receive, by way of a first software interface, data from the provider computing instance, where the data is an update to a field within the table; (ii) validate that the provider computing instance is permitted to update the field; (iii) write a representation of the data to the field; (iv) receive, by way of a second software interface, a request from the recipient computing instance for the data; (v) validate that the recipient computing instance is permitted to access the field; and (vi) transmit the data as stored in the field to the recipient computing instance.

Abstract: An example embodiment may include a central computational instance, as well as a plurality of computational instances that are configured to execute a software module. The central instance may be configured to deliver updates to configuration data for the software module at a plurality of release times. The embodiment may involve a computing device disposed within a particular instance of the plurality of instances transmitting a request for an out-of-band delivery of the configuration data, where the out-of-band delivery is to be made during a time other than any of the release times, receiving the configuration data from source field(s) of a central database of the central instance, and writing the configuration data to destination field(s) of a local database of the particular instance. The embodiment may also involve executing the software module according to the configuration data stored in the destination field(s).

Abstract: In accordance with the present approach, an edition-managing software application may be provided to query registries of client devices for edition information associated with a target software package. When retrieved, the edition information may then be stored in a universal storage location from which the edition-managing software application may generate an edition report that provides an accurate representation of actual installations of each edition of the target software package on the client devices. Further, in accordance with the present approach, a usage-tracking software program may be provided to retrieve a last used date of a target software package on client devices. If the last used date is beyond a threshold time period for the client devices, the enterprise may determine that the target software package is underutilized compared to a desired usage. Then, the target software package may be uninstalled from the client devices and installed on other client devices.

Abstract: A system may include a database and server device(s) disposed within a remote network management platform. The database may contain established normalization information for a plurality of software applications installed on computing devices of a managed network.

Abstract: A system may include a database and server device(s) disposed within a remote network management platform. The database may contain established normalization information for a plurality of software applications installed on computing devices of a managed network.

Abstract: An example embodiment may include a central computational instance, as well as a plurality of computational instances that are configured to execute a software module. The central instance may be configured to deliver updates to configuration data for the software module at a plurality of release times. The embodiment may involve a computing device disposed within a particular instance of the plurality of instances transmitting a request for an out-of-band delivery of the configuration data, where the out-of-band delivery is to be made during a time other than any of the release times, receiving the configuration data from source field(s) of a central database of the central instance, and writing the configuration data to destination field(s) of a local database of the particular instance. The embodiment may also involve executing the software module according to the configuration data stored in the destination field(s).

Abstract: A system may be configured to: provide, to a client device of a managed network, a representation of a graphical user interface (GUI) that displays a nominal configuration of a computing device on which a particular software application is deployed or is a candidate for deployment, where licensing information in a database of the system respectively indicates a first license rights consumption for the particular software application; receive, by way of the GUI and from the client device, an indication of a proposed configuration of the computing device; in response to receiving the indication of the proposed configuration, determine a second license rights consumption that results from deploying the particular software application in accordance with the proposed configuration; and provide, to the client device, an updated representation of the GUI that displays a graphical indication of the second license rights consumption.

Abstract: A system may include a database and server device(s) disposed within a remote network management platform. The database may contain established normalization information for a plurality of software applications installed on computing devices of a managed network.