Use Cases and versioning
Use Cases and versioning
Problem context
During a Automation Process Project lifecycle, there are cases when you need to keep and execute multiple AP versions on a same Control Server. To support this scenario, you are required to clone every single AP Project artifact and give it a unique name and version.
You can perform such cloning process manually. Mind that it takes a few hours every time and becomes a potential source of human mistakes, thus this work must be automated.
Overview
For now platforms supports UCing and versioning for datastores only. In Future it will be extended for all platforms entities like Automation Process, Secret Vaults and so on.
usecase.properties
Its possible to enable runtime rendering of an Entity's physical Data Store's name according to a Use Case resource naming pattern.
For that the following steps needs to be done:
- Make sure you have defined use case naming pattern in the distribution package. For that 'src/main/resources/usecase.properties' file should have 'uc_resource_name_pattern' property set - for example "uc_resource_name_pattern=UC_${uc_name}_${entity_name}_${uc_version}"
- It the 'uc_resource_name_pattern' property is not defined it is uc_resource_name_pattern=${entity_name}, i.e. no versioning
- Naming pattern will be applied during an AP run from the distribution package. Its possible to use any AP parameter in the naming pattern for the entity.
- Note that in this scenario its possible to use only properties defined in the usecase.properties.
- Finally, at AP run, any AP parameter will override the same-name property from usecase.properties.
Here is the file sample:
