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

custom_instantiation.cfg - can we use Javascript of FormAPI?

FurnaceFace

Env: Teamsite 6.7.1 on Solaris 9

Hello,

I'm trying to use javascript in the custom_instantiation.cfg to no avail.

Brave new world here with Workflow Modeler 1.0.0 Smiley Wink

Can I use formAPI or regular Javascript? I've attached my sample instantiation screen (renamed from .cfg to .txt)

Any help or direction pointing would be helpful!

Thanks,
/FF

Find more posts tagged with

Comments

FurnaceFace

Digging Digging digging through devNet and I came across this post...

http://devnet.interwoven.com/forums_vb/showthread.php?t=8584

is this still the best way to perform javascript on an WF instantiation page?

thanks
/FF

ISCBorisB

Digging Digging digging through devNet and I came across this post...

http://devnet.interwoven.com/forums_vb/showthread.php?t=8584

is this still the best way to perform javascript on an WF instantiation page?

thanks
/FF

Either it is or it isn't, what does it have to do to the "Brave new world of Workflow Modeler" in the first place?

FurnaceFace

Hi Boris,

I'm talking about the fact that one could use the old way of doing workflow with wft files or you could use the new way which uses ipm files. Your WF instantiation page is now handled externally to the main workflow file.

I'm referring to the "brave new world of workflow modeler" because it is a relatively new product *TS 6.7.1* and the documentation is somewhat lacking.

Your tone seems to indicate you are angry at something I said Boris. Not sure what it is I said that offended you. Regardless, I appreciate your reply though I don't think it related to my question.

Thanks
/FF

ISCBorisB

Hi Boris,

I'm talking about the fact that one could use the old way of doing workflow with wft files or you could use the new way which uses ipm files. Your WF instantiation page is now handled externally to the main workflow file.

I'm referring to the "brave new world of workflow modeler" because it is a relatively new product *TS 6.7.1* and the documentation is somewhat lacking.

Your tone seems to indicate you are angry at something I said Boris. Not sure what it is I said that offended you. Regardless, I appreciate your reply though I don't think it related to my question.

Thanks
/FF

Hi FF. I'm sorry if my tone looked that way. I know I can be pretty abrasive but this time I did not at all mean to.

I certainly know about new wf modeler and various issues around it. My remark was prompted by the fact that your thread started as a
request regarding JS in custom_instantiation.cfg (I'm not aware of any mechanism to do so) and continued by referencing an old thread
that illustrates JS *injecting* into traditional wft Files. IMO that's a different topic.

To answer your question, for the traditional wft schema *pre* and/or *post* tagtable_html's is not so much good/bad as the only
API that IWOV exposed for Workflow developers. As far as I know, you can not leverage wft solution for the Modeler.

Again, my apologies.

thereIsNoSpoon

wrong post

FurnaceFace

Hi Boris,

You are right, I did reference both the new and old way of doing things - I guess my post was missing the hour of research I had done and it left out the mental connections/questions I had done during that time. My bad. Smiley Happy

Your reply did answer my question - the old way of injecting JS into the instantiation screen cannot be used in the new way of doing workflows. Thank you very much.

Thanks for your apologies though I believe you were in the right. I didn't explain myself clearly enough on my posts.

Thanks again for your help Boris,
/FF

Adam Stoller

Env: Teamsite 6.7.1 on Solaris 9

Hello,

I'm trying to use javascript in the custom_instantiation.cfg to no avail.

Brave new world here with Workflow Modeler 1.0.0 Can I use formAPI or regular Javascript? I've attached my sample instantiation screen (renamed from .cfg to .txt)

Any help or direction pointing would be helpful!

Thanks,
/FF

Since custom_instantiation.cfg is a DCT using the datacapture6.0.dtd - you should be able to use FormAPI just like in a FormsPublisher DCT.

justanickname

Env: Teamsite 6.7.1 on Solaris 9

Hello,

I'm trying to use javascript in the custom_instantiation.cfg to no avail.

Brave new world here with Workflow Modeler 1.0.0 Can I use formAPI or regular Javascript? I've attached my sample instantiation screen (renamed from .cfg to .txt)

Any help or direction pointing would be helpful!

Thanks,
/FF

Remove the comment line within your javascript code and the CDATA block within the <script> tag as they seem to cause problems within custom_instantiation.cfg.
Smiley Wink

Here is a working example of FormAPI used within workflow custom instantiation screen. Its show/hiden and make required or not the province drop-down list based on the mediaType radio button selected.

justanickname

Sorry for my last post had some issue with an HTML tag.... Hope i did not screw up the thread...

Remove the comment line within your javascript code and the CDATA block within the script tag and it should work. It seems that there is some issue when they are used in a custom_instantiation.cfg file...

Here is a working example of FormAPI in custom workflow instantiation screen. It show/hide and make required or not the province drop down list based on the mediaType radio button selected.

FurnaceFace

Ahhh thanks for the help. Good little quirk to be aware of.
Thanks
/FF

ISCBorisB

Sorry for my last post had some issue with an HTML tag.... Hope i did not screw up the thread...

Remove the comment line within your javascript code and the CDATA block within the script tag and it should work. It seems that there is some issue when they are used in a custom_instantiation.cfg file...

Here is a working example of FormAPI in custom workflow instantiation screen. It show/hide and make required or not the province drop down list based on the mediaType radio button selected.

Are you sure that in the Modeler CDATA Block prevents FormAPI code from running? If that's the case, it should be reported to IWOV as a bug.

What if your JS contains something like "for (var i=0; i < myArray.length; i++)"?
Without CDATA that will make your script Tag malformed. JS Comments will have the same effect, etc...

justanickname

Hi ISCBorisB,

I've tried again this morning with a CDATA block and it works well so it was not a problem.

The problem seems to be only the comments, even with a CDATA block or not as soon as i add comment within the code it doesn't work anymore.