Abstract: Composable events to provide a dynamic user interface are disclosed. In various embodiments, a definition of a custom user interface event is received. The definition includes an identification of a data value to be associated with the event, a scope of the event within which the event will be consumed, and an event trigger in response to which an instance of the custom user interface event is to be published. Application user interface code configured to provide one or more application user interface elements configured to publish or subscribe to the custom user interface event is generated programmatically, based at least in part on the definition.

Abstract: Composable events to provide a dynamic user interface are disclosed. In various embodiments, a definition of a custom user interface event is received. The definition includes an identification of a data value to be associated with the event, a scope of the event within which the event will be consumed, and an event trigger in response to which an instance of the custom user interface event is to be published. Application user interface code configured to provide one or more application user interface elements configured to publish or subscribe to the custom user interface event is generated programmatically, based at least in part on the definition.

Abstract: Techniques to dynamically discover and manage page fragments, e.g., to provide a dynamic application user interface, are disclosed. In various embodiments, an indication to add a fragment dynamically to a current application page is received. The fragment to be added is determined, in response to the indication, and added dynamically to the current application page.

Abstract: Composable events to provide a dynamic user interface are disclosed. In various embodiments, a definition of a custom user interface event is received. The definition includes an identification of a data value to be associated with the event, a scope of the event within which the event will be consumed, and an event trigger in response to which an instance of the custom user interface event is to be published. Application user interface code configured to provide one or more application user interface elements configured to publish or subscribe to the custom user interface event is generated programmatically, based at least in part on the definition.

Abstract: Composable events to provide a dynamic user interface are disclosed. In various embodiments, a definition of a custom user interface event is received. The definition includes an identification of a data value to be associated with the event, a scope of the event within which the event will be consumed, and an event trigger in response to which an instance of the custom user interface event is to be published. Application user interface code configured to provide one or more application user interface elements configured to publish or subscribe to the custom user interface event is generated programmatically, based at least in part on the definition.

Abstract: Composable action flows are disclosed. In various embodiments, a definition of one or more processing steps comprising an action flow is received. A definition of one or more transitions between processing steps comprising the action flow is received. The processing step and transition definitions are used to generate programmatically application code to implement the action flow.

Abstract: Developer-composed custom application session parameters are disclosed. In various embodiments, a definition of a custom application session parameter is received via a software development tool user interface. Application code to store and manage the custom application session parameter, including by making the custom application parameter available across a plurality of application user interface pages, is generated programmatically based at least in part on the definition.

Abstract: Composable action flows are disclosed. In various embodiments, a definition of one or more processing steps comprising an action flow is received. A definition of one or more transitions between processing steps comprising the action flow is received. The processing step and transition definitions are used to generate programmatically application code to implement the action flow.

Abstract: Composable action flows are disclosed. In various embodiments, a definition of one or more processing steps comprising an action flow is received. A definition of one or more transitions between processing steps comprising the action flow is received. The processing step and transition definitions are used to generate programmatically application code to implement the action flow.

Abstract: Techniques to dynamically discover and manage page fragments, e.g., to provide a dynamic application user interface, are disclosed. In various embodiments, an indication to add a fragment dynamically to a current application page is received. The fragment to be added is determined, in response to the indication, and added dynamically to the current application page.

Abstract: Techniques to dynamically discover and manage page fragments, e.g., to provide a dynamic application user interface, are disclosed. In various embodiments, an indication to add a fragment dynamically to a current application page is received. The fragment to be added is determined, in response to the indication, and added dynamically to the current application page.

Abstract: Developer-composed custom application session parameters are disclosed. In various embodiments, a definition of a custom application session parameter is received via a software development tool user interface. Application code to store and manage the custom application session parameter, including by making the custom application parameter available across a plurality of application user interface pages, is generated programmatically based at least in part on the definition.

Abstract: Developer-composed custom application session parameters are disclosed. In various embodiments, a definition of a custom application session parameter is received via a software development tool user interface. Application code to store and manage the custom application session parameter, including by making the custom application parameter available across a plurality of application user interface pages, is generated programmatically based at least in part on the definition.