SBL-UIF-00401: View: %1 does not contain applet: %2.

APPLIES TO:

Siebel Tools - Version 8.0.0.2 [20412] and later
Information in this document applies to any platform.
Checked for Relevance on 05-Aug-2013

GOAL

In log files generated by their customized Siebel application the customer noticed multiple errors like the following:
- - -
SBL-UIF-00401: View: xxx does not contain applet: yyy.
- - -

They determined that these errors are generated while accessing a view with several dynamic applet toggles. They found then the following information in the Bookshelf version 8.0:

Configuring Siebel Business Applications > Configuring Screens and Views >About Applet Toggles
- - -

# You cannot configure more than one applet toggle in a view.

CAUTION:  Only one static applet toggle is supported in each view. If you create more than one applet toggle in a particular view, unpredictable behavior might occur. Instead, you can use detail views with the Parent Category property set to Detail Category to access multiple views. For more information, see About Screen Views.

# You cannot use a static and a dynamic applet toggle in the same applet.
...
- - -

They were unclear if the sentence "You cannot configure more than one applet toggle in a view" applies to both dynamic and static applet toggles or to static applet toggles only. They wanted to know if their configuration was supported or not.

SOLUTION

The error:
- - -
SBL-UIF-00401: View: xxx does not contain applet: yyy.
- - -

appears also in log files generated by standard Siebel application if you access a view containing an applet that has dynamic applet toggles and a toggle is triggered. An example is the standard view 'Account Detail View' (labeled "More Info") in screen "Accounts Screen". This view contains the applet 'Account Profile Applet' that has several applet toggles.

This error is benign and can be ignored therefore.

Note also that the sentence:
- - -
# You cannot configure more than one applet toggle in a view.
- - -

apples to static applet toggle only.

It is indeed supported to have multiple dynamic applet toggles in a single view and it is also supported to have one static applet toggle and multiple dynamic applet toggles.

BUG 10562399 has been logged asking to clarify this matter in the Bookshelf. UPDATE: This information has now been added in the Bookshelf version 8.0 and 8.1.

On the other hand it is important to be aware of potential performance impact of using applet toggles, particularly dynamic toggles. This matter is discussed in the Bookshelf:

Siebel Performance Tuning Guide
Tuning Customer Configurations for Performance
Best Practices for User Interface Objects Layer
Maintaining Performance When Using Applet Toggles

APPLIES TO:

Siebel Tools - Version 7.7.2.5 [18368] and later
z*OBSOLETE: Microsoft Windows Server 2003
Database: Microsoft SQL Server 2000 SP4
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-3053292323.
”Checked for Relevance on 29-01-2013”
**Checked for Relevance on 04-07-2014**

GOAL

Is there a way to remove SBL-UIF-00401: View: XYZ does not contain applet: .(dot) from OM log file.

SOLUTION

OM Log error " SBL-UIF-00401 " can be ignored and that is the only work around at this stage.

APPLIES TO:

Siebel Tools - Version 7.8.2.3 [19221] and later
Information in this document applies to any platform.

SYMPTOMS

When attempting to navigate to the "All Agreements" and "All Agreements Across Org" views the displayed data is not being filtered with correct visibility settings and the following error occurs in the log file.

ERROR
-----------------------
SBL-UIF-00401: View: Agreement List View does not contain applet: Agreement List Applet No Parent.

The issue can be reproduced by navigating to either the "All Agreements" and "All Agreements Across Org" view in the customer application.

CAUSE

The unexpected behavior was due to misconfiguration of the Visibility Applet property for the views Agreement List View and All Agreements across Organizations. The views objects were incorrectly configured to reference a Visibility Applet called "Agreement List Applet No Parent". No such applet was configured to appear on these views.

This resulted in the errors:

SBL-UIF-00401: View: Agreement List View does not contain applet: Agreement List Applet No Parent.
SBL-UIF-00401: View: All Agreements across Organizations does not contain applet: Agreement List Applet No Parent.

Due to the errors, the correct SQL query was not executed to populate the view with data relating to the correct visibility for the views.

SOLUTION

The view objects were incorrectly configured to reference a Visibility Applet called "Agreement List Applet No Parent". It was advised to review the configuration of the view objects and ensure the Visibility Applet property was correctly set.

It was suggested that the appropriate value should have been "Agreement List Applet No Parent - Read Only" as this was the only list applet appearing on the views.

