Informatica and PEGA Platform Fundamentals

To add a property to a Section rule, you can drag property-related controls (Input Box, Radio Button, etc.) into the section and associate them with a property, or directly drag the Property from Application Explorer. Updating HTML property rules or dragging Label controls are not valid methods for adding properties to sections.

When configuring a runtime Ruleset list, Pega evaluates rules from top to bottom. Placing specific rulesets above general ones ensures that specialized rules are found and executed first.

In Pega, properties are rules. They are subject to rule resolution and can be overridden in different rulesets or ruleset versions to specialize behavior.

The Section rule in PRPC contains the Auto-Generate HTML feature, which automatically generates the HTML for the section's UI elements. Gadgets, HTML Properties, and HTML Fragments do not have this auto-generation capability - sections are specifically designed for visual UI layout with HTML generation.

When configuring a Repeat Row layout in Pega, you must specify a Page List or Page Group property as the source, and define the class of the pages contained within that list or group.

In Pega, Router, Notify, and Utility shapes in a flow diagram reference Activity rules to perform their respective backend processing, routing, and notification tasks.

In Pega PRPC, ruleset prerequisites are configured in the Ruleset Version rule. This defines which rulesets must be present for this ruleset to function properly. Application rules reference rulesets but don't configure prerequisites. Access Group Instances control user access, not ruleset dependencies.

Pega Rule Resolution first searches rulesets listed in the user's Access Group. When 'Available Production Rulesets' is enabled in the Access Group, those rulesets get highest priority. Application Rulesets are searched after Access Group rulesets. This ensures production rules override development rules during runtime.

Connector Activities in Pega reference a connector rule (which defines the external system interface). They are invoked in flows using the Integrator shape. They do not always use Stream rules (only when streaming large data). They should be created in the class where the integration logic belongs, which may differ from the connector rule's Data- class.

Pega Rule Resolution uses: the operator's RuleSet list (from Access Group) to determine available rulesets, the rule name to identify candidates, and Circumstance values for situational variants. Last update date is not used (it's not a selection criterion). Short Description is documentation text, not a resolution factor. The rule with highest specificity (ruleset, version, circumstance) wins.

Rule Check-in requires identifying which ruleset the rule belongs to (Ruleset Name) and who is performing the check-in (Operator ID). Application Rule is the rule itself, not a check-in field. Ruleset Version is typically auto-generated or managed separately, not required for the check-in action itself.

Step page names must be specified when the current step operates on a different page context than the activity's primary page. This is necessary when working with page lists, page groups, or any embedded pages. Specifying step pages 'always' or 'never' would be incorrect - it depends on the specific step's context.

Both Case statements and Validation components can be used to validate data in different contexts - Case transformation validates data conditionally, while Validation is a dedicated validation mechanism. SQL is for queries, Query is for data retrieval, not validation.

Merge transformation does NOT produce default groups automatically. All groups must be explicitly defined - if no groups are specified, all rows go to a single output, not a default group.

Data Transfer is NOT used to delete and insert data - it handles bulk data movement between sources. The delete-then-insert pattern describes specific update strategies, not the general Data Transfer transformation.

The Query transformation is used to evaluate expressions in ETL workflows. It allows dynamic computation and conditional logic. SQL is for database queries, Pivot reshapes data, Case handles conditional branching.

Table comparison transformation in ETL tools like Informatica produces four record types: Insert (new rows in target), Update (changed rows), Delete (rows removed from source), and Normal (unchanged rows that pass through). The Normal flag identifies rows that matched but had no changes, which is useful for auditing and tracking processing statistics.

TYPE1 SCD mappings in Informatica can be created either using the built-in Slowly Changing Dimension wizard (which generates the framework) or manually (by designing the transformation logic yourself with lookup, update strategy, and other transformations). Both approaches are valid.

In databases, sequences are typically accessed using CURRVAL to get the current value and NEXTVAL to increment and get the next value. The question asks about accessing existing sequence values, and CURRVAL is the standard SQL function for retrieving the current sequence value without incrementing it.