\wfgen\wfapps\webforms[process name]\V[version number]) and start your development.
[process name]\V[version number]) as a sub-folder within the web forms web application (
\wfgen\wfapps\webforms) or transform this folder into a web application in IIS.
\App_Themes, etc.) as it did prior to migration.
\binsub-folder to your web form’s folder and refresh the opened project in Visual Studio, if needed.
\wwwroot\wfgen\web.configare available for use in the Form Designer and Global Lists except for the master database connection string. While the application tries to verify that user-supplied SQL queries used in these contexts are secure and contain only
SELECTstatements, you should also make sure that exposed connection strings are secured at the database level. This means that if you don’t want a process manager or a Global List manager to be able to update or modify a certain database, the connection string should have read-only access to your database.
web.configfiles are not exposed in the WorkflowGen UI, so for process designers to be able to use them, they must know the name of the connection string. This is also a convenient way to give different process managers access to specific connection strings.