Create a new Industry table.

Create a new foreign key on S_INDUST that points to S_ORG_EXT.

Validate there is a foreign key on S_ORG_EXT that points to the Industry business component's
main table.

Validate there is a foreign key to the Industry business component's main table on the
S_ORG_INDUST table.

Validate there is a foreign key on the Industry business component's main table that points to the
S_ORG_EXT table.

View object definitions

Applets that have been bound to a view

Controls that have been bound to an applet

Siebel tags used to define the applet parameters in a view

Batch assignment

Dynamic assignment

Interactive assignment

Manual assignment

This table does not contain a ROW_ID column.

The user key for this table is ROW_ID, NAME, TYPE.

The table cannot be added to an existing dock object.

This table contains a PAR_ROW_ID column acting as a foreign key to the S_PARTY table.

You can create an intersection table to support M:M relationships between business components
based on this table and other business components.

includes static, referential data

has access controlled at the record level

can be grouped into catalogs and categories

is created and managed by only company administrators

DELETE MATCHES

DELETE EXACT

DELETE ALL ROWS

DELETE WHERE

The Web update protection key is invalid.

The Drilldown Add-in has not been installed.

You do not have the appropriate responsibility.

Siebel Tools is not properly connected to the data source.

Siebel Tools

Siebel Server

Siebel Web Client

Sample Database

Gateway Name Server

Siebel Web Server Extensions

Database Configuration Utilities

Users will be able to delete a record because the least restrictive setting is used.

Users will not be able to delete a record because the most restrictive setting is used.

Only the record owner will be able to delete a record because of the conflicting settings.

Users will be able to delete a record because the business component setting overrides the applet
setting.

Undo

Pause/Resume

sharing of tasks

transferring of tasks

branching within a task

It is manually moved to the package directory.

It is generated via the admpkgr generate command.

It is automatically generated by the export processes.

It is used by the deploy copy command to create the deployment session.

It is used by the deploy load command to map contents to the Management Server database.

supports simulating interactive workflows

requires both Siebel Tools and a Siebel Client

requires the use of a local developer database

supports editing of process properties during a simulation

supports simulating workflows that involve a server component

supports simulating workflows with a run-time event on a start step

Primary keys

Foreign keys

User keys

Indexes

configure a Control User Property to pass [Id] to the workflow

configure an Applet User Property to pass [Id] to the workflow

add a Row ID process property to the workflow

set the Pass Row ID property of the button to True

Create a new business component to store these phone numbers.

Determine which column on the base table you can use to store these phone numbers.

Determine which column on the one-to-many extension table you can use to store these phone
numbers.

Run the MVG Wizard in Siebel Tools, specify the business component, and have it automatically
select the appropriate column.

Examine the existing application to determine whether there is already a multi-value group you
could leverage to store phone numbers.

Contact

Account

Position

Opportunity

The control is not mapped to a web template item.

The control is not mapped to a field on the business component.

The Join property on the single value field that the control maps to is blank.

There is no data in the database for the column to which the control maps.

The RUNTIME value is set to FALSE on the picklist associated with the control.

Divisions can be deleted, organizations cannot.

Organizations can be deleted, divisions cannot.

Positions are assigned to organizations, and not divisions.

Organizations are used for Access Control, divisions are not.

Create two views and set the No Update property to TRUE for one of them.

Create two views and set Read Only View to TRUE when you add one to the responsibilities.

Create two list applets and set the No Delete and No Update properties to TRUE for one of them.

Create two form applets and set the No Delete and No Update properties to TRUE for one of
them.

Create two business components set the No Delete and No Update properties to TRUE for one of
them.

It improves performance.

Without a primary, only one record can be referenced.

The multi-value group will not function without a primary.

Primaries are necessary, as only they can modify the data.

Update Server

Assignment Management

Enterprise Integration Manager (EIM)

Application Deployment Manager (ADM)

Siebel Audit Trail

Siebel Dynamic Picklists

Siebel State Model

Siebel Data Manager

Implicit joins are not used with party data.

To bring party data into a non-party business component.

To bring party data into another party business component.

To map columns in party extension tables to party business components.

