This model api tool allows you to restrict on a CA Plex object type and list the occurrences and properties from your local model while also allowing for some fundamental filtering.
Add-In SettingLaunch application from Plex Add-In tool bar. If you are unable to see the Add-In toolbar from View, Toolbars… menu option choose Show toolbar.
Alert Message “Application Models Dialog”This message is to alert the developer to the current application models found in their template plex.in file (found in CA Plex installation directory). System Section: [Options] System Key: GMFileX which will make up the list of libraries shown in the combo box.
If you don’t see all your models that you want termed as application models you need to copy GMFile settings from your user plex.ini file to your template plex.ini file found in the CA Plex installation directory.
It is important to have a complete list because not only does this define which models are application models but also the logic is anything else must be a shipped library
Search Criteria Entry
ExampleList all Functions with the unscoped name starting with 'Edit' that at the current local model configuration have the following settings
Example ResultsCreate XML/XHTML/CSV Files of your Tables/Views (and their Fields)Go to C:\StellaTools\Docs directory and see for yourself what StellaTools Tables v1.2 look like in XML / XHTML / CSV ![]() Example of XHTML outputExample of CSV outputModel,StellaTL,2014-05-16 21:59:55.782,Admin,V1.0,V1.0,Base,English
Object,28,StellaTL,View:StellaTools.AutoTestBox.Data.Repository.Location.Fetch, STREPLV1,ODBC,Yes,Y
Field,StellaTools.AutoTestBox.Data.Repository.Location.Fields.Identifier,Numeric,9, Undefined,STjaA,Undefined,Long,Undefined,StellaTL
Field,StellaTools.AutoTestBox.Data.Repository.Location.Fields.LocationName,Character, 16,Undefined,STpwA,Undefined,Undefined,Undefined,StellaTL Performance“Good things come to those who wait” is a phrase propounding the virtue of patience OR a pint of Guinness which ever you prefer
Listings can take hours depending on sheer numbers of objects in your local. At least you can run a listing in the back ground or conduct the search at the end of the day, but what you can be sure of is the results will not contain human error and you can arguably have greater confidence in the results in contrast to you picking through the model(s) yourself. You could argue with your boss that you were working after hours also ;) Silly jokes aside performance is not great but the results are Earlier versions of the model api did lead to gpfs which would have been very frustrating had a process been running for hours for it then to fail but version 3.0 of the model api has greater error handling and reduced memory leaks etc |