Hi Dennis, thanks for taking the time to look at this, but I have to insist that this is a FORMS issue not a CMS issue. The test scenario you used does not use forms at all. The fact is that using forms v8.3.2 works and v8.7.6 does not. Having decompiled Umbraco.Forms.Core.dll for each version there are definite code differences in the parsing functions. The forms assemblies were only upgraded in order to fix a security vulnerability up to and including v8.7.5. We are in a strange situation in that we cannot go to the latest version of forms 8 (even then the magic string issue could still exist) because it breaks our CMS at v8.5.5, and we cannot upgrade the CMS very easily as we have made some deeply embedded custom code changes which we simply don't have the resources to re-apply.

Bottom line is that a magic string in the submission message of a form workflow that worked in Forms 8.3.2 no longer works in Forms 8.7.6 which can be proved by simply swapping out the three Umbraco.Forms assemblies.

Thanks in anticipation of a resolution.

Hi Ashford

I can see that I forgot to include the word Forns in my message last time. So just to make it clear I used Umbraco Forms 8.10.2.

I got it to work by doing this

In the template, I added the following code

@{
    // Set a test session variable
    Session["TestSessionMessage"] = "Hello";
}

And then I configured this for the message to display on submit:

Thank you - this is from the session: [%TestSessionMessage]

And in Umbraco Forms 8.10.2 it worked for me

I also just tried to install Umbraco Forms 8.10.2 on Umbraco 8.5.5 and it works fine after the install

You can of course have some custom code that I am not aware of

Sorry for the little confusion here

All the best,

/Dennis