While the Innovation Pack 2017 (IP207) is getting ready to be “GA”d, I am trying to highlight some of the key features here.
First in the series, that excited me, is Production Version of “WebTools”. (IP2015,IP2016 were only the Developer Preview).
WebTools have come up pretty good, where the Siebel Development team is ensuring that the UI and configuration steps matches the Siebel Tools.
This also empowers the Developers to configure online via web browser, a step forward towards cloud enablement.
Key Observations :
- Types Mode and Flat Mode of Object Explorer is still available
- Collapsable/Expandable Objects tree
- Tree type of navigation similar to Siebel Tools
- Native OUI Applet features for search, Add, Delete, Query etc
- Ability to select/unselect the Objects and child objects within the OE Pane.
- Settings Button, have most of the Methods that were available in Right click.
- Web Template files are migrated to WebTools, so that the Templates can be edited online with styling and Preview options available.
- And the new “Workspace” concept, which will help in
- Parallel developments within Releases (Eg: Developer 1 and Developer 2 working in Q1 Release)
- Parallel Release development (Eg: Q1 Release and Q2 Release can go hand in hand within a single development Server, Which means reduced infrastructure and Maintenance)
- Better Control over the items being merged into a release. (with Approval Manager)
- Preview (“Inspect”) option for the developers will eliminate the need of any SRF Migration and server bounce and help in faster development cycle
- Better Conflict resolution options (Rebase etc)
- Elimate the need of SRF File. ( This is a single big step, which will help in achieving “Zero Down Time” for SRF Related deployments.)
Saying that, WebTools has still evolve. Some of things, which you still will not be able to do with WebTools are :
- Wizards (Applet, BC, etc)
- Task Based UI Configurations
- Workflow creation and debugging
- Applet, BC, BS Browser scripts and Server Scripts
- Applet Edit WebTemplate option not available
- Debugging the Scripts in Applet,Application,BC or BS
- EIM Mappings
- Importing the Objects from Archives (SIF’s)
- And few more, yet to explore 🙂
All in all, I hope that this WebTools will
- Ease up the work of developers,
- Less work for Siebel Admin’s
- Faster deployment cycles and
- Reduce cost of ownership for the enterprises
Will try to elaborate on other “Game changer” features of IP2017 in future topics.
Found this simple image explaining the Cloud offerings – IaaS,PaaS and SaaS comparing with On-Premise. Thought of sharing…
Siebel by default does validation of the email addresses that are used in the outbound communication manager. Basic validations like having a “@” or a “.com” or “co.*” are present. Some times there might be an exception scenario where these validations needs to be overwritten to cater to the customer needs where they might encounter validation errors like :
Invalidate eMail address:****@abc.support.(SBL-EML-00050)
To overcome these validations, you need to set system preferences. Following steps needs to be followed :
- Navigate to Administration – Application –> System Preferences
- Query out “Enable EmailAddress Validation”
- Set its value to “FALSE”
- Bounce Siebel Service
When changing System Preferences (normally by the administrator), Siebel Application Object Manager component needs to be restarted to make it reload the new System Preferences settings.
Test and Deploy!!
Since the List applet in OpenUI uses the JQgrid frame work, it gives some very good capabilities of JQGrid. One of them is the “Filter Toolbar”, which gives us additional filtering options within the List Applet.
Additionally, you can now programmatically control the contents in list applet (Like filtering, Searching etc).
Following code in PR can get you the “Filter Toolbar” in your list applet:
To add a filter condition, you can try the below script:
$(“#gs_Location”).val(‘H’); // Setting the filter condition
this.GetGrid().triggerToolbar(); // Trigger the Filter condition
Where “gs_Location” needs to be replaced with the correct List Column name. Here I have added a filter condition of “H”. Once you set a value, Trigger the toolbar to execute your filter condition.
Also, you can hide the toolbar, if you do not want your users to use it, or to have the filtering in the background.
Recently I have been working on some of the Performance related issues in Siebel. The usual way is to get the OM logs with SQL logging level set to 4/5. Now the big task is to analyze these log files to find Long running queries which cause the performance degradation.
So, I have come up with my own “Siebel Log Analyzer” which will check for long queries pertaining to :
a) SQL Prepare Time
b) SQL Execute Time
c) SQL Fetch Time
You need to enter the Log File Path and give a value for Threshold (Threshold time above which all the values to be captured . Eg : 0.4 sec, 0.7 sec etc)
On clicking the “Analyze File”, the output is generated in a new excel sheet like this :
Now it’s some what easier to find where the issues are. This is especially helpful when the log file size is very huge.
Let me know if any of you need to try this. You can email me to get a copy!!
var currentPageUrlIs = document.location.toString().toLowerCase().substr(7,24);
var currentlocale = window.location.pathname.toString().toLowerCase().substr(12,3);
Note : change the substring numbers according to your url and OM Name.
Dear OpenUI Developers,
Those working with earlier version of OpenUI ( 188.8.131.52, .10, .11) will see that the custom JS files/folder will not show up in the browser console anymore. (IP2015 onwards).
Open UI now loads scripts “as needed” as opposed to pre-load via direct includes. This prevents the script from showing up in a list with a named reference.
To Debug the PMs, PRs files use debugger call in the script and this will open the script in browser console and you can set breakpoints as and when needed. When keyword “debugger;” is added to script which will make the browser stop the script that line for debugging.
Happy debugging!! 🙂