Created by James Hurrell, last modified on Jan 11, 2021
This documentation is not maintained. Please refer to doc.castsoftware.com/technologies to find the latest updates.


  • 5.2.2-funcrel
  • 5.2.1-funcrel
  • 5.2.0-funcrel

    • 5.2.6

    Note

    This release is compatible with Siebel extractions performed with the Siebel extension 5.2.2-funcrel - 5.2.5-LTS. In other words, if you have already performed an analysis/snapshot using any of 5.2.2-funcrel - 5.2.5-LTS you can upgrade to 5.2.6-LTS and then perform a new analysis/snapshot without having to re-action an extraction and set as current version.

    Resolved Issues

    Customer Ticket IdDetails
    29709Fix applied to prevent extraction failures with the error "Extraction error: ORA-01652".

    Other Updates

    Details
    The Siebel extension (when used with AIP 8.3.38 and above) will now check for the presence of the default Filters in custom Modules in CAST Management Studio (when configuring the Project application) and if they are present they will be removed. This process automates a manual check of the application configuration process for the "Project" application.

    New Support

    SummaryDetails
    Support for Microsoft SQL Server (BETA)This release provides support for extracting Siebel repositories hosted on Microsoft SQL Server.

    5.2.5

    Note

    This release is compatible with Siebel extractions performed with the Siebel extension 5.2.2-funcrel, 5.2.3-funcrel and 5.2.4-funcrel. In other words, if you have already performed an analysis/snapshot using either 5.2.2-funcrel, 5.2.3-funcrel or 5.2.4-funcrel you can upgrade to 5.2.5-LTS and then perform a new analysis/snapshot without having to re-action an extraction and set as current version.

    Resolved Issues

    Customer Ticket IdDetails
    28363Modify the Siebel Extractor to make sure it accepts only Siebel .castextraction files.
    23943Support natural metrics with Siebel analyzer : activate 'Avoid Too Many Copy Pasted Artifacts' and 'Avoid Artifacts with high Commented-out Code Lines/Code Lines ratio' using default CAST parameter values. New violations may be discovered for existing unchanged source code when re-analyzed with this release of the extension.

    Rules

    Rule IdNew RuleDetails
    7156TRUEAvoid Too Many Copy Pasted Artifacts has been activated in this release of the extension.
    7126TRUEAvoid Artifacts with high Commented-out Code Lines/Code Lines ratio has been activated in this release of the extension.

    5.2.4-funcrel

    Note

    This release is compatible with Siebel extractions performed with the Siebel extension 5.2.2-funcrel and 5.2.3-funcrel. In other words, if you have already performed an analysis/snapshot using either 5.2.2-funcrel and 5.2.3-funcrel, you can upgrade to 5.2.4-funcrel and then perform a new analysis/snapshot without having to re-action an extraction and set as current version.

    Resolved Issues

    Customer Ticket IdDetails
    27803The Description section of the rule "SiebelReview: Duplicate Column Mappings " has been updated.
    27802The Description section of the rule "Siebel: Don't overload Siebel Tables" has been updated.
    28217False positive for rule "SiebelReview: Custom Business Component Contains No Required Fields"
    28139False Positive found for rule "Siebel: Business Component Field should have same type as related Table Column"
    28138False Positive found for rule "Siebel: Length of the Column should not exceed the length of the Field"
    28137False Positive found for rule "Siebel eScript: Avoid Functions without Try, Catch and Finally block"
    27835False positive for rule "Siebel: Defining Ancestry of Custom Business Components"

    Other Updates

    Details
    Cast Upgrade py files should be upgraded to 1.6.5 in end_application instead of 1.5.20

    Rules

    Rule IdNew RuleDetails
    1520162FALSEDocumentation for the rule "1520162 Siebel: Do not add custom Fields to a Siebel Base table" has been improved.

    5.2.3-funcrel

    Resolved Issues

    Customer Ticket IdDetails
    23780Rules coming up Empty for 2 modules from cloned applications
    9320The section detailing 'Post Snapshot Checks' in Siebel Application Management page should be updated. See https://doc.castsoftware.com/display/TECHNOS/Siebel+5.2+-+Application+management#Siebel5.2Applicationmanagement-ChecktheresultsintheCASTdashboards.
    23905Update the Siebel Doc to say that Vanilla and Project Repo ID should be different. See https://doc.castsoftware.com/display/TECHNOS/Siebel+5.2+-+Application+onboarding.

    Other Updates

    Details
    Simplify and fix issues in SIEBEL_DISCRIMINATION scripts.
    A warning will be listed in the analysis log when AIP and extension versions are different for Siebel Vanilla and Project. For example: "RuntimeError: SIEBEL-111 VANILLA and PROJECT siebel extension version should be same."
    The extraction process will now detect if the Project or Vanilla's Repository ID has been used for both Vanilla and Project extractions (using the same repository ID for both Vanilla and Project must be avoided). An error message will be added to the log file if this is the case: "SIEBEL-105 VANILLA and PROJECT Repository Id should not be same. Refer to the documentation."

    Rules

    Rule IdNew RuleDetails
    1520774FALSEAvoid setting field values using hard-coded values (Siebel) - the title of this rule has been changed: in previous releases it was called "SiebelScriptReview: Setting field values using hardcoded values".

    5.2.2-funcrel

    Updates

    Changes to database extraction

    In this release, Siebel workflow objects (SiebelWorkflow) are no longer extracted from the target database when running a new extraction. This change has been introduced to improve the performance of the extraction and analysis process. This change is valid for databases hosted on DB2 or Oracle servers and is also valid when using the extractor embedded in the CAST Delivery Manager Tool or when running the extraction using the Siebel-Extract-CLI.bat file. 

    As a result of this change, SiebelWorkflow objects will no longer be present in the analysis results. There is no impact to rule results for existing analyses, nor on other metrics such as Technical Size.

    If you use the option Reuse existing Siebel extractor output, SiebelWorkflow objects will still be present since it is the extraction process itself that has changed.

    Rule documentation improvements

    The documentation for Siebel specific rules has been updated to ensure that all rules now have complete documentation. See https://technologies.castsoftware.com/rules?sec=srs_siebel&ref=||5.2.2-funcrel for the list of rules provided in 5.2.2.

    Resolved issues

    Internal IDTicket IDDescriptionAffects Version
    SIBL-16323356

    Siebel analysis stuck 5 days on same .uax file containing Siebel Workflow object instance and children

    		5.2.1-funcrel
    SIBL-17023659

    Siebel Content Enrichment file not run - "(b'ERROR', b'23505', b'duplicate key value violates unique constraint "pk_bcf_calculated"')"

    		5.2.1-funcrel
    SIBL-15218563

    Incomplete quality rules description on technologies.castsoftware.com and dashboard

    		5.2.0-funcrel

    5.2.1-funcrel

    Changes to the Siebel-Extract-CLI.bat file

    The Siebel extension provides the following batch file for automating the extraction of Vanilla and Project databases using the CAST Database Extractor - see Siebel 5.2 - Application onboarding for more information:

    %PROGRAMDATA%\CAST\CAST\Extensions\com.castsoftware.siebel.<version>\TOOLS\OfflineExtraction\Siebel-Extract-CLI.bat

    This batch file has been modified to add configurations for accessing Oracle Server using a Service as well as a SID (as in previous releases). Lines 28 - 34 are new:

    rem ****************************************************************************
