|
Branding and theming
|
Do you want your workspace to match your brand?
|
A theme sets the visual style of a workspace experience and provides a consistent look and feel across all pages.- Choose colors suited for an effective agent experience and in line with your overall branding strategy.
- Adhere to logo size and acceptable format guidelines.
For more information see:
- [View the brand and theme setting in your workspace experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/application-development/workspace-view-theme-setting.md)
- [Working with themes in Next Experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-user-interface/next-experience-theming.md)
|
|
Landing page
|
Do you want to update the headers, containers, or widgets on the landing page?
|
<add intro>.- The information on the landing page should be relevant to the logged-in user.
- Consider the key metrics and condensed data views that the user needs to see regularly.
|
|
Tab settings: New record menu
|
Are new record menus needed for other tables, such as Contact or Case? \(The + button that enables an agent to create a new record.\)
|
- Use Interaction as an entry point for case creation. Capture initial triage information separately and provide for first time-resolutions that don’t need a subsequent task \(such as a case, incident, or request\) to be created.
- User must have create access to the table\(s\) for the button to appear on their records menu in the workspace.
- Include only those tables that are most frequently used by agents, such as Case and Interaction.
|
|
Service catalogs
|
- Will agents use service catalogs to create requests on behalf of customers?
- Which service catalogs need to be added to the service portal to enable this?
|
- Consider the holistic agent experience, including case, incident, and request management, to define an effective process.
- Encourage self-service by customers. Agents creating requests on behalf of users should be for exceptional scenarios.
|
|
Lists
|
- Are new list categories and lists required?
- Do existing list categories and lists need to be removed?
- Are access controls needed for lists for specific roles or groups?
- Disable the New button on the List view?
- Are UI notifications required when a record is updated?
|
Configure list categories, filtered lists, and tailor lists to show specific items by user role in a configurable workspace.- The order of list categories and lists should make sense to the logged-in users.
- Remove unwanted lists and list categories to avoid information overload.
- If UI notifications are required for record updates, define the recipients and the trigger conditions.
|
|
Form headers
|
For each form:- Is a header required?
- If yes, which fields should be included in the header?
|
- Form headers are optional.
- Headers provide information that agents can see at a glance.
- Review the existing headers in the baseline workspace experience and update as needed.
|
|
UI actions
|
For each form:- Are updates required to existing actions?
- What additional actions do agents need?
|
- Focus on actions used by agents.
- Leverage actions provided in the baseline workspace experience.
- If custom actions are needed, use correct scripting meant for workspace.
|
|
Ribbon
|
Do you need to add or change the ribbon widgets displayed for Case records? If yes, specify the following information:- Data table
- Widget
- Width
- Attributes
- Placement
|
In the in the baseline workspace experience, the ribbon includes three widgets: Customer 360, SLA, and Timeline.- To choose suitable widgets, identify the data frequently required by agents to be more effective and productive.
- The total ribbon width is 12 units. Divide the width between the widgets based on volume of information they contain.
Train your agents on the ribbon widgets to drive its usage.
|
|
Ribbon widgets
|
Customer 360:- Provide primary user tables to be displayed \(for example, Contact or Consumer\).
- Provide primary user fields to be displayed \(for example, Name or Phone\).
- Provide secondary fields to be displayed.
Timeline: Specify which task states denote that the task is awaiting customer response.
|
- Customer 360: Fill out secondary fields so that the widget isn't empty when primary user details are missing.
- Timeline: Educate agents that not updating task states correctly will impact calculations in this widget.
- SLA: Train agents to interpret colors for SLAs that are approaching breach limits.
|
|
Contextual side panel
|
For each record page:- What will the agents need to access quickly?
- Which tables or related records are involved?
- Should it be enabled or disabled for specific types of case forms?
|
Display frequently referenced information that might often take the agent out of the workspace
|
|
Form layout
|
The overall structure of the record page displayed in the workspace, including the arrangement of tabs, sections, and components.- Which tabs and sections are needed on the form?
- Should sections be collapsible or mandatory?
|
- Group related fields logically to improve agent understanding.
- Keep important fields higher on the page for visibility.
- When possible, reuse baseline layouts to ensure consistency.
|
|
Form templates
|
Which form templates do you need? Form templates can pre-populate fields, provide conditions that need to be met, user and group access, and other requirements.
|
- Identify the fields most used by agents and use form templates to automate manual input.
- Identify tables with standard fields that can be pre-populated \(For example, Order or Major Case\).
|
|
Lookup and verify
|
- Do you want to use the Lookup and verify feature? If yes, for which customers \(for example, Contact or Consumer\).
- Is caller verification done prior?
|
Consider using automated authentication methods for enabling the **Verify** check box in the Lookup and verify feature.
|
|
Search sources: AI Search in Recommended Actions
|
- Configure the Recommended Actions component to include AI Search.
- Map search sources with guidance inputs for accurate results.
|
AI Search for Recommended Actions displays relevant search results as cards in the contextual side panel.Recommended Actions is the default for the Front-line case record page and Chat interaction record page. This default provides access to AI Search and Genius results and single-click attach capability.
|
|
Search sources: Genius results
|
Do you want to enable Genius results? If yes, configure the Recommended Actions component to include Genius results.
|
Genius results provide AI-driven, contextually relevant answers and actions.
|
|
Customer Central
|
- Specify information to be displayed in ‘Customer Information’: reports, lists, records.
- Any updates required to ‘Customer Activity’ tab?
|
- Pick critical customer information that agents will need quick access to
- To keep the view refreshed with accurate information, configure the number of days to display data for
|
|
Major case management
|
- Do you want Major Case Management to be accessible from the workspace?
- Any updates required to lists, filters, fields, process and access-control for it?
|
- Ensure major case managers do not need to use both, classic UI and workspace, spoiling their overall user experience
- Use manager-specific lists and form layout to avoid displaying excessive information more relevant for agents.
|