Siebel Open UI Adv JavaScript API — Lesson 2: JavaScript API, Events, Manifest, and Custom Controls

Technical Scope

• Open UI JavaScript API, PM properties, methods, notifications, and event attachment
• manifest administration, expressions, files, sequence, usage type, and conditional loading
• custom controls, templates, third-party libraries, DOM isolation, and accessibility
• event duplication, load-order conflicts, browser compatibility, and controlled correction

Instructor Demonstration

The instructor diagnoses Open UI JavaScript API, PM properties, methods, notifications, and event attachment, then connects it to manifest administration, expressions, files, sequence, usage type, and conditional loading. The demonstration captures the exact configuration, transaction, command, query, log, or screen evidence needed to prove intended behavior and the applicable control boundary.

Applied Workshop

Learners build and verify an implementation covering manifest administration, expressions, files, sequence, usage type, and conditional loading and custom controls, templates, third-party libraries, DOM isolation, and accessibility. The exercise introduces a realistic exception related to event duplication, load-order conflicts, browser compatibility, and controlled correction and requires a reversible correction supported by before-and-after evidence.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration or analysis and record exact steps.
3. Validate functional behavior, security, data integrity, and operational observability.
4. Introduce the defined failure condition, diagnose the cause, and apply a safe correction.
5. Document rollback, acceptance evidence, unresolved risk, and ownership.

Validation Standard

Acceptance requires accurate handling of custom controls, templates, third-party libraries, DOM isolation, and accessibility, traceable proof for Open UI JavaScript API, PM properties, methods, notifications, and event attachment, and a repeatable recovery path for event duplication, load-order conflicts, browser compatibility, and controlled correction. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when event duplication, load-order conflicts, browser compatibility, and controlled correction occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested javascript api, events, manifest, and custom controls implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.