After reconfiguring the view objects to have the correct value for the Visibility Applet is was confirmed that correct visibility was being applied in all the views and expected agreement records were now visible to the user.

APPLIES TO:

Siebel Tools - Version 7.8.2 [19213] and later
Information in this document applies to any platform.
*** Checked for relevance on 07-NOV-2011 ***
Error Message Area:UI Framework - UIF
Version:Siebel 7.8
""CHECKED FOR RELEVANCE ON 13-JUN-2013""

PURPOSE

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00401: View: %1 does not contain applet: %2.

SCOPE

This document is informational and intended for any user.

DETAILS

Explanation

1. Either the applet is not set as a View Web Template Item or is not set as an Applet Toggle in the repository.

2. If you are using eMail Response and the Spell Check feature is enabled you will encounter this error if you have made modifications to the name of the Comm Outbound Item Form Applet as this applet is used by Spell Check.

Corrective Action

1. Set the applet as a View Web Template Item or an Applet Toggle in the repository.

NOTE: The following bookshelf reference is also applicable to the version listed in the header of this error message documentation.

For more information on View Web Template Items, refer to Siebel Bookshelf version 7.8 > Object Types Reference > Siebel Object Types > View Web Template Item.

For more information on Applet Toggles, refer to Siebel Bookshelf version 7.8 > Object Types Reference > Siebel Object Types > Applet Toggle.

2. You should not modify the name of this applet if you want to enable Spell Check in the eMail Response views as the name of the applet is hard coded in the Spell Check functionality

Change Request 12-MAEFZJ has been logged to address this documentation enhancement request.

APPLIES TO:

Siebel Tools - Version 7.5.3 [16157] and later
Information in this document applies to any platform.
Error Message Area:UI Framework - UIF
Version:Siebel 7.5.3
""CHECKED FOR RELEVANCE ON 28-MAR-2013""

PURPOSE

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00401: View: %1 does not contain applet: %2.

SCOPE

This document is informational and intended for any user.

DETAILS

Explanation

1. Either the applet is not set as a View Web Template Item or is not set as an Applet Toggle in the repository.

2. If you are using eMail Response and the Spell Check feature is enabled you will encounter this error if you have made modifications to the name of the Comm Outbound Item Form Applet as this applet is used by Spell Check.

Corrective Action

1. Set the applet as a View Web Template Item or an Applet Toggle in the repository.

NOTE: The following bookshelf reference is also applicable to the version listed in the header of this error message documentation.

For more information on View Web Template Items, refer to Siebel Bookshelf version 7.8 > Object Types Reference > Siebel Object Types > View Web Template Item.

For more information on Applet Toggles, refer to Siebel Bookshelf version 7.8 > Object Types Reference > Siebel Object Types > Applet Toggle.

2. You should not modify the name of this applet if you want to enable Spell Check in the eMail Response views as the name of the applet is hard coded in the Spell Check functionality

Change Request Bug Id 0477343 has been logged to address this documentation enhancement request.

SBL-UIF-00359

APPLIES TO:

Siebel Marketing - Version 8.1.1.6 SIA [21233] and later
Information in this document applies to any platform.

SYMPTOMS

On : 8.1.1.6 SIA [21233] version, Siebel Marketing

When attempting to save list record, inconsistent error message shows up.
the following error occurs.

ERROR
-----------------------
When saving using on the List Form :
"'List Name' is a required field. Please enter a value for the field.(SBL-DAT-00498)"

When saving on the Form applet :
"Please use the file selection menu to select a file.(SBL-UIF-00359).

STEPS
-----------------------
The issue can be replicated if you follow the steps below:
1. Go to Site Map > List Management > Lists.
2. Click New on the list applet.
3. Save the record without populating any field. Error message displayed is "'List Name' is a required field. Please enter a value for the field.(SBL-DAT-00498)"
4. Click OK to close the error message. Do not undo the record.
5. Go to the bottom applet (form applet) and save again the record without populating any field. Error message displayed is "Please use the file selection menu to select a file.(SBL-UIF-00359).

CAUSE

 This behavior has been reproduced internally and Bug has been raised to address this.

SOLUTION

 See Bug:14333724 - INCONSISTENT ERROR MESSAGES DISPLAYED WHEN SAVING RECORD IN LIST MGMT

APPLIES TO:

Siebel Tools - Version: 8.x - Release: V8
Information in this document applies to any platform.

