• Replies 3 replies
  • Subscribers 338 subscribers
  • Views 14 views
  • Users 0 members are here
Related

using the Guideline section on system tables

Jason Buehrer
$organization

Does anyone currently add information to the guideline section of a system table? I did a little testing and found that I could save information there but I am not sure if this will cause problems down the line. If anyone does do this, do you have any best practices rules?

This idea occurred to me while creating a post implementation document. Essentially a journal that documents some of the choices that we made so that current and future users will have some idea why we did something.

Part of that is documenting system table entries and I thought this might also be a good place to save this information in addition to the manual.

Thank you,

Jason Buehrer

Parents
  • $organization

    The Guidelines section resides in the "description" column in the table GOOESOFT_REPORT. We put whatever we want here, for custom reports in particular. If you added text to a standard report here it might get overwritten at some point but otherwise I can't think of any issues this would cause.

    The column is limited to 1024 characters, FYI.

  • Former Member
    Former Member $organization in reply to Chris Jensen
    I think Jason is actually talking about the system table guidelines here, rather than the Report guidelines. They live in the T_REFERENCE_TABLES_GUIDELINES table, in the guideline column, which is text, so it's effectively unlimited. We add lots of notes to Tess system tables, as well as our own, and they persist through upgrades quite happily - mostly hints for system admins along the lines of this one (from TR_CUSTOM_TAB) ------------------------------------- ACCESS UCSS System Admin only **Don't forget to update LP_CONST_MERGE for any Constituent customs screens** ----------------------------------- I guess there's a chance that Tess might over-write ours in an upgrade, but it doesn't seem to have happened yet. Ken
  • $organization in reply to Former Member

    Thanks Ken, that was what I was hoping for!

    Thank you, Chris and Ken for weighing in.

    Jason Buehrer

Reply Children
No Data