Use a property on the Contact Activity Link

Use a property on the Contact business component

Use a Contact business component user property

Use a workflow policy to monitor contact records

Use a workflow triggered by a delete run-time event on the Contact business component

Web Client

Handheld Client

Mobile Web Client

Wireless Web Client

Dedicated Web Client

Any position on the team

Leader

Primary

Administrator

No child records appear for any parent.

All child records appear for each parent.

The same set of child records appear for each parent.

The view will not display the applet associated with the business component.

Assign a company to Joe.

Assign a position to Joe.

Assign a responsibility to Joe.

Assign Joe to an access group.

Install the application on his machine.

Create Joe as an employee in the application.

Audit trail

System Alerts

Siebel State Model

Component Event Logging

Both Active and Red Customer accounts, because the search results are ORed together.

Nothing, because the search results are ANDed together.

Only Active accounts, because the search specification on the business component takes
precedence.

Only Red Customer accounts, because the search specification on the applet takes precedence.

An error message, because the application detects the conflicting search specifications.

Applet

Application

Business object

Business component

Create a named subsystem (or profile).

Copy the component to inherit the original parameter values.

Right-click the Parameter Details list and select Propagate Parameters from the menu.

Select all of the parameters from one component, then copy and paste them into the other
components.

EXISTS "Marriott "

EXISTS (Marriott)

EXISTS ("Marriott")

IS IN "Marriott"

IS IN (Marriott)

IS IN ("Marriott")

Copy your local Siebel repository file to the server.

Archive your work into a .sif file and then import that .sif file into the server repository.

Check out the Opportunity project again, and then check the project back in.

Archive your work into a .sif file, check the project out, import the sif file into the local repository,
and then check the project back in.

Criteria

Rule group

Candidate

Mode

There is no explicit Join or Join Specification.

Destination Column = ROW_ID and Source Field = Id

Destination Column = PAR_ROW_ID and Source Field = Id

Destination Column = ROW_ID and Source Field = Opportunity Id

Destination Column = PAR_ROW_ID and Source Field = Opportunity Id

Modify component parameters while allowing existing component tasks to continue running using
the old parameters.

Activate reconfigured components at the next server restart.

Move server components from one server to another.

Stop all current instances of a component and restart them with new parameters.

No rows will be returned.

You will get an SQL error.

The implicit join will override this join.

All rows in the S_SRV_REQ will be returned.

All rows in the S_ASSET table will be returned.

siebel.srf

.swt file

eapps.cfg

uagent.cfg

file system file

a Siebel task

an iHelp item

a workflow policy

Siebel Activity Plan

an assignment manager rule

a workflow process to notify the manager

Create a new position and assign the set of users to it.

Blank out the sequence number for the Accounts Screen in the application object definition in
Siebel Tools.

Show the users how they can change the Screen Tab Layout in User Preferences when they log
in to the Call Center application.

Change the configuration in Siebel Tools so that the Contacts Screen Override property is set to
TRUE.

They cannot be exported.

They are created from an object type.

They are compiled into the file system.

They are displayed in the object explorer.

They are displayed in the object list editor.

They are defined by assigning values to properties.

They are edited using the client application or Siebel Tools.

You cannot copy records whose Job Title is NULL.

You must modify the JOB_TITLE column of the S_CONTACT table to make it non-nullable.

Existing contacts whose Job Title is NULL will be visible only in the contacts administration screen.

You specify the Job Title field as required by setting the Required flag to TRUE in the appropriate
applet(s).

You specify the Job Title field as required by setting the Required flag to TRUE in the appropriate
business component.

when there is only one child record in the dataset

any time you have more than one child record in the dataset

when the external system defines which child record should be the primary

when the external system does not define which child record should be the primary

Select Debug from the View > Options menu and enter the local client start-up information.

Right-click the design canvas and select Simulate, then enter the local client start-up information.

Select Simulator Options from the View > Options menu and enter the local client start-up
information.

Right-click the design canvas and select Simulate Options, then enter the local client start-up
information.

Task flow

Task view

Task applet

Task screen

Task chapters

Task group item

Create separate rule groups for each rule.

Add scores to evaluate the skills of the employees.

