nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

HTTP Posting into TeamSite workflow

kgrimm

I am attempting to integrate a web application with a teamsite workflow containing a simple CGI task. The requirements are that the user kicking off the workflow should be able to kick it off through the web application (currently through a POST), that the user be authenticated in TeamSite and that the modifications made (meta-tagging using 'iwextattr') should have that user's TeamSite id as the submitter. The workflow must also be able to read parameters from the site's initial POST request. I have attempted to POST into the following mechanisms to kick off the workflow:

/iw-cc/newjob

and

/iw-bin/iw_cgi_wrapper.cgi/iwwft_instantiator.cgi

I am running into issues either way. With the new job approach I am unable to figure out how to get ahold of the POST data. Using iwwft_instantiator.cgi I am able to read the POST data but it expects the user to already have a valid TeamSite session otherwise I get an error that iw_session was not found.

Find more posts tagged with

Comments

Rick Poulin

Try combining iwwft_instantiator.cgi with Jenni's approach to validating session info, i.e. use something like this as a POST target (you may have to GET instead):

http://teamsite.company.com/iw-cc/command/iw.base.show_done_page?full_redirect=true&done_page=/iw-bin/iwwft_instantiator.cgi?launch_parm=PRODUCT~cms_menu

kgrimm

Thank you, that does appear to work. It is unfortunate that so many redirects are involved since I'd want to be passing in a series of vpaths which could quickly eat up the 2048 character IE GET request limit... I may have to think about a whole new way to do this.