Siebel Open UI >  Siebel Open UI - PDQ Displays End Of File Error

Siebel Open UI - PDQ Displays End Of File Error

APPLIES TO:
Siebel CRM - Version 8.1.1.11.10 [IP2013] and later


SYMPTOMS
Errors appear in activity list screen with customised body to be able to view email body when using Predefined Queries. It works in High interactive interface.

But in Open UI v8.1.1.11 when user selects a Pre defined query, it shows End of file error. Error doesn't appear in log files.


CAUSE
Identifed as a bug in v8.1.1.11. Reproduced in Patchset 12.

This has been logged as a BUG 19986828 - SIEBEL OPEN UI - PDQ DISPLAYS END OF FILE ERROR IN 8.1.1.11.12

Standard Siebel v8.1.1.11 Patchset12 connected to sample DB.

Steps to reproduce :

 

1. Login to Siebel Tools:
2. Applet > Activity Form Applet.
- Add a Toggle applet

Activity Form Applet > Applet toggle.
Applet: Activity Form Applet
Auto Toggle Field: Type
Auto Toggle Value: Email - Inbound

3. Login to Siebel client application (dedicated client).
-Navigate to Activities > My Activities.
-In the Activity List applet > create new activity record with values in the Comment Field.
Make sure comment field contains large number of HTML text (tags).

-Select Type from dropdown and select "Email - Inbound".

4. Step off the record and save it.

5. Create PDQ in My Activities.

- In Activity List Applet, click Query button.
- Execute a query with Type = "Email - Inbound"
- From the application-level menu, choose Query, then Save Query As.
- In the Save Query As dialog box, enter a name for the query e.g "Email Inbound".
- The query is added to your list of predefined queries.

6. Navigate to some other screen.

7. In Siebel Tools > Compile the object [ Activity Form Applet ].

8. After compiling, navigate to My Activities.
9. From top select the PDQ.
10.Navigate to the record you created by drilling down.

Result: An end of file error has occurred.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00393)

SOLUTION
Parent Bug: 19986828 opened against 8.1.1.11 (IP 2013) version.

Child Bug: 20352081 opened against 8.1.1.11 (IP 2013) was closed by Engineering citing not feasible to fix.

Child Bug: 20523773 opened against 8.1.1.14 (IP 2014) was closed by Engineering citing not a bug. This is because the issue is not reproducible in IP 2014 version. Its plausible that the issue might have gotten inadvertently fixed in IP 2014.