Documenting Customizations (v8.03)

We've taken a brute force method and simply created an Excel sheet with a tab for each of the following:
UD fields, UD tables, Forms, UDMenus, UDSecurity Groups, RDD's, customized Crystal reports, BAQ's, BAM's, BAQ reports, BPM's with notation on what customization requirement (also catalogued)causd this to be used and what it is used for.

--- In vantage@yahoogroups.com, Waffqle <waffqle@...> wrote:
>
> For fields, use Extended Property Maintenance. It'll allow you to document
> what the fields are used for and ensure you don't accidentally use the same
> field twice.
>
> As far as your customizations and such go, it's not too hard to write a
> little report/dashboard that will show you that information. Unfortunately I
> forget what table(s) you need for that. We generally just check the Menu
> Maintenance for a given screen to see what's up when changes are needed.
>
> On Wed, Sep 7, 2011 at 9:35 AM, c.krusen1 <ckrusen1@...> wrote:
>
> > **
> >
> >
> > To all of those who have implemented customizations, what methods do you
> > use to document what was done? We're not regulated by the FDA or any other
> > agencies that have specific quality requirements for enterprise software.
> > Just want to make it easy to maintain them, and do future customizations
> > without fubar-ing the old ones.
> >
> > Area's of interest:
> > * User fields in tables (like: Character01, Number11, etc...)
> > * Customized forms & underlying code
> > * Which customization for a particular program is the current one
> >
> > And on a related topic, how do you determine if a user field in a table is
> > referenced in any customization?
> >
> > Thanks,
> >
> > Calvin
> >
> >
> >
>
>
>
> --
> *Waffqle Driggers*
> *High End Dev, System Design, Profit Drinking
> *
> *:: 904.962.2887*
> *:: waffqle@...*
> *:: NO FAXES*
>
> *
>
> *
>
>
> [Non-text portions of this message have been removed]
>
To all of those who have implemented customizations, what methods do you use to document what was done? We're not regulated by the FDA or any other agencies that have specific quality requirements for enterprise software. Just want to make it easy to maintain them, and do future customizations without fubar-ing the old ones.

Area's of interest:
* User fields in tables (like: Character01, Number11, etc...)
* Customized forms & underlying code
* Which customization for a particular program is the current one

And on a related topic, how do you determine if a user field in a table is referenced in any customization?

Thanks,

Calvin
For fields, use Extended Property Maintenance. It'll allow you to document
what the fields are used for and ensure you don't accidentally use the same
field twice.

As far as your customizations and such go, it's not too hard to write a
little report/dashboard that will show you that information. Unfortunately I
forget what table(s) you need for that. We generally just check the Menu
Maintenance for a given screen to see what's up when changes are needed.

On Wed, Sep 7, 2011 at 9:35 AM, c.krusen1 <ckrusen1@...> wrote:

> **
>
>
> To all of those who have implemented customizations, what methods do you
> use to document what was done? We're not regulated by the FDA or any other
> agencies that have specific quality requirements for enterprise software.
> Just want to make it easy to maintain them, and do future customizations
> without fubar-ing the old ones.
>
> Area's of interest:
> * User fields in tables (like: Character01, Number11, etc...)
> * Customized forms & underlying code
> * Which customization for a particular program is the current one
>
> And on a related topic, how do you determine if a user field in a table is
> referenced in any customization?
>
> Thanks,
>
> Calvin
>
>
>



--
*Waffqle Driggers*
*High End Dev, System Design, Profit Drinking
*
*:: 904.962.2887*
*:: waffqle@...*
*:: NO FAXES*

*

*


[Non-text portions of this message have been removed]
Does v8 have solutions manager? I use that in 905 to view what is all out there.

--- In vantage@yahoogroups.com, Waffqle <waffqle@...> wrote:
>
> For fields, use Extended Property Maintenance. It'll allow you to document
> what the fields are used for and ensure you don't accidentally use the same
> field twice.
>
> As far as your customizations and such go, it's not too hard to write a
> little report/dashboard that will show you that information. Unfortunately I
> forget what table(s) you need for that. We generally just check the Menu
> Maintenance for a given screen to see what's up when changes are needed.
>
> On Wed, Sep 7, 2011 at 9:35 AM, c.krusen1 <ckrusen1@...> wrote:
>
> > **
> >
> >
> > To all of those who have implemented customizations, what methods do you
> > use to document what was done? We're not regulated by the FDA or any other
> > agencies that have specific quality requirements for enterprise software.
> > Just want to make it easy to maintain them, and do future customizations
> > without fubar-ing the old ones.
> >
> > Area's of interest:
> > * User fields in tables (like: Character01, Number11, etc...)
> > * Customized forms & underlying code
> > * Which customization for a particular program is the current one
> >
> > And on a related topic, how do you determine if a user field in a table is
> > referenced in any customization?
> >
> > Thanks,
> >
> > Calvin
> >
> >
> >
>
>
>
> --
> *Waffqle Driggers*
> *High End Dev, System Design, Profit Drinking
> *
> *:: 904.962.2887*
> *:: waffqle@...*
> *:: NO FAXES*
>
> *
>
> *
>
>
> [Non-text portions of this message have been removed]
>
Our (mostly manual) process:

- spreadsheet with UD fields in use, project/reason/etc

- customizations are given sequential numbers - OE2 replaces
OE1 & includes all its code plus new stuff

- customizations are exported as XML & checked into source code
control (subversion) just as a history

- couple queries that show customizations active in the menu
(the Menu table, Arguments field).



Brian.



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of c.krusen1
Sent: Wednesday, September 07, 2011 9:35 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Documenting Customizations (v8.03)





To all of those who have implemented customizations, what methods do you
use to document what was done? We're not regulated by the FDA or any
other agencies that have specific quality requirements for enterprise
software. Just want to make it easy to maintain them, and do future
customizations without fubar-ing the old ones.

Area's of interest:
* User fields in tables (like: Character01, Number11, etc...)
* Customized forms & underlying code
* Which customization for a particular program is the current one

And on a related topic, how do you determine if a user field in a table
is referenced in any customization?

Thanks,

Calvin





[Non-text portions of this message have been removed]