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

skip the workflow instiation screen

krishnakishore

how to skip the workflow instiation screen in particular branch or Folder.

Find more posts tagged with

Comments

curiousmaverick

how do u want the job to be invoked?

ISCBorisB

how to skip the workflow instiation screen in particular branch or Folder.

With the WFT Model it's trivial, you make all user input optional or do not configure any.
With the WFM Model it can not be done in any supported manner, Ghoti filed FR TS-8028 to develop this feature

Migrateduser

how to skip the workflow instiation screen in particular branch or Folder.

Not sure what version of TeamSite you are running on, but read this for information on customizing your workflow.

https://customers.autonomy.com/support/secure/docs/Attachment/KB/external/9121_CustomizingWorkflowInstantiation.pdf

You could possibly put some javascript that performs the submit on that screen for you. It will should run fast enough to where a user doesn't see the screen.

[PHP]
<script type="text/javascript">window.document.iwwft_instantiator.submit();</script>
[/PHP]

You have to make sure that you don't have any required fields that a user needs to fill out or it won't submit.

There may be a better way to skip the screen that I am unaware of. I haven't messed with workflows for a while and haven't use the new modeler.

jbonifaci

With the WFT Model it's trivial, you make all user input optional or do not configure any.
With the WFM Model it can not be done in any supported manner, Ghoti filed FR TS-8028 to develop this feature

Yeah, the WFM thing is annoying. I do this:

function initializeForm()
{
 ///////////////////////////////////////////////////////////////////////////////////////////////////////////////
 // This is an unsupported way to auto submit the instantiation form.  It is simply the same javascript function
 // for the onclick event of the Submit link.
 ///////////////////////////////////////////////////////////////////////////////////////////////////////////////
 parent.saveAndInstantiate();
}//function initializeForm()

IWEventRegistry.addFormHandler('onFormInit', initializeForm);

~Jeff

krishnakishore

I got the solution. Thank you for all.

Jcse

I got the solution. Thank you for all.

Hi

Can you share the approach that you have followed for acheving the solution.

Migrateduser

I got the solution. Thank you for all.

Nothing annoys me more than someone who takes, but doesn't give to the forum. Please share your solution so that others may benefit.

ISCBorisB

Nothing annoys me more than someone who takes, but doesn't give to the forum

Then you must be annoyed permanently. How many active contributors are left in the Forum, 10 - 12?

Adam Stoller

I'd assume the solution was the one provided by jbonifaci - though it would be nice to have that confirmed by the thread initiator.

ISCBorisB

I'd assume the solution was the one provided by jbonifaci - though it would be nice to have that confirmed by the thread initiator.

There is a serious difference between "I've got the solution!" and "Thank you Jeff, your solution worked perfectly".
Yes, I also think that it should have been the latter

itsamb

I got the solution. Thank you for all.

Its a very old post now. But, it will be helpful for the community if you can remember and care to post the solution.

nipper

Its a very old post now. But, it will be helpful for the community if you can remember and care to post the solution.

There is an answer for WFM in this thread.

For WFT, it is very easy.

Have you tried anything ?

itsamb

Andy,
yes, I tried one solution provided in the thread. It was showing error for me. I investigated, fixed it (it was error in my code) and the same solution is transiting to the first CGI task.

thanks..

Migrateduser

I must be a moron. (shut it, Nipper) I cannot get the solution that's shown in this thread to work. The instantiation form is still coming up and staying up. Can someone (pretty please) post or PM me a full custom_Instantiation.cfg where this is working?

If it matters, I'm on 7.2.1 on Linux

jbonifaci

I must be a moron. (shut it, Nipper) I cannot get the solution that's shown in this thread to work. The instantiation form is still coming up and staying up. Can someone (pretty please) post or PM me a full custom_Instantiation.cfg where this is working?

If it matters, I'm on 7.2.1 on Linux

Dave,

The solution above that I posted above is/was my entire custom_instantiation.cfg (minus comments). I haven't tested this on 7.2.1, but if that's all you have in your custom_instantiation.cfg and it isn't working, I can take a look.

~Jeff

jbonifaci

Dave,

The solution above that I posted above is/was my entire custom_instantiation.cfg (minus comments). I haven't tested this on 7.2.1, but if that's all you have in your custom_instantiation.cfg and it isn't working, I can take a look.

~Jeff

Hey Dave,

I realized after the fact that that couldn't be my entire custom_instantiation.cfg. It was my entire javascript file (I always do includes and put the js in a custom location under httpd/iw). Anyway, I went ahead and verified that the below works in 7.3.1 (and I would assume 7.2.1):

