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

How Can I Add Inline Command Parameters

Yuemin

When I tried to use "inline command" through iwutild.cfg (describes in TeamSite ® Supplement Release 6.7.2 document), I found that it is not possible to add parameters in the command line.

This is old way(works) to call inline callout script in datacapture.cfg:

The third item "..\\royal\\ship_list" considered as a "parameter".

This is the new way to call in datacapture.cfg:

This works with the new way when there is no parameter defined in iwutild.cfg:

path="F:\iw-home\teamsite\custom\common\scripts\printFileToStdout.ipl"
script="F:\iw-home\teamsite\iw-perl\bin\iwperl.exe " />

But this does NOT work with the new way if the parameter is added in path field like this:

path="F:\iw-home\teamsite\custom\common\scripts\printFileToStdout.ipl F:\\iw-home\\teamsite\\custom\\extracts\\data\\royal\\ship_list"
script="F:\iw-home\teamsite\iw-perl\bin\iwperl.exe " />

Does anyone know how to add the parameter to the inline command call?

Thank you very much!

Yuemin ****

Find more posts tagged with

Comments

Adam Stoller

When I tried to use "inline command" through iwutild.cfg (describes in TeamSite ® Supplement Release 6.7.2 document), I found that it is not possible to add parameters in the command line.

This is old way(works) to call inline callout script in datacapture.cfg:
<inline command="F:\\iw-home\\teamsite\\iw-perl\\bin\\iwperl F:\\iw-home\\teamsite\\custom\\common\\scripts\\printFileToStdout.ipl F:\\iw-home\\teamsite\\custom\\extracts\\data\\royal\\ship_list" />

The third item "..\\royal\\ship_list" considered as a "parameter".

This is the new way to call in datacapture.cfg:
<inline command="utild:getShipList" />

This works with the new way when there is no parameter defined in iwutild.cfg:
<command impersonate="true" name="getShipList"
path="F:\iw-home\teamsite\custom\common\scripts\printFileToStdout.ipl"
script="F:\iw-home\teamsite\iw-perl\bin\iwperl.exe " />

But this does NOT work with the new way if the parameter is added in path field like this:
<command impersonate="true" name="getShipList"
path="F:\iw-home\teamsite\custom\common\scripts\printFileToStdout.ipl F:\\iw-home\\teamsite\\custom\\extracts\\data\\royal\\ship_list"
script="F:\iw-home\teamsite\iw-perl\bin\iwperl.exe " />

Does anyone know how to add the parameter to the inline command call?

Thank you very much!

Yuemin ****

Did you even bother trying to PREVIEW your post before submitting it? Did you even bother to LOOK at your post after you submitted it? Most of the information was missing because you didn't properly format the post - I've taken the liberty of fixing that for you, please take the time to do it yourself in the future.

Having done that - I'm not sure what the issue is - did you try just using the old format instead of worrying about iwutild.cfg?

Yuemin

Thank you Ghoti for fixing the format.
The issue is that we are trying to convert the old way to use inline callouts to the new way (TeamSite ® Supplement Release 6.7.2) for security reason.
When I configured iwutild.cfg, I don't know how to add the parameter into iwutild.cfg which was using in the old way: "F:\\iw-home\\teamsite\\custom\\extracts\\data\\royal\\ship_list". The only 4 attributes(in the document) in command tag are: impersonate, name, path and script. I have tried to add the parameter in "path", it won't work. I don't know if there is any other attribute like "param" which extra parameters can be included.
Hope this is clear.

Adam Stoller

What page of what manual (PDF) are you looking at that talks about using iwutild.cfg for configuring DCT inline scripts?

Previously I had assumed that you read some new piece of functionality that I had somehow missed over the various releases, but I just checked the FormsPublisher Developer's Guide, Release Notes, and the TeamSite Administrator's Guide and didn't find anything that seemed to suggest that these two concepts (inline scripts and iwutild) are connected.

ISCBorisB

What page of what manual (PDF) are you looking at that talks about using iwutild.cfg for configuring DCT inline scripts?

Previously I had assumed that you read some new piece of functionality that I had somehow missed over the various releases, but I just checked the FormsPublisher Developer's Guide, Release Notes, and the TeamSite Administrator's Guide and didn't find anything that seemed to suggest that these two concepts (inline scripts and iwutild) are connected.

In my Doc Version: ts_672_supp_v03_en.pdf - TeamSite Supplement Release 6.7.2. It looks
like 11:59 additions to document features that did not make Developer/Admin Guide Cut.
Look for New Features -> Changes To Forms -> Processing Scripts through iwutild.cfg.

An idea to use named Entities for Inline's is solid. It provides better portability to move
DCTs unmodified across various TS Instances and Platforms, solves infamous inline Path
issues. It also gives better security by requiring Execution rights only for certain Processes
rather than potentially every CC User, etc...

Unfortunately, the Documentation is extremely limited (surprise, surprise). I was not able to
find any related DTD either (if it even exists).

Yuemin

Thanks ISCBorisB, this is exactly what I want to say.

Frederik

I was wondering the same / or similar point...

Is it possible (in datacapture.cfg, formspublisher) to pass command line args to an inline command run via [HTML][/HTML]
something like (just dreaming):
[HTML][/HTML]

PS:
It's pretty shocking that this utild/datasource inline is still not documented in 7.1 or 7.2 docs... The only doc that seems to mention this is the "6.7.2 supplement" (ts_672_rn_v04_en.pdf, ts_672_supp_v04_en.pdf)