We are using the wip-edit plugin version 11.5 p4. If a letter has a multiline text field in it and you edit it (by either double-clicking into it or highlight it and clicking the edit button) then hit F3 to exit edit mode, any other non-multiline fields turn to all caps as we tab or click through them. There's no way to get them back to the normal. We can no longer enter anything but caps into those fields without deleting the letter and starting from scratch. We don't even have to change the contents of the multiline field to see this behavior, just enter edit mode and exit edit mode. Has anyone experienced this before? I don't see any peculiar settings on our multiline fields. They work fine in 11.4.
Yes, positive there is no mask. This wasn't an issue until we upgraded to the 11.5 plugin. And the capitalization only happens after editing an unrelated multiline text field then going back into the other field.
You can set case on a multiline field when in edit mode on the selected text using these key combos
Upper Case = Alt + U
Lower Case = Alt + L
Sentence Case = Alt+ S
Title Case = Alt + C
So you might try one of those combinations to see if it corrects the changed field.
BTW. This issue is being worked on by Oracle Support and Development under BugDB #14751246.
If your field data does not change to uppercase until you tab (or click) through them, that would seem to imply one of the following:
1. The field has a type that requires uppercasing the data. You should go into Studio, open the section and click on the field to check the type. If it says "Uppercase" in the type, then that is what you will get when you tab through it. It may not initially be uppercased depending upon how you mapped the data because not all mapping rules care to look at the field type. Entry will always care when you tab through the field.
2. The field may have a post-edit DAL script that is changing the data. Whatever the script returns will become the data or the script may assign the data specifically.
Both of these are situations that might change the data after the initial mapping just by tabbing through the fields. It would seem unlikely that dropping into edit mode on a MLT field would be the cause, but if it did, then that would be something to send to Support.