1E Catalog 2.0 release notes – last updated  

These release notes contain late-breaking information about the Catalog. For the most up-to-date information, see the online release notes and known issues.

New features

This release introduces the following 1E Catalog features for customers using Tachyon 4.2 or later:

  • Support for EXE file mapping to multiple products - In real environments, different products may have executables with the same name. For example two products from the same company that work with both SQL Server and Oracle may use the same executable name. Previously 1E Catalog had a restriction that executables could only map to a single product, this restriction is now lifted.
  • Changes to 1E Catalog definitions are now tracked - when a change to a product occurs that requires a change to the 1E Catalog, the earlier entry is stored together with the change. This means that previous entries can now be easily updated to the new one. For example let's say there was a product where the vendor ACME Corporation had a title called E-Business Suite, 1.0.0, Professional edition. If ACME Corporation was acquired by Coyote Inc, this would require a change to the 1E Catalog showing the new vendor. In this case the previous ACME Corporation entry would be kept and associated with the new Coyote Inc. entry. The result is that any customers with software that matched the ACME Corporation product could then be automatically updated to the new Coyote Inc. product.
  • Installer enhancements:
    • AI model file download option is configurable during installation
    • Support for Network Service account. Please refer to Installation and upgrades: Service account for more details
    • 1E Catalog installer now supports TLS 1.2 using ADO.NET SQLClient. The previously used installer setting to enable TLS 1.2 support is no longer needed
    • Sysadmin is no longer a requirement for installation. Instead, the more specific roles of dbcreator and securityadmin are required by the installation account on the SQL instance where the 1E Catalog resides. Please refer to Installation and upgrades: Prerequisite Checks for more details.
  • Custom configuration changes are kept as part of the upgrade process - Any custom user entries in the Web.config and CatalogUpdateService.exe.config files are added back to the upgraded files during 1E Catalog upgrade. Though, it is still recommended that you make a backup of the config files before proceeding with the upgrade. Please refer to Installation and upgrades: Upgrade the 1E Catalog for more details.
  • Additional enhancements:
    • Hotfixes for 1E Catalog are now supported
    • 1E Catalog UI now sets Customer as the submission source instead of 1E for customer-curated data
    • UNSPSC Software Category is now passed from 1E Catalog to the SLA component in Tachyon 5.0 in a readable format
    • 1E Catalog now provides Latest Version information to SLA component in Tachyon 5.0 - this extra column is fetched from 1E Catalog during SLA normalization.

For customers who are using the early adopter AI features in SLA 3.3:

  • AI-Autocurated entries are no longer deleted following a 1E Catalog sync, resync or upgrade.



Catalog release history 

1E Catalog 2.0.0.296 ()

Features

  • Support for EXE file mapping to multiple products
  • Surrogate keys - used in tracking changes to 1E Catalog
  • Installer enhancement: AI model file download switch (Installer and DB setting); default off
  • Installer enhancement: Catalog installer changes to support TLS 1.2 using ADO.NET SQLClient
  • Installer enhancement: Support for Network Service account
  • Installer enhancement: Remove sysadmin requirement in installation
  • Custom user entries in Web.config file need to be parsed and added back to the new config file during Catalog upgrade 
  • Hotfix Capability
  • Catalog UI should set the "Customer" as submission source instead of "1E" for customer curated data.
  • UNSPSC Software Category must be available to user in human-readable format on the SLA UI
  • Changes to support "Latest Version" field in SLA - Extra column will be returned during SLA normalization with Catalog.
  • Now, AI Auto-curated entries will not be deleted after sync/resync/upgrade.

Fixes

  • The 1E Catalog Installer's Database Server Prerequisites check incorrectly referred to Database Server this has now been corrected to Database Instance.

