Cumulative Known Limitations

Cumulative Known Limitations

The following table describes known limitations that are carried forward from previous releases:
Reference Number
Description
TCR-4830
In the Customer Portal, on the
General information
page of the registration form, the lookup values in the State of Incorporation field display state codes instead of state names.
TCR-4805
After you validate the database schema before upgrading Customer 360, if you find the following errors in the validation report, contact the Informatica Global Customer Support:
  • E360_COMPONENTCONTAINER_COMPONENT.StartPage|StartPageStartPageLayout1|c3|chartscomponent_assign_tasks_by_users
  • E360_COMPONENTCONTAINER_COMPONENT.StartPage|StartPageStartPageLayout1|c4|chartscomponent_closed_tasks_by_users
  • E360_COMPONENTCONTAINER_COMPONENT.StartPage|StartPageStartPageLayout1|c2|chartscomponent_assign_tasks_by_user_roles.
TCR-4797
On the
Insurance
tab of the Customer Portal, after a portal user filters the policies based on the policy number, the filter type value disappears when the filter is removed.
TCR-4750
On the
Submitted
tab of the
My Records
page in Customer 360, the hierarchy tasks display incorrect number of days in the status of the task.
TCR-4601
When a user with the data analyst role deletes a contact of a record, the contact gets deleted without triggering a review process.
TCR-4556
In the Customer Portal, on the
Key Executive
page of the registration form, if a portal user applies a filter, the values of the Executive Type field is change to
None
.
TCR-4548
In the Customer Portal, on the
Key Executive
page of the registration form, if a portal user sets the
Items Per Page
to 10, the values for some of the
Executive Type
fields are changed to
None
.
TCR-4547
In the Customer Portal, on the
Key Executive
page of the registration form, if a portal user sorts the fields by executive type, the values of the fields might change.
TCR-4067
When you access the online help in Customer 360, the Data Director online help opens.
Workaround: Access the Informatica MDM - Customer 360 User Guide from the documentation portal.
TCR-3799
After you enable Elasticsearch on a Process Server, if you run the
BG_ All_Lookup_Load
batch job without configuring Elasticsearch on the Provisioning tool, the batch job might fail with the following error:
java.rmi.RemoteException: com.siperian.common.SipException: SIP-52071: Elasticsearch cluster is not configured for this ORS [localhost-ora18c-C360_ORS].
TCR-3020
In IBM DB2 or Microsoft SQL Server environments, you cannot migrate to the data model based on the Party table from the data model based on the Party Role table.
TCR-3019
In IBM DB2 and JBoss environments, the dashboard view of a record might display the following error message in the Hierarchies panel:
Internal error. Cannot load the hierarchy.
Workaround: Perform the following tasks:
  1. Open the following file:
    <JBoss installation directory>/standalone/configuration/standalone-full.xml
  2. Add the following attribute to the
    xa-datasource
    section of the
    Customer 360
    Operational Reference Store:
    <xa-datasource-property name="AllowNextOnExhaustedResultSet">1</xa-datasource-property>
  3. Save the file, and restart the application server.
TCR-3014
When you use the Java project that is included in the
Customer 360
installation files to extend the user exit, the Java project fails when you compile it.
Workaround: Before you compile the project, perform the following tasks:
  1. Run the following commands:
    mvn install:install-file -Dfile=<MDM Hub installation directory>\hub\server\lib\mdm-ue.jar -DgroupId=com.informatica.mdm -DartifactId=mdm-ue -Dversion=10.3.0-SNAPSHOT -Dpackaging=jar
    mvn install:install-file -Dfile=<MDM Hub installation directory>\hub\server\lib\siperian-api.jar -DgroupId=com.informatica.mdm -DartifactId=siperian-api -Dversion=10.3.0-SNAPSHOT -Dpackaging=jar
    mvn install:install-file -Dfile=<MDM Hub installation directory>\hub\server\lib\siperian-common.jar -DgroupId=com.informatica.mdm -DartifactId=siperian-common -Dversion=10.3.0-SNAPSHOT -Dpackaging=jar
  2. Comment the following code in the Java project:
    <repository> <id>infamdm.external</id> <url>http://mdmmaven01.informatica.com:8081/nexus/content/repositories/thirdparty/</url> </repository> <repository> <id>mdmcentral</id> <name>MDM Proxy Repository</name> <url>http://mdmmaven01.informatica.com:8081/nexus/content/repositories/mdminfa/</url> </repository>
TCR-3012
In IBM DB2 environments, when you run the
lookup_localization
script, the script imports the lookup data in all the languages except the Russian language. The script fails with the following error message:
com.informatica.solutions.lookup.localisation.exception.LookupLocalisationException: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.19.26
TCR-2980
After you update an active record, the dashboard view of the record shows the updated values even though the changes are not approved.
TCR-2966
In environments that use the data model based on the Party Role table, when you add a relationship between two Person records, an empty Related Person record is created for one of the records.
TCR-2930
In a localized environment, when you open a record, the hierarchy name is not localized in the Hierarchy panel.
TCR-1908
On the
Home
page, when you sort the tasks based on priority, the tasks are incorrectly sorted.
TCR-1899
When you edit a record, if you update an address child record, you cannot save the changes and get the following error message:
SIP-50112: Could not run the WriteCO business entity service.
TCR-1647
In WebSphere environments, Customer 360 integration with Product 360 does not work.
TCR-1527
During a file import, if you configure the header row to a value other than 1, Customer 360 shows an incorrect preview of your imported file.
TCR-1358
In a hierarchy, if you add a relationship from a B2C customer to a B2B customer, Customer 360 does not display the change history.
TCR-1297
Customer 360 does not support the TIFF image format in the Product Details widget.
TCR-1169
For the Organization customer type, when you edit a relationship or classification to add additional relationship attributes, Customer 360 does not save the attributes that you add.

0 COMMENTS

We’d like to hear from you!