Abstract: Generating a token for tracking a state of communications with multiple external services. Data is caused to be acquired from external services as a result of interpreting a communication from a client. The causing of the data to be acquired comprises causing a request to be issued for data from a first external service and receiving a response from the first external service. The response from the first external service includes at least a token associated with the first external service. In response to receiving the response from the first external service, an aggregate token is generated that includes the token associated with the first external service and a status of the request to the first external service. The aggregate token is caused to be sent to the client and is interpretable to inform the computer system of the status of the request to the first external service.

Abstract: A client device includes a processor and memory. An operating system and a client application are executed by the processor and memory. The client application is configured to determine first and second coordinated universal time (UTC) time intervals for a first non-UTC time interval associated with a first event type and a second non-UTC time interval associated with the first event type; generate a single request for the remote activity feed server to aggregate corresponding events during the first UTC time interval and the second UTC time interval; and send the single request via a network interface to the remote activity feed server.

Abstract: Described herein are various technologies pertaining an extensible, cloud-based service for creating and executing applications (e.g., business or industry-specific workflows). A user knowledgeable about a particular field can utilize a client-hosted design studio or a web-based portal to create an application (“app”) (e.g., data transform) relevant to the particular field. The system thus enables users to build mobile applications across platforms without having to write computer code to communicate with backend services such as data sources and/or workflow management systems.

Abstract: Sharing a bundle. A method includes identifying a bundle defined by a first user. The bundle includes a number of portions. One or more portions are configured to provide data from a data source. The method further includes identifying within the bundle one or more portions of the bundle that can be changed when the bundle is consumed by other users. The method further includes modifying the identified portions before the bundle is consumed by other users.

Abstract: Autocompleting into an invite box for purposes of sharing an executable computing resource such as an application or portion thereof. However, the autocomplete is populated with potential sharees of multiple tenants or with identities that are not registered with the tenant directory of the user. Thus, potentially any potentially sharee worldwide may be populated within the list of potential sharees. As the desired potential sharee comes into view, that potential sharee may be selected, and added to a list of one or more selected sharees. At some point, a control may be selected to allow the executable computing resource to be shared with the selected sharees within the list.

Abstract: Generating a token for tracking a state of communications with multiple external services. Data is caused to be acquired from external services as a result of interpreting a communication from a client. The causing of the data to be acquired comprises causing a request to be issued for data from a first external service and receiving a response from the first external service. The response from the first external service includes at least a token associated with the first external service. In response to receiving the response from the first external service, an aggregate token is generated that includes the token associated with the first external service and a status of the request to the first external service. The aggregate token is caused to be sent to the client and is interpretable to inform the computer system of the status of the request to the first external service.

Abstract: Securely storing assets in a cloud computer storage service. Preparation to store assets for a user may comprise determining a location to store the assets, generating a write access signature, and sending the determined location and the signature to the user. A request is received from the user to store the assets. Such a request includes the assets, the location, and the signature. In response to receiving the request, a determination is made regarding the write access signature whether the request should be honored. When the request is honored, the assets are stored in the determined location and the write access signature is invalidated. Upon subsequent user requests to access the assets, short-term read access signatures are generated and provided to the user. The assets are written once per generated write access signature and reads are to be performed close in time to when short-term read access signatures are requested.

Abstract: Sharing a bundle. A method includes identifying a bundle defined by a first user. The bundle includes a number of portions. One or more portions are configured to provide data from a data source. The method further includes identifying within the bundle one or more portions of the bundle that can be changed when the bundle is consumed by other users. The method further includes modifying the identified portions before the bundle is consumed by other users.

Abstract: A client device includes a processor and memory. An operating system and a client application are executed by the processor and memory. The client application is configured to determine first and second coordinated universal time (UTC) time intervals for a first non-UTC time interval associated with a first event type and a second non-UTC time interval associated with the first event type; generate a single request for the remote activity feed server to aggregate corresponding events during the first UTC time interval and the second UTC time interval; and send the single request via a network interface to the remote activity feed server.

Abstract: Autocompleting into an invite box for purposes of sharing an executable computing resource such as an application or portion thereof. However, the autocomplete is populated with potential sharees of multiple tenants or with identities that are not registered with the tenant directory of the user. Thus, potentially any potentially sharee worldwide may be populated within the list of potential sharees. As the desired potential sharee comes into view, that potential sharee may be selected, and added to a list of one or more selected sharees. At some point, a control may be selected to allow the executable computing resource to be shared with the selected sharees within the list.

Abstract: Described herein are various technologies pertaining an extensible, cloud-based service for creating and executing applications (e.g., business or industry-specific workflows). A user knowledgeable about a particular field can utilize a client-hosted design studio or a web-based portal to create an application (“app”) (e.g., data transform) relevant to the particular field. The system thus enables users to build mobile applications across platforms without having to write computer code to communicate with backend services such as data sources and/or workflow management systems.