I'm trying to trigger an interactive automation script from protocol.
It looks like DM is unable to find my client. Below you can see this with the first highlighted entry from the SLAutomation logging. When triggering the script from the automation module then it does find my client and I get the pop-up (second highlighted entry). When doing this through the SLNet client test tool by triggering an ExecuteScriptMessage I get the same behavior. My options are given below. The User cookie is retrieved by logging it from the QAction.
Does anyone know what I'm missing?
Found the trick.
You need to add the following at the beginning of your automation script:
engine.FindInteractiveClient("message test", 5, "user:"+engine.UserLoginName, AutomationScriptAttachOptions.AttachImmediately);
Then trigger the automation script with the following options from your QAction:
string scriptOptions =
SLNetMessages.ExecuteScriptMessage message = new SLNetMessages.ExecuteScriptMessage(scriptName)
Options = new SLNetMessages.SA(scriptOptions),
var response = protocol.ExecuteScript(message);