Oracle CRM On Demand Connected Mobile Sales Administration Guide > Using Application Composer >

About the Application Composer User

The user ID that you use to sign on to Application Composer affects which fields are available to the users of Oracle CRM On Demand Connected Mobile Sales. You may need to create a special user ID and role solely for the purpose of using Application Composer. This user ID is called the Application Composer user. The role and data access of the Application Composer user determines which fields all users of Oracle CRM On Demand Connected Mobile Sales can access. Fields that the Application Composer user cannot access are unavailable to all users of Oracle CRM On Demand Connected Mobile Sales.

To make sure that all users have the same access to fields in Oracle CRM On Demand Connected Mobile Sales as they do in Oracle CRM On Demand, you can create a user and role in Oracle CRM On Demand for the purpose of signing on to Application Composer. This user and role must have access to a superset of the fields required by all roles. Users are still restricted by their roles when using Oracle CRM On Demand Connected Mobile Sales. For example, if you added the Partner Organization Status field to the Account layout, your users with Sales Rep roles still cannot access it because it is not included in their role's definition.

You must create an Application Composer user if all of the following conditions apply:

• You have users with different roles using Oracle CRM On Demand Connected Mobile Sales
• Those roles have different page layouts

If one or more of these conditions do not apply to your implementation then you do not need to create an Application Composer user.

You create the Application Composer user and role in Oracle CRM On Demand. While creating the role, you must take into account the page layouts assigned to the role. For each record type you can choose a Page View Type and a Page Layout Name. You must choose page layouts that specify the superset of fields you require. In some cases, you might have to create such a page layout if one does not already exist.

If a selected page layout has both static and dynamic page view types, choose the static page view type. Oracle CRM On Demand Connected Mobile Sales loads all the fields on the page layout, which for a static layout is a known list of fields. If you are using Release 29 or later and if the page layout is dynamic, Oracle CRM On Demand Connected Mobile Sales cannot determine which fields might be used in all forms of the dynamic layout, and so it loads all possible fields.

NOTE:  Dynamic layout support requires the Manage Dynamic Layouts privilege and Oracle CRM On Demand, Release 29 Hot Fix 029.015.000.002HF or later. Users configured with a dynamic page layout in Oracle CRM On Demand see all the configured fields in the default layout of the assigned dynamic layout in Oracle CRM On Demand Connected Mobile Sales.