SYMPTOMS

Customer has upgraded from 7.0 to 8.0. In Siebel 8.0, while trying to attach files, if the user types in the File Name, instead of selecting the file from “Add Attachments” dialog box, the following error message is displayed:

“Siebel Error Message SBL-DBC-00111: An error has occurred writing to a record. Please continue or ask your systems administrator to check your application configuration if the problem persists.”

Whereas in Siebel 7.0, if the same action is done, the following error message is displayed:

“Siebel Error Message SBL-UIF-00359: Please use the file selection menu to select a file.”

CAUSE

The reported behavior by the customer seems to be a new product defect in Siebel 8.0. The same behavior was reproducible Standard 8.0. with the following steps:

1. In "Service Request Attachment List Applet", creat a new record from Applet Menu.

2. Type in some characters for the "Attachment Name" column and try to save it.

3. It will the same error (SBL-DBC-00111) that the customer has mentioned.

Then, on testing in Standard 7.8, following the same steps as above, got a different error message like below, which is much more readable format for end-users:

"Siebel Error Message SBL-UIF-00359: Please use the file selection menu to select a file."

Hence the behavior reported by the customer should be a product defect in 8.0.

SOLUTION

A new bug #- 12-1PG85NN has been logged to address this behavior. Please note that bugs will be considered and prioritized only for future releases.

As a workaround, you may consider writing a script in PreWriteRecord of the Attachment BC to generate an error message as required. For example:

function BusComp_PreWriteRecord ()
{
if (this.GetFieldValue("ActivityFileDeferFlg")== "")
{
TheApplication().RaiseErrorText("Please use the file selection menu to select a file.");
return (CancelOperation)
}
return (ContinueOperation);
}

APPLIES TO:

Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372]
Database: Oracle 9.0.1.0
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-3276810871.

SYMPTOMS

We are getting an error "Please use the file selection menu to select a file. (SBL-UIF-00359)" when saving a New List in List Mgmt. The error only occurs when the user tries to save from the form applet; the list applet does not receive the error. We have experimented with the Form applet class and the behavior is only on the CSSSWEFrameFileFINSListMgmt and CSSSWEFrameFileListMgmt classes. We also see in Siebel Support numerous change request in other modules for various releases with a similar issue. Do these change request extend to List Mgmt?

SOLUTION

Message 1

For the benefit of other users:

The reproted behavior was reproduced inhouse by following the below mentioned steps:

1. On the FINS List Mgmt Lists Entry Applet make a “Region” field displayed required in the List Mgmt Lists BC.
2. Compile List Mgmt Lists BC
3. Navigate to the My List Mgmt Lists View in List Mgmt.
4. Select NEW Button or CTL+N
5. From the lower form applet (FINS List Mgmt Lists Entry Applet) select SAVE RECORD (CTL+S)

You will get the incorrect error message SBL-UIF-00359. If you select CTL+S from the LIST APPLET ABOVE (List Mgmt Lists List Applet) you will get the correct message "'Region is a required Field... (SBL-DAT-00498)"

To address this issue I have logged CR “12-1IAUGW9 - FINS List Mgmt Lists Entry Applet applet displaying incorrect error message” and associated to this service request.

As a workaround, now to overcome the issue, you may follow any of the below mentioned option:

1. If your business permits, disable the Menu Item – Save in the “FINS List Mgmt Lists Entry Applet”
2. You can have your own custom Alert message in Browser Script tp display "required" error message.

APPLIES TO:

Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Fin Svcs
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4

This document was previously published as Siebel SR 38-1850892562.

SYMPTOMS

SBL-UIF-00359, SBL-DAT-00498

We have an issue with creating "New URL" on Attachment Applets when there are required fields. If I add a "New URL" and then try to step off the record, without the required field being populated, I get the following error message:

"Please use the file selection menu to select a file.(SBL-UIF-00359)"

This is incorrect behaviour, as I would expect the required field message to be shown.
Also, this does not occur when using 'New File' function which produces a correct message.

Please advise. 

SOLUTION

Message 1

For the benefit of other readers:

The behavior described by the customer is reproducible using a standard Siebel environment version 7.7.2 SIA and the sample database. The steps are the following:

Using Tools:
----
- In 'Account Attachment' BC set the 'Required' property of field 'Comment' to TRUE.

