Abstract: A feedback service for use with a cloud application and a method of the feedback service are disclosed. The feedback service is coupled to a page of the cloud application. A pane of the feedback service is selectively displayed with the page, and the pane requests user input regarding the page.

Abstract: Selective validation of subgroups of users against group rule parameters is performed to validate group rule parameters for a dynamic group rule. An administrator defines the group rule parameters and selects individual user accounts which are either expected to be included within and/or excluded from a full membership list for the dynamic group rule. For example, the administrator may select first user accounts that are expected to be included within the full membership list and/or second user accounts that are expected to be excluded from the full membership list. Then, a subgroup validation report is generated to inform the administrator whether or not individual user accounts from the subgroup of user accounts satisfy the group rule parameters and, therefore, will be included within the full membership list of the dynamic group rule. The subgroup validation report reveals the efficacy of the group rule parameters.

Abstract: A feedback service for use with a cloud application and a method of the feedback service are disclosed. The feedback service is coupled to a page of the cloud application. A pane of the feedback service is selectively displayed with the page, and the pane requests user input regarding the page.

Abstract: The embodiments described herein generally relate to systems and methods for providing human interaction with a business application from an email client. To complete a business process, individuals often must provide information to a business application. However, it may be difficult for the individual to interact with the application if the user is not familiar with the application's user interface (UI) or if it is necessary to navigate to the application's UI. Accordingly, it may be more efficient to interact with the application using a UI within an email client. User input for an automated business process can be submitted from a general-purpose email client. Benefits from such include providing input to a business application while working within the familiar email interface; not needing to switch contexts to complete work for the application; and completing work for the application while being offline or having limited corporate network connectivity.

Abstract: Metadata is used to create customized user interface (UI) portions for an application. The metadata may be XML-based and can be interpreted and then rendered to implement a customized UI that also supports data binding between data and the UI controls. Once created, the metadata is processed by a rendering engine to display the UI controls. An interpreter may be used to interpret the metadata file before it is sent to the rendering engine. Neither the rendering engine nor the interpreter needs knowledge of the host application and provides support for arbitrary metadata driven UI. The metadata schema may include mechanisms to create custom controls for the UI; programmatically modify the UI controls by providing access to a code-behind assembly as well as support event handling for the UI controls.

Abstract: The embodiments described herein generally relate to systems and methods for modeling a user-initiated request to a business process application as an email form. It is often necessary for individuals to communicate, or exchange information, with a business application. Inefficiencies and delays arise where individuals are required to work within the context of the business application to accomplish desired actions or to determine the status of a requested action. By allowing a user to request an action from a business application using an email form, such inefficiencies and delays are minimized, if not eliminated altogether. A user may therefore initiate a request to a business application by working within the familiar and readily-available UI of the user's general-purpose email client and may receive status updates regarding such a request with the same UI of the original request.

Abstract: The embodiments described herein generally relate to systems and methods for providing human interaction with a business application from an email client. To complete a business process, individuals often must provide information to a business application. However, it may be difficult for the individual to interact with the application if the user is not familiar with the application's user interface (UI) or if it is necessary to navigate to the application's UI. Accordingly, it may be more efficient to interact with the application using a UI within an email client. User input for an automated business process can be submitted from a general-purpose email client. Benefits from such include providing input to a business application while working within the familiar email interface; not needing to switch contexts to complete work for the application; and completing work for the application while being offline or having limited corporate network connectivity.

Abstract: Metadata is used to create customized user interface (UI) portions for an application. The metadata may be XML-based and can be interpreted and then rendered to implement a customized UI that also supports data binding between data and the UI controls. Once created, the metadata is processed by a rendering engine to display the UI controls. An interpreter may be used to interpret the metadata file before it sent to the rendering engine. Neither the rendering engine nor the interpreter needs knowledge of the host application and provides support for arbitrary metadata driven UI. The metadata schema may include mechanisms to create custom controls for the UI; programmatically modify the UI controls by providing access to a code-behind assembly as well as support event handling for the UI controls.