Ignore Permission Errors OnDelete

This Integration component user property set to Y can be used to suppress the errors that arise from having the NoDelete user properties set to Y.


The error is ignored and processing continues.

For Example,

An Integration Object : Order Entry Orders IO has two Integration Components :

Order Entry - Orders and

Order Entry - Line Items (Parent IC : Order Entry - Orders)

Generally Orders have multiple line items.

If an Inbound request XML message contains Order record details ; and only few Line Item Record Details (Not all line items).

And if this input is passed to 'EAI Siebel Adapter' Business Service and Method Update

This Operation will update only the line Items as mentioned in Input XML message ; but will delete the line items which are not mentioned in XML Message

Only use of IC user Property NoDelete was giving errors.

To avoid this use Integration Component User Property for IC Order Entry - Line Items

NoDelete with value Y and IgnorePermissionErrorsOnDelete with value Y

Pick List User Keys

In case of dynamic picklists, pick map may bring many fields,One of the tasks the integration object designer needs to perform is to determine which of these fields is used to identify the required field.


For example:
Consider a field Accout which is a dynamic picklist and contains many fields such as Account, Account Location, Account Integration Id, Currency Code,Price List, and so on

If the PicklistUserKeys user property on the integration component field that is mapped to the field with the picklist (in the example above: Account) is not defined, then any integration component fields that are mapped to columns in the U1 index of business component's base table, and are present in the pickmap will be used by the EAI Siebel Adapter to find the matching record in the picklist. (In the example above, this would be Account and Account Location.)

In cases where the default user key for the picklist does not satisfy your business requirements (for example, Account Integration Id should be solely used instead of the default user key to pick an Account), or you want to make the user key explicit for performance reasons, then use the

PicklistUserKeys user property.

Syntax for Integration component Field User Property:

Name: PicklistUserKeys Value : PickmapFieldname

Eg: Name: PicklistUserKeys Value : Account Integration Id

To Open a Popup window

Business Requirement: Customer wanted to open a new IE window from within Siebel and freeze Siebel application until the new window is closed.


Technical Solution: Used Siebel browser-script function theApplication().ShowModalDialog() to achieve this requirement.The function "theApplication().ShowModalDialog()" opens a new IE window from within Siebel and does not allow any operation in Siebel application until the new IE window is closed.

The syntax for ShowModalDialog() function is as follows:

TheApplication().ShowModalDialog(sURL [, vArguments] [, sFeatures])

Loading Account Parent-child hierarchy during the Initial Load into UCM

The way to do this in Siebel UCM 8.0 is to use the EIM_UCM_ORG table (one record per account), filling the PAR_OU_ID field with the ROW_ID of the related parent account. This entails the need to load parent accounts before respective children, and get their ROW_IDs. One tiny possible configuration is to add an EIM Foreign Key Mapping for the field S_UCM_ORG_EXT.PAR_OU_ID. This way, it would be possible to specify the parent account using its user key values (name, location, and organization) instead of the ROW_ID.


The attached document describes this change ("How To Add an EIM Foreign Key Mapping for S_UCM_ORG_EXT.PAR_OU_ID.doc").

But take into consideration that Oracle Siebel Expert Service must be involved before applying it in a production environment, since a modification to the S_UCM_ORG_EXT.PAR_OU_ID base table column is needed.

Restrict the Entry of Characters in a List Column or Control

The length of the fields can be restricted on the application UI level with the help of the Field User Property called Text Length Override. Below is the syntax for configuring this Field User Prop:


Name: Text Length Override

Value:

For example, if the requirement is to restrict the 'Description' field in the 'My Opportunities View' to 10 characters, then perform the following steps:

Log into Siebel Tools.

Query for the Opportunity business component, expand to its child object Field, and then query for field "Description".

Expand to this field child's object Field User Prop and add a new record.

Specify the properties Name as Text Length Override (Case is Important) and value as 10.

This user property is restricted for Text type fields. This cannot be used for Number type fields

Workflow monitor agent controls

The Action Interval parameter of Workflow Monitor Agent is always controls, how the Action should be executed.


1) Just Navigate to Sitemap-> Administration->Server Configuration->Enterprises->Component Definitions->Choose Workflow Monitor Agent Component.

In the Component Parameters List choose Action Interval and check the default value is “3600” seconds (This is the default value to Action Interval Parameter).

2) Change the default value to 60. It means depending on the value of the Action Interval parameter for Workflow Monitor Agent, the action is taken.

3) Once Workflow Monitor Agent performs an action on the record in violation, an entry is logged into the S_ESCL_LOG table. If the same record comes into violation again within the Action Interval time, the Workflow Monitor Agent will not perform the action again on the same record. It will only remove the row from S_ESCL_REQ table. As a result, it is possible that Workflow Monitor Agent clears many records from the S_ESCL_REQ table for which no actions have been performed.

4) Setting the Action Interval = 0 is not recommended by Siebel Systems because the following behaviors have been observed to occur with this setting:

-> Actions performed for rows in S_ESCL_REQ without checking if conditions are met or not.

-> Actions do not get executed at all at times.

-> Duplicate actions occur for the same record.

-> Performance issues occurs because this setting causes Workflow Monitor Agent to be busy all the time. Thus, Workflow can cause resource crunch in terms of CPU utilization and memory, etc.