siebel-development（西贝尔发展）

Siebel Development

Development Workflow

For any Siebel requirement, follow this approach. To start, use the New Requirement Workflow.

1. Understand - Clarify the business requirement and identify affected objects
2. Design - Choose the right approach (Configuration vs Scripting vs Workflow)
3. Implement - Build using appropriate Siebel tools
4. Test - Validate in Siebel client
5. Document - Create implementation notes

Coding Standards

🚨 MANDATORY: Always use Oracle Courseware Style. See Coding Standards.

Decision Guide

🧭 Decision Principles

When answering, the agent should:

• Prefer configuration over scripting
• Prefer server-side logic over browser script
• Avoid performance-heavy patterns by default
• Clearly state trade-offs when multiple solutions exist
• Highlight risks in production scenarios

🎓 Answer Style

• Explain WHY before HOW
• Use enterprise terminology
• Assume production scale
• Mention performance and maintenance impact
• Avoid tutorial-style explanations unless asked

Quick Patterns

Trigger Workflow on Record Save

1. Create Workflow (Business Object = target BO)
2. Create Runtime Event: Object=BusComp, Event=WriteRecord
3. Create Action Set: Service=Workflow Process Manager, Method=RunProcess

Call REST API from Siebel

1. Create Business Service with eScript
2. Use EAI HTTP Transport: SendReceive method
3. Set: HTTPRequestURLTemplate, HTTPRequestMethod, HTTPContentType

Open UI: Conditional Display by User Profile

1. Get SessionAccessService, call GetProfileAttr
2. Check resultSet.GetProperty("Value")
3. Show/hide UI based on result

→ Full patterns: Open UI Patterns

Reference Files

Key Siebel Objects Hierarchy

Application
└── Business Object (BO)
    └── Business Component (BC) ──► Table
        ├── Fields ──► Columns
        ├── Links ──► Parent-Child relationships
        └── Applet ──► UI display

Skill-Building Framework (Mentorship Mode)

For complex requirements, create a skill_building.md using this 8-section framework:

1. Requirement Breakdown - Rewrite in simple technical terms
2. Impact Analysis - Identify ALL impacted objects
3. Implementation Strategy - Step-by-step in correct sequence
4. Skill Upgrade - Concepts this strengthens
5. Edge Cases & Performance - Possible issues
6. Testing Strategy - Unit and negative tests
7. Deployment Checklist - Pre/post checks
8. Interview Angle - How to explain in interview

Repository Organization

Requirement Folder Structure

domain-name/
├── README.md           # Analysis, decision, interview guide
├── implementation.md   # Implementation steps & code
├── testing.md          # Verification steps
└── assets/             # Screenshots, diagrams

Best Practices Summary

1. Configuration over Scripting: Prefer User Properties, Calculated Fields, Workflows
2. Naming Convention: Use X_ prefix for custom columns
3. Open UI: Use Plugin Wrappers for field changes; PR for layout
4. Testing: Test in all supported locales
5. Manifest: Double-check registration—silent failures common
6. Code Style: Follow Oracle Courseware patterns