Add the rules to a rule group and assign the finance rule a lower sequence number.

Add the rules to a rule group and assign the finance rule to a higher sequence number.

Set the rules to be exclusive.

The views are listed only on the Site Map.

The Screen containing the views is available on the Site Map, but it is empty.

The views are only accessible through a drilldown.

The screen is not available in the application, either through a screen tab or the Site Map.

You set the Operation property to Query.

You set the Operation property to Search.

You set the Operation Property to Update.

You set the Business Object property to Service Request.

You set the Business Component property to Service Request.

activate the rule module

assign a business object

set an expiry date for the rule

set the Data Assertion Mode to runtime

synchronize the rule with the repository

select one or more rule module relations

You select Save Record from the applet-level menu.

You enter data into a field and then select a different field.

You enter data into the record and then select a different record.

You click on the form applet to enter data into a field that is not available in the list applet.

The parent tables must have a type set to Data (Intersection)

The new table will have type setting of Data (Intersection)

The new table will include two foreign key columns

The new table will include a PAR_ROW_ID column

create additional process properties

assign a value to the Business Service Name property

assign a default value to the Object Id process property

assign a value to the Business Service Method property

create input arguments by right-clicking the business service step and selecting Show Input
Arguments

create one or more output argument records for the business service and set the type to Business
Service

Business rules can be centrally developed and administered.

Business rules do not require compilation of the repository file.

Business rules are modeled using a precise graphical modeling language.

Business rules typically execute faster than repository-based configuration.

Business rules can be easily updated to implement rapidly changing business policies.

must be named siebfile

must be a single file system on a single drive

must support long and case-sensitive filenames

must be accessible from machines running Siebel Servers

You forgot to add the view to a screen.

You gave the wrong view name to the administrator.

The administrator forgot to activate the responsibility.

The administrator assigned the view to a responsibility that none of the users in Group B possess.

The administrator set the Read Only View flag to TRUE when adding the view to the responsibility.

Web Single Sign On

database authentication

Windows authentication

Directory Server authentication

The base table of the parent business component.

Standard interface tables supplied by Siebel.

Standard 1:M extension tables supplied by Siebel.

New tables that you create with the Business Component wizard.

Undo the check out and continue working locally.

Perform a Get on the project, lock it, and continue working locally.

Save your current changes as a .sif file and continue working locally.

Cancel the check out, lock the project locally, and continue working locally.

Check in the project while maintaining the lock, undo the check out, and continue working locally.

A task view step that is bound to a summary view.

A Siebel operation step to create a new account record.

A task view step that displays a view containing, at minimum, a task applet.

A Siebel operation step to create a transient business component.

A decision step that controls flow to a Siebel operation step to create a new contact.

A commit step to save each contact record entered before the user enters a new one.

You forgot to add the view to a screen.

You gave the wrong view name to the administrator.

The administrator forgot to activate the responsibility.

The administrator assigned the view to a responsibility none of the users possess.

You left the Category Name blank when you created the Screen View object definition.

The Default Local Access flag was set to TRUE by the administrator when adding the view.

It is used to lay out form applets.

It can be used to add and remove applet Web template items.

It is invoked automatically upon completion of the List Applet wizard.

Items not on the template can be imported using the Web layout editor.

Add the business component to the appropriate Access Group.

Add the business component to the appropriate responsibilities.

Set the Owner property in the business component's Properties window.

Add the necessary owner types to the Business Component View Modes list for the business
component.

A hyperlink is not added to the thread bar.

A question mark is displayed in the thread bar.

The Title property is used to populate the thread bar.

The name of the business component is used to populate the thread bar.

includes dynamic, transactional data

cannot be grouped into catalogs and categories

is created and managed by end-users of the application

access is controlled at the level of catalog and category

link

view

MVG

applet

MVG applet

business object

business component

business object component

to identify the possible candidates that can be assigned to records

to describe when a record should be assigned to candidates

to identify the types of data to assign using Assignment Manager

to evaluate all people for a matching skill in order to assign records

never

to insert data into Siebel EIM (interface) tables such as EIM_ACCOUNT

to drop tables from the database

