On our Workflow server, we are running many processes relying heavily on the Database Query plugin. We never use the static connection string functionality in production, we only ever use it during setup in order to populate the field list used in the “Create data pages as follows”, since I couldn’t figure a way out to blank the static value afterwards, we just leave it as is and set-up the “Dynamic SQL” tab.
We have undergone an infrastructure replacement last year, which resulted in a change to our connection strings for queries to two external servers. Since we only ever use dynamic SQL for the queries, we updated the relevant global variables and it kept working as normal without any issues.
After the update to version 2020.2.1.9 from whatever the previous one was, Workflow started having a problem with the static connection strings that were still pointing to the old server (even though they were not used).
We managed to figure out how to avoid manually changing the values through the GUI and waiting a few minutes for the interface to become responsive. We exported an .OL-workflow file, searched for instances of <InputDBPlugin> and changed the values wrapped in <database> and </database> tags. Upon loading the file back onto the server, the issue seems to have stopped occurring when attempting to edit.
I want to make sure this is never an issue again in case we grow the infrastructure, so I briefly considered changing all instances of
<database>[whatever-the-connection-string-was]</database>
to
<database/>
only leaving the dynamic SQL fields populated. Is this safe to do or is this going to destroy the data pages setup? I’d appreciate somebody from Internal confirming.
