"GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools."
"We’ve often heard that our REST API was an inspiration for other companies; countless tutorials refer to our endpoints. Today, we’re excited to announce our biggest change to the API since we snubbed XML in favor of JSON: we’re making the GitHub API available through GraphQL."
The specified module could not be found
regarding the edge
and edge-js
libraries when accessing the /wfgen/graphql
, /wfgen/hooks
, or /wfgen/scim
web apps. http://localhost/wfgen/graphql
http://localhost/wfgen/graphql
http://localhost/wfgen/graphql/schema
GraphQL will first look for each parameter in the URL's query-string:/graphql?query=query+getUser($id:ID){user(id:$id){name}}&variables={"id":"4"}
If not found in the query-string, it will look in the POST request body. If the POST body has not yet been parsed, express-graphql will interpret it depending on the providedContent-Type
header:
application/json
: the POST body will be parsed as a JSON object of parameters.application/x-www-form-urlencoded
: this POST body will be parsed as a url-encoded string of key-value pairs.application/graphql
: the POST body will be parsed as GraphQL query string, which provides the query parameter.
web.config
file by setting the GraphqlGraphiqlEnabled
parameter to Y
.maxAllowedContentLength
property in the WorkflowGen web.config
file. The following example shows how to configure this property as 1 MB (note that the value should always be specified in bytes, so the value in the example is 1,024,000 bytes). The default value is 30000000 bytes.GraphqlInputFileAllowedFolders
parameter in the WorkflowGen web.config
file.)*
c:\*
c:
c:\Inetpub\*
c:\Inetpub\folder*
c:\Inetpub
folders whose names start with folder
📌 Examples:c:\Inetpub\folder1
c:\Inetpub\folder1\abc
c:\Inetpub\folder2
c:\Inetpub\folder2\abc\def
*
https://*
http://*
http://mydomain/*
http://mydomain/folder/*
http://mydomain/folder*
folder
📌 Examples:http://mydomain/folderfile.jpg
http://mydomain/folder/file.jpg
http://mydomain/folder2/file.jpg
http://mydomain/folder/file.jpg
GraphqlMaxInputFileSize
parameter in the WorkflowGen web.config
file.GraphqlMaxInputFileContentSize
parameter in the WorkflowGen web.config
file.iisnode
in \wfgen\graphql\web.config
):nodeProcessCountPerApplication
setting is set to 0
by default for the best performance in Node.js applications. This creates one node process based on the number of virtual processors that are configured. You can change this value at any time to a custom number of node processes; for example, nodeProcessCountPerApplication=2
will create two node processes independently of the number of virtual processors.maxConcurrentRequestsPerProcess
value based on the number of potential concurrent users and requests.cors
node with the list of external domains and their methods and headers (where HTTP requests will be allowed) to the WorkflowGen web configuration settings (located in \wfgen\web.config
). See some common examples below.Authorization: Bearer <ACCESS TOKEN>
(replace<ACCESS TOKEN>
with your access token).\wfgen\graphql
folder can also be customized to accommodate many other authentication methods (such as OAuth2, JWT, etc.) thanks to node libraries such as Passport.js.UpdateRequestDataset
) require users to have system access to perform the operations. This can be configured in the System operations allowed users field, under Security on the Integration tab in the Configuration Panel.x-wfgen-impersonate-username
HTTP request header.GraphqlImpersonateUserNameHttpHeader
setting in the \wfgen\web.config
file (e.g. <add key="GraphqlImpersonateUserNameHttpHeader" value="my-custom-impersonate-username" />
).ProcessesRuntimeWebServiceAllowedUsers
setting in the \wfgen\web.config
file.onBehalfOf
argument.VXNlcjoy
:onBehalfOf
argument is set, it is propagated implicitly to the all the sub-queries and fields until a User type is used.id: ID!
field. This ID is global and is unique for all WorkflowGen objects.node(id:ID!)
query to retrieve a WorkflowGen object by its ID.createRequest
operation payload. Be aware that a data with the same name and data type must previously exist in the process for each parameter in the array to store the parameter's value. The following example shows how to send parameters corresponding to the four supported data types (TEXT, NUMERIC, DATETIME, and FILE).assigneeUserName
or the assigneeId
.