to insert data into Siebel customer (data) tables such as S_ORG_EXT

are J2EE application servers

may run the Call Center object manager

may run the Siebel Web Server Extension

may run the Enterprise Integration manager

can only be installed on one machine in the enterprise

may be installed on several machines in the enterprise

Values are displayed from the S_LST_OF_VAL table.

They can be bounded or unbounded.

They usually display values in a pick applet for selection.

Values displayed in the picklists change during run time based on changes end-users make to
data.

It allows users to select more than one primary.

It indicates which child record cannot be deleted.

It permits users to see and change the primary child record.

It allows users to change which field is referenced in the child business component.

Create a pre-defined query.

Create a deployment session.

Use the Siebel client to create an export file.

Use Siebel Tools to export the object definition.

Move the descriptor file and object definition to the package sub-directory.

Move the updated .swt to a package sub-directory.

No records violate the policy.

The duration has been exceeded.

You ran Generate Triggers with Exec=False.

You failed to compile the Workflow Policy object.

You did not activate the workflow process specified for the policy action.

They have properties.

They have properties and values.

They are edited using Siebel Tools.

They are templates for writing SQL.

They are displayed in the object explorer.

They are displayed in the object list editor.

They are compiled into the Siebel repository file.

Independent

Organization-oriented

Person-oriented

Org & person-oriented

It can only contain single value fields.

Its data disappears once the task is paused.

Its data disappears once the task completes.

It stores one or more records in its base table.

Its data disappears once the task is cancelled.

It collects only data that is used to control task flow.

It requires a task applet to collect and display the data for a transient business component.

A Contact/College link.

A College/Contact link.

A College business object.

A College business component.

A join between S_CONTACT and CX_COLLEGE.

An intersection table between S_CONTACT and CX_COLLEGE.

Child access groups can contain only user lists.

Child access groups inherit access rights from parent access groups.

A child access group may be assigned to multiple parent access groups.

Child access groups can have more access rights than their parent groups.

Batch assignment

Dynamic assignment

Interactive assignment

Manual assignment

Compile a new .srf.

Set Keep Creator to TRUE on the Account Assignment Object.

Set Default Employee to SADMIN on the Account Assignment Object.

Set Keep Manual assigned to TRUE on the Account Assignment Object.

Set Ignore Assignment Attributes to TRUE on the Account Assignment Object.

Write assignment rules that recreate the criteria the VP used to manually assign the records.

can be created using Siebel Tools

can be activated using Siebel Tools

can be simulated using Siebel Tools

can be exported to XML files in Siebel Tools

can be exported to XML files in the Siebel Client

can be published using the Siebel Client

Delete the inherited parameter and input a new parameter.

Use the current parameter on all levels higher than the current level.

Remove the current parameter and reinstate parameter inheritance.

Override the current parameter for the next single instance of the component.

It is the default authentication method for Siebel applications.

It typically uses a single reserved database login for all users.

It requires additional infrastructure components, such as security adapters.

User authentication is performed by a third-party service at the Web server level.

Table, Business Component, Applet

Business Component, Table, Applet

Table, Applet, Business Component

Business Component, Applet, Table

Applet, Business Component, Table

Applet, Table, Business Component

A user must have at least one position.

A user must have at least one responsibility.

A user must be assigned to at least one division.

A user must be assigned to at least one organization.

A user must be assigned to at least one access group.

A user must be authenticated; for example, by having credentials such as a username and
password.

an object type

a business object

a sequence number

a business component

the name of the rule module

a business service and a method

You forgot to run a backup command.

You forgot to generate a mid-level release in Siebel Tools.

You sequenced User List before Users in the deployment.

You sequenced Users before User List in the deployment.

No Insert = TRUE and No Update = FALSE on the Opportunity business component.

No Insert = TRUE and No Update = FALSE on one of the fields of the Opportunity business
component which is displayed in the list applet but not in the form applet.

No Insert = TRUE and No Update = FALSE on the Opportunity List Applet.

No Insert = TRUE and No Update = FALSE on one of the list columns of the Opportunity List
Applet.

You failed to compile the Opportunity List Applet, hence it is still checked out and cannot accept
new data.

