To save a work class to a dedicated table, its class group indicator must be set to "is a class group".
Meanwhile, the "Create Case(s)" smart shape in 7.1.7 sources its available work classes from the pyGetWorkClasses report definition which has two filter conditions which exclude these classes on both counts. (Neither the class group indicator, nor the class group match.)
Is the intended workaround to alter this report definition? Shouldn't it include these work classes already?
If you have a case type rule in the work class then by default the work class will appear in the drop down of Create Cases smart shape. Can you please elaborate what exactly you are looking regarding the dedicated table for work class.
If the class group indicator is set to 'is a class group' or 'belongs to a class group' then automatically a dedicated table will be associated to the work class. If the work class is not inherited from Work-Cover- then you cannot create a case type rule and you cannot see the work class in the drop down of Create Cases smart shape.
The source of the dropdown to select the class of work to be created inside the 'Create Cases' smart shape is below.
Any work class which 'is a class group' will be excluded regardless of its class group, and any work class which 'belongs to a class group' but differs from the class group of the current thread will likewise be excluded.
Since (to the best of my knowledge) the class group directly determines which table a work class is saved to, this report definition excludes all work types which save to any table different from that of the class group corresponding to the current thread.