2019.1

HTML response file and do not pass through a process to get served so the process is very
quick. Static resources are especially useful for additional formatting of HTML files such as JS
(JavaScript) scripts, CSS files and images, since they are not dynamic and generally shared
between multiple dynamic files.
l
Serve HTTP resource: Check to activate static resource serving.
l
Resource action name: Enter a name that will be simulated as a folder in your
HTTP structure. For example, if you enter images in this box, you would refer to any
files in this folder as href="images/file.ext" .
l
Resource folder: Type the path of the folder where your resources are located, or
click the Browse button and choose the folder in the browse dialog.
Note
Subfolders are accepted in the structure, so if your resource folder contains a folder
called faces, you could refer to a file in this folder as
href="images/faces/johnsmith.jpg".
l
Capture OnTheGo group
l
Authentication Key: Enter the authentication key for the COTG repository. This key
can be found in the Settings section of the COTG Web Administration Panel.
l
Cross-Origin Resource Sharing (CORS)
l
Allowed Origins: Enter an origin (everything in a URL before the path, e.g.
http://www.example.com). The Workflow server will add this value to the Access-
Control-Allow-Origin header, which signals to the browser that it is allowed
to make the request. This enables cross-origin resource requests, such as AJAX
requests.
The default setting "*" is a wildcard that allows all cross-origin resource requests.
l
Form Data Encoding: Specifies how form data, which was sent to the web server,
should be interpreted.
Even though it is strongly recommended to use the <meta charset="utf-8"/> element in
web pages, some might use another encoding or not have the element at all, affecting the
character set used by the browser to send the parameters and file names.
Page 686