30 Jul 4.1.4 Upgrade Instructions

Post-upgrade instructions

ElasticSearch

We’ve made significant changes to how MintHCM uses ElasticSearch.

The main change is the ability to boost records. For example, from this version on, a phrase found in a last name or record name is considered more important than one in the description. This makes working with lists or Global Search more practical.

• Add an entry to legacy/config.php: 'elasticsearch_index_prefix' => 'mint_prod_' (you can choose a short value). This is the prefix for indices stored in ElasticSearch. In previous versions, unique_key was used, but it was too long.
• Perform a rebuild in the system: Administration -> Repair -> Quick Repair and Rebuild to rebuild the field mapping file for ES.
• Reindex the records. Go to the instance directory and run: ./MintCLI elasticsearch:reindex. If the file is not executable, add execution permissions.

API Extensibility

We’ve made several changes to API files to allow upgrade-safe customization of configuration files, such as:

• api/constants/legacy_views.php
• api/constants/list_constants.php
• api/constants/module_icons.php
• api/constants/quick_create.php

If you want to modify these files, you can create custom files in the appropriate folders. For example:

api/custom/constants/legacy_views/custom_legacy_view.php

with a sample body like:

<?php

return [
    'SalaryRanges' => [
        'list' => true,
        'record' => true,
    ],
    'mn_CustomModule' => [
        'list' => false,
        'record' => true,
    ],
];

These files will be aggregated and will override the default settings. This will make future Mint upgrade processes easier.