Siebel and PeopleSoft Enterprise Applications

In PeopleSoft, PSDBFIELD is the system catalog table that stores the definitions of all fields used to create page controls and database columns.

PeopleSoft Application definitions (records, pages, menus, etc.) are stored in PeopleTools tables, which are system tables that store metadata about application objects. Application Tables store actual business data, and System Catalog is a database-specific concept.

Application data is cached on the Application server to improve performance. This cache reduces database hits by storing frequently accessed data in memory. Web servers handle HTTP requests, and Batch servers process background jobs.

The Reasonable Date property validates that dates are within an acceptable range (like not more than 30 days from current date). It prevents users from entering unrealistic dates. Required, Default, and Constant settings don't perform this date range validation.

PeopleSoft uses the prefix 'PS' followed directly by the record name (e.g., PSRECORDNAME) for its internal system tables, distinguishing them from application tables which use 'PS_'.

With a Default Century setting of 50, entering a two-digit year from 00 to 50 causes PeopleSoft to default the century to 2000 (resulting in years 2000-2050).

Selecting the 'Search Edit' property on a PeopleSoft record field forces the system to validate the data entered in that field when the search dialog is saved or executed.

Mobile Web Clients and Handheld Clients run locally on user devices and require local configuration (.cfg) and Siebel Repository File (.srf) files to execute the application offline.

The statement 'Picklist values change at runtime' is NOT true for static picklists - static picklists have fixed values that are defined at design time and do not change during application execution. This is what distinguishes them from dynamic picklists. Options B, C, and D are true characteristics of static picklists (they can be bounded/unbounded, derive from List of Values, and are based on Picklist Generic Business Component).

In Siebel, Link is a child object of the Project or Application level, not a child of the Business Component object. Joins are child objects of Business Components, making the statement false.

In Siebel CRM, Accounts, Contacts, and Opportunities are major transactional entities that support multi-value group assignment to a team of users. Service requests do not use this team assignment model.

Siebel Web Clients and Wireless Web Clients connect to the Siebel Application Object Manager via a web server (using the Siebel Web Server Extension). Dedicated Web Clients connect directly to the database.

Dedicated Web Clients, Wireless Web Clients, and standard Web Clients all directly access and interact with the server database. Mobile Web Clients, conversely, primarily access a local database.

Mobile Web Clients and Handheld Clients in Siebel rely on local databases to operate offline. Consequently, they require periodic synchronization with the main enterprise server database to keep data consistent.

The Siebel Gateway Server must be running during Siebel Server installation because it acts as the communication gateway and handles name resolution for Siebel Enterprise. The installation process requires it to be available to register and configure the new Siebel Server properly. This is a standard Siebel architecture requirement.

In Siebel's architecture, Business Component is the layer that contains business logic and data access for a specific business entity. View is the UI presentation layer, Applet is the UI container, and Business Service contains reusable business logic methods. Only Business Component (C) represents the business objects layer.

In Siebel personalization, a rule set specifies the search specification condition that determines when the rule applies. Options A, C, and D describe different aspects: order condition determines execution sequence, set of actions defines what happens, and set of events triggers evaluation. Only Search Specification (B) defines the matching criteria.

Standard Extension database columns in Siebel are custom columns that developers can add to extend base tables. They are always prefixed with 'X_' to distinguish them from standard Siebel columns. Option B is correct: they are prefixed with 'X_'. Option A is incorrect (type is not private data), Option C is misleading (they are for developer use but not provided by Siebel), Option D is incorrect (they can be edited).

In Siebel assignment rules, the criteria with the highest score has the most importance. Given scores: Product=10, Country=15, Language=5, Country has the highest score (15) and therefore is the most important criteria. Higher score = higher priority in assignment matching.