Abstract: Techniques for generating application interfaces based on semantic-level data are described herein. Application developers may semantically define an application flow. Based on the definition, a system may identify a template of a multipage navigable interface that is compatible with the flow. If multiple templates are compatible, then a template may be recommended or automatically selected based on the semantic information provided by the developer. The system may generate, based on the template and the semantic definition, a multipage navigable interface. The template may encapsulate some design and functional elements in a manner that is independent of the semantic definition.

Abstract: Techniques for component-based software engineering, and more particularly, to techniques for enhancing component based development systems by making components self-aware with respect to the applications that they may be consumed in or other peer components within the applications. An exemplary technique includes determining an addition of one or more components to an interface of an application; identifying an asset definition within metadata of a component of the one or more components added to the interface of the application, where the asset definition provides self-wiring or self-configuring instructions for an asset that needs to be created for the component within a predefined scope when the component is added to the interface; and creating the asset for the component based on the asset definition.

Abstract: Techniques for generating application interfaces based on semantic-level data are described herein. Application developers may semantically define an application flow. Based on the definition, a system may identify a template of a multipage navigable interface that is compatible with the flow. If multiple templates are compatible, then a template may be recommended or automatically selected based on the semantic information provided by the developer. The system may generate, based on the template and the semantic definition, a multipage navigable interface. The template may encapsulate some design and functional elements in a manner that is independent of the semantic definition.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: Techniques for component-based software engineering, and more particularly, to techniques for enhancing component based development systems by making components self-aware with respect to the applications that they may be consumed in or other peer components within the applications. An exemplary technique includes determining an addition of one or more components to an interface of an application; identifying an asset definition within metadata of a component of the one or more components added to the interface of the application, where the asset definition provides self-wiring or self-configuring instructions for an asset that needs to be created for the component within a predefined scope when the component is added to the interface; and creating the asset for the component based on the asset definition.

Abstract: Techniques for component-based software engineering, and more particularly, to techniques for enhancing component based development systems by making components self-aware with respect to the applications that they may be consumed in or other peer components within the applications. An exemplary technique includes determining an addition of one or more components to an interface of an application; identifying an asset definition within metadata of a component of the one or more components added to the interface of the application, where the asset definition provides self-wiring or self-configuring instructions for an asset that needs to be created for the component within a predefined scope when the component is added to the interface; and creating the asset for the component based on the asset definition.

Abstract: Systems and methods are provided for managing and tracking process pipelines and other flows in a way that reduces the requirement for a central controlling process to manage every step of the associated pipeline flow and the state associated with each running instance. Job information and pipeline state are tracked by each worker involved in the pipeline. This enables some key capabilities within these process pipelines such as dynamic process re-writing and cross security domain job execution.

Abstract: Techniques for component-based software engineering, and more particularly, to techniques for enhancing component based development systems by making components self-aware with respect to the applications that they may be consumed in or other peer components within the applications. An exemplary technique includes determining an addition of one or more components to an interface of an application; identifying an asset definition within metadata of a component of the one or more components added to the interface of the application, where the asset definition provides self-wiring or self-configuring instructions for an asset that needs to be created for the component within a predefined scope when the component is added to the interface; and creating the asset for the component based on the asset definition.

Abstract: Systems and methods are provided for managing and tracking process pipelines and other flows in a way that reduces the requirement for a central controlling process to manage every step of the associated pipeline flow and the state associated with each running instance. Job information and pipeline state are tracked by each worker involved in the pipeline. This enables some key capabilities within these process pipelines such as dynamic process re-writing and cross security domain job execution.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: Systems and methods are provided for managing and tracking process pipelines and other flows in a way that reduces the requirement for a central controlling process to manage every step of the associated pipeline flow and the state associated with each running instance. Job information and pipeline state are tracked by each worker involved in the pipeline. This enables some key capabilities within these process pipelines such as dynamic process re-writing and cross security domain job execution.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow a desktop integration framework to optimize retrieval of custom string resources from resource bundles hosted by server computer systems. A client computer that uses a document as a user interface to a web-server application hosted by a server-computer system can determine which custom string resources are to be utilized in the document. The client computer system can request only the custom string resources that are determined to be utilized in the document from the server-computer system in a single request thereby optimizing retrieval without requesting entire resource bundles.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: Systems and methods are provided for managing and tracking process pipelines and other flows in a way that reduces the requirement for a central controlling process to manage every step of the associated pipeline flow and the state associated with each running instance. Job information and pipeline state are tracked by each worker involved in the pipeline. This enables some key capabilities within these process pipelines such as dynamic process re-writing and cross security domain job execution.

Abstract: In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow a desktop integration framework to optimize retrieval of custom string resources from resource bundles hosted by server computer systems. A client computer that uses a document as a user interface to a web-server application hosted by a server-computer system can determine which custom string resources are to be utilized in the document. The client computer system can request only the custom string resources that are determined to be utilized in the document from the server-computer system in a single request thereby optimizing retrieval without requesting entire resource bundles.