Using Siebel application:
----
1. In Siebel application go to Accounts > Attachments
2. Create a new record using the "New URL" button and save it:
> You will get this error that is not appropriate:
----
Please use the file selection menu to select a file.(SBL-UIF-00359)
----

3. Click the "New URL" button again or the "Query" button:
> The correct message will be displayed:
----
Comment is a required field. Please enter a value for the field.(SBL-DAT-00498)
----

The behavior is as expected when the "New File" button is used.

This behavior is not specific to 'Account Attachment' BC. It is for example also reproducible with 'Contact Attachment' BC. Note that it is the same in version 7.7 SEA.

Change Request 12-VSCWP4 has been logged to address this product defect.

'Account Attachment' BC is based on specialized class CSSBCFile and 'Account Attachment Applet' is based on specialized class CSSFrameListFile. The behavior observed cannot be changed via standard configuration or scripting.

[...]

Message 2

[...]

Note that a similar issue related to BC 'Action Attachment' in version 7.5 is discussed in posting 38-896713951. Change Request 12-F2PSUK has previously been logged to address this issue that has been fixed in Siebel application version 7.7.

APPLIES TO:

Error Message Area:UI Framework - UIF
Version:Siebel 7.8

PURPOSE

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00359: Please use the file selection menu to select a file.

SCOPE

This document is informational and intended for any user.

SBL-UIF-00359: PLEASE USE THE FILE SELECTION MENU TO SELECT A FILE.

Explanation

When doing a file upload, either the user has not selected a file to upload, or tries to upload an empty file.

Corrective Action

Please inform the user that he needs to select a non-empty file in order to successfully upload the file.

SBL-UIF-00348: Method %1 is not allowed here.

APPLIES TO:

Siebel Tools - Version 7.8.2 [19213] and later
Information in this document applies to any platform.
*** Checked for relevance on 30-OCT-2011 ***
Error Message Area:UI Framework - UIF
Version:Siebel 7.8

PURPOSE

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00348: Method %1 is not allowed here.

SCOPE

This document is informational and intended for any user.

DETAILS

Explanation

The Method cannot be invoked. The reason depends on the circumstances. For instance, the applet may be configured as not editable, but the EditRecord method is being invoked. Under the standard configuration, if a method cannot be invoked, the button on the web page would have been either grayed out or hidden. Most likely, the method is invoked by customized code.

Corrective Action

If the method is invoked by customized code, please check the return value of CanInvokeMethod call before invoking the method. If this is not the case, please contact Siebel Technical Support and provide details about the steps used to cause the error especially with regard to navigation in the User Interface, and include relevant details about customizations made in the environment.

APPLIES TO:

Siebel Tools - Version 7.8.2.6 [19230] and later
Information in this document applies to any platform.

GOAL

The requirement is to deactivate sort column functionality in some list applets due to the huge amounts of data which affects performance. To do so, the following script has been used:

function WebApplet_PreCanInvokeMethod (MethodName, &CanInvoke)
{
   if (MethodName=="SortAscending" || MethodName=="SortDescending")
   {
      CanInvoke = "FALSE";
      return (CancelOperation);
   }
   else
      return (ContinueOperation);
}

This eScript works fine, but the system displays a general Siebel error message ("Methode SortAscending hier nicht zul䳳ig. (SBL-UIF-00348)") (translated to "Method SortAscending is not allowed here. (SBL-UIF-00348)"). How can a customized message text be used in place of this error?

FIX

It is not possible to replace the "Methode SortAscending hier nicht zul䳳ig. (SBL-UIF-00348)" system message with a customized message. However, to prevent such an error from showing, rather than placing the script in "WebApplet_PreCanInvokeMethod" event to disable the ability to sort, "WebApplet_PreInvokeMethod" event can be used to cancel the sorting. For example:

function WebApplet_PreInvokeMethod (MethodName)
{
   if (MethodName=="SortAscending" || MethodName=="SortDescending")
   {
      TheApplication().RaiseErrorText("Sorting is not allowed here"); //Add this, if needed
      return (CancelOperation);
   }
   else
      return (ContinueOperation);
}

If needed, you could add in your custom error message here by using "RaiseErrorText" method.

In addition, disabling column sorting for the whole application is not available. Bug 10564912 CR 12-1STC0Q5 has been logged to request for this feature.

Disabling column sorting can only be performed as follows:
(1) On a specific applet by using script.
(2) On a specific column/field by using "DisableSort" user property. This property can be used in list column user property or business component field user property. A value of "TRUE" or "FALSE" will determine if the sorting can be performed. For details on this property, please refer to Siebel Developer's Reference > User Properties.

APPLIES TO:

Siebel Tools - Version 8.1.1.3[21219] and later
Information in this document applies to any platform.
Checked for Relevance on 04-05-2013

SYMPTOMS

On : 8.1.1.3[21219] version, Siebel VB / eScript / COM

In Prospects>Opportunities, When New Button is clicked then It navigates to Opportunity>My Opportunity – Individual Access, creating a new record and the cursor points to the child applet.

ERROR
-----------------------
"Method NewRecord is not allowed here.(SBL-UIF-00348)"


STEPS
-----------------------
The issue can be reproduced at will with the following steps in custom Srf:
1. Navigate to Prospects Screen >> Opportunities
2. In My Opportunity – Individual Access >> Click "New" button
3. It navigates to Opportunity>My Opportunity – Individual Access view> then it displays the error :SBL-UIF-00348

BUSINESS IMPACT
-----------------------
Due to this issue, users cannot create new Prospects record.

CAUSE

Improper usage of script is causing the issue. The following line was failing when there were no records in the current BusComp context:

var sStatus = this.BusComp().GetFieldValue("BNYM Final Status");


From the script, FieldValue from the current record is being fetched. Since there are no records to be displayed for New Position, this part of script is failing which is causing the all the methods to be disable.

SOLUTION

1.
Change the script as follows:
var sStatus;
var count = this.BusComp().CountRecords();
if(count != 0)
{
sStatus = this.BusComp().GetFieldValue("BNYM Final Status");
//then paste all your code for if MethodName here
} /

2. Remove the Applet_PreInvoke method script

3.Compile and Test

APPLIES TO:

Siebel Tools - Version 7.8.2.5 SIA [19227] and later
Information in this document applies to any platform.
”Checked for Relevance on 24-Jan-2014”

SYMPTOMS

After returning to an MVG applet after attempting to delete multiple records customer we are experiencing error "Method DeleteRecord is not allowed here (SBL-UIF-00348)" and buttons which were previously enabled are being disabled.

CHANGES

In order to allow multi-row selection in MVG applet customer has set the HTML Multi-Row Select property = TRUE.

CAUSE

Customer was getting error (SBL-UIF-00348) because Siebel application does not have the ability to delete multiselected rows in a list applet.

The following Enhancement Request has been logged and they are still target to future version.

Bug 10455778: Delete is disabled after multi select...

Actually the “Delete” button should be disabled when multiple rows are selected, however in Standard Interactivity Mode the applet is not refreshed when you select the rows by checking the rows and due to that it is not disabled in the UI.

However if you perform the multi-select and then highlight a different row the applet is refreshed and button is disabled correctly.

It was also verified that the same behavior also happens with List applets.

SOLUTION

Bug 10539898 DELETE BUTTON IS NOT DISABLED IN SI WHEN MULTISEL has been logged to address the issue where “DELETE” button appears enabled when selecting multiple records in standard interactivity mode.

Currently no workaround has been found to refresh the applet when selecting multiple rows in standard interactivity mode.

SBL-UIF-00340

APPLIES TO:

Siebel CRM - Version 8.1.1.10 [23021] and later
Information in this document applies to any platform.

SYMPTOMS

In Siebel Open UI, when attempting to drill-down an attachment search result, the below error message is displayed:

Error

 

We detected an Error which may have occurred for one or more of the following reasons:
Invalid parameter: '1-2B09' passed to SWE.(SBL-UIF-00340)




Steps To Reproduce
The issue can be reproduced at will with the following steps:
1. Configure Siebel Search: Siebel and Oracle Secure Enterprise Search (OSES or SES) have been integrated.
2. Open the Search center.
3. Select a search attachment category, e.g.: 'SR Attachment'.
4. Enter a keyword.
5. Execute the search operation.
6. Click 'Show All' button.
7. Drill-down a search result.
8. The below message is displayed:
    invalid parameter: '1-2B09' passed to SWE.(SBL-UIF-00340)

CAUSE

This behavior occurs with search results that have child records. The behavior does not occur due to user specific privileges; it occurs due to differences in the responsibilities of Client and Server part in 'High Interactivity' (HI) and 'Open UI' (OUI) clients.

