Along with the import script / function naming issue and this you don't seem be having the smoothest intro to FDMEE However, trial and error is the best method of learning and hopefully this post will help some others with their first exposure to DLR's.
You are right. I havent had an FDMEE intro. So it is just the requirement, the admin guide and me. Frankly: the admin guide is sometimes not really helping. And sometimes the easiest things are not that obvious, especially in the beginning.
But anyway, as you said: my intention with this post was to help other newbies.
If you have any specific areas where the admin guide has caused you problems then I'd say to log an SR and ask for a document defect to be logged. I've been quite prolific on the doc defect front myself (I think the doc team possibly have my face on a dart board somewhere ). There are always areas where things can be clarified or better explained and it's only going to change for the better if the bars are rattled from time to time and these issues are pointed out to the powers that be.
Francisco's blog is a good resource, here is the link in case you don't have it bookmarked - fishing with FDMEE
He has been pretty prolific in highlighting the features in FDMEE since its release. Not so much recently since his new baby arrived but I'm sure that will change once his body and mind adjust to the new reality of 4 hours sleep per day!
Thank you for your hint, I will note it for the future. Is there not an easier way to send feedback rather than open a SR? An official email adress perhaps?
@SH: I love Francisco's blog! His blog helped me a lot to understand FDMEE. In some cases one screenshot on his blog was more meaningful than a page in the admin guide.
1 person found this helpful
The 188.8.131.52 doc site has an email address on this page https://docs.oracle.com/cd/E17236_01/dcommon/html/feedback.htm where it has this:
Oracle welcomes your comments and suggestions on the quality and usefulness of its documentation. Your comments are an important part of our revision process.
- Did you find errors?
- Is the information clearly presented?
- Do you need more information? If so, where?
- Are the examples correct? Do you need more examples?
- What features did you like most about the document?
If you find any errors or have any other suggestions for improvement, please indicate the title of the documentation along with the chapter, section, and page number, if available. Send email to EPMDOC_WW@oracle.com. Include contact information if you want a reply.
To track the resolution of an issue, please contact Customer Support to file a service request.
So that might be an avenue you could explore. Nice doc btw
Great! Thank you Craig!
hahahaha I'm back!!!