\bin
directory under your project root folder (e.g. \wfgen\wfapps\sdk\MyProject\bin
).
WorkflowGen.My.dl
l file to this folder.
\bin
directory you created and choose the WorkflowGen.My.dll
file, then click OK. WorkflowGen.My is now referenced in your project.WorkflowGen.My.dll
to DRIVE:\Windows\system32
.
DRIVE:\Program Files (x86)\Microsoft Visual Studio 14.0\SDK\v3.5\Bin
.
gacutil /i c:\windows\system32\WorkflowGen.My.dll
, then press ENTER
. WorkflowGen.My is now in your GAC.Copy Local
property to False
for that assembly if you don't want the assembly to be copied locally to your project folders. At runtime, the application will automatically use the assembly from the GAC.app.config
or web.config
)\wfgen\bin
, \wfgen\ws\bin
, and DRIVE:\Program Files\Advantys\WorkflowGen\Services\bin
.DRIVE:\MyWorkflowApps\Assembly.dll
, and then use that specific path in the workflow application’s definition.\bin
folders. Alternatively, they can be installed into the system’s global assembly cache (GAC) if they are strong-named assemblies.ContextParameters
instances from JSON strings. The JSON should respect the following structures:null
values have been removed from the JSON context.ContextParametersobject
instance. Usually, you will receive the context in a string variable. The following sample code loads the context from a workflowGenContext
string:contextHandler
(ContextParameters
instance) that you created in the previous section. When you access a single parameter, you store it in a ContextParameter
object to manipulate it. The following example accesses a DATE_EXAMPLE
parameter in the previously loaded context:ContextParameter
valueValue
property of the ContextParameter
instance that you retrieved in the previous section:dateValue
variable now contains the DATE_EXAMPLE
parameter value.ContextParameters
collectionContextParameters
instance. You could do this by using a filter and then using the collection enumerator. Don't forget to remove the filter afterward, or else you won't be able to access the other parameters.ContextParameter
, you can modify its value:ContextParameter
instance, define its name and direction, and then add it to the ContextParameters
instance you already have:ContextFileReference
instance. The following is an example that extracts a file parameter value into a ContextFileReference
, then modifies the file parameter so that it points to another sample file.fileValue
URL field (see https://en.wikipedia.org/wiki/File_URI_scheme for more information).\wfgen\wfapps\WebServices\MyWebProc
folder.MyWebProc
because of those changes, you should duplicate MyWebProc
beforehand and create another IIS application, otherwise the two versions of the process will use the same modified MyWebProc
.\wfgen\wfapps\webservices\MyWebProc
.
web.config
file:true
:mode="Off"
:web.config
file. The following are the necessary nodes to insert in the system.web
node of your web.config
file:web.config
file.aspx
pages trigger request validation by adding the following code to your web.config
file:WorkflowGen.My.dll
in your web project, and then add a using
statement (for the WorkflowGen.My.Data
namespace of the WorkflowGen.My assembly. For example:App_Code\Service.cs
file, to your web procedure's Service
class (note that ScriptService
signatures aren't required for other context formats). Your service class should look like this:WebMethod
attribute can be remotely executed. The default web method signature created with your web service should look like this:application/json
content type, or if the context format is XML ADO.NET DataSet with application/xml
content type, the web method will not receive any parameter. Otherwise, if you exchange a JSON or ADO.NET DataSet context using the application/x-www-form-urlencoded
content type, your method must receive a string parameter called WFGEN_CONTEXT
.application/json
) and XML ADO.NET DataSet (application/xml
) context formatsapplication/x-www-form-urlencoded
content typeWFGEN_CONTEXT
, which is case sensitive.application/json
or application/xml
, respectively), the context is retrieved from the HttpContext
request as shown in the following example:WFGEN_CONTEXT
in parameters (this is the case for JSON and XML ADO.NET DataSet contexts when using the application/x-www-form-urlencoded
content type), it is available to be used within the method.ContextParameters
instance that will be used to manipulate the WorkflowGen context:NUMERIC_IN
value into our numericIn
double variable, and at the same time, we'll verify that the value is not null (if it is, we'll send an exception):application/json
content typeapplication/x-www-form-urlencoded
content typeapplication/xml
content typeapplication/x-www-form-urlencoded
content typeweb.config
file.
WorkflowGen.My.dll
in your web project, then add a using
statement for the WorkflowGen.My.Data
namespace of the WorkflowGen.My assembly:WebMethod
attribute can be remotely executed. If the chosen context format is JSON with the application/json
content type, or if the context format is XML ADO.NET DataSet with application/xml
content type, the web method will not receive any parameters. Otherwise, if you exchange a JSON or ADO.NET DataSet using the application/x-www-form-urlencoded
content type, your method must receive a string parameter called WFGEN_CONTEXT
.application/json
) and XML ADO.NET DataSet (application/xml
) context formatsapplication/x-www-form-urlencoded
content typeWFGEN_CONTEXT
, which is case sensitive.application/json
content type, your incoming payload will have the following structure:application/json
and application/xml
respectively, the context is retrieved from the HttpContext
request:WFGEN_CONTEXT
in parameters (this is the case with the JSON and XML ADO.NET DataSet contexts when using the application/x-www-form-urlencoded
content type), it is available to be used within the method.ContextParameters
instance that will be used to manipulate the WorkflowGen context.NUMERIC_IN
value into our numericIn
double variable, and at the same time, we'll verify that the value is not null
; if it is, we'll send an exception:context
and the replyToUrl
values should be stored. In this example, we'll use files for this purpose:application/json
content typeapplication/x-www-form-urlencoded
content typeapplication/x-www-form-urlencoded
content typeapplication/xml; charset=UTF=8
content type