https://community.blueprism.com/t5/Product-Forum/Optional-Parameters-Inputs/m-p/66638#M19243 Hi Irwin, welcome. There's no set way of handling an optional input, and your 'unused' keyword could work, provided everyone knew that was the standard. Fri, 16 Mar 2018 14:34:00 GMT John__Carter 2018-03-16T14:34:00Z https://community.blueprism.com/t5/Product-Forum/Optional-Parameters-Inputs/m-p/66637#M19242 Hi All, This is my first time posting on this forum and I'm still very new to BluePrism, so please forgive me if this is a stupid question :p The novice way in which I'm handling optional parameters is €” when using inputs, the inputs' corresponding data items are set to an initial value of "UNUSED_PARAMETER".  I then check if that has been overwritten, if so, then utilising the provided data.  I noted that in another forum thread, people recommended just leaving the string blank, and then doing a string comparison to check for an empty string, but this isn't viable for myself as an empty string is an acceptable/valid input in many scenarios. Is there a smarter or more elegant way of going by this? Thanks for your time :) Regards, Irwin Fri, 16 Mar 2018 07:18:00 GMT https://community.blueprism.com/t5/Product-Forum/Optional-Parameters-Inputs/m-p/66637#M19242 Anonymous 2018-03-16T07:18:00Z https://community.blueprism.com/t5/Product-Forum/Optional-Parameters-Inputs/m-p/66638#M19243 Hi Irwin, welcome. There's no set way of handling an optional input, and your 'unused' keyword could work, provided everyone knew that was the standard. Fri, 16 Mar 2018 14:34:00 GMT https://community.blueprism.com/t5/Product-Forum/Optional-Parameters-Inputs/m-p/66638#M19243 John__Carter 2018-03-16T14:34:00Z