Changes introduced by
OPENIDM-6656 to use the RepositoryService when performing CRUD operations against the scheduler objects has resulted in objects being distributed across both the genericobjects and schedulerobjects tables.
The problem is caused by the fact that our OOTB repo.jdbc.json sample configurations declare the generic scheduler object as follows:
because we are now using the RepositoryService for CRUD operations, child objects below the base scheduler object type are considered generic objects and written to the genericobjects table.
We need to change the above scheduler object definition to the following in order to include child objects: