Is it possible to have templates create documents of a different class?

For objects with the 'Is Template?' property set to yes, is it possible to make adjustments in the admin console so that new objects created from this object are created with different property values? 

I would like to change the Class of the created object, as well as one other property (from the Compliance Kit, we have a property called Document Type - I am trying to make the template have the Document Type = Inspection, where the created object form the template would have the Document Type = Inspection Record). 

thanks. 

  • Just to clarify - I would like to have the properties of the new object automatically change. So, after user double clicks or uses 'New From this Template', the new object metadata card populates with the adjusted properties. 

  • In M‑Files, templates are always created within a specific class, and that class is inherited by any new object created from the template. This behavior is by design and cannot be changed in the Admin tool.

    So for objects where “Is Template?” = Yes:

    • The Class of the created object will always be the same as the template’s class.
    • You cannot configure a template so that it creates an object in a different class.
    • Likewise, property values defined on the template are copied to the new object, unless the user changes them manually (or via automation).
    • You can reuse the same template in multiple classes using the Additional Classes property.

    Refer to Using document templates in the user guide.

    If your requirement is to create an object in a different class or even a different object type, then templates are not the right mechanism. In that case, you should look at the Object Creator module of Compliance Kit.

    Object Creator allows you to define granular creation rules, including creating objects in a different class or object type and mapping metadata between them. For example, if you are managing employee lifecycle data in M-Files, you could create a new Employee object from a Candidate object when a person is hired.

    TL;DR: Templates always create objects in their own class. Use Additional Classes for template reuse, and Object Creator when class or object‑type transformation is required.