couple WFM Custom Instantiation questions

1. Pre-selected Files cause WFM Instantiation Form to automatically generate/include
Files' text areas for the "Submit" comment. How can I suppress this (eg, I do not want
these areas to appear on instantiation Form)?

2. This is more in the nuisance category, just wonder if others noticed it too.
It *seems* that the single line comment (two slashes) causes JS error within WFM FormAPI, like this[php]. . .
<script><br>/* This is perfectly good comment */<br><br>// This however will cause JS Error<br></script>
[/php]In the DCT I can use both commenting formats so it's not FormAPI per se. Note that the problem
manifests irrespectively of CDATA bracketing and that XML Parser is happy with either comment.
What gives?

Find more posts tagged with

Comments

Rick Poulin

1- There's a true/false flag on the "Workflow Model Properties" in your WFM to turn this off. It's only accessible from the 'tree' box on the left.

2- I'm half-guessing here, but I suspect that the "DCT" for the instantiation screen doesn't keep the pretty printing internally, and when everything is mushed onto the same line, the // comments are commenting-out the end of your functions, thereby causing the error.

ISCBorisB

1- There's a true/false flag on the "Workflow Model Properties" in your WFM to turn this off. It's only accessible from the 'tree' box on the left.

2- I'm half-guessing here, but I suspect that the "DCT" for the instantiation screen doesn't keep the pretty printing internally, and when everything is mushed onto the same line, the // comments are commenting-out the end of your functions, thereby causing the error.

Thanks

Adam Stoller

2- I'm half-guessing here, but I suspect that the "DCT" for the instantiation screen doesn't keep the pretty printing internally, and when everything is mushed onto the same line, the // comments are commenting-out the end of your functions, thereby causing the error.

I'll confirm your guess - the script code is condensed such that all newlines are removed, and thus // style comments break things.
Confusing - yes?
Annoying - yes?
Necessary - not really.
Documented - not as far as I know.

10-22-2014 2-53-54 PM.pdf

ISCBorisB

I'll confirm your guess - the script code is condensed such that all newlines are removed, and thus // style comments break things.
Confusing - yes?
Annoying - yes?
Necessary - not really.
Documented - not as far as I know.

Works fine in Form Publisher DCT - go figure Smiley Sad

Rick Poulin

If your code is large enough to warrant it, you could perhaps externalize your code into a JS file, and then reference it with a <script> tag... (not sure if that works in instantiation dcts)

ISCBorisB

If your code is large enough to warrant it, you could perhaps externalize your code into a JS file, and then reference it with a <script> tag... (not sure if that works in instantiation dcts)

I always abstract out DCT JS code into JS libraries. Probably will turn to that in WFM as well - if it works for custom_instantiation.

jbonifaci

I always abstract out DCT JS code into JS libraries. Probably will turn to that in WFM as well - if it works for custom_instantiation.

It does, I do this all the time.

ISCBorisB

It does, I do this all the time.

Thanks Jeff, good to know