In the vRealize Automation 8.7 release a feature was implemented which allows the users to modify the custom resource type schema, in order to have more flexibility.
As part of this feature it changed the way the resource properties are displayed. So, now they are displayed based on that schema.
The missing properties can occur if they are added to the create workflow after the custom resource type was created and the schema was initially generated without them.