![]() | ![]() |
|
Duplicate objects not picked up until check-in. Duplicate items can be accidently created when importing data (eg using the translator to import multiple objects from excel). Although it lets you have those duplicate items there - when you try to check them into KE the Check in will not occur and it is difficult to find out why.
The validation of duplicates should be at a point before checkin. Either duplicates should be allowed, or duplicates should be picked up by the translator import. Alternatively there should be a nice way to consolidate duplicate items.
Sometimes when duplicate items are imported it will only take the first and the rest are not retained - in this case there again is no warning that this data is being deleted. Perhaps there should be a warning, an option for consolidation or the option to add a suffix to the end of the duplicates (as in when merging databases).
What ever the solution more validation is required when using the translator or other input methods that should be equivalent to the validation required for check-in to KE
You must be a registered user to add a comment here. If you've already registered, please log in. If you haven't registered yet, please register and log in.
How to Be Notified of New Releases
How to Suggest Product Enhancements
Metastorm BPM 7.6.4 Hotfix 2 (7.6.4.2) is now available for download in the 'Patches' section of the Knowledge Center here.
Metastorm BPM Widgets Release 2 for OpenText Smart Business Workspace Version 9.1 and Metastorm BPM 9.1.3 is now available for download in the 'Patches' section of the Knowledge Center here. For more information see this post.
Metastorm BPM 9.1 SR3 (9.1.3) is now available for download in the 'Patches' section of the Knowledge Center here. For more information see this post.
Metastorm BPM 9.1.2 Hotfix 2 (9.1.2.2) is now available for download in the 'Patches' section of the Knowledge Center here.
Note: Software and documentation are now in the Knowledge Center (KC) located here.
Have a question about the Community Site? Contact Us
![]() |
![]() |
![]() |
|
|
![]() |
![]() |
![]() |
















