little bit of user input- like the type that an @Picklist or an @Prompt could
deliver. With simple input, developing your own form seems like overkill.
Writing the whole agent in @functions, however, is cumbersome. This is a
classic case of needing to combine LotusScript with an @function side-effect,
something that the documentation says you can't do. By doing the following,
however, you can bend rules a bit.
1. Create an editable, Hidden Text <field> somewhere on a form which will be
used by the current document
2. In the Input Translation event, place the following code:
@If(<field> = "Something"; "Continue";@Return(""));
@Prompt([OkCancelEdit];"Great Lies";"Enter a benevolent person";"My Boss")
(or alternatively, an @Picklist or something of that ilk)
3. In your LotusScript, when you want the @Prompt to be kicked off, execute the
Dim ws as New NotesUIWorkspace
Dim uidoc As NotesUIDocument
Set uidoc = ws.CurrentDocument
Call uidoc.FieldSetText("<field>", "Something")
TheAnswer = uidoc.FieldGetText("<field>")
This trick sure beats creating a dialog box for every eventuality- and it is
the *only* way I can think of to kick off an address dialog box in code...
Dig Deeper on LotusScript
Auto-generate LotusScript setter and getter properties for class variables
Remove orphaned Lotus Notes documents on Domino databases with a 'virtual delete'
Copy email and attachments to a Lotus Notes database using LotusScript
Workaround for @DBLookup error: 'The specified database lookup generated more than 65,000 bytes of r