Exposing Save button in Siebel HI user interface

Requirement:

  Expose Save Button in Siebel UI in high interactivity.

 Solution: 
            Siebel Application running in High Interactivity mode doesn't need a explicit save button as they have the implicit save functionality. Though there is option to save from the menu, we had requirement to make it easy for user to do this.
So add the button to the UI and then compile to see if the button appears. If it doesnt go the application cfg file to add an additional parameter

ShowWriteRecord=TRUE
This parameter is located in the InfraUIFramework section of the configuration file. 
Note that the Save buttons use the WriteRecord method.

 This is also a parameter in the component parameter if you configure in thin client.

Comments

Post a Comment

Popular posts from this blog

Refresh Siebel Applet not Buscomp - "RefreshBusComp" Alternative

Need: User wants to update the data being displayed on UI after performing some validation and updates via a script on the underlying BC.   Solution: A vanilla Business Service “FINS Teller UI Navigation” can be used to refresh an Applet after updating the underlying data, without breaking the current query.       One of the most commonly used approach is to invoke the "RefreshRecord" method on the Business Component. However, this does not promise to work on all Business Components.        Another alternative is to call the BS method "RefreshCurrentApplet" on the BS "FINS Teller UI Navigation".   Syntax: TheApplication().GetService("FINS Teller UI Navigation").InvokeMethod ("RefreshCurrentApplet", TheApplication(). NewPropertySet(), TheApplication().NewPropertySet()); Eg: BusComp_WriteRecord() { Code Goes Here //TheApplication().InvokeMethod(“RefreshBusComp”);    --Commented TheApplic
Read more

BCHasRows - Validation with no scripts

Need:   To do validation without using siebel scripts.  Solutions:         BCHasRows : Validation Without Scripting Scenario:            To check/search in child Bus comp field values for some validation  without scripting.  For Example:            When the Specified Account has any "Active" child Activity, the Activity flag should be true Implementation without scripting:           Create a  calculated field Name: Check Activity  Calculated = Y Calc Expression: BCHasRows("Account", "Action", '[Account Id] ="' + [Id] +'" AND  [Type] = "Active"',"All")         This returns Y, if any child activity found. Create a User property “On Field Update Set” to set the Activity Flag ; Value : “Check Activity”, “Activity Flag”                            Syntax:  BCHasRows ( BO , BC , search_expr, visibility)
Read more

Deploying Integration Object at Runtime (Siebel)

Image
Feature: Starting with  Siebel  8.1, Integration Objects can be deployed at runtime just like workflows to the runtime database. Modifications to the IO can be deployed to the server without having to recompile the changes to SRF, shutting down the server and then moving the changes. Steps to follow: 1.         Open a Dedicated connection to the server database(Works on local db too) 2.         Go to the IO in the Object Manager 3.         Select the IO that needs to be modified and deploy 4.         Right Click on the IO and select “Deploy to Runtime Database” 5.         Log into  Siebel  Web Client 6.         Go to Site Map ->Administration – Web Services >Deploy Integration Object 7.         The IO will now be available 8.         In order to un-deploy the IO, go to  Siebel  Tools ->Integration Objects > Right Click on the IO and select “UnDeploy” 9.         Clear the cache every time before deploying/un-deploying( Administration – Web
Read more