You know that YepCode allows you to manage different versions of your processes and modules, so then you may start execution using an specific version of the source code.
This is great, but we wanted to go beyond... so we have introduced YepCode Version Aliases that are pointers to a process version that you can update with ease
This feature addresses the need to change the version used by an external service without deploying changes to that service.
Consider a scenario where an external service calls YepCode via a webhook, specifying a process version (e.g., v1.0) in the invocation header.
When you release a new process version (e.g., v2.0) and want to switch to it, updating the external service can be cumbersome. Instead, by using an alias in the webhook invocation (e.g., stable), initially linked to version v1.0, you can seamlessly transition to version v2.0 by simply updating the alias in the YepCode UI.
This approach eliminates the need to modify the external service, making version management more efficient
Version aliases can be used exactly in the same scenarios where process versions are available: run now, webhooks or scheduled configurations.