Catalog 1.2.100.80 ()

 In this release we have added support for an Artificial Intelligence (AI) engine in catalog :- 

  • Catalog Sync     
    • Client Catalog will sync Artificial Intelligence (AI) prediction engine artifacts from cloud.
    • Artificial Intelligence (AI) generated and auto-curated records will be pushed from client catalog to cloud catalog.
    • AI Auto-curated data will be deleted after every sync (frequency 24 hrs).
  • Auto-curation and normalization
    • Auto-curation support for all the AI predicted records.
  • Installer
    • Deletion of AI/Catalog Curated records during upgrade.
  • Re-sync
    • Deletion of AI/Catalog Curated records during upgrade.
  • Miscellaneous
    • Improvement in processor normalization and processor match.
    • Added API support for consumers to get the latest AI engine artifacts from the catalog cloud.
  • Fixes
    • TFS169408 - Site defined records are not getting processed, if they are in the queue table of Staging database.
    • TFS155362 - Catalog Installer Preference for site defined vendor alias in case duplicate vendor alias exist in catalog.

Catalog 1.2.0.303 Web release ( )

  • Installer
    • Catalog upgrade support (uninstall/reinstall is not required).
    • Installer to remove all auto-curated entries.
  • Re-sync
    • Re-Sync to remove all auto-curated entries.
    • Resync auto-scheduled – run once every week by default; can be re-configured by customers.
  • Database schema
    • Additional product field to capture service pack.
    • IsDeleted column in ProcessorSockets.
  • Auto curation and normalization
    • Product auto-curation – Inherit IsLicensable, IsBundle and IsDistributable fields from closest neighbour in SP v1.1.
    • Processor auto-curation – Auto-normalize processor information based on models already curated in the Catalog.
    • ProductFileNormalize SP v1.0 to consistently send hash for same level (V+T or V+T+Ver.maj+Ver.min).
    • Do not normalize/ auto-curate entries if vendor is deleted.
    • Redundant spaces and leading zero in versions will be auto fixed to avoid creating duplicate entries in Catalog.
  • Miscellaneous
    • UI changes – Removed AppClarity Logo from Catalog UI, Catalog Synchronization/Logs folder called 1E Catalog and not AppClarity.
    • Flip the delete flag if user creates a site defined vendor, which is marked deleted.
    • TLS 1.1 and 1.2 support .
  • Fixes
    • TFS129577 - Warning showing in logs- 'The maximum key length for a nonclustered index is 1700 bytes'.
    • TFS141913 - Update Proc: PatchIdentifier & PatchEnum doesn't get updated.
    • TFS140324 - Update Proc- If User tries to update Non-Null Coll. version  with NULL then creation date should not be changed.

    • TFS140501 - Rule Set creation date is not considered in updating LastPullTime after fresh install.
    • TFS144527 - ProductLicense_cr is creating license set for those records which are marked isdeleted = 1.
    • TFS144561 - ProductVersionEditionExpansion: Uninstall strings are null when version pattern is '*'.
    • TFS144564 - ProductVersionEditionExpansion: return invalid Cost information.
    • TFS144565 - ProductVersionEditionExpansion: Pricing information exists for the Vendor = 'Microsoft Corporation' and Title = 'Access' but still Cost column null.
    • TFS146937 - Device maxsocketcount can’t be null in v1.2.
    • TFS145264 - Duplicate device match is getting created with deleted and active device.
    • TFS147574 - User can create a product for which vendor is already deleted in catalog.
    • TFS153984 - Site defined entries are not getting retained for processor and processor match on doing major upgrade.
    • TFS148147 - Product normalize sp gives vendor as null in output if that vendor is deleted in catalog.
    • TFS150953 - ProductProductMatch_cr is creating Bundle set for those records which are marked isdeleted = 1.
    • TFS151405 - Processor Normalization - Auto-curated record created with 1E Verified =1 flag.
    • TFS151479 - Duplicate match rules created by ProcessorMatch _CR SP.
    • TFS152205 - Processor Normalization- if processor vendor is deleted then do not normalize the record.
    • TFS152966 - Processor variant view - show isdeleted=1 for the records where vendor is deleted.
    • TFS149118 - Partial match returns false result when input has special char in version field.
    • TFS153645 - Product Normalization - deleted vendor is considered in partial matching.
    • TFS154141 - SLA - Bulk-curation : 500 internal server error - Could not find a part of the path 'C:\\ProgramData\\1E\\AppClarity\\FailedBatch.tsv

    • TFS154193 - Resync fails to insert site defined [EntitlementProductSet]

    • TFS154327 - Resync fails to insert site defined [EntitlementProductProductMatchs]
    • TFS154057 - Resync is failing after installing the catalog with service account

