The July 2024 release of Business 360 Console includes the following new features and enhancements.
Watch the What's New video to learn about the new features and enhancements in the July 2024 release.
Dynamic fields
You can now add dynamic fields to business entities. Dynamic fields are a set of attributes that can vary for different records of a business entity based on their relationship. For example, Borges Penne and Teddy 5G Mobile are records of the Item business entity that can have different sets of attributes.
You can configure survivorship for the dynamic fields. Dynamic field definitions can be selected and inherited across a hierarchy. You can also add these fields to custom pages. Additionally, you can ingress data into dynamic fields and egress data from dynamic fields.
For more information about dynamic fields, see Dynamic fields.
Hierarchies as search filters
You can include hierarchies as search filters. To filter records based on hierarchies, you can configure hierarchies as searchable and include hierarchy filters to the search layout. Ensure that you index the records of all the searchable hierarchies by running process hierarchies jobs.
When you configure DaaS real-time address verification, you can now specify how to store the enriched address values in the source records. You can choose to create a patch record or update the existing source record for address enrichment. MDM SaaS uses this setting when you enrich address values using REST APIs.
By default, MDM SaaS creates a patch record to store enriched address values for existing DaaS rule associations. If you add new DaaS rule associations, by default, MDM SaaS overwrites the enriched address values in the source record.
You can now localize search preferences in Japanese. To enable business users to perform searches in Japanese, within the business applications, add Japanese as a search language on the Localization page. To allow business users to search for records in English and Japanese, you can enable multilingual search for business entity fields.
You can enable multilingual search for text data type fields in your business entities.
You can now delete source records that you don't need. However, the records are not permanently deleted from the data store. You can restore deleted master and source records through business applications or REST APIs. You can delete and restore source records through ingress jobs. The jobs display metrics about records that are skipped, deleted, and restored in the load step. You can also egress the deleted records.
You can now search for deleted master records. To view the master records that were deleted before the July 2024 release, run a reprocess master data job. The reprocess master data job indexes the deleted master records for search and recalculates the trust scores for the deleted master records.
Use the Search REST API to search for records in English or Japanese. To specify your language preference, use the searchLocale parameter in your request. Based on the value you specify, such as en for English or ja for Japanese, the response returns records in that language.
For more information about searching for records using the search REST API, see Search API.
Null matching
When you configure a declarative rule that allows matching null values, you have the option to retain either the match pair with the highest score or all the null value match pairs in a record pair group. When you choose to retain all pairs, you allow multiple null value pairs within a record pair group. If record pair groups include all the null value match pairs, it reduces the chances of forming individual master records from null value match pairs with lower scores.
For more information about null matching, see Null matching.
Trust decay
When you configure trust decay, you can now specify trust scores with two decimal places, from 0 through 1, such as 0.05, 0.65, and 0.66.
When you use Business 360 FEP connector in the mapping for an egress job for exporting field groups, the exported data now includes the source systems of the field groups. If field groups contain multiple entries, you can identify them based on their source systems in the exported data.
For more information about exporting data, see Exported data.
Supplier 360 Extension for SAP
You can now egress the processed supplier records from Supplier 360 to SAP S/4HANA as business partner records in batches. You can also ingress incremental records from SAP ECC and SAP S/4HANA and process these records in Supplier 360.