As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
I am interested in getting feeback on naming conventions for .fex procedures in WebFOCUS. We currently have no particular form to follow. What are some suggestions? Any feedback is greatly appreciated.
Thanks in advance!This message has been edited. Last edited by: viking08,
I asked the very same question a couple of months ago.
I use a naming convention that is supposed to give me some insight as to what the fex does, viz: sales_prodvolume_across_month.fex but as you can see these can get really long, and don't necessarily indicate everything that's in the report.
I've started a Lotus Notes database that includes the fex name, a snapshot of the input parameters screen and a sample of the output, so my users can browse through the reports and select one before asking me to produce yet another report that has essentially the same information as an existing one.
But that's still in development and as the old saying goes:
When you are up to your arse in alligators, It's often difficult to remember That the first objective Was to drain the swamp.
(Sorry about going all English on you but it seems this forum software objects to the word *** - even though it's just a donkey and appears countless times in popular religous books ! I bet if I wrote bum it would get through ...).This message has been edited. Last edited by: George Patton,
Here is an option that we use at one of my previous companies. Just like mentioned above. Using a DEPT/AREA/GROUP and a Number for the procedure which was always on the page bottom of the report/html etc.. We also had a database table with that as the key value along with a description. you could always add a url to a sample report. having a database also lends itself to quering by WebFOCUS.