Kbase 16918: ADM Modification Support Policy
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
ADM Modification Support Policy
INTRODUCTION
============
This knowledgebase entry discusses Progress Technical Support
support policy concerning modifications made to the SmartObject
ADM (Application Development Model).
WHY YOU NEED TO KNOW THIS
=========================
If you have modified the ADM you should know the level of support
that will be provided by Progress Technical Support. This
knowledgebase will also give guidelines and information about
what you can do to determine where a problem may be occuring
so that you will get the quickest resolution possible from
Technical Support.
POLICY
======
If you have problems with the functionality of your SmartObject
application after changing the underlying ADM code, it is your
responsibility to determine if the problem you are having is
related to that change or not.
You should first try to remove your changes and see if the
problem still occurs with the ADM as we ship it. If the
problem you are having still occurs under the original versions
of the ADM then Technical Support may be called after you have
a clear understanding of the problem as a result of the normal
debugging process, as with any issues reported to Technical
Support. You should also use the On-Line Knowledge Base to
find a possible solution. Technical Support may then help to
further diagnose the problem and log the appropriate bugs/suggest
feasible workarounds.
If the problems do not occur with the ADM as we ship it and they
appear to be related to changes you have made then you will need
to debug the problems that were introduced to the underlying
code OR call our Consulting services to help you with debugging.
Knowledgebase entry 16775: How to
Compile / Preprocess a SmartObject to Read ADM Code may
help you with this process.
Through this debugging you may determine one of four things:
1) The change that you have made to the ADM has unintentionally
broken another part of the ADM. In this case you need to
consider how far reaching your changes are and possibly
re-design your modifications to only affect what you meant
to change originally.
2) The change that you have made to the ADM doesn't work as
intended, like #1 you need to re-design your modifications
to get the behavior you want without causing problems
with the functionality of the application.
3) You may be running into a problem with the 4GL that has
nothing to do with the ADM. For example, you have
added functionality (4GL code) to the ADM and that 4GL
just isn't working correctly.
In this case you may want to try reproducing the problem
outside of your SmartObject application with the functionality
that you have added to the ADM. This would prove that the
problem is not with the ADM and would provide for a much quicker
resolution since the complexity of the application (the
SmartObjects) has been removed.
4) The change that you have made to the ADM may be causing
another problem in the ADM but you do not feel that it should
have. You may have found a problem with the ADM logic that
was not apparent until you made your changes. This is a
is a complex sitution and should be logged as an
enhancement request with Technical Support. A reproduction
of this type of issue against the sports database would
be helpful for Technical Support to log an enhancement.
For issues of type #1 and #2 you may contact Consulting
Services (see our home page for info on contacting Consulting
Services) if you need help to re-design your ADM
modifications. For issues of type #3 and #4 you may contact
Technical Support, as discussed above with problems that can be
reproduced with the ADM as shipped, once you have a clear
understanding of the problem and have narrowed it down through
debugging.
Progress Software Technical Support Note # 16918