MDM: known issues and known limitations

• The integrated matching feature supports only primary keys of the type string.
• The integrated matching feature does not support matching on entities with composite primary keys.
• The mapping between MDM and Talend Data Stewardship only applies to simple type elements at the root level in an MDM entity, and will ignore complex type elements or repeatable elements.

By default, when reading or writing values of a record through the mdm_context variable, the permissions checks are performed on the current assigned user of a task.

• For non-human tasks, there is no associated user, when directly reading or writing values of a record through the mdm_context variable, you can
  • use the setBypassSecurity method to bypass security checks, by enclosing your code between the following two lines to disable then re-enable security checks.

    mdm_context.setBypassSecurity(true); // disabling
    ...
    mdm_context.setBypassSecurity(false); // enabling again

    or

  • use the setUpdateUser method to set a valid user prior to performing read or write actions and reset the current user to nothing after that, without having to bypass the permissions checks.

    mdm_context.setUpdateUser("username"); // specify a given user as the current one
    ....
    mdm_context.setUpdateUser(null); // reset the current user to nothing

• For human tasks,
  • when executing read or write operations through the mdm_context variable, the current assigned user is automatically used to verify read or write permissions onto the values. If you want to use another user, you can overwrite it by using the setUpdateUser method.
  • when outside the operations, for example, in a local variable, there is no assigned user, which is similar to non-human tasks.

1. Deploy all objects except the Workflow.
2. Start the manual synchronization process from the User Management tab in the Talend MDM Web UI whenever a user or a role is created/changed to ensure that the corresponding information will be properly created in Bonita (Demo_User and Demo_Manager roles and their associated users).
3. Deploy the Workflow.

1. Unzip Talend Studio as usual.
2. Open a Terminal window on the folder where you unzipped your Talend Studio.
3. Execute either of the following commands.

   xattr -d com.apple.quarantine *

   Or

   xattr -c *

1. Click the Apple icon, and then click System Preferences.
2. Under System Preferences, click Security & Privacy.
3. Under Security & Privacy, click General tab.

4. Click the lock icon next to Click the lock to make changes, and then identify yourself using the user name and password for an account with administrator rights. Only administrators can change the security settings.

5. Under Allow apps download from, select the Anywhere radio button then confirm your choice in the dialog box that opens.
6. Close all windows, so that your Mac automatically locks the Security & Privacy settings for you again.
7. Install Talend Studio (or whatever other executable you want to install) by following the usual installation procedure. Note that, when you double click the Talend-Studio-macosx-cocoa.app file, you will see a warning saying that it is an application downloaded from the Internet, but if you click Open, your Mac should let you install it without further issues.
8. Once you have completed the installation process, you can repeat the above steps to return your Security & Privacy settings to their previous value if you want.

For more information, see https://jira.talendforge.org/browse/TMDM-6805.

In particular, make sure you process the ACTIVE and FAILED queue before performing any migration, since the migration procedure will cause ACTIVE, FAILED and COMPLETED queues to be lost.