Abstract: A user experience repository may contain base layouts and variant metadata for applications of an enterprise. An application design platform may receive, from a designer, an indication of a selected base layout for a selected application and interact with the designer to create a user experience variant (e.g., a page layout). The designer may then define an assignment rule for the user experience variant, the assignment rule including custom logic and multiple user parameters (e.g., a user role, country, language, etc.), and the system may store information about the user experience variant and assignment rule. An enterprise application service platform may determine that a user is accessing the selected application and evaluate the custom logic of the assignment rule based on user parameters of the user accessing the selected application. In accordance with the evaluation, the system may arrange to provide the appropriate user experience variant to the user.

Abstract: Some embodiments may be associated with a system to extend business logic for cloud application services. A custom logic user interface may receive, from a user via a flow-based editor, information creating a custom logic business expression (e.g., a determination or a validation) and information about the custom logic business expression may be stored in a custom logic metadata repository. A computer processor of an application service platform may access the custom logic business expression from the custom logic metadata repository and receive an Application Programming Interface (“API”) call from an API consumer. Responsive to the API call, the system may arrange for execution of the custom logic business expression in accordance with information in the custom logic metadata repository and invoke a pre-hook trigger event to call a custom logic service. Standard application logic may then be executed, and a post-hook trigger event may be invoked to call the custom logic service.