What's New > Upgrade > Post-upgrade tasks for the October 2024 release
  

Post-upgrade tasks for the October 2024 release

Perform the following tasks after your organization is upgraded to the October 2024 release.

Reindex records to view filter values

To get additional filter values, Blank, Not Blank, and Is in business applications, ensure that you reindex the records of business entities.
To reindex records of business entities, run the generate search and report indexes or match keys job.
For more information about the generate search indexes or match keys job, see Define and run the generate search indexes or match keys job.

Import the process for the reprocess master data job

You need the predefined Cloud Application Integration process, MDMProcessMasterData, to recalculate the trust scores of the active and deleted master records.
To reprocess master data, ensure that you perform the following tasks after the organization is upgraded:
  1. 1Modify permissions for the existing process.
  2. 2Import the process to reprocess master data.
  3. 3Get the artifact ID of the process.
  4. 4Modify permissions and create a user for reprocessing master data.
  5. 5Publish the process for reprocessing master data.

Modify permissions for the existing process

If you don't have the MDMProcessMasterData process in your organization, you can start by importing the process to reprocess master data. For more information about importing the process to reprocess master data, see Import the process to reprocess master data.
If you have the MDMProcessMasterData process from the July 2024 release, you need to get the latest process file that supports processing active and deleted records. Before you get the latest file, remove the read-only access to the process so that you can overwrite the existing file with the latest file.
To set the update permissions, use the UpdateACL API and submit a POST request.
To submit a POST request, use the following URI with the session ID of the administrator who manages the organization:
<baseApiUrl>/frs/v1/UpdateACL
When you submit a POST request to set the update permissions, you require the artifactId of the process. To get the artifactId of the process, see Get the artifact ID of the process.

Sample Request

Use the following POST request to set the update permissions of the MDMProcessMasterData process:
POST https://use4-mdm.dm-us.informaticacloud.com/frs/v1/UpdateACL
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
Content-Type: application/json
{
"artifactId": "9TvdYgWHVOrhUHnMLMCc0z",
"aces": [
{
"operation": "CREATE_ACE",
"permission": {
"changePermission": true,
"read": true,
"update": true,
"delete": true,
"execute": true
},
"idsInfo": {
"id": "User ID",
"type": "USER"
}
}
]
}

Sample Response

After the POST request to modify the permissions of the MDMProcessMasterData process, you get the following response:

{
"@odata.context": "$metadata#BaseEntities",
"value": [
{
"guid": "FRS_ID",
"code": "FRS_200",
"message": "Successfully Updated ACLs"
}
]
}

Import the process to reprocess master data

To reprocess master data, import the MDMProcessMasterData process after you upgrade the organization.
    1To request the MDMProcessMasterData process, contact Informatica Global Customer Support.
    After the necessary approvals, you'll receive a ZIP file that contains the MDMProcessMasterData process.
    2In Cloud Application Integration, click Explore.
    3Navigate to the Business360 folder.
    4Click Import.
    5On the Import Assets page, click Choose File, and select the ZIP file that contains the MDMProcessMasterData process, and click Open.
    6Click Import.

Get the artifact ID of the process

To modify permissions and create a user to access the MDMProcessMasterData process, you require the artifact ID of the process to uniquely identify it.
To get the artifact ID of the process, use the LookupArtifactsDetailsByPath API and submit a POST request with the following URI:
POST <baseApiURL>/frs/api/v1/LookupArtifactsDetailsByPath

Sample Request

Use the following POST request to get the artifact ID of the MDMProcessMasterData process:
POST https://use4.dm-us.informaticacloud.com/frs/api/v1/LookupArtifactsDetailsByPath
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
Content-Type: application/json
{
"lookupParamPath": [
{
"name": "MDMProcessMasterData",
"type": "PROCESS",
"location": [
{
"type": "Space",
"name": "REG"
},
{
"name": "Business360",
"type": "Project"
}
]
}
]
}

Sample Response