rem Database parameters = Access to the database hosting the Siebel repository
rem ****************************************************************************
rem for Oracle : oracle
rem for DB2 : db2
SET DBTYPE=<PARAM>

rem URL for Oracle = jdbc:oracle:thin:@<SERVER_NAME or IP>:<PORTNUMBER>:<SID>
SET JDBC_URL_ORACLE_SID=jdbc:oracle:thin:@%SERVER_NAME%:%PORTNUMBER%:%DATABASE_NAME%
rem URL for Oracle = jdbc:oracle:thin:@<SERVER_NAME or IP>:<PORTNUMBER>/<SERVICE>
SET JDBC_URL_ORACLE_SERVICE=jdbc:oracle:thin:@%SERVER_NAME%:%PORTNUMBER%/%DATABASE_NAME%

rem Choose %JDBC_URL_ORACLE_SID% or %JDBC_URL_ORACLE_SERVICE%
SET JDBC_URL_ORACLE=%JDBC_URL_ORACLE_SID%

rem either a host or an IP
SET SERVER_NAME=<PARAM>  
SET PORTNUMBER=<PARAM>
SET DATABASE_NAME=<PARAM>

rem user used for the SQL connection
rem SET /p DBUSER="CONNECTION USER: "
SET DBUSER=<PARAM>
rem SET /p DBPWD="CONNECTION PASSWORD: "
SET DBPWD=<PARAM>

    Therefore when editing this batch file for your own environment, ensure that you configure line 34 in addition to all instances of <PARAM> (which also require changing) by choosing between %JDBC_URL_ORACLE_SID% (for access via a SID) or %JDBC_URL_ORACLE_SERVICE% (for access via a Service). By default the batch file will be configured to use an Oracle Server SID, i.e. the same behaviour as in previous releases of the extension:

    rem Choose %JDBC_URL_ORACLE_SID% or %JDBC_URL_ORACLE_SERVICE%
SET JDBC_URL_ORACLE=%JDBC_URL_ORACLE_SID%

    5.2.0-funcrel

    Resolved issues

    Internal IDTicket IDDescription
    SIBL-15518027Vanilla objects are coming up in project violations list even though discrimination was done