Reading the RemoteLaunch Automated Testing User Guide ( https://www.inflectra.com/Documents/SpiraTest-Team%20RemoteLaunch%20Automated%20Testing%20User%20Guide.pdf ) There seems to be a bit of a discrepancy. On page 59 it says "Note: that the SoapUI engine doesnGÇÖt currently support the passing of parameters to an automated SoapUI test script" However, on page 61, it explains how to use parameters and says "Note that the plugin currently only supports GÇ£Project PropertiesGÇ¥ and not Global or System Properties." If project properties are in fact supported, Can you explain how the naming works? Creating parameter in SpiraTeam called login for example makes a parameter named "${login}". So, in SoapUI, which name am I supposed to use when creating the parameter login or ${login}? Thank You - Sarah en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/remotelaunch/automation-engines/51.aspxthreadId=51Sarah McCaffery (sarah.mccaffery@ermscorp.com)Reading the RemoteLaunch Automated Testing User Guide ( https://www.inflectra.com/Documents/SpiraTest-Team%20RemoteLaunch%20Automated%20Testing%20User%20Guide.pdf ) There seems to be a bit of a discrepancy. On page 59 it says "Note: that the SoapUI engine doesnGÇÖt currently support the passing of parameters to an automated SoapUI test script" However, on page 61, it explains how to use parameters and says "Note that the plugin currently only supports GÇ£Project PropertiesGÇ¥ and not Global or System Properties." If project properties are in fact supported, Can you explain how the naming works? Creating parameter in SpiraTeam called login for example makes a parameter named "${login}". So, in SoapUI, which name am I supposed to use when creating the parameter login or ${login}? Thank You - Sarah Thu, 14 Apr 2011 15:06:40 -04002011-04-14T16:25:39-04:00/Support/Forum/remotelaunch/automation-engines/51.aspxmessageId=106Sarah McCaffery (sarah.mccaffery@ermscorp.com) OK so I think I answered my own question. It seems to be working now. So in case anyone else is reading this. In SoapUI, you create a parameter called login (or whatever else you want to call it) and set the value to ${login}. Thu, 14 Apr 2011 15:20:10 -04002011-04-14T15:20:10-04:00/Support/Forum/remotelaunch/automation-engines/51.aspx#reply106messageId=107David J (adam.sandman+support@inflectra.com) You are correct - SoapUI does support parameters. Originally the plugin didn't support them, which could explain the dicrepency. We shall fix that to avoid further confusion. Thu, 14 Apr 2011 16:25:39 -04002011-04-14T16:25:39-04:00/Support/Forum/remotelaunch/automation-engines/51.aspx#reply107