Adding a default to Input Type Code on the attribute on the Resource Object is not considered when one creates a new Resource in Adminstration > Resources. The new resource created in the app shows the field blank as opposed to being populated with the default value.
STEPS TO REPRODUCE:
Expected Result: Default values should be populated on the Resource profile
Actual Result: The default value was not populated for the Input Type Code
Note: The same result is found for users created via XOG or LDAP SYNC JOB.
Clarity 16.0 and earlier releases.
The application is behaving as expected.
Setting default values on the Resource Object is for setting the defaults on new Resource profiles created from the Main Application -> Resources, not from creating a Clarity User from the Admin Tool -> Resources. The Admin Tool -> Resources functionality is for creating end-user profiles and for adding security access rights to the end-user profile. When creating a new Clarity User in the Admin Tool, the Create layout does not include the Input Type Code and therefore, the application cannot populate it with the configured default value. This applies to other attributes that may be configured with default values. If setting default values are important to your process for creating resources, implement a business rule to have your Clarity Administrator create the Resource profile in the Main Application -> Resources first, then go into the Admin Tool and add the security access rights.