Skip to main content

Next and Previous record button got disappear on photographs applet in Siebel

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

ACTUAL BEHAVIOR
---------------
Next and Previous record buttons are missing on photographs applet when large image (i.e. 2000 X 1600) is used.



EXPECTED BEHAVIOR
-----------------------
The next and previous buttons should be visible.

DETAILS
-------------------
1. What browser are you using, and what version of it? Does it happen on other browsers also (Chrome, Firefox, IE)
>> Chrome, IE

2. Do you experience this on all Siebel clients (Dedicated and Web)?
>> Both

3. What applet are you using?

PUB Immigration Contact Photograph Form Applet. This is used to show images that are already uploaded via List Applet.

PUB Immigration Contact Photograph List Applet. This is the applet which is used to upload image/photograph.

>>Clones of above objects, first list applet than form applet to display the image. If I select the next image record from list applet, on form applet image is changing as well.

4. If you attach multiple images are you able to see the navigation buttons?
>> if images are in small size, than navigation button appears on form applet but if image is in large size button got hide, even I could not able to find the controls using inspect element from browser.

Summary
-------------------
When navigating to the context and a high-resolution image is displayed, the next and previous image buttons are missing.
Setting a custom height and width to the image that causes the issue, the buttons are visible.
Next step is to set a maximum height to the image. The image is from an external application.

Solution
-------------------

To implement the solution, please execute the following steps:

1. Set a maximum size for the image in the custom CSS if not possible control the image size before adding.

2. Retest the issue.

3. Migrate the solution as appropriate to other environments.

Source:
Oracle Support
SR 3-23281950151

Comments

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...