MDM - Customer 360
- MDM - Customer 360 10.4 HotFix 3
- All Products
Reference Number
| Description
|
|---|---|
TCR-5449
| When you refresh the
Home page or re-login to Customer 360, the
Customers Added by Year and
Source Systems charts do not appear on the
Home page.
|
TCR-5335
| If you use the special character ampersand (&) in the
Full Name field when you create a Person record, the
Person
Dashboard displays ampersand as
& .
|
TCR-5317
| When you create a Person business entity record, the data entry form displays the fields of the
Specialization child record as mandatory fields.
|
TCR-5247
| On the
My Records page, when you adjust the number of tasks to view on the page, the submitted records count displays incorrectly as 6 even though the actual count is different.
|
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
Executive Type fields might change.
|
TCR-5343
| In a Linux and WebSphere environment, the Customer 360 installer fails.
|
TCR-4797
| In the Customer Portal, if a portal user filters the policies based on the policy number from the
Insurance tab, the filter type value disappears after the filter is removed.
|
TCR-4548
| In the Customer Portal, if a portal user sets the
Items Per Page to 10 on the
Key Executive page of the registration form, the values for some of the
Executive Type fields change to
None .
|
TCR-4556
| In the Customer Portal, if a portal user applies a filter on the
Key Executive page of the registration form, the values of the
Executive Type field change to
None .
|
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:
|
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-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:
|
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:
|