Screen Configuration Settings

Screen configuration settings define the page, dialog boxes, context menus and other elements visible to a certain user type. They also support the context layout editor, in which the content, arrangement, and visibilities of each context are set.

The Screen configuration tab contains the list of all contexts available in Oracle Field Service. All contexts are split into three sections that correspond to their location in the application:

• Application screens: The contexts used in Core Application.

• Collaboration and Identifiers: The contexts used in Oracle Field Service Collaboration Service and the entity identifier contexts.

The Screen configuration tab is active when the Allow access to web application option is selected for the user type. The same settings also influence the availability of the configuration sections. If the Allow access to web application option is deselected for the user type, the Application screens section is collapsed and inactive.

The list of settings is organized hierarchically and shows the relationships between different contexts. All context names are links to the context layout editor pages. This screenshot shows the Screen configuration tab:

Note: Any settings configured in the Application screens section are retained if the Allow access to web application option is deselected afterward for the user type. If the access is allowed again, the same configuration settings apply again for the user type.

Links to new (not edited) or empty contexts are shown in red, while links to edited contexts are shown in blue. If you remove all elements from a context, its link color changes from blue to red to indicate that the context is now empty. If you create a user type without copying the settings of another user type, all contexts are shown in red. When configuring pages for a user type, the Context layout structure page provides an indicator to show that a property is configured. When you add an item to the Layout structure column of the page, it appears in red until you add visibility to the field. After you define a visibility for the item, it is no longer highlighted in the Layout structure column.

Note: You can add or remove the Collaboration Group and Operator of Helpdesk properties from the context layout structure of the Add/Edit User context for each user type. After you update the properties in the Add/Edit User context, select a user from the Resource Settings, Users page and click Modify to view the updated properties.

The hierarchy of contexts starts from the Main menu items context defining the main menu items available or unavailable for the current user type. The configuration of the Main menu items context defines the menu bar elements visible or hidden for a particular user type. Each menu bar element opens a certain page and, therefore, provides access to its functionality. If a certain page has been made available for a user type, all users of such type have access to the entire functionality implemented on that page. Similarly, if a page has been made unavailable for a user type, all users of such type cannot use the functionality implemented on that page.

Changing the visibility of the Message Scenarios menu item to Read-write allows the user to view and edit all elements of a message scenario. With the Read-only visibility, they can only view them. This screenshot shows the Settings tab of the View scenarios step, which was set as read-only in the Screen Configuration page:

The links to contexts are connected with arrows showing the relation between the contexts. Hovering the mouse over an arrow highlights it in red for better visibility. This screenshot shows a highlighted arrow, which means you are hovering the mouse over that arrow:

Click a link to open the Context layout structure page and define the fields and actions of the context, and their visibilities for the user type. You can copy a context layout to another user type if the other user type uses the same or slightly modified layout of the same page or window. For this purpose, the Context layout structure page has the Copy to button, which opens the list of all user types in the application.

For the form type contexts, the link leads to the Visual Form Editor page, where you can edit context layouts in an easier and more transparent manner. You can delete the default Read/Write visibility on the sections and tabs in the Visual Form Editor. Additionally, Read/Write visibility is not added after migration. When the visibility condition for a property is mandatory and the property value is cleared, the value is set to null and the visibility is selected.

If you have shared the configuration for the current user type with one or more other user types, such user types are preselected in the Copy to list. If the user type selected in the list shares its configuration with other user types, such user types are automatically selected as well. The current context layout is applied to the selected user types. In this case it replaces the previous context layout settings, if any.

When a context layout is copied for another user type, only the current context is copied, while the rest of the configuration remains unchanged. When a context layout is copied, two separate identical context layouts are created. You can edit each layout independently without affecting the other one. However, if the destination configuration is shared with other user types, the current context layout is copied to all user types sharing the same configuration.

Context layout copying is confirmed with the message, Layout has been successfully copied. Closing the Context layout structure page returns the user to the User types page.

The Collaboration and Identifiers section contains the contexts falling under two groups:

• Identifiers: Includes the identifier contexts for activity, inventory and service request

• Collaboration: Includes all contexts related to the Collaboration module, as shown in this screenshot:

Note: Text formatting such as modifying the text size, bold/non-bold, italic, or coloring or properties is not supported.