This procedure lets you launch a new process from another application using SDK-style parameters.
Notes
The process to be launched must be a public access level sub-process.
This solution is not available with WorkflowGen Standard and StandardOne licenses in version 5.
URL
Use the URL http://[myserver]/wfgen/show.aspx?QUERY=PROCESS_START_REMOTE, replacing [myserver] with the name of your server.
Required parameters
PROCESS
Type: String
Description: Name of process to launch
TEST
Type: String (Y or N)
Description: Launch process in test mode?
Optional parameters
CONTEXT
Type: String
Description: XML-structured IN/OUT parameters to send to the process start. If omitted, a default context with NULL values will be created. (See Web Services API: WorkfowContext specifications and usage for instructions on how to create context parameters.)
REQUESTER_USERNAME
Type: String
Description: Username of the user launching the request. If omitted, the connected user will be used as the requester.
Sample
Download SDK_CS_RemoteLaunchURL_v5.zip and follow the instructions in the included setup.txt for an example of usage.
This and other integration-related FAQs have been compiled and updated in the new WorkflowGen Integration Guide. The material from the article you were looking for can be found in the Web Services API section.
I am getting the following error notification:
“The process ‘“SDK_CS_REMOTE_LAUNCH”’ cannot be found”.
(–> I tried with several other processes as well)
Am I missing something? Is the syntax incorrect?
How can I call the right process?
Hi Eddy,
thank you, now it works
But:
I expected that the request sheet would open in the browser. Instead, I only see the requests’ ID ("ID=“1905”). In order to see the form sheet, I need to go via the portal again.
The goal for the remote launch was, that requesters can launch a request via URL and not need access the portal.
Is that possible? Do I need to add additiotnal parameters to the URL?
Then add some custom Javascript / JQuery to retrieve the URL parameter and autofill the values. In this case, we have to retrieve the parent URL’s query parameters since the iframe’s URL does not contain the additional query parameters.
<script>
function getQueryString() {
var queryStringKeyValue = window.parent.location.search.replace('?', '').split('&');
var qsJsonObject = {};
if (queryStringKeyValue != '') {
for (i = 0; i < queryStringKeyValue.length; i++) {
qsJsonObject[queryStringKeyValue[i].split('=')[0]] = queryStringKeyValue[i].split('=')[1];
}
}
return qsJsonObject;
}
$(document).ready(function(){
$("#REQUEST_SUBJECT").val(getQueryString().REQUEST_SUBJECT);
});
</script>
