Idea: T_DEFAULTS Auto-documentation Table

I don't know about you, but I wouldn't be surprised if one in six of my support tickets circle back to T_DEFAULTS.

I'm embarking on a project to normalize our T_DEFAULTS settings across our organizations, clear up old TR_ORGANIZATION organizations we no longer need, check the integrity of our T_DEFAULTS fields, review those we have to share, and prepare ourselves for the new entries coming in v16.  The latter item has left me running around in circles numerous times over the course of our now multiple abortive v16 upgrade attempts eating up large amounts of valuable time.

Our T_DEFAULTS is just messy: we've been around a long time, but then added two consortium members recently (well recently to me), and have never properly resolved the original organization continuing to use Impresario for it's T_DEFAULTS org, nor discussed all the fields whose settings we have to agree on: meanwhile I have tons of old fields added to support customizations and integrations, some current some long forgotten.

Going back and forth between all the different documentation pages and tabs for two versions and then back to the System Tables is grueling, so I've taken all of the documentation and shoved it into a table that I can join directly to T_DEFAULTS to build my own integrity reports and maybe even script out field generation for new organizations.  As I've done that, I've packaged up what I think should be the way that the T_DEFAULTS table is organized and presented so that others needn't go through this.  If any of that sounds interesting, please give it a look over and comment!

Idea: T_DEFAULTS Auto-documentation Table

Parents
  • On further review with support, it appears that current T_DEFAULTS documentation is spread across a number of unconnected documents, with specific entries for NSCAN, Analytics and TNEW potentially containing additional values outside of those listed in the main T_DEFAULTS documentation pages.  Also able to confirm that there are a few application-defined field names that are missing from any documentation location.

Reply
  • On further review with support, it appears that current T_DEFAULTS documentation is spread across a number of unconnected documents, with specific entries for NSCAN, Analytics and TNEW potentially containing additional values outside of those listed in the main T_DEFAULTS documentation pages.  Also able to confirm that there are a few application-defined field names that are missing from any documentation location.

Children
No Data