3Initial Setup

About Initial Setup

After you successfully install your Siebel Business Applications, you must perform numerous tasks to set up and administer them.

You must complete initial setup tasks in order for your Siebel Business Applications to work correctly, and then you can complete these tasks infrequently as your company grows. Complete ongoing tasks on an occasional or ongoing basis. Ongoing Application Administration Tasks describes these ongoing tasks.

Process of Implementing Initial Setup

To implement initial setup, perform the following tasks:

  1. Add any custom views.

    Custom views are created in Siebel Tools and must be added to your Siebel application. Add custom views to the Views view before you define responsibilities. For information about adding views, see Adding Views to the Siebel Application.

  2. Determine access control strategy and define business environment structure.

    You can set up your Siebel Business Applications to support many strategies for your company to control access to views and data. These strategies include methods such as defining your business environment structure (organizations, internal and external divisions, and so on), defining employee positions, and creating access groups so that specific groups of people have access to specific views and data.

    Make these decisions early in the deployment process, so that you can implement the strategy during the initial setup. For more information about controlling access to views and data, and the procedures for implementing access control, see Siebel Security Guide.

  3. Enter employee records into the Siebel application and determine employee access to views and data.

    Enter employee records after you have defined your business environment structure. You must assign at least one responsibility to each employee, and you can also assign organizations, positions, or other access control parameters. For more information about entering or deactivating employee records, see Siebel Security Guide.

  4. Complete employee setup. For information about associating additional information to an employee record, see Completing Employee Setup.

  5. Assign employee skills. For more information, see Assigning Skills.

  6. Set up locales.

    Locale Codes and parameters are necessary for a global deployment. For more information, see Setting Up Locales.

Adding Views to the Siebel Application

Developers create new views through Siebel Tools. In order for the views to become available for administrators to work with, you must add them to the Views screen in the Siebel application before you define your business environment.

For example, you want to add an Opportunities view in the Reference screen. In Siebel Tools, you create the view and name it Reference Opportunities. In your Siebel application, you follow the steps in this topic, and add the Reference Opportunities view in the View Administration view. After it has been added in both places, the view can be made accessible to the appropriate users. For details on creating views, see Configuring Siebel Business Applications. For details about controlling visibility to views, see Siebel Security Guide.

You generally do not have to modify or delete views that are already listed. You must modify a view only if its name was changed in Siebel Tools. You must delete a view only if it no longer exists in the data model schema, or if you do not want anyone to have access to it. Instead of deleting views, administrators remove the views from responsibilities and keep them in the Siebel database.

Note: Only visibility-level views can be configured to appear in the Site Map.

This task is a step in Process of Implementing Initial Setup.

To add customized views to the Siebel application

  1. Navigate to the Administration - Application screen, then the Views view.

  2. In the Views list, create a new record, and complete the necessary fields.

Completing Employee Setup

After completing the employee setup procedures, which are required to allow employee access to the Siebel application, views, and data, you complete employee setup by providing additional information. For information about the employee setup procedures, see Siebel Security Guide.

