Deployment mechanism for non-versioning business process artifacts

A non-transitory, computer-readable medium storing program code executable by a computer to perform a method, said method comprising:

• detecting that a deployment archive to be deployed to a runtime server includes first and second business process artifacts, wherein the first artifact supports versioning and the second artifact does not support versioning;
• calculating a version identifier to be associated with the second artifact;
• determining at least one prior version identifier of the second artifact, associated with at least one prior deployment of the deployment archive to the runtime server, based on information from a version history database;
• deploying the deployment archive containing the first and second artifacts to the runtime server along with the at least one prior version of the second artifact associated with the determined prior version identifiers;
• and
• storing a new version history in the version history database by adding the newly calculated version identifier to the at least one determined prior version identifier.

A system, comprising:

• a computer;
• and
• a non-transitory, computer-readable medium storing program code executable by the computer to perform a method, said method comprising:
• detecting that a deployment archive to be deployed to a runtime server includes first and second business process artifacts, wherein the first artifact supports versioning and the second artifact does not support versioning;
• calculating a version identifier to be associated with the second artifact;
• determining at least one prior version identifier of the second artifact, associated with at least one prior deployment of the deployment archive to the runtime server, based on information from a version history database;
• deploying the deployment archive containing the first and second artifacts to the runtime server along with the at least one prior version of the second artifact associated with the determined prior version identifiers;
• and
• storing a new version history in the version history database by adding the newly calculated version identifier to the at least one determined prior version identifier.