Abstract: A method implemented in a software as a service (SaaS) management platform, includes: accessing a respective plurality of SaaS applications, to obtain customer event data from SaaS applications to which customers subscribe; periodically aggregating the event data for each SaaS application over a moving time window to generate customer usage data indicating use of SaaS application features; anonymizing the customer usage data for the SaaS applications across the plurality of customers of the SMP to generate anonymized usage data; responsive to a request from a client device, reading the anonymized usage data for a given SaaS application, defining a cohort of anonymized customers, generating benchmarks defining median use of respective features of the given SaaS application by the anonymized customers, and returning the benchmarks to the client device.

Abstract: A software as a service (SaaS) management platform, includes: a plurality of connectors configured to access a respective plurality of SaaS applications, wherein said connectors are used to obtain customer event data from SaaS applications to which customers subscribe; an aggregation job that periodically aggregates the event data for each SaaS application over a moving time window to generate customer usage data indicating use of SaaS application features; a benchmark background job that anonymizes the customer usage data for the SaaS applications across the plurality of customers of the SMP to generate anonymized usage data; a benchmark backend that, responsive to a request from a client device, reads the anonymized usage data for a given SaaS application, defines a cohort of anonymized customers, generates benchmarks defining median use of respective features of the given SaaS application by the anonymized customers, and returns the benchmarks to the client device.

Abstract: A non-transitory computer-readable medium having program instructions for a method implemented in a software as a service (SaaS) management platform, includes: accessing a respective plurality of SaaS applications, to obtain customer event data from SaaS applications to which customers subscribe; periodically aggregating the event data for each SaaS application over a moving time window to generate customer usage data indicating use of SaaS application features; anonymizing the customer usage data for the SaaS applications across the plurality of customers of the SMP to generate anonymized usage data; responsive to a request from a client device, reading the anonymized usage data for a given SaaS application, defining a cohort of anonymized customers, generating benchmarks defining median use of respective features of the given SaaS application by the anonymized customers, and returning the benchmarks to the client device.

Abstract: A software as a service (SaaS) management platform, includes: an uploader process for receiving a plurality of contract files relating to purchases of a SaaS application; parsing logic that identifies terms in the plurality of contract files; normalization logic for assigning a normalization SKU to respective contract files based on the terms identified in the respective contract files; a background process that generates anonymized contract data by storing the terms of each contract file in association with the normalization SKU assigned to the contract file in an anonymous manner; a backend process that, responsive to a request from a client device, accesses the anonymized contract data to generate a distribution of terms of the anonymized contract data, generates benchmark data identifying an approximate location of terms of a given customer's contract file within the distribution, and returns the benchmark data to the client device for rendering through a user interface.

Abstract: A method implemented in a software as a service (SaaS) management platform, includes: receiving a plurality of contract files relating to purchases of a SaaS application; identifying terms in the plurality of contract files; assigning a normalization SKU to respective contract files based on the terms identified in the respective contract files; generating anonymized contract data by storing the terms of each contract file in association with the normalization SKU assigned to the contract file in an anonymous manner; responsive to a request from a client device, accessing the anonymized contract data to generate a distribution of terms of the anonymized contract data, generating benchmark data identifying an approximate location of terms of a given customer's contract file within the distribution, and returning the benchmark data to the client device for rendering through a user interface.

Abstract: The automated validation of one or more test cases in a validation pass. The validation pass is enabled using a plurality of scenario runners, which are executable components that respond to instructions to run one or more scenarios of a validation pass by beginning to run through such scenarios during the validation pass. The validation pass may be associated with a maximum time such that upper limits on how long the scenario runners may run is set. This likewise limits the time it takes to validate the results of the scenario. The scenario runners provide events that occur during the running of their respective scenarios into an event collector. The events of the validation pass may then be evaluated against one or more test cases to determine whether or not the events have a state indicative of a success or failure of each test cases.

Abstract: Techniques for identity management for permissions are described. According to various embodiments, a user establishes a communication relationship with another user, referred to herein as a “contact.” According to various embodiments, the contact is associated with multiple identities. Accordingly, embodiments discussed herein enable a primary identity to be specified such that permissions for the primary identity are enforced for interactions with the contact. Further, techniques discussed herein enable a primary identity to be updated based on a change in identity state of a contact.

Abstract: The automated validation of one or more test cases in a validation pass. The validation pass is enabled using a plurality of scenario runners, which are executable components that respond to instructions to run one or more scenarios of a validation pass by beginning to run through such scenarios during the validation pass. The validation pass may be associated with a maximum time such that upper limits on how long the scenario runners may run is set. This likewise limits the time it takes to validate the results of the scenario. The scenario runners provide events that occur during the running of their respective scenarios into an event collector. The events of the validation pass may then be evaluated against one or more test cases to determine whether or not the events have a state indicative of a success or failure of each test cases.

Abstract: Techniques for identity management for permissions are described. According to various embodiments, a user establishes a communication relationship with another user, referred to herein as a “contact.” According to various embodiments, the contact is associated with multiple identities. Accordingly, embodiments discussed herein enable a primary identity to be specified such that permissions for the primary identity are enforced for interactions with the contact. Further, techniques discussed herein enable a primary identity to be updated based on a change in identity state of a contact.

Abstract: In one embodiment, a client-opaque synchronization state reference 612 may increase the scalability of a synchronization server 120. The synchronization server 120 may create a synchronization state reference 612. The synchronization server 120 may send the synchronization state reference 612 to a client device 110. The synchronization server 120 may receive a synchronization request 600 with the synchronization state reference 612 from the client device 110. The synchronization server 120 may determine a synchronization update 706 based on the synchronization state reference 610.

Abstract: Described is a pipeline for handling notification messages sent to a mobile messaging message (e.g., SMS or SMTP) recipient, and handling a reply to that notification message, including correlating the notification message with the reply. An engine receives a notification message, and for a notification message to which a reply is possible, maintains state data for use in correlating a received reply with the notification message. The state data includes metadata that indicates that text or code data is expected in any reply. For a reply providing code data, the engine calls a selected URL corresponding to the code. To facilitate message delivery, the engine may format the notification message, including shortening a URL of the message, and/or splitting a longer notification message into shorter notification messages.

Abstract: Tasks can be developed and maintained with synchronous code while concurrently being asynchronously executed, e.g., during time consuming operations. The tasks need not include asynchronous flow callbacks within the task framework. The callbacks can be transparently incorporated within the execution flow utilizing a callback wrapper(s) which transparently maintains and manages the necessary callbacks for asynchronous execution of the tasks. Thus a generic solution can be easily and effectively implemented for, e.g., production/request work item processing, that can be applied to both backend services and/or client software.

Abstract: Described is a pipeline for handling notification messages sent to a mobile messaging message (e.g., SMS or SMTP) recipient, and handling a reply to that notification message, including correlating the notification message with the reply. An engine receives a notification message, and for a notification message to which a reply is possible, maintains state data for use in correlating a received reply with the notification message. The state data includes metadata that indicates that text or code data is expected in any reply. For a reply providing code data, the engine calls a selected URL corresponding to the code. To facilitate message delivery, the engine may format the notification message, including shortening a URL of the message, and/or splitting a longer notification message into shorter notification messages.

Abstract: Described is a notifications platform that routes notifications to endpoints of recipients, corresponding to email, instant messaging, text messaging, telephones, social networks, blogs and/or the like. A publisher of a notification designates the recipients, while preference data of each recipient determines whether that publisher is able to send to that recipient, and if so, to which endpoints. The notification may be modified via one or more templates to be appropriate for a locale of the recipient, as well as appropriately formatted for the endpoint, which may also be locale-specific.

Abstract: A strategy is described for forwarding content accessed using a first device to a second device. For instance, the first device can comprise a personal computer and the second device can comprise a mobile telephone. The strategy employs general purpose content-forwarding (CF) functionality. Different providers of content can rely on the same general purpose CF functionality to forward content to the second device, without requiring time-intensive and cumbersome manual modification of the CF functionality for each application.

Abstract: A strategy is described for forwarding content accessed using a first device to a second device. For instance, the first device can comprise a personal computer and the second device can comprise a mobile telephone. The strategy employs general purpose content-forwarding (CF) functionality. Different providers of content can rely on the same general purpose CF functionality to forward content to the second device, without requiring time-intensive and cumbersome manual modification of the CF functionality for each application.