processingPrompt noValue=true is not working

[Ihor]

I have an inbound call flow which has a data action with processingPrompt NoValue: true

                          - callData:
                              name: Call Data Action
                              processingPrompt:
                                noValue: true

But when i publish it and check the architect flow UI i can see that data action is set to System Prompt.
Why does not the architect honor the processingPrompt NoValue?

[charlie.conneely]

Hi Ihor

I'm not seeing this behaviour on my end. Everything is working fine. I did notice my test flow had these properties also:

inboundCall:
    # ...
    settingsActionDefaults:
        callData:
          processingPrompt:
            noValue: true

Maybe this could help in your case?

Also, would you mind adding the Architect tag to this post? I don't believe this is CX as Code related

-Charlie

[Ihor]

I found that the issue occurs if there is a processing prompt specified in the default data action settings.
However i want for some specific data action not to use processing prompt so i set it noValue:true.
Why does architect not tolerate a local data action setting and overwrite with the default settings. Not that it works if i do it via UI so it should work when using archy or terraform.