Siebel

How To Uncompress Files in the Siebel File System with the Original File Names?

The Siebel File System stores all file attachments in a compressed format with a proprietary naming convention. Neither Siebel InterActive nor the Fulcrum SearchServer can access or read these files directly. If either of these modules is used, maintain a copy of all file attachments in an uncompressed format in a separate directory accessible to SearchServer or Siebel InterActive.

How to split up the Siebel filesystem with sfspartition in Siebel 8

Bookshelf 8.0,
Siebel System Administration Guide > Siebel Server Infrastructure Administration > Administering the Siebel File System >
Partitioning the Siebel File System

is using wrong parameters - Change Request 12-1LMZIFJ
has been logged to correct this, but was closed without implementing changes in bookshelf, as it focussed on functionality issues.

Debugging Profile Attribute

There would have been umpteen number of situations where you might have felt the need for an easier way of debugging profile attributes than logging the values in a script, haven't you?.If yes, then here is a much simpler way and you can do this on the fly.
When the web client is up, replace the URL with the following script:

Limit Text Field Length - Text Length Override

User is using a column "PROTOCOL_NAME" (varchar-100) to store the value entered in the Field "Name"(varchar-30) but can enter more than 30 characters.
It seems intuitive that a field attribute called "Text Length" would set a limit to the amount of text that could be entered into a field.

Refresh an applet instead of the Business component

User wants to update the data being displayed on UI after performing some validation and updates via a script on the underlying BC.

Solution:

A vanilla Business Service “FINS Teller UI Navigation” can be used to refresh an Applet after updating the underlying data, without breaking the current query.

Approach:

Identify drilldown list columns for Validations : SWEField

We may need to perform certain operation/validation when user drilldown on a particular field in a List Applet.
Vanilla provides a method Drilldown at applet level which can be captured.
The problem here is if there are more than one drilldown list column in applet, clicking on any of them will trigger our validation logic.
 
Solution :
The Workaround to the problem is to use the SWEField property pas
Recent content