This content has been marked as final. Show 3 replies
I don't know what you exactly mean by auto-capitalization, but it sounds to me like you have the field type set to use the "Uppercase" field type. When choosing the field type, there is Alphanumeric and Uppercase Alphanumeric. If you pick the latter, the data will be capitalized after entry. It's either that or you have a DAL script associated with the field that is performing the uppercase.
As for your second question, I do not believe there is any field-level user security. The difference would have to be how the fields are mapped. Fields can be set to no-edit and even DAL can protect or unprotect a field. Fields that are propagated (at Form or Form Set scope) cannot be edited. It is assumed that you have to return to the original (usually first) entry of that field and it would be editable. There are a couple of other methods that might set the field to protected, but none of them would be related to the user rights.
So, it would take more information to know exactly what you are seeing.
Thank you for the response.
It turns out the first issue was a bug in studio. It was successfully patched with a separate file provided by Documaker.
The second issue I am going to let rest till I see it again. Perhaps I was having difficulty with our system the day I posted but I don't see anything wrong now.
Please post the bugdb number for this issue and please mark this question answered.