Generate Mid-Level Release

Need:

         Export all the objects files for a specific release or from a specific date.

Solution:

      This is a very useful functionality that can be executed from siebel tools to export all the objects those are modified from a certain date.
We have the option to export individual object sifs or one sif for all objects. that is mostly based on our requirement

 Steps:

  • Set the desired date, objects modified post this date are all exported as a part of this operation.


  •  Click on "Generate Mid - level Release



  • The window opens which will prompt you to name the export with a label and once label is named you will asked to do "Generate List". Once after this is done cross check the list of objects for the objects you have modified. Also take no extra objects are found, if so you might need to specify a correct date.



  • Now after checking is complete "Export" the objects to the ADM folder within which a new folder is created with the name of the label.
This could be helpful to partial move objects to the target environment instead of moving the entire repository for a minor releases. 


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