Hi Nicolas!
Use wfGetActionDoc() to retrieve the Action document you want to process then use wfProcessAction() to run it. You must save your document after calling wfProcessAction. In a view you can create an agent with a loop and cycle through selected documents.
wfGetActionDoc (paramActionName As String, paramWFName As String, paramDB As notesDatabase, paramActionRef As String) As notesDocument
PARAMS
paramActionName - The name of the action you want to get
paramWFName - the Workflow name in which the Action exists
paramDB - the NotesDatabase in which they all live
paramActionRef - optional reference number (a_Name) of the Action instead of paramActionName. This parameter takes precendence over paramActionName
RETURN
Returns the Action as a NotesDocument object.
wfProcessAction (ActionDoc As notesDocument, paramDoc As notesDocument, optNotification As Integer, optIgnoreGlobalValidations) As Integer
PARAMS
ActionDoc - The Action you want to run as a NotesDocument object
paramDoc - The context for the Action (ie the user document)
optNotificaiton - set to True if you want Notifications sent from the Action
optIgnoreGlobalValidations - set to True to ignore any Global validations specified by the Action's parent Workflow.
RETURN
Returns True if successful, false if it failed.
USAGE
This function processes a given QAF Action. Ie. The Action is processed in the same way as though it was selected by a user from the user interface (Action & Close / Create/ Admin Tools buttons), with the exception that the user document is not saved (you must do this), and window is not closed. This function can be called by server code only if the Action does not declare or use any UI classes in any called code.