Your responsibility is not correctly configured; you do not have permission to see the New
Opportunity view.

They are stored in a knowledge base.

They are created using the HaleyAuthority application.

They are executed in the Business Rules Service server component.

They are executed by invoking the Business Rules Service business service.

They are automatically updated whenever the object definitions in the Siebel repository are
changed.

S_CONTACT

S_USER

S_EMP_PER

S_PARTY

to the .ifb file

in your source data

using the application administrative screens once the import is complete

to the EIM_PROD_INT and EIM_PROD_LN tables after loading the source data into them

to the EIM_PROD_INT and EIM_PROD_LN tables before loading the source data into them

Siebel Servers

Siebel Web Client

Siebel Web Server

Siebel Gateway Name Server

Mar?iot?

Mar?iot?*

Mar*iot*

IS LIKE (Mar?iot?)

IS LIKE (Mar*iot*)

Positions

Responsibilities

Persons

Organizations

Accounts

Values must be provided for these columns.

Required columns that are left blank will automatically be assigned a value of system

These columns must be changed from equired to ptional before running the EIM process

Required columns can be left blank during EIM and will be updated with default values when the
records are updated through the user interface.

The field used must be a single-valued field.

The field used cannot contain more than twelve states.

The field used should have no dependencies on other fields.

The field used should not be named in any Workflow processes.

Copy the local .srf file.

Copy the local .dbf file.

Check in projects into the server.

Use archive files to back up repository data.

You did not activate the task.

You did not clear the task cache.

You did not add the task to a responsibility.

You did not assign the task to a task group.

You did not compile the views and applets in the task.

Clicking an account record navigates you to sales team details.

Clicking a contact name hyperlink always navigates to the contact detail.

Clicking an account name navigates you to the last field of the current record in the current list.

Clicking a contact name hyperlink navigates to contact details for US contacts and account details
for non-US contacts.

Run Health Check.

Run Environment Verification Test.

Examine the Siebel Web Client registry file.

Rerun the Installation Program and select Verify.

S_PARTY table

S_ACCOUNT table

S_ORG_EXT table

S_ORG table

You will get an error because you cannot assign a manager view to someone who does not have
a manager position.

The view will not display to him since he doesn't have a manager position.

He will see the view, but he will not see any records.

He will see the view, but he will only see records for which he is the primary on the Account Team.

You cannot add extension columns to interface tables.

The new column name is automatically suffixed with _X.

The new column name is automatically prefixed with X_.

You must check out or lock the appropriate project/object definition before adding a column.

You failed to assign a Project.

You picked the wrong Web Template.

You selected the wrong Business Object for the view.

The applet object definition has Inactive set to FALSE.

The Business Component that the applet is based on is not part of the Business Object the view is
based on.

Developers should be registered as a mobile client.

Developers should be database owners of the Siebel database.

Developers must be added as an employee in the application.

Developers must be assigned the Administrator responsibility.

PAR_ROW_ID

BU_ID

EMP_ID

ROW_ID

by scheduling an activity

by a long-running workflow

by clicking a link in the task pane

by clicking an entry in the user's inbox

by navigating to the Tasks screen in the site map

by right-clicking on a view and selecting Invoke Task

Fields

Columns

Business objects

Business components

You have already checked out the project.

Another developer has already checked out the project.

Allows Object Locking is set to TRUE for this project.

You have not yet performed a Get on this project.

A Developer Web Client is running and connected to your local database.

A Developer Web Client is running and connected to your server database.

You modified the 1:Base mode.

You modified the 1:EditList mode.

You compiled All Locked Projects from Tools into the client .srf file.

You set the HighInteractivity parameter to TRUE in the client uagent.cfg.

You forgot to compile All Locked Projects from Tools into the server .srf. file.

You previously used Columns Displayed to save a set of columns for the applet that did not
include that column.

in the Start step properties

on the branch following the start step

in the Siebel Operation step properties

on the branch following a Siebel Operation step

delete a division

remove an organization

change a division's organization

change the name of an organization

in cascading style sheets

in Siebel configuration files

in Siebel Web template files

in Siebel Web Server Extension files