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; } } }

calling scripts from workflow

Ottawa_IWOV

I am invoking mtmetaproxy.cgi (MetaTagger) from a workflow, but I am not getting the same look and feel as when I call it from File > Set MetaData in the WebDesk Pro interface. I think it is because of the window sizing I have pre-set in iw.cfg. Is there a way to make sure this window sizing is also called in the workflow?

Thanks.

Lucas Cochrane
lcochrane@dc.com

Find more posts tagged with

Comments

akshathp

You could use the CGI_info tag to control the browser window parameters on instantiator window. For more details on this tag, please refer to CGI_Info tag in Workflow Developer's guide.

Hope this helps!

Akshat Pramod Sharma
Interwoven Inc.

Migrateduser

I believe he is referring to a cgitask window, not the instantiator UI.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

akshathp

SO if his task is a CGItask that calls mtmetaproxy.cgi, won't it run in the same browser window that instantiator opens? And if we set CGI_INfo parameter for this instantiator, then the CGI task which is running in that browser will retain the settings.

Hope this helps!

Akshat Pramod Sharma
Interwoven Inc.

Migrateduser

I thought the CGI_info directive only applied to the initial UI, not any resulting cgitask scripts. If that's the case, there must be some hidden workflow variables that get passed on from the wft file for these CGI properties? What are they?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

akshathp

As per what I understand, it goes something like this:
Instantiator reads the CGI_info tag from wft and applies it on the initial browser. And since the initial browser is retained for the CGItasks, the browser window size and properties don't get changed. So it retains the size of browser window which was set by instantiator. CGI in the CGItask is just running in the open browser without bothering about the size.

Hope this helps!

Akshat Pramod Sharma
Interwoven Inc.

james1

The initial instantiator browser window is retained if the workflow contains a cgitask with start='t' and immediate='t' and owner equal to the current user. Any other cgitasks get opened in new browser windows from WebDesk and/or WebDesk Pro. I know of no way to control the attributes of those browser windows.

-- James

--
James H Koh
Interwoven Engineering

akshathp

Oh ok. So if the CGItasks one after another are all with immediate="t", then will they all run in the same browser one after another?
Maybe that's why for my Workflows, once I set the initial browser window, it remains same size for all CGItasks as I have them as immediate="t".

Akshat Pramod Sharma
Interwoven Inc.