Import-Deploy operation for high Security Level should work for import files holding unversioned items

Current Situation

When trying to import and to deploy objects from an import archive file containing versioned items and unversioned items, deployment fails with the error:

No versionId found in configuration. Deployment will not be processed.

.
The error occurs when trying to determine the versionId from the first JSON configuration file.

• If the first file, for example is a Job Resource, then no versionId is available as Job Resources are unversioned items. This will raise the error.
• If the first file is a workflow, then the versionId can be determined successfully and deployment works fine.

Desired Behavior

The steps to determine the versionId from configuration files in the import archive file

• should always check the next file, if no versionId is found,
• should continue checking the next file until first occurrence of a versionId.
• The error should be raised when applicable only, for example if the import archive file contains no workflows and not a single file in the import archive file specifies a versionId

Patches

Patches are needed for JOC Cockpit if operated for the high Security Level. Other Security Levels are not affected.

• 2.5.9
  • https://download.sos-berlin.com/patches/2.5.9-patch/js7_joc.2.5.9-PATCH.API-2.JOC-1877.jar [ sha256 ] [ sig ] [ tsr ]

• 2.6.6
  • https://download.sos-berlin.com/patches/2.6.6-patch/js7_joc.2.6.6-PATCH.API-2.JOC-1877.jar [ sha256 ] [ sig ] [ tsr ]

• 2.7.1
  • https://download.sos-berlin.com/patches/2.7.1-patch/js7_joc.2.7.1-PATCH.API-3.JOC-1877.jar [ sha256 ] [ sig ] [ tsr ]