APPLIES TO:
Siebel Tools - Version 8.0.0.2 [20412] and laterInformation 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.
- - -
- - -
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.
- - -
# 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.
- - -
- - -
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.
- - -
- - -
# 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:
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
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**
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.
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.
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.
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""
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.
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.
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""
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.
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.
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.