When I enter/edit any table entry in configuration, as I enter a the description, I'd like to be able to enter the definition of that value beneath it.
Going one step farther, I'd then like to be able to print all of the tables with their table entries and definitions from Raiser's Edge -- an important step in creating end-user documentation.
But to eliminate the need to look the definition up in separate documentation outside of RE, I'd like these definitions to be available when you hover over the drop down menu or by pressing a 'help' function key (like F1).
This would help tremendously with user training, clarify what the values mean, explain why a value has been marked inactive, and much much more to help keep our data bases clean and filled with meaningful information. When I started in a new position, I had to guess what the values meant and how they were previously used. I also have table entries that may have great value, but I don't know what they mean.
It makes the most sense to track and store this important information within the database instead of as a separate document independent from the database.
Having the ability to create additional tables and values is wonderful. However, RE falls short on what would be a very simple fix. Typically, each entry should have at minimum, two(2) fields - 1) The Code, and 2) The Description.
The CODE should be short sweet and to the point (so 10-12 character field). The DESCRIPTION should be, at minimum, a 25-50 character field allowing you to enter a 'self-documenting' description as Debra pointed out in her comment.
This simply is just good db design. I find it very odd to only have a single field to which to describe something while keeping it short and to the point.
Guest
When I enter/edit any table entry in configuration, as I enter a the description, I'd like to be able to enter the definition of that value beneath it.
Going one step farther, I'd then like to be able to print all of the tables with their table entries and definitions from Raiser's Edge -- an important step in creating end-user documentation.
But to eliminate the need to look the definition up in separate documentation outside of RE, I'd like these definitions to be available when you hover over the drop down menu or by pressing a 'help' function key (like F1).
This would help tremendously with user training, clarify what the values mean, explain why a value has been marked inactive, and much much more to help keep our data bases clean and filled with meaningful information. When I started in a new position, I had to guess what the values meant and how they were previously used. I also have table entries that may have great value, but I don't know what they mean.
It makes the most sense to track and store this important information within the database instead of as a separate document independent from the database.
Having the ability to create additional tables and values is wonderful. However, RE falls short on what would be a very simple fix. Typically, each entry should have at minimum, two(2) fields - 1) The Code, and 2) The Description.
The CODE should be short sweet and to the point (so 10-12 character field). The DESCRIPTION should be, at minimum, a 25-50 character field allowing you to enter a 'self-documenting' description as Debra pointed out in her comment.
This simply is just good db design. I find it very odd to only have a single field to which to describe something while keeping it short and to the point.