We have seen lot of out-of-the-box Siebel list applets with Show More/Show Less button which is placed at top right corner. In a recent implementation I had to do the same thing on custom Siebel List Applets. Here is how I did it.
1) Create a Control in your list applet with the below properties:
| Name: |
ToggleListRowCount |
| Caption: |
ToggleListRowCount |
| HTML Bitmap: |
BTTNS_MORE |
| HTML Display
Mode: |
EncodeData |
| HTML Icon Map: |
ToggleListRowCount |
| HTML Type: |
Link |
| Method
Invoked: |
ToggleListRowCount |
2) Edit the Web Layout and place this control at the end in the buttons bar.
3) Compile your changes.
There are 2 ways we can do Clear Cache using eScript:
1) By invoking method "ClearLOVCache" of "List Of Values" BC
- This method can be used with button controls on any applet based on BC "List Of Values", since this method is available under the business component "List Of Values".
- This method can also be invoked from other Applet, BC, BS scripts by using below code.
var oBO = TheApplication().GetBusObject("List Of Values"); var oBC = oBO.GetBusComp("List Of Values");
oBC.InvokeMethod("ClearLOVCache");
2) By using OOTB Business Service (Undocumented)
- Business Service Details
- BS Name: LOV Cache Clear Service
- Method: Activate (This method does not require any input arguments which is logical)
var bsSvc = TheApplication().GetService("LOV Cache Clear Service");
var psIn = TheApplication().NewPropertySet();
var psOut = TheApplication().NewPropertySet();
bsSvc.InvokeMethod("Activate", psIn, psOut);
- This Business Service also has another method 'RestoreActivate', use of which is not known to me yet.
- I also found out that Application Deployment Manager (ADM) invokes this business service to clear LOV cache after the deployment.
Define dependency between fields by using the user properties of the integration component field. The names of these user properties must start with FieldDependency, and it is recommended that the value of each property contain the name of the field on which the associated field is dependent. The EAI Siebel Adapter processes fields in the order defined by these dependencies, and generates an error if cyclic dependencies exist.
The EAI Siebel Adapter automatically takes into account the dependencies of the fields set by a PickList on the fields used as constraints in that PickList. For example, if a PickList on field A also sets field B, and is constrained by field C, then this implies dependencies of both A and B on C. As a consequence, the EAI Siebel Adapter sets field C before fields A and B.
User Property Name: FieldDependency<field_name>
Value: Any active integration component field name within the same integration component
For the complete list Of Integration Object User Properties, refer to bookshelf.
