• Notes Client crash

    By Mark Demicoli 2 decades ago

    PROBLEM

    it appears that the wfSortArray() function is causing crashing for some users. This function is called by many API functions including wfSetState(). wfSetState() is called by Action & Close workflow Actions so the crashing may be consistent for some users. In some circumstances Action & Close does not cause crashing, but calling wfSetState() or other functions that call wfSortArray() in user scripts causes the crash.



    DIAGNOSIS

    The problem seems to have something to do with using the @Sort function within an Evaluate statement, using a temporary (unsaved) document as context.





    SOLUTION

    Previously, the @Sort function was called using the Evaluate function, with a temporary document as context. Now, native lotusscript is used to sort arrays. The code has been taken from the Domino Directory template (QuickSort function & associated routines).

    • Can you post a "hotfix" release ASAP with just this bug fixed?

      By Kevin Pettitt 2 decades ago

      Thanks for being on top of these Mark. I'm using the Jul-5 version as the basis for integrating Qenos into my SuperNTF framework, and hope to show this off in the next release. I'll probably be hitting you up for some minor changes to Qenos that will make the integration smoother. Also, I have a wierd error "Could not create field %1" that appears when I open the the QAF Template to the splash page. Based on the fact that the error occurs in the same wfSortArray function/sub/whatever, it is probably related to this bug (although the error occurs BEFORE the Evaluate (@Sort) call. I can provide more details and screenshots if you email me.



      Kevin

      www.lotusguru.com

      • Bun's in the oven

        By Mark Demicoli 2 decades ago

        Kevin, have sent you a patched template to try out. Will post here when bug is no more. Bring on the requests. :] Looking forward to seeing how you integrate this with your puppy.

        • By Kevin Pettitt 2 decades ago

          Thanks Mark, I'll look for that email. As for the integration with SuperNTF, It looks like the idea that is working best is to create a new top-level frameset into which all the workflow configuration bits fall neatly. This would involve having an outline entry on the main outline for "Workflow Config" right below "Administration". It would work much the same way, in that the entry would only show if 1) Qenos elements were present and 2) the current user had rights. It would also launch a completely new window/frameset just like the Administration link does now. The design of the frameset would be two frames, top and bottom. I would size the top carefully to fit the current designer form, using the lower frame to preview whatever is selected in the embedded view (which means your first change would be to add a single-click target frame to the embedded view called "NotesPreview").



          I've had to make a handful of other changes to several other QAF elements so far to get things working smoothly, but I don't think anything that should necessarily interfere with "normal" use. Stay tuned.