My Oracle Support Banner

Why Does Siebel Systems Not Support Calling Undocumented Methods in a Custom Script or Using Undocumented User Properties? (Doc ID 747177.1)

Last updated on NOVEMBER 22, 2019

Applies to:

Siebel Tools - Version 7.5.1 [15026] to 8.0.0.4 [20417] [Release V7 to V8]
Information in this document applies to any platform.
Checked for Relevance on 27-Feb-2013

Goal

Introduction

Many Siebel application objects contain specialized methods to perform certain functionality on an applet or business component. Often, these methods are visible in Siebel Tools, in the Method Invoked property of a button on an applet. However, as noted in Siebel Bookshelf > Siebel Object Interfaces Reference > Interfaces Reference, Siebel Systems does not support calling specialized methods from within a custom script or through custom buttons, unless the method is explicitly documented in Siebel Bookshelf. Similarly, Siebel Systems does not support using undocumented User Properties in your configuration. This is noted in Siebel Bookshelf > Siebel Developer's Reference > User Properties > About User Properties.

The main reason why Siebel Systems does not support this technique is that undocumented methods or user properties may, without prior notice, change their behavior or become obsolete in future versions of the Siebel application.

Another reason is that undocumented methods might require a certain execution context or a certain set of input arguments in order to work correctly. For example, a given method might only run on a particular applet, or only when the business component has been queried and contains at least one record.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.