This setup can include the following:

  • Assignment Rules. Allows you to see and administer the assignment rules for an employee. For more information about assignment rules, see Siebel Assignment Manager Administration Guide.

    Note: You must be logged on to a server database to use the Employee Assignment Rules view.
  • Availability. Lists the projects for which an employee is on staff, or for which an employee has been requested. For more information, see Siebel Project and Resource Management Administration Guide.

    Note: Employees can also change their availability in the Availability view on the User Preferences screen.
  • Exception Hours. Specifies the days and hours an employee is not available.

  • Utilization. Displays a chart with the monthly and quarterly utilization of the currently selected employee. Managers use this chart for monitoring professional services projects and employees. For more information about professional services, see Siebel Project and Resource Management Administration Guide.

  • Tools. Defines the tools that field service engineers carry with them or have access to. It allows a call center person to check whether the engineers have the correct tools for the jobs they are assigned to.

  • Job Information. Specifies the job profile, salary, compensation ratio, pay currency, and location of employee.

  • Calendar administration. Defines the calendar properties and access for an employee. For more information about Calendar administration, see Calendar.

  • Assignment Skills. Defines an employee’s skills and skill items, along with their level of expertise. Skills can be used as assignment criteria in Siebel Assignment Manager. For more information about how the Siebel application uses skills, see Siebel Assignment Manager Administration Guide.

    Skills can also be used in the Project and Resource Management product for managing resources. For information about these types of skills, see Siebel Project and Resource Management Administration Guide.

  • Employee Query. Allows queries to identify employees with particular skills and expertise.

  • Service Details. Provides details about the shift start and end locations, hourly costs, overtime availability and other details for a service employee.

  • Competency. Provides a list of areas in which the employee has some demonstrated level of knowledge or accomplishment.

  • Education. Provides details of an employee’s education history.

  • Past Work Experience. Provides details of an employee’s work history.

  • Honor/Award. Provides list of honors and awards earned by an employee.

  • Membership. Provides details of an employee’s memberships in various organizations.

  • Certification. Provides details of an employee’s certification.

This task is a step in Process of Implementing Initial Setup.

To complete the employee setup

  1. Navigate to the Administration - User screen, then the Employees view.

  2. In the Employees list, drill down on Last Name field for an employee record.

  3. Navigate to the More Info view.

  4. In the form, complete the necessary fields.

    Some of the fields are described in the following table.

    Field Comments

    Configuration

    Select the Siebel application or group of software components to associate with the currently selected employee. For more information, see Siebel Anywhere Administration Guide.

    Available Until

    Select a date and time to indicate the active period of an employee. This field is used in conjunction with the Availability, Overtime Availability, and Next Available fields.

  5. Navigate to another appropriate view.

  6. Create a new record, if needed, and complete the necessary fields.

Assigning Skills

At the levels of organizations, positions, and employees, you can add skills. Skills are used for assigning employees to certain projects, service requests, and so on. Skills added to an organization apply to all employees assigned to that organization. Skills assigned to a position apply only to the employee assigned to that position. You create skills with Siebel Tools.

Employees can track and update their own skill profiles in the User Preferences Profile view. For more information about how your Siebel application uses skills, see Siebel Assignment Manager Administration Guide.

This task is a step in Process of Implementing Initial Setup.

Setting Up Locales

A locale is a set of rules guiding how common data appears to the user or is received from the user. These rules are used to format data from a Siebel database before displaying the resulting information in output fields on the user interface. Siebel Business Applications use local settings to support language and geographical conventions for the display language of drop-down lists, and formatting of data such as dates, times, numbers, and currencies.

The Locale information is stored in the Locale Table (S_LOCALE). The data in this table is maintained by the administrator using the Locale Administration view. For more information about languages and locales, see Siebel Global Deployment Guide. For more information about configuring the formatting for dates and currency, see Configuring Siebel Business Applications.

The locale with which a Siebel Application Object Manager component is initialized is determined by the value of the parameter Locale Code. Although the locale is set during initial installation and configuration, it can be changed to any locale that is preconfigured with the Siebel application or that has been added by the administrator. The Locale Code parameter can be set at the Enterprise, Server, or Component level.

Several locale definitions come with the standard Siebel application. You can also revise these existing locales, or create new locales, using the Locale Administration view.

Note: Create a new locale only if a locale is not already defined that can meet your requirements.

After a locale and its settings are defined, you can create translations for locale names that appear in the locale pick applet, rather than the three-letter acronym locale code. For example, instead of showing ENU as the locale name, the administrator provides English–United States as a translation for English speakers, Inglese–Stati Uniti d’America for Italian speakers, and so on. Only translated locale names appear to users on locale pick applets.

