Hierarchical processing (adding and calling) of installed resources is now implemented as follows:
Old approach of making a class derived from AResource is still there, naming convention is still the same. (Make sure it is unique, our approach is concatenate the folderstructure and name of the class as the classname, this is just a practice we use, not a obligatory thing).
Then once you created your resource, you can publish it by using our API, so just like adding a 'generic' resource like CSV, excel,... The parameters that need to be passed can be checked out on our TDTInfo/Admin resource; these are:
classname ( the classname of the installed resource )
location ( relative from custom/packages; so if you have a resource X in folder /custom/packages/Y your location value should be X/Y )
Hierarchical processing (adding and calling) of installed resources is now implemented as follows:
Old approach of making a class derived from AResource is still there, naming convention is still the same. (Make sure it is unique, our approach is concatenate the folderstructure and name of the class as the classname, this is just a practice we use, not a obligatory thing).
Then once you created your resource, you can publish it by using our API, so just like adding a 'generic' resource like CSV, excel,... The parameters that need to be passed can be checked out on our TDTInfo/Admin resource; these are:
classname ( the classname of the installed resource ) location ( relative from custom/packages; so if you have a resource X in folder /custom/packages/Y your location value should be X/Y )