Multidomain MDM
- Multidomain MDM 10.3 HotFix 2
- All Products
Reference Number
| Description
|
---|---|
MDM-22814
| Siperian workflow engine. When you try to reassign a claimed task, the Assignees list is empty in the Edit task dialog box.
|
MDM-14205
| If you use the sample Operational Reference Store, an error occurs when you open the Workflow Manager in the Hub Console. In the sample Operational Reference Store, the value of WORKFLOW_ENGINE_NAME in MDM_SAMPLE.C_REPOS_DB_RELEASE does not match the value of NAME in CMX_SYSTEM.C_REPOS_WORKFLOW_ENGINE.
Perform one of the following workarounds:
|
MDM-13359
| If you use ActiveVOS, a user cannot belong to a role that creates an unmerge task and also belong to a role to approves that task type. If a user belongs to both roles, an error occurs when the user tries to approve the unmerge task.
|
MDM-12011
| When you install the MDM Hub with ActiveVOS, the following exception appears in the postInstallSetup.log file:
You can safely ignore this exception. |
MDM-9079
| In the ActiveVOS Console, on the
MDM Identity Provider page, you must enter the password of the MDM Hub user named
admin in the
MDM Connection Settings Password field. You cannot use the password for any other user, even if the user has administrative privileges.
|
MDM-9041
| When multiple workflow triggers apply to an action, the first applicable trigger is applied, even if subsequent triggers are specific to the business entity.
Workaround: In the task configuration file, place the triggers that are specific to a business entity at the beginning of the file. Place the more general triggers at the end of the file.
|
MDM-8763
| When you install the MDM Hub with embedded ActiveVOS in a Linux environment, the following error appears in the postInstallSetup.log:
You can safely ignore the error.
|
MDM-8622
| When you import ActiveVOS tasks from version 9.7.1 and run a batch file to add presentation parameters to the tasks, an error occurs.
You can safely ignore the error.
|
MDM-8086
| The task priority set by the MDM Hub cannot be used to trigger an ActiveVOS escalation.
|
MDM-6473
| The Hub Server silent installation process sets the incorrect ActiveVOS database URL when the silent installer property
AVOS.ORACLE.CONNECTION.TYPE is set to
SID .
Workaround: Before you perform the Hub Server silent installation, set the silent installer property
AVOS.ORACLE.CONNECTION.TYPE to
Service Name .
|
MDM-5290
| When you change the BPM adapter, the number of merge tasks is counted incorrectly and the number might exceed the threshold value for merge tasks.
Workaround: Set the value of the ROWID_TASK column in the _MTCH table to NULL.
|