Guide to configuring the analysis of impactful errors and filtering out the insignificant ones. In other words, this guide helps in understanding how Germain can concentrate on errors that impact Siebel CRM Users or Business Processes while excluding the numerous benign ones.
Tag Errors that Affect Siebel Users (Configure)
Check how to tag Siebel Errors that affect Users and ignore the others.
Tag OM Errors to watch out for (Configure)
Germain UX allows to map all Siebel custom error codes to their corresponding display messages visible to your end users. To configure this mapping please follow the below steps:
Extract all of your Siebel Error codes using
errmsg.exeSiebel’s utility (available only on Windows platforms). Siebel keeps these codes in the resource catalogs (core.cat, apps.cat, vsia.cat, inst.cat, …) in the %SIEBEL_ROOT%\bin\%language_folder%. Example below shows how to extract these codes from Siebel resource catalog in English language format:CODE
%SIEBEL_ROOT%\bin\errmsg.exe /l ENU enu\core.cat > errors.txt
errors.txtoutput file and find all of your custom errors, e.g.CODE
... SBL-GEN-02011 Error parsing Siebel message file header: incorrect facility name ...
Once all custom error code extracted from the
errors.txtfile, insert them into
SIEBEL_ERROR_CODE_MAPPINGtable available in your Germain UX Datastore. Example below for MySQL database:
INSERT INTO SIEBEL_ERROR_CODE_MAPPING (CODE,MESSAGE) VALUES ('SBL-GEN-02011','Error parsing Siebel message file header: incorrect facility name');
Please go here to see KPIs for Siebel Errors.
A number of dashboards are preconfigured for Siebel CRM, here are just a few main ones, but there might be more.
Go to Germain Workspace > Left Menu > Dashboards > All
Search for any “Siebel…” dashboards, such as:
Siebel User Experience
Search for portlets called “…Error…” or create them or we can help.
Feature Availability: 2014.1 or later