0
Not a bug

Session.GuestLoggedOnUserName and Session.GuestMachineName blank on first trigger email

HDClown 3 years ago updated by Ben Burner 3 years ago 2

I have the following trigger defined:


Filter

Event.EventType = 'Connected' AND Connection.ProcessType = 'Guest' AND (Session.SessionType = 'Support' OR Session.SessionType = 'Meeting') AND Session.HostConnectedCount = 0


Action - Send Email 

Subject = : [SC] User "{Session.GuestLoggedOnUserName}" on computer "{Session.GuestMachineName}" has connected to your session "{Session.Name}"

Body = blank


I create a new secure code session but I do not join it as a host.  The guest joins and the trigger fires off an email.  The Session.GuestLoggedOnUserName and Session.GuestMachineName attributes in the email are blank, but Session.Name does have the correct session name.


I Join the session, and use the gear icon to exit it, so the guest is disconnected, then I close my host window.


I leave the secure code session active (do not end it), and have a different guest connect.  The trigger fires and the email subject has Session.GuestLoggedOnUserName and Session.GuestMachineName from the PREVIOUSL guest's computer details.


This is reproducible.  The initial email has these properties as blank, and the subsequent emails are "behind" in the data that is being sent, using the prior session's information.


ConnectWise Control Version:
1
Server Affected:
Host Client Affected:
Guest Client Affected:

Answer

Answer
Not a bug

Good afternoon,


I am moving this post to "not a bug" status, given that the GuestLoggedOnUserName and GuestMachineName values aren't populated by the Connected event used in the trigger definition prior to sending the email, and this is by design.


I recommend adding your input/use case to the ConnectWise Control feature request portal. I believe the following feature request may address the behavior you're requesting: http://product.screenconnect.com/topics/122-add-the-ability-to-have-time-delayed-triggers-that-can-activate-after-a-pre-defined-time/


Since the current trigger fires immediately after the event conditions are met (and before the requested information is populated on the session), adding a delay would give the session time to update GuestLoggedOnUserName and GuestMachineName based off of newly received guest info prior to sending the email.


Regards,

Ben

Good morning,


Thank you for reporting this behavior. The SMTP trigger email subject doesn't contain the expected GuestLoggedOnUserName and GuestMachineName values because the email content is generated prior to the session being updated with the most recent information from the guest client.


I have registered a bug with development and it's currently under investigation.


Cheers,

Ben

Answer
Not a bug

Good afternoon,


I am moving this post to "not a bug" status, given that the GuestLoggedOnUserName and GuestMachineName values aren't populated by the Connected event used in the trigger definition prior to sending the email, and this is by design.


I recommend adding your input/use case to the ConnectWise Control feature request portal. I believe the following feature request may address the behavior you're requesting: http://product.screenconnect.com/topics/122-add-the-ability-to-have-time-delayed-triggers-that-can-activate-after-a-pre-defined-time/


Since the current trigger fires immediately after the event conditions are met (and before the requested information is populated on the session), adding a delay would give the session time to update GuestLoggedOnUserName and GuestMachineName based off of newly received guest info prior to sending the email.


Regards,

Ben