Catalog 1.1.100.25 Maintenance release (03 July 2018)

  • Support for Nullable MaxSocketCount in Device set.
  • Fix Issue: changes in Ruleset related to the secondary apps section

Catalog 1.1.100.6 Maintenance release (29 June 2018)

  • Partial Version matching for incomplete Versions in input.
  • Rulesets Schema and Normalization support in Catalog.
  • Product Normalize Performance Improvements.
  • Fix Issue: Error while installing Catalog on system where OS language is set to English (South Africa).
  • Fix Issue: Duplicate Devices created on Sync.
  • Fix Issue: MaxSocketCount input is always default (1024) while creating a Device.
  • Fix Issue: Installer reads old duplicate fileset .tsv file and throw message of duplicate exes.
  • Fix Issue: ProductMatchs are getting synced.

Catalog 1.1.0.122 Web release (07 February 2018)

  • Best match – on the SLA unmatched screen, improvements to the best match API to identify unknown signatures leverages the existing data in the Catalog.
  • Synchronization improvements – previously, you could either enable or disable cloud upload and download synchronisations. You can now make use of the unidirectional synchronization feature to only download content from the cloud whilst disabling the upload. You can also run a resynchronization event to rebuild your Catalog in the event of a corruption where you can opt to retain or flush sited defined items.
  • Auto-curation intelligence – improved algorithms increases accuracy for edition-based products resulting in companion products such as the Windows Servicing Suite and AppClarity benefiting from more accurate data. The logic creates match sets automatically for new versions if the Catalog has a existing match set. The logic also ensures that any Licensable/Bundled information is retained for the auto-curated items.
  • Managing filesets – filesets define which files are used by a particular product and we now prompt you if you attempt to associate an executable to a product and that particular product already has an existing association to eliminate duplicates associations. In addition, when you carry out an upgrade, any duplicates are removed and flagged for your attention.
  • Catalog works with FIPS compliance settings on.  It uses MD5 hashes to allow faster lookups and processing, but not to encrypt data.

Catalog 1.0.500.106 (22 September 2017)

  • Sync timeout issue with large site defined data.

Catalog 1.0.500.101 (15 September 2017)

  • Sync Improvement

Catalog 1.0.500 Web release (22 August 2017)

  • Installer improvements. Installation time is reduced to few minutes only
  • Best match API enhancements
  • Batching is introduced for monitoring cloud sync progress
  • Cloud SSL support

Rolled-up hot fixes (22 July 2017)

  • Q13139 – Enhancement to view the progress of data processing in the queue.

Catalog 1.0.400.107 (10 July 2017)

  • Fileset schema changes - File linked directly to products instead of Versions and editions
  • Catalog UI - Files managed from Product List
  • New fields in EntitlementProductProductMatch - IsLicenseUpgrade, IsMultiInstanceAllowed, SecondaryUseCount
  • New Entities for Entitlement - EntitlementProductVersionUpgradeBranchMatch, EntitlementProductEditionDowngradeMatch
  • Support for Reclaim strings storage and sync
  • Enhancement in auto-curation - Auto-curation now works with Vendor, Title
  • Version normalization

Catalog 1.0.300.2 (28 April 2017)

  • Fix Product creation logic to avoid Duplicate Catalog MD5 creation
  • Existing product set can be updated
  • Delete Duplicate Catalog MD5 from existing Catalog

Catalog 1.0.200.662 (14 February 2017)

  • Enhanced coverage for usage and products (i.e. match sets)
  • Defect fix for the Catalog UI