• WFDevDefaultWorkflow Environment var broken on local db

    By Kevin Pettitt 2 decades ago

    I noticed on the "_QAF WF Dev Workflow View" form that the "Workflow" drop-down field actually tries to remember it's last value with an Environment variable, but fails on local installations because of the different ways that @DbName and db.filepath work. Specifically, @DbName only includes the relative path (e.g. QAF\db.nsf) whereas db.filepath (local only, server is fine) includes the absolute path (e.g. c:\lotus\notes\data\qaf\db.nsf).



    Consequently, the value that the @Function code in the default formula is looking for is never found because it was set using lotusscript. In fact, this is probably the reason for a huge number of duplicate environment variables listed in my Notes.ini file.



    While we're on the topic, it's probably also worth trying to figure out a way to avoid quite so much reliance on environment variables, because every workflow enabled database looks like it spawns several persistent environment variables that build up in the Notes.ini and never get deleted. Considering that anyone needing these variables (e.g. XXXWFDevDefaultType=State), certainly has at least author and probably editor access, user profile documents are probably a better bet. Most of the environment variables I use are very "fleeting", meaning that as soon as they finish the job of transferring a value from one context to another, I blank them out, which causes them to disappear from the notes.ini file. This may in fact be the way to avoid the problem above altogether.

    • INI file

      By Mark Demicoli 2 decades ago

      ahhh I thought you'd never see that mess.. ;] Agreed - profile docs definitely the way to go.