Describe the bug
Using the mass import you expect an error message for every kind of failure in creating processes for the given ids. You get a error listing for ids already existing in your process list. But a failure in importing caused by f.e. a missing roleCode in the ruleset is not reported at all - this id will be skipped without any comment and the mass import will end without any protocol. Afterwards it's quite cumbersome to find the skipped id(s).
To Reproduce
Steps to reproduce the behavior:
Create a tiny list of ids - containing one problem item (perhaps prepared by an alignement for the roleCodes in ruleset to cause an error)
Execute the procedure of massimport
See error
Expected behavior
Including this kind of failure in creating processes in the existing error logging:
Describe the bug Using the mass import you expect an error message for every kind of failure in creating processes for the given ids. You get a error listing for ids already existing in your process list. But a failure in importing caused by f.e. a missing roleCode in the ruleset is not reported at all - this id will be skipped without any comment and the mass import will end without any protocol. Afterwards it's quite cumbersome to find the skipped id(s).
To Reproduce Steps to reproduce the behavior:
Expected behavior Including this kind of failure in creating processes in the existing error logging:
Release Version 3.6.1