The sample response shows the HTTP 200 OK response code and gets the artifact ID of the MDMProcessMasterData process. The response shows the artifact ID as 9TvdYgWHVOrhUHnMLMCc0z in the artifact section.
{
"@odata.context": "$metadata#BaseEntities",
"value": [
{
"orgId": "4MEN7vwklj8biicae7QiKX",
"status": {
"code": "FRS_200",
"message": ""
},
"tags": [],
"artifact": {
"@odata.type": "#OData.frs.Document",
"id": "9TvdYgWHVOrhUHnMLMCc0z",
"name": "MDMProcessMasterData",
"description": "",
"owner": "2UQOrM7xtu1euGYkYlBeOr",
"createdBy": "2UQOrM7xtu1euGYkYlBeOr",
"lastUpdatedBy": "2UQOrM7xtu1euGYkYlBeOr",
"lastAccessedBy": "2UQOrM7xtu1euGYkYlBeOr",
"createdTime": "2024-07-25T04:01:13Z",
"lastUpdatedTime": "2024-08-01T11:29:30Z",
"lastAccessedTime": "2024-08-01T11:29:30Z",
"expiresBy": "2038-01-18T00:00:00Z",
"parentInfo": [
{
"parentId": "7cCn5thwWFLhiZoSosphKL",
"parentName": "REG",
"parentType": "Space"
},
{
"parentId": "0XuRGcy4SdyehONacV75yq",
"parentName": "Business360",
"parentType": "Project"
}
],
"documentType": "PROCESS",
"contentType": "application/json; charset=utf-8",
"documentState": "VALID",
"aclRule": "org",
"subcontainerCount": 0,
"customAttributes": {
"stringAttrs": [
{
"name": "publishedBy",
"value": "Delta_Apr4Adm"
},
{
"name": "SubType",
"value": ""
},
{
"name": "binding",
"value": "rest"
},
{
"name": "ReferencedPublishingAllowed",
"value": "true"
},
{
"name": "APIName",
"value": "MDMProcessMasterData"
},
{
"name": "publicationStatus",
"value": "published"
}
],
"numberAttrs": [],
"dateAttrs": [
{
"name": "publicationDate",
"value": "2024-08-01T11:29:39Z"
}
]
},
"repoInfo": {
"repoParams": [],
"repoPath": null,
"repoHandle": "tf2VR4109cjIw8j-gt-3576941-2024-07-25T04:01:13.177Z::pd.xml",
"frsPath": null
},
"isSourceControlled": false,
"checkedOutById": null
},
"docRef": null
}
]
}

Modify permissions and create a user for reprocessing master data

After you import the MDMProcessMasterData process, set the process to read only so that users can't modify it. Also, create a user to access the MDMProcessMasterData process.
To set the read-only permission for the process and to create a user for the process, use the UpdateACL API and submit a POST request. To submit a POST request, use the following URI with the session ID of the administrator who manages the organization:
<baseApiUrl>/frs/v1/UpdateACL

Sample Request

Use the following POST request to modify the permissions of the MDMProcessMasterData process to read only:
POST https://use4-mdm.dm-us.informaticacloud.com/frs/v1/UpdateACL
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
Content-Type: application/json
{
"artifactId": "9TvdYgWHVOrhUHnMLMCc0z",
"aces": [
{
"operation": "CREATE_ACE",
"permission": {
"changePermission": true,
"read": true,
"update": false,
"delete": false,
"execute": true
},
"idsInfo": {
"id": "Organization ID",
"type": "ORG"
}
}
]
}

Use the following POST request to create a user to access the MDMProcessMasterData process:
POST https://use4-mdm.dm-us.informaticacloud.com/frs/v1/UpdateACL
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
Content-Type: application/json
{
"artifactId": "9TvdYgWHVOrhUHnMLMCc0z",
"aces": [
{
"operation": "CREATE_ACE",
"permission": {
"changePermission": true,
"read": true,
"update": true,
"delete": true,
"execute": true
},
"idsInfo": {
"id": "USER ID",
"type": "USER"
}
}
]
}

Sample Response

After the POST requests to modify the permissions of the MDMProcessMasterData process and create a user to access the MDMProcessMasterData process are successful, you get the following response:
{
"@odata.context": "$metadata#BaseEntities",
"value": [
{
"guid": "FRS_ID",
"code": "FRS_200",
"message": "Successfully Updated ACLs"
}
]
}

Publish the process for reprocessing master data

After you modify permissions and create a user for the MDMProcessMasterData process, publish the process to invoke or run it.
    1In Cloud Application Integration, click Explore.
    2Navigate to the Business360 folder.
    3Select the MDMProcessMasterData process, and click Actions.
    4Click Publish.

Match and export data

To match external data with master data without importing the external data, the match process requires match keys for master records. You can generate match keys for master records by using a generate search indexes or match keys job. Additionally, you need the predefined Cloud Application Integration process, MDMExternalMatch, to match and export data.
To match external data, ensure that you perform the following tasks after you upgrade your organization:
  1. 1Generate match keys for master records by using a generate search indexes or match keys job.
  2. 2Import the MDMExternalMatch process to your organization.
  3. 3Get the artifact ID of the MDMExternalMatch process.
  4. 4Modify permissions and create a user for the MDMExternalMatch process.
  5. 5Publish the MDMExternalMatch process.

Step 1. Generate match keys for master records

To match external data with master data, generate match keys for master records by running a generate search indexes or match keys job. The match and export process uses match keys of master records for matching.
For more information about the generate search indexes or match keys job, see Define and run the generate search indexes or match keys job.

Step 2. Import the process for match and export orchestration

MDM SaaS uses the predefined MDMExternalMatch process to orchestrate the match and export process. After you upgrade the organization, import the process.
    1To request the MDMExternalMatch process, contact Informatica Global Customer Support.
    After the necessary approvals, you'll receive a ZIP file that contains the MDMExternalMatch process.
    2In Cloud Application Integration, click Explore.
    3Navigate to the Business360 folder.
    4Click Import.
    5On the Import Assets page, click Choose File, and select the ZIP file that contains the MDMExternalMatch process, and click Open.
    6Click Import.

Step 3. Get the artifact ID of the process