When results are searched for any Search Categories, Siebel gets all intended results from SES in the form of URL for each results.
In the URL, the ROWID will be of parent record(i.e. if there is no child record present) or corresponding Child record.

The differences in the responsibilities of Client and Server part in HI and OUI clients are as follows:

HI
The View mode is selected to VIEWALL while querying the records from the related buscomp of the search category.
In customized rendered, the same URL is used to create a hyper link of the search result, which will be encoded/decoded and later converted to Name-Value pair.
Later, a view method is used to create the view and show the page.
It successfully drills-down all search result records, be it Parent or Child.

OUI
If the record returned is having a child record, the RowID is replaced by the Parent RowID. And the control is getting returned from Server to Client to display the Search Results in UI.
For drill-down on any search results, the view method invoked is different; no Name-Value pair is used.

As per information found while investigating Bug 16287768 - OUI Search: Indexing And Drilldown Of SR Attachment For FTP/HTTP Should Work,  the way to build the view and show the page is OUI is different from HI.
In OUI there's a limitation related to parent-child pair records.
 

SOLUTION

The fix of Bug 16287768 has been implemented in 8.1.1.11 fix pack.

Also one of the below 2 changes should be implemented.

CHANGE 11. Navigate to Administration - Search > Search Index Settings > select the attachment search category (e.g.: 'SR Attachment') > click 'Delete Index' button.
2. Open the field-mappings file.
3. Modify the attachment BC by setting the parent and fkey-field to blank in BC's header. For example:

From

<BusComp name="Service Request Attachment"  ui-name= "SR Attachments" on-name=""
url="http://myweb.com/callcenter_enu/start.swe?SWECmd=GotoView&SWEView=#VIEWNAME#&SWERF=1&SWEHo=myweb&SWEBU=1&SWEApplet0=#APPLETNAME#&SWERowId0=#ROWID#&sblindexcategory=#SBLINDEXCATEGORY#"parent="Service Request" fkey-field="Activity Id">

To

<BusComp name="Service Request Attachment"  ui-name= "SR Attachments" on-name=""
url="http://myweb.com/callcenter_enu/start.swe?SWECmd=GotoView&SWEView=#VIEWNAME#&SWERF=1&SWEHo=myweb&SWEBU=1&SWEApplet0=#APPLETNAME#&SWERowId0=#ROWID#&sblindexcategory=#SBLINDEXCATEGORY#"parent="" fkey-field="">

3. Restart the Siebel Server for changes to take effect.

4. Index again the attachment search category.

5. Any drill-down on an attachment search result in either HI or OpenUI should be successful. 

Or

CHANGE 2
1. For Destination/Target view, change the visibility to ALL.
For example: for 'SR Attachment' with 'Service Request detail view w/attachments' as Destination/Target view.
  a. Open Siebel Tools and navigate to View
  b. Select 'Service Request detail view w/attachments' view
  c. Change the below view’s column values as mentioned:
      Visibility Applet : Service Request Detail Applet
      Visibility Applet Type : All
  d. Compile the changes.
  e. Deploy the new SRF.

2. When drilling down on SR attachment records, it behaves as per the expected behavior. If the above mentioned tools changes are done, then the Siebel user can view all the SR attachment records. The same applies for tree drilldown views.

APPLIES TO:

Siebel Tools - Version 8.1.1.11 SIA [23030] and later
Information in this document applies to any platform.

SYMPTOMS

On :  8.1.1.11 SIA [23030] version, Configuration - General

In Open UI, when drilling into a record in the find results from find objectst, the following error occurs.

ERROR
-----------------------
Invalid Parameter: '<FIELD>' passed to SWE.(SBL-UIF-00340).


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Select a customized find object.
2. Search for a record.
3. Click on "Find" button.
4. On the returned results, drill into the record.

CAUSE

The mentioned behavior has been reported in Bug 18221843 : ERROR SBL-UIF-00340 ON CUSTOMIZED SEARCH ITEM IS GIVING ERROR IN OPENUI.
 

SOLUTION

The error is no longer seen in patchset 9. As such,  please download "8.1.1.11 SIA [23030] patchset 9". The patch number is 19079078.

APPLIES TO:

Siebel CRM - Version 8.1.1.11 SIA [23030] and later
Information in this document applies to any platform.

SYMPTOMS

On : 8.1.1.11 SIA [23030] version, Configuration - General

