Update to Java Version 21

EDC upgrade to 0.7.5

APIs: Added a major version number to all API endpoint paths and changed the structure of the DNS addresses. Company identification is now in the path.

Update to Java Version 21

Name search for business partners now case-insensitive and delivers results on partial matches
​
Updated logic in repository function which is being used by BusinessPartnerFetchService.
Affected endpoints GET - ‘/v6/legal-entities’, POST- ‘/v6/legal-entities/search’ and POST- ‘/v6/members/legal-entities/search’ which use to query business partner data of type legal entity.
​
​Before: Previously, the search functionality was case-sensitive and required full matches to return results. For example, searching for "Acme" would not return "acme" or "Ac" as results for legal name in business partner.

Now: The search functionality is case-insensitive and supports partial matches. This means that a search for "Acme" will return "acme", "Ac", "ACME Corp", etc., making it easier to find relevant business partners without exact matches.

Now validate and reject data in golden record tasks only if it is needed for processing
​
Refactored logic for service named as TaskStepBuildService

Before: there were multiple fields present which were really not being used for updating partner data.

Now: This change, fixes the Pool's behaviour of validating business partner fields that are actually not used for updating data. This lead to a too strict behaviour and now let's sharing members leave out unnecessary information in the business partner data. This approach minimizes disruptions caused by non-essential data errors and streamlines the data processing workflow, leading to better data integrity and performance.

New API endpoints to query business partner data which belongs to Cofinity-X members (customers) only
​
These new endpoints are included in the ‘Business Partner Explorer’ (BPDM Light) service on our marketplace.
​
Resource path for endpoints – ‘/v6/members/changelog/search’, ‘/v6/members/legal-entities/search’, ‘/v6/members/sites/search’ and ‘/v6/members/addresses/search’
​
​

API Permissions: Overhaul of the permissions needed to access the API endpoints

Removed the static prefixes 'api/catena' from all API endpoint paths

Removed the flags for is legal address and is site main address from the logistic address

Fix Pool trying to update golden records which the golden record process indicated to have no changes

Now correctly sending NULL values for alternative addresses to the golden record process
This was a bug. If we hadn't fixed it, the BPDM gate would have continued rejecting business partner records that lacked an alternative address.
​
​

Configuration update
​
The configuration update allows for more control over the data handling process within the GATE microservice.
​Now: A new configuration has been introduced to prevent uploaded business partner data from automatically entering the golden record process. Instead, the data can now be manually submitted to the golden record process via the new sharing-state/ready API endpoint, offering greater flexibility and control over data handling.
​
​

Multi-tenancy support
​
GATE's multi-tenancy support enables each tenant (organization) to maintain its own isolated data environment, with business partners segregated by the owner-BPNL. The owner is derived from the 'bpn' claim in the token, ensuring that users can only view and edit their own business partner data, thereby maintaining data isolation and security.

Payload structure

Please see attached file for payload structure on Jupiter:

Payload_jupiter.txt

Remove unused business partner type filter in query parameters from sharing state endpoint

Removed all Legal Entity, Site and Address endpoints (The generic business partner endpoint is their successor)

Removed legal entity classifications form business partner

Remove business partner type from API models and filters

Remove BPN from the sharing state

Remove the static prefixes 'api/catena' from all API endpoint paths

Fix not correctly updating business partner output data from golden record updates in the Pool

Fix not correctly updating confidence values it receives from the golden record process