Note: While the Siebel Web Clients use the locale settings specified in the Locale Administration view, the Siebel Mobile Web Client and the Siebel Developer Web Client use the locale settings defined in the Regional and Language Options settings on the client computer.

Setting up a Siebel Application Object Manager component includes assigning it a locale. Because the locale directs how locale-sensitive information such as dates, times, and numbers differs between countries, customers can configure a Siebel Application Object Manager for each country or other geographical setting in which they have users, and provide these users with data that appears correctly for their locale.

This task is a step in Process of Implementing Initial Setup.

To create a locale

  1. Navigate to the Administration - Data screen, then the Locale view.

  2. In the Locale list, create a new record, and complete the necessary fields.

    Some fields are described in the following table.

    Field Comments

    Locale Code

    Type the locale code. Siebel Business Applications use the three-letter acronym conventions of Microsoft for the locale codes. In most cases, the acronym is created by taking the two-letter language abbreviation from ISO Standard 639 and adding a third letter to form a unique identifier.

    For example, ENU (English–United States), ENG (English–United Kingdom), or FRA (French–France)

    For information about Microsoft codes, see your Microsoft documentation.

    Locale Name

    Type the locale name. The naming convention for locales is generally Language Name–Territory (for example, English–United States, English–United Kingdom, or French–France).

    Description

    Type optional text describing the locale.

    UI Directionality

    Select a value for the direction of the text that appears in the user interface. Values are:

    • Right To Left (Arabic and Hebrew)

    • Left To Right (all other predefined locales)

    International Dialing Code

    Select the country code to appear in phone numbers. This field suppresses the country code for phone numbers that are in the user’s locale. For example, the phone numbers for two accounts are the following:

    • +33 1-23 42 34 56, for an account based in France (+33 is the country code for France)

    • +1 6502955000, for an account based in the U.S. (+1 is the country code for the U.S.)

    To a user based in the U.S. (locale ENU), the International Dialing Code value is “USA and Canada (1)", and the phone numbers given here appear as follows:

    • +33 1-23 42 34 56

    • (650) 295-5000

    Positive Currency Format

    Select a value for the location of the currency symbols with respect to the digits (100).

    For example, for U.S. format, $32.45, select s100.

    Negative Currency Format

    Select a value for the location of the negative sign (-) with respect to the currency symbols and digits (100).

    Examples follow:

    • For U.S. format, ($32.45), select (s100).

    • For British format, -£32.40, select -s100.

    Currency Decimal Separator

    Type the symbol to indicate the decimal place in currency.

    Currency Grouping Separator

    Type the symbol to group numbers in currency. Use \B to designate a space.

    Number Decimal Separator

    Type the symbol to indicate the decimal place in numbers.

    Examples follow:

    • For French format, 1 234,34 (comma as decimal symbol)

    • For U.S. format, 1,234.34 (period as decimal symbol)

    Number Grouping Separator

    Type the symbol to group numbers.

    Examples follow:

    • For French format, 1 234 (space as number grouping separator). Use \B to designate a space.

    • For German format, 1.234 (period as number grouping separator)

    • For U.S. format, 1,234 (comma as number grouping separator)

    Number Leading Zero

    Select the check box to display a leading zero in numbers less than one (for example, 0.7, not .7).

    Number Fractional Digits

    Type the number of digits after the decimal separator. For example, the number 12.340 has a number fractional of 3.

    This field applies to data fields of type DTYPE_NUMBER.

    List Separator

    Type the symbol to separate consecutive numbers in a list.

    In the U.S., consecutive numbers are separated by a comma (for example, 1.23,3.57,4.01),

    In France, consecutive numbers are separated by a semi-colon (for example, 1,23;3,57;4,01).

    Long Date Format

    Type the appropriate long date format, which typically contains day and month names. For example, the dddd, dd mmm, yyyy format yields a date such as Friday, 07 Jun, 2004.

    The following date format options represent the day of the month:

    • d specifies the day of the month, with no leading 0 for single-digit days (1, 2, 3, ...).

    • dd specifies the day of the month, with a leading 0 for single-digit days (01, 02, 03, ...).

    • ddd specifies the abbreviated name of the day of the week (Mon, Tue, Wed, and so on).

    • dddd specifies the full name of the day of the week (Monday, Tuesday, Wednesday, and so on).

    The following date format options represent the month:

    • m specifies the month, with no leading 0 for single-digit months (1, 2, 3, ... 12).

    • mm specifies the month, with a leading 0 for single-digit months (01, 02, 03, ... 12).

    • mmm specifies the abbreviated month name (Jan, Feb, Mar, and so on).

    • mmmm specifies the full month name (January, February, March, and so on).

    The following date format options represent the year:

    • yy specifies the last two digits of the year (00, 01, 02, ... 99).

    • yyyy specifies the full four digits of the year (1999, 2000, 2001, ... 2099, ...).

    Date formats can include literal delimiter characters, such as a space, comma, period, hyphen, or forward slash (/). The Date Separator character is usually one of these characters. A delimiter can be any non-numeric character, but avoid using the date format options for the Long Date Format field in the delimiter.

    Long Date Format (continued)

    If you must use a date format option in a delimiter, then enclose the delimiter in single quotation marks. For example, a date of Thursday, January 24, 2013 in English is quinta-feira, 24 de janeiro de 2013 in Portuguese. The de delimiters (which mean “of") in the Portuguese date include the letter d, which is a date format option for the day of the month. You specify the English date in a format of dddd, mmmm dd, yyyy. But you must specify the Portuguese date in a format of dddd, dd 'de' mmmm 'de' yyyy. You enclose the de delimiters in single quotation marks so that the letter d in these delimiters is not interpreted as the day of the month.

    Note: Long dates are supported only for the calendar, the Gantt chart, salutation text on the home page, and balloon text in some charts.

    Short Date Format

    Type the appropriate shortened date format.

    Examples follow:

    • yymmdd (081104 or 080321)

    • m/dd/yyyy (11/04/2008 or 3/21/2008), the default U.S. format

    • dd.mm.yyyy (04.11.2008 or 21.03.2008), the default German format

    For information about other elements used in date formats, see the description for the Long Date Format field.

    Date formats can include literal delimiter characters, such as a space, comma, period, hyphen, or forward slash (/). The Date Separator character is usually one of these characters. A delimiter can be any non-numeric character, but avoid using the date format options for the Long Date Format field in the delimiter.

    Note: If you enter a month number greater than 12, then the month defaults to 12. If you enter a day number greater than the number of days in the month, then the day defaults to the last day of the month. For example, if you enter 42/99/03 (U.S. format), then the date defaults to 12/31/03.

    Date Separator

    Type the symbol to use in a date format to separate the components of the date. It must be a single non-numeric character that is not one of the elements representing day, month, or year.

    Time Separator

    Type the symbol to separate hours from minutes in a time format.

    Time Leading Zero

    Select the check box to display a leading zero in time fields.

    Examples follow:

    • 01:03 AM, 01:03 PM, 12-hour clock with leading zero

    • 1:03 AM, 1:03 PM, 12-hour clock without leading zero

    • 01:03, 13:03, 24-hour clock with leading zero

    • 1:03, 13:03, 24-hour clock without leading zero

    24-hour clock

    Select the check box to indicate use of the 24-hour clock. Clear the check box to indicate use of the 12-hour clock.

    Time A.M. Designator

    Type the symbol for designating time between 00:00 and 12:00 (for example, AM, a.m., or am).

    Time P.M. Designator

    Type the symbol for designating time between 12:00 and 24:00 (for example, PM, p.m., or pm).

    Creating a Translation for a Locale Name

    Complete the following procedure to create a translation for a locale name.

    To create a translation for a locale name

    1. Navigate to the Administration - Data screen, then the Locale view.

    2. In the Locale list, select the appropriate record.

    3. Navigate to the Locale Name Translation view.

    4. In the Locale Name Translation list, create a new record, and complete the necessary fields.

      Some fields are described in the following table.

      Field Comments

      Language

      Type the language code of the translation of the locale name. For examples of language codes, see Siebel Global Deployment Guide.

      Translated Name

      Type the exact translation of the locale name to appear in the drop-down list for users with the designated language code. For example, for the locale English–United States:

      • For the locale with the language code ENU, the locale name is English–United States.

      • For the locale with the language code ITA, the locale name is Inglese–Stati Uniti d’America.

      Description

      Type the translated description of this locale.

      Editing the Current Locale

      Complete the following procedure to edit the current locale.

      To edit the current locale

      1. Edit the locale record.

        For more information about access the locale record, see Setting Up Locales.

      2. To have the edits take effect, restart the Siebel Application Object Manager component.

        For information about shutting down and starting Siebel Server components such as a Siebel Application Object Manager, see Siebel System Administration Guide.

        Setting Up Satmetrix Survey Reports

        Note: This topic applies only to those who have purchased Siebel Satmetrix Surveys or who have purchased surveys directly from Satmetrix Systems.

        To view Satmetrix survey reports through your Siebel application, you must:

        • Add the Account Satmetrix Survey View view to the appropriate user responsibilities. For information about how to add views to responsibilities, see Siebel Security Guide.

        • Enter the secret key string provided by Satmetrix Systems into the Satmetrix Key Value system preference. For information about how to change system preferences, see Setting System Preferences.

        • Complete the procedures in this topic.

          Extending the List of Values

          Extend the List of Values for WI_ARG_TYPE. This LOV defines the arguments for integrating with other portal and internet applications. For more information about creating records for Lists of Values, see Working with Lists of Values.

          To extend the List of Values for WI_ARG_TYPE

          1. Navigate to the Administration - Data screen, then the List of Values view.

          2. Create a new record, and complete the fields, using the following table as a guide.

            Field Value

            Type

            WI_ARG_TYPE

            Display Value

            Satmetrix

            Language-Independent Code

            Satmetrix

            Active

            Yes

            Translate

            Yes

            Replication Level

            All

            Setting Up The Symbolic URL

            Next, set up the symbolic URL for access to the Satmetrix reports server. For more information about symbolic URLs, see Siebel Portal Framework Guide.

            To set up the symbolic URL for access to Satmetrix Reports

            1. Navigate to the Administration - Integration screen, then the WI Symbolic URL List view.

            2. From the visibility filter, select Symbolic URL Administration.

            3. In the list of symbolic URLs, select SatmetrixSurvey.

            4. Make sure the URL is the URL for the reports server provided by Satmetrix Systems.

            5. In the Symbolic URL Arguments list, complete the fields, using the following table as a guide.

              Name Required Argument Argument Type Argument Value Append as Argument Sequence

              EncodeUrl

              Yes

              Command

              FALSE

              Yes

              1

              version

              Yes

              Constant

              Obtain from Satmetrix

              Yes

              2

              windowsize

              Yes

              Command

              WebControl width=1000 height=500 border=1

              Yes

              3

              type

              Yes

              Constant

              acct

              Yes

              4

              acctid

              Yes

              Field

              Id

              Yes

              5

              acctname

              Yes

              Field

              Name

              Yes

              6

              contactid

              Yes

              Constant

              *

              Yes

              7

              contactname

              Yes

              Constant

              *

              Yes

              8

              user

              Yes

              Profile Attribute

              Login Name

              Yes

              9

              domain

              Yes

              Constant

              Obtain from Satmetrix

              Yes

              10

              model

              Yes

              Constant

              Obtain from Satmetrix

              Yes

              11

              created

              Yes

              Field

              Timestamp

              Yes

              12

              token

              No

              Satmetrix

              Satmetrix Surveys, CalculateToken

              Yes

              13