This issue was already solved. I only posted so others can find what I could not find when searching for this.
In a cloud system, I have edited the "Error message of invalid input" for a field mask, but the error message displayed to the user is the original message, instead of the new edited message.
How can I display to users the new error message for this field mask without creating an entirely new field mask and replacing in all dialogs?
EDIT: If it matters, the OrgID is in the new 5000000 range.
EDIT 2: After about 20 minutes, the new error message is now being displayed to the user.
I recently installed the latest DW7 minor update (2019-01-18) for a customer, and I have a handful of people who are used to using the right-click context menu to paste into input fields. I myself almost always use ctrl-c / ctrl-v so I didn't notice, but from what I hear the input field context menu was available before and has now been disabled in this version.
This is definitely a minor thing, but I'm curious enough to ask. All the stanadard keyboard shortcuts still work, so it's just a bit of training for some people, a matter of being used to one method and now having to use another. Believe it or not, ctrl-c / ctrl-v is a brand new concept for some of our users!
Previously running: 2018-12-07 update
Currently running: 2019-01-18 update
I guess the KB article just had the wrong date. It now shows 12/07.
I didn't think to look at the individual fix items before, they probably already matched the items in the 12/07 release PDF.
You may find that lowering the interval between (i.e. increasing the frequency of) recycling events in the application pools mitigates this to some extent. When I experienced this blank page with 6.11 it was rather persistent. Increasing frequency of recycling events did help a bit. Further, scheduling "iisreset" to run at the start and end of the business day was another mitigator.
On one installation, increasing the VM memory allocation (from 3GB to 6GB) entirely resolved the blank page issue (after a 6.11 hotfix still let it happen from time to time).
I know none of this is a solution, and it's all a stab in the dark since you're on 7. I hope one or more of these can relieve some pressure off you until there is a good solution. Best of luck!