Find Fails With SBL-UIF-00340 Error While Drilling Down An Find Result

ERROR
-----------------------
We detected an Error which may have occurred for one or more of the following reasons:
Invalid parameter: '1-2B09' passed to SWE.(SBL-UIF-00340)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Create a new Find object with Applet as "Order Entry - Line Item List Applet (Sales)", Drilldown View as "Order Entry - Line Items XA View (Sales)" and Preview as "Order Entry - Line Item List Applet (Sales)"
2. For this Find object, add the Find fields as follows:
  i. Field: Order Number
Display In Results: True
Display In Entry: True
Drilldown Business Component: Order Entry - Orders
Drilldown Destination Field: Id
Drilldown Source Id: Order Header Id
Drilldown View: Order Entry - Line Items XA View (Sales)

  ii: Field: Service Id
Display In Results: True
Display In Entry: True
Drilldown Business Component: Order Entry - Orders
Drilldown Destination Field: Id
Drilldown Source Id: Order Header Id
Drilldown View: Order Entry - Line Items XA View (Sales)

3. Add this Find object in Application --> Application Find object "Siebel Power Communications"

After that
1. Login to Application
2. Click on Search.
3. Select Order Line Items in the search.
4. Provide any Service Id and click on search button.
5. All the relevant records will be available.
6. Drilldown on any Service Id field.
7. As soon as we drilldown on the Service Id, we get the error.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot access Find Results

CAUSE

This is a known issue.


 

SOLUTION

 Bug 18226723 - NAVIGATION ON CUSTOMIZED SEARCH ITEM IS GIVING ERROR IN OPENUI, was logged.

Keyword: binaculor search

APPLIES TO:

Siebel CRM - Version 8.1.1.11 SIA [23030] and later
Information in this document applies to any platform.

SYMPTOMS

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Login into the OpenUI Application
2. Make sure you have records with rowid's with "+" sign for example '1+QMD+ABCN'
3. Open Search Center (binoculars).
3. Under Find category select account and execute a find operation.
4. Find results are displayed.
5. Drill-down on Find result which has rowid with "+" sign.
6. The drill-down fails with below message:   Invalid parameter: 'x xxx xxxxx' passed to SWE.(SBL-UIF-00340)

CAUSE

Product issue so following bug is opened for 8.1.1.11

Bug 17958953 - ERROR DRILLING INTO FIND RESULT WHERE ROWID OF THE RECORD CONTAINS '+' (PLUS)

SOLUTION

Issue is resolved

in 8.1.1.11 apply PATCHSET4

SBL-UIF-00335: BACK or REFRESH

APPLIES TO:

Siebel CRM - Version 8.0.0.4 SIA [20417] and later
Information in this document applies to any platform.

SYMPTOMS

On : 8.0.0.4 SIA [20417] version, Client Functionality

SBL-UIF-00335 on dedicated client

During debugging, the customer killed one of the session, from then on, every time they use dedicated client the web browser would show below. error message

'Encountered an error.
We are unable to process your request. This is most likely because you used the browser BACK or REFRESH button to get to this point.(SBL-UIF-00335)'

They cleaned the cache/history and restart the pc and tried to clear the log but the issue was not resolved.

CAUSE

The cause of the issue was resolved by the customer , they found from reviewing of their Templates that some were missing and after replaceing the missing templates the issue was resolved.

No further details as to which templates were missing so you should confirm that all are present .

SOLUTION

 Replace missing Templates

APPLIES TO:

Siebel Healthcare Service - Version 8.0.0.6 [20423] and later
Information in this document applies to any platform.

SYMPTOMS

It was reported that when the default homepage view for the application is not part of the user's responsibilities, that a white page and SBL-UIF-00335 error is shown. In this case, the application did not load, and a white page was shown instead.

This is illustrated below:



The text of this error is listed below:

Encountered an error.
We are unable to process your request. This is most likely because you used the browser BACK or REFRESH button to get to this point.(SBL-UIF-00335)

EXPECTED RESULT:
The expected behavior in this scenario is that instead of a white page and the SBL-UIF-00335 error, the application should load properly and a SBL-DAT-00329 error should be shown. When the user does not have access to the default starting view of the application, the user should be able to continue to use the application and access the other views which they have been granted access by responsibilities.

The expected error message is shown below:



(Note that in this example, the test user has access to only one view in the Contact screen.)

The text of the expected error for this situation is listed below:

