Clarification on Config Variable Behavior During Integration Testing

[DigitalD]

Hi All,

I encountered an issue while testing the usage of config variables in an integration and wanted to clarify if this behavior is by design or if I might be missing something. Below are the steps I followed:

1. I created the config variables during the integration setup.
2. During the publishing process, I was prompted to enter values for the config variables.
3. I provided the required values and successfully published the integration.
4. However, while testing the integration, I was prompted again to enter the config variable values.
5. When I entered different values during testing, the output still reflected the original values provided during publishing, rather than the new ones.

Could you please help me understand the purpose of the config variable prompt during testing? Is this expected behavior, or could there be something I’ve overlooked in the process?

Thank you for your assistance. I look forward to your guidance on this matter.

[deepgoel · Accepted solution]

Hey, Thanks for pointing it out. This is not the intended behavior for the config variable. The will be fixed soon. As far as config variable intended use is concerned when you publish the integration with the config variable their value cannot be altered. Please let me know if you have any further question. Thanks!

[DigitalD]

Thanks for the clarification...