<data-capture-requirements  dtd-system-identifier="http://localhost/iw-cc/datacapture6.0.dtd"  dcr-validation="reject-invalid"  xmlns="http://www.interwoven.com/schema/datacapturedtd">
 <ruleset name="Config">
  <script>
  <![CDATA[
   function initializeForm()
   {
    parent.saveAndInstantiate();
   }

   IWEventRegistry.addFormHandler('onFormInit', initializeForm);
  ]]>
  </script>
  <root-container location="Config" name="Config">
  </root-container>
 </ruleset>
</data-capture-requirements>

Let me know if you have any issues.

~Jeff

AllParameter.rptdesign

Migrateduser

It's still not working for me. I am getting a blank form popping up with just the 2 buttons on the bottom. What's odd is that I'm putting alerts in the beginning of the functions and the alerts are not showing up, so I don't think it's ever getting to my function "onFormInit". I'm not a javascript expert so I'm kind of stuck. So frustrating.

Migrateduser

Finally got it working - many thanks to both Jeff and Boris (who was PMing me tons of help). Turns out Jeff's command really doesn't work. Boris suggested that it might not and offered this instead:

top.saveAndPostForm();

This works for me and is doing what I need it to do.

My initial problem with nothing working stems from the fact that I deleted everything in the root-container element in my custom_instantiation.cfg. Apparently it will not run the onFormInit handler if there's nothing in the root-container. So once I added a hidden field, it started to work.

Thanks again for your help!

Migrateduser

Well the joy was shortlived. This does not work when you instantiate the model using the DCR tt_data wizard. It throws a javascript error in the JSP that is handling what would be the instantiation form in the wizard. I'm guessing since that isn't just a pop-up that can be "saved and posted", it's puking. I have no idea how to get around this. Do you?

ISCBorisB

Well the joy was shortlived. This does not work when you instantiate the model using the DCR tt_data wizard. It throws a javascript error in the JSP that is handling what would be the instantiation form in the wizard. I'm guessing since that isn't just a pop-up that can be "saved and posted", it's puking. I have no idea how to get around this. Do you?

Feels like very typical manifestation of hacking problems. You never know what will bite you.

Brief investigation showed that neither "saveAndInstantiate" nor "saveAndPostForm" are used in tt_data mode.
For that matter, they no longer belong to the "top" of tt_data Instantiation Form either. Instead, the Form is
using "iw_wizard_doFinish" Function. I do not know what Object that belongs to, it *may" be located
somewhere within top.dcfScreen Object ( as in top.dcfScreen.something.somethinElse.iw_wizard_doFinish() ) - or not.

You may perhaps follow this "If tt_mode do "this" else do "that" line of hacking. Whether it's worth your while,
well...

Migrateduser

Thanks Boris. I was figuring, rather than further hacking and getting myself further in the weeds, I would likely just clone the workflow and put a blank instantiation form in for the tt_data version of it, and leave the submit version of it as is with the hack. The user has to click something to get through the wizard anyway, so this shouldn't cause them undue pain. It's unfortunate but I blame Interwoven for not giving us a way to bypass the instantiation form in the first place. That they haven't added that in since WFM has been widely accepted and used is yet another "shame on them" moment.

ISCBorisB

Thanks Boris. I was figuring, rather than further hacking and getting myself further in the weeds, I would likely just clone the workflow and put a blank instantiation form in for the tt_data version of it, and leave the submit version of it as is with the hack. The user has to click something to get through the wizard anyway, so this shouldn't cause them undue pain. It's unfortunate but I blame Interwoven for not giving us a way to bypass the instantiation form in the first place. That they haven't added that in since WFM has been widely accepted and used is yet another "shame on them" moment.

If I were you I would have done something similar - further hacking is not worth the efforts IMO...

Perhaps you do not even have to clone it. Chances are, hidden entry you've added made the Form "valid"
for "saveAndInstantiate". Try Jeff's proposal again, parent.saveAndInstantiate() - note "parent", not
"top" Object. ( top will work too, but only for new_job. It'll throw an error in tt_data mode).

If that works in new_job mode, you *should* be able to use that same Model for tt_data. Granted, command
will be ignored there but you should not have any JS Errors, your user will just have to click "Finish"
button again.

Migrateduser

Jeff's thing doesn't work. I have no idea why. I really want it to work, but no such luck. I will probably just clone it then. Thanks for trying to help me out!

Migrateduser

I guess one last resort would be to turn the thing into a WFT, but that would wreak havoc because undoubtedly someone (else) would want to change the workflow and wouldn't be able to find it because it's configured in a different config file and the source is in a different place. Havoc, I tell you...