This idea is based on a support call I logged. A global attribute not displaying when setting it to "read only" in the create UI even though a default value has been specified. see attached document.
PTC response to the call was as follows:
"So sorry for not satisfying your request.
A it is working to spec and you can not accept the workaround, I am thinking how can I help it.
When I check another cases for the request, there was no other way.
Development’s comment :
A default value that is defined in the Type manager will not be automatically assigned by default. This default value is essentially a “suggested value”, something that will be available to the user in the UI by default, and if they wish to keep it/use it, then they can populate/leave the input field populated with this value. When an input field populated with this value, then it will be saved.
When the attribute is marked read-only (unassignable) during a Create operation, then it means – “prevent a value from being set on this attribute”.
Do you want to request an enhancement for the issue? I can help to guide the process.
Or there could consider complementary customization to keep the default value when the document is created?"
Hence this Product Idea.
