Hi,

This is not possible at the moment at least. Assuming you meant that these methods would be part of the “new type”, and not of the FolderType instances, I’m not even sure this is allowed by the specification, as version 1.03 Part 4 Table 64 on Call Service Parameters do state for the objectId parameter:

The NodeId shall be that of the Object or ObjectType on which
the Method is invoked.
In case of an ObjectType the ObjectType or a supertype of the
ObjectType shall be the source of a HasComponent Reference
(or subtype of HasComponent Reference) to the Method
specified in methodId.
In case of an Object the Object or the ObjectType of the Object
or a supertype of that ObjectType shall be the source of a
HasComponent Reference (or subtype of HasComponent
Reference) to the Method specified in methodId.
See Part 3 for a description of Objects and their Methods.

I’m my opinion, semantically if there would be methods under the FolderType instance, then those methods are for that instance, not for the “new type”.
Anyway, the codegen creates method implentations for direct HasComponent references and assumes the other methods are part of the instances, which would mean their type/code would contain those method implementations. You could create a subtype of FolderType and the methods to it, but it does mean that those methods should work on instances of that type without the context of the instance being part of a larger type.

This is similar to e.g. a Java type A having field of type B. If B has a method B.example(), then calling this from A would be A.getB().example(), but the instance of B returned by A.getB() would have no knowledge of it being part of A.

– Bjarne