To modify permissions and create a user to access the MDMExternalMatch process, you require the artifact ID of the process to uniquely identify it.
To get the artifact ID of the process, use the LookupArtifactsDetailsByPath API and submit a POST request with the following URI:
POST <baseApiURL>/frs/api/v1/LookupArtifactsDetailsByPath

Sample Requests

Use the following POST request to get the artifact ID of the MDMExternalMatch process:
POST https://use4.dm-us.informaticacloud.com/frs/api/v1/LookupArtifactsDetailsByPath
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
Content-Type: application/json
{
"lookupParamPath": [
{
"name": "MDMExternalMatch",
"type": "PROCESS",
"location": [
{
"type": "Space",
"name": "REG"
},
{
"name": "Business360",
"type": "Project"
}
]
}
]
}

Sample Response

The sample response shows the HTTP 200 OK response code and contains the artifact ID of the MDMExternalMatch process. The response shows the artifact ID as a7d1raphIOLdjfNVarUJaC in the artifact section.
{
"@odata.context": "$metadata#BaseEntities",
"value": [
{
"orgId": "lkV1tSYJzKYcdNHddSjsWN",
"status": {
"code": "FRS_200",
"message": ""
},
"tags": [],
"artifact": {
"@odata.type": "#OData.frs.Document",
"id": "a7d1raphIOLdjfNVarUJaC",
"name": "MDMExternalMatch",
"description": "",
"owner": "dR1G6Qi59OKj6qCYOfWZsA",
"createdBy": "dR1G6Qi59OKj6qCYOfWZsA",
"lastUpdatedBy": "dR1G6Qi59OKj6qCYOfWZsA",
"lastAccessedBy": "dR1G6Qi59OKj6qCYOfWZsA",
"createdTime": "2024-06-11T09:22:29Z",
"lastUpdatedTime": "2024-06-11T09:22:29Z",
"lastAccessedTime": "2024-06-11T09:22:29Z",
"expiresBy": "2038-01-18T00:00:00Z",
"parentInfo": [
{
"parentId": "7cCn5thwWFLhiZoSosphKL",
"parentName": "REG",
"parentType": "Space"
},
{
"parentId": "9Lf4MSeHu5vkk8CS6pTcA2",
"parentName": "Business360",
"parentType": "Project"
}
],
"documentType": "PROCESS",
"contentType": "application/json; charset=utf-8",
"documentState": "VALID",
"aclRule": "org",
"subcontainerCount": 0,
"customAttributes": {
"stringAttrs": [],
"numberAttrs": [],
"dateAttrs": []
},
"repoInfo": {
"repoParams": [],
"repoPath": null,
"repoHandle": "f2B7O2htghGZ5i4-gt-483987-2024-06-11T09:22:29.093Z::pd.xml",
"frsPath": null
},
"isSourceControlled": false,
"checkedOutById": null
},
"docRef": null
}
]
}

Step 4. Modify permissions and create a user for the match and export orchestration

After you import the MDMExternalMatch process, set the process to read only so that users can't modify it. Also, create a user to access the MDMExternalMatch process.
To set the read-only permission for the process and to create a user for the process, use the UpdateACL API and submit a POST request. To submit a POST request, use the following URI with the session ID of the administrator who manages the organization:
<baseApiUrl>/frs/v1/UpdateACL

Sample Requests

Use the following POST request to modify the permissions of the MDMExternalMatch process to read only:
POST https://use4-mdm.dm-us.informaticacloud.com/frs/v1/UpdateACL
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
Content-Type: application/json
{
"artifactId": "a7d1raphIOLdjfNVarUJaC",
"aces": [
{
"operation": "CREATE_ACE",
"permission": {
"changePermission": true,
"read": true,
"update": false,
"delete": false,
"execute": true
},
"idsInfo": {
"id": "Organization ID",
"type": "ORG"
}
}
]
}
Use the following POST request to create a user to access the MDMExternalMatch process:
POST https://use4-mdm.dm-us.informaticacloud.com/frs/v1/UpdateACL
IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX
Content-Type: application/json
{
"artifactId": "a7d1raphIOLdjfNVarUJaC",
"aces": [
{
"operation": "CREATE_ACE",
"permission": {
"changePermission": true,
"read": true,
"update": true,
"delete": true,
"execute": true
},
"idsInfo": {
"id": "3VMH0uFUXQVddwVkjrfJUv",
"type": "USER"
}
}
]
}

Sample Response

After the POST requests to modify the permissions of the MDMExternalMatch process and create a user to access the MDMExternalMatch process are successful, you get the following response:
{
"@odata.context": "$metadata#BaseEntities",
"value": [
{
"guid": "FRS_ID",
"code": "FRS_200",
"message": "Successfully Updated ACLs"
}
]
}

Step 5. Publish the process for match and export orchestration

After you modify permissions and create a user for the MDMExternalMatch process, publish the process to invoke or run it.
    1In Cloud Application Integration, click Explore.
    2Navigate to the Business360 folder.
    3Select the MDMExternalMatch process, and click Actions.
    4Click Publish.