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

Overriding the OOTB "Default Submit" workflow

jtram98

Hi. How does one override the default submit workflow? I'm using the Workflow Modeler. Is is just a matter of loading up the workflow making changes and then publishing it back to the server and updating available_models.xml?

I've updated the workflow so that the reviewer is sent an email once the author submits the file. In addition, the author should receive an email if the reviewer rejects their work. I want this to happen, once the author has submitted their work. However, emails are not being sent.

If I instantiate the job via the CCPro (Actions --> New Job), emails are sent out. My suspicion is the the default submit workflow is being used and not my modified version.

I have read the manuals, though I don't see anything about how to override the defaults.

Software version:

TS 6.7.2 on Solaris 10
Workflow Modeler 1.0.1.0 build 69622

Thanks
John

Find more posts tagged with

Comments

Migrateduser

Are you using Java or perl for your email script? Are you using a custom email script or the one IW supplies in their sample workflows? How did you modify the default workflow?

It's probably a good idea to copy the sample workflow they give you into a new workflow that you modify. That way if you really eff it up, you still have the sample to work from as a baseline.

jtram98

Hi Dave.

I am using the email script IW supplies in their sample workflows, which I believe is the Java version.

I modified the original workflow and saved it under a new name. I modified it using the Workflow Moderler client supplied by IW.

Thanks
John

Migrateduser

I'm not going to be much help - we are using a custom built email class based on the sample MailNotificationTask.java that IW supplies. I didn't write this code, and I'm not sure how to configure it to work for your email server. It's likely you will have to configure something to make the email code work for you.

Have you looked at your logs to see if there are any errors recorded when your workflow is supposed to be sending emails? That could be a good indicator of why it isn't sending emails out. You should tail servletd_out.log as you're running your workflow and see if you get any exceptions or errors.

jtram98

I'm pretty sure the default config is ok, since I do receive emails when I instantiate the job myself. I'm just trying to figure out how to make it use my workflow instead of the default one when a user submits a file for review. My assumption is that IW is using the default workflow and not mine...

Thanks again.
John

Migrateduser

Oooooooooooooooh. That's different. And much easier.

You need to modify your available_models.cfg, but do it under your Administration tab and choose Manage Workflows. You can edit in inline and save it right there. You want to disable the default workflow for whatever branch/role combination is appropriate and then set up that same branch/role combination to be active for your new workflow. The docs should help with this. It all depends on how granular you need to control the workflow access.

Adam Stoller

Oooooooooooooooh. That's different. And much easier.

You need to modify your available_models.cfg, but do it under your Administration tab and choose Manage Workflows. You can edit in inline and save it right there. You want to disable the default workflow for whatever branch/role combination is appropriate and then set up that same branch/role combination to be active for your new workflow. The docs should help with this. It all depends on how granular you need to control the workflow access.

I'm not positive, but I believe the "Default Submit" workflow is still a WFT and not a WFM - and all it does is version the file (no reviews, no email) - so if the issue is that you want to replace that with your own custom "Default Submit" workflow - you probably need to edit the available_templates.xml file first to disable the OOTB one as well as configuring your custom one in the available_models.xml file.

If the issue is not the "Default Submit" workflow, but rather the workflow which appears at the top of the selection list and is defaulted to being pre-selected - that's another issue altogether - I believe they are alphabetically sorted by "name" and you'd just have to name the one you want at the top in a manner that puts it there alphabetically.

ayash123

Are you using Java or perl for your email script? Are you using a custom email script or the one IW supplies in their sample workflows? How did you modify the default workflow?

It's probably a good idea to copy the sample workflow they give you into a new workflow that you modify. That way if you really eff it up, you still have the sample to work from as a baseline.

I think WFM can also be used. its always better and good practice to inherit from the default workflows rather that creating new workflows from scrach.

Thanks,
Ayash

Migrateduser

its always better and good practice to inherit from the default workflows rather that creating new workflows from scrach.

Not always. And for WFTs I would say not even most of the time. If you have to do anything remotely complex, the default workflows are pretty useless.

new_report_4.rptdesign

nipper

Not always. And for WFTs I would say not even most of the time. If you have to do anything remotely complex, the default workflows are pretty useless.

Now which of the default workflows did you write when you were at Interwoven ?

Migrateduser

Now which of the default workflows did you write when you were at Interwoven ?

The ones you shouldn't use as your baseline. Smiley Surprised

Adam Stoller

The ones you shouldn't use as your baseline. p

Fortunately, at least as of 672SP1 - those WFTs no longer seem to appear in the IWHOME/local/config/wft/default directory ;-)

jtram98

ghoti,

Thanks for your suggesting of changing available_templates.cfg ... I found that file and commented out all the templates and now my custom workflow is working - sort of. I'm getting emails now, though not to and from who I want; the author submitting the email is getting the email intended for the reviewer. I think its probably the way my workflow is set up.

One thing I also found out is that in the available_models.xml file, when you list more than one user, you must put them inside an OR tag, otherwise IW complains that there are no templates available for the user submitting the files.

i.e. this does not work ...
[html]

[/html]

this does ...
[html]

[/html]

To IW vets this is probably common knowledge, but to new users, well, it just makes you say "yeah, that makes sense".

BTW, I do spend a lot of time reading all the manuals before I post here and I spent a week trying to solve this issue myself. However, does it explicitly say anywhere in the workflow manuals about disabling the WFT if you want to use WFM?

Thanks
John

nipper

ghoti,

To IW vets this is probably common knowledge, but to new users, well, it just makes you say "yeah, that makes sense".

BTW, I do spend a lot of time reading all the manuals before I post here and I spent a week trying to solve this issue myself. However, does it explicitly say anywhere in the workflow manuals about disabling the WFT if you want to use WFM?

Thanks
John

Welcome to Interwoven. :-)

There are a number of areas where you *might* have found the information about the user. The DTD is often a good place to look (though a pain in the a$$ to parse).

Now to your other question. You do not need to stop using WFT to get WFM to work. I run both. Have been for many years.

In any case, there are multiple different email tasks available, in WFT and WFM. They work differently and are configured differently.

Your WF is a WFT (I suspect - though there is a WFM version) but uses the URL tasks for email, deployment, etc. I hate those and tend to use perl invocation instead. They work better and are easier to debug.

That comes form experience. Others will tell you they have the URL tasks running fine.

jtram98

Andy,

Thanks for the tips. You are correct about WFT and WFM working together. My issue had to do with not putting multiple users in an OR tab in the available_models.xml file. I took out the comments in the available_templates.cfg file and now the the author is given the choice of using the WFT or my WFM.

John

nipper

Got it. I use OR tags all the time out of habit. It may be that you found and "undocumented feature" in WFT that IWOV fixed in WFM. There was one that people loved in the 5.X time frame (you could put a path in available_templates that was to a folder or a file in a workarea). That allowed you to have a workflow for a specific file. I have no idea why they "fixed" it in 6.X to only allow workareas.

jtram98

Thanks everyone for your help. Things are working now - to a certain degree Smiley Happy

John