Good topic, post, and replies..
Timely, as we are using a pre-pre-FM 16 version that is on the To Do list for a modernization.
We use this type of Calculation/Custom Function as part of our HelpRequest system. Currently we "Get" info from 3 scopes: Script, File&Layout, and Environment/Install passing them along the ScriptStack and writing them out to fields in a HelpRequest record.
We also add some items:
- Script Comment
- @scriptID
- @layoutID
- DatabaseNames
- WindowNames
- etc.
Might (or might not) be good to break this code up by "scope".
- Would that make the code much more efficient?
- Easier to upgrade as new Get ( Functions ) ship, for example, Get ( ScriptStack ) and Get ( DockDetails ) ;-0 ?
This Scope InfoG probably has a few errors (and is obviously not up to date)