We detected an Error which may have occurred for one of the following reasons:
The responsibility of user '<user id>' does not allow accessing view '<view name>'.(SBL-DAT-00329"

Note that <user id> is a placeholder for the user id, and <view name> is a placeholder for the view name.

CAUSE

This issue was reproduced by Oracle Technical Support in a standard 8.0.0.10 application by creating a test user who only had one custom responsibility, which contained only the FINS Home Page View.

Note - Testing has shown that this behavior did not happen in lower 8.0.0.x fix packs.

A bug was logged to report this issue. Product defect bug 11846694 ( bug 11846694 ) was logged to report this issue.

SOLUTION

As of the publishing of this document, this issue reported in bug 11846694 ( bug 11846694 ) has been closed as not feasible to fix.  However, there is a workaround for this issue.

Workaround:
The workaround for this issue is to ensure that all users have access to the default starting view, which will avoid this error.

APPLIES TO:

Siebel CRM - Version 8.1.1.11 SIA [23030] and later
Information in this document applies to any platform.

SYMPTOMS

The OpenUI Mobile client is logging in intermittently on the mobile device : Samsung Galaxy Trend Plus

The login will render this message after login :

SBL-UIF-00335 We are unable to process your request. This is most likely because you used the browser BACK or REFRESH button to get to this point.

After 2 or 3 tries, the login is successful

The problem occurs :

- If HTTPS is enabled (with HTTP only, the login is always successful)

- The Chrome browser is used on the device : Samsung Galaxy Trend Plus


Using a PC and Firefox (running with a user agent string emulation, to emulate the phone) - the login using HTTPS is consistently working

CAUSE

The problem was caused by the use of a self-signed certificate.

Mobile phones deal with self-signed certificate differently to certificates from a Trusted Certificate Authority.

In this instance, the phone's native browser accepted the self-signed certificate consistently.  However, the Chrome browser only accepted the self-signed certificate on an intermittent basis.

 

SOLUTION

Using a valid certificate from a Trusted Certificate Authority resolved the issue.

The Mobile phone can consistently access the Siebel Open UI application using the Google Chrome browser, when a certificate from a Trusted Certificate Authority was used.

APPLIES TO:

Siebel Tools - Version 7.7.1 [18306] and later
Information in this document applies to any platform.
Error Message Area:UI Framework - UIF

PURPOSE

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00335: We are unable to process your request. This is most likely because you used the browser BACK or REFRESH button to get to this point.

SCOPE

This document is informational and intended for any user.

DETAILS

Explanation

1. If the error occurs when drilling down on a record, most likely the record has been deleted by other users.

2. If the error occurs after clicking on the browser BACK or REFRESH button and then clicking on a link or button, it is because the original buscomp context cannot be fully restored.

3. Maybe the request is to retrieve a frame layout that is supposed to be cached on the server but is not found for some reasons.

Corrective Action

If the error occurs when drilling down on a record, please try to search the record again. It may have been deleted by other users. 

The SBL-UIF-00335 error is a generic error that can have many different causes.  It could be the environment setup, a custom configuration or an incorrect behavior, bug, with the Siebel product.  The following information will help to narrow down the cause of this error.

Is this error reproducible or is it intermittent? If a user reports this frequently but can not reproduce the error, enable detailed logging to review their steps.

When did this error start occurring?

Does this happen in all Siebel Environments? Production, QA, Dev? Does it reproduce only in the thin client, dedicated web client, or the mobile client? 

Is this an High Interactivity client (HI), Open UI client (OpenUI), Standard Interactivity (SI) client, or a Mobile client?

If the error is reproducible, first verify that there are no expired license keys in the Siebel application.

Production Down with Error SBL-UIF-50103 and Associated SBL-UIF-00369 and SBL-UIF-00335 (Doc: 1382256.1)

Test with a standard "out of the box" siebel_sia.srf (specific to the Siebel version past Siebel 8.1.1.10) on the most similar view to to see if SBL-UIF-00335 reproduces with the standard configuration.

If the SBL-UIF-00369 only reproduces with the custom configuration, then test without Server Scripting, Browser Scripting and Open UI scripting customizations.

These suggestions should help to define circumstances that cause the SBL-UIF-00335 errors.

If these suggestions do not help, please contact Siebel Technical Support and provide details about the steps used to cause the error especially with regard to navigation in the User Interface, and include relevant details about customizations made in the environment.