App level versioning doesn't support when engagement services are configured in MF app. How to achieve versioning in this case?

HCL Volt MX Volt MX Forum
1
This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal.

And service level versioning doesn't maintain uniqueness of changes. For instance, if i have versioned a service from 1.0 to 2.0 and modified some of the request & response parameters in 2.0. These changes are reflected in 1.0 as well.

So finally, we ended up with creating new service by cloning it and named the service as 'Servicev1' and 'Servicev2'.

2

Can you please provide the steps that you are executing for the app level versioning use case that you mention? We can take a guess but would like to know the flow exactly before we can respond.

3

Hi,

I will schedule a call to discuss more on this.

Thanks and Regards