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

configurable_default_submit workflow problem

Khateef

Dear All,

We are using configurable_default_submit workflow for the process (Teamsite 6.7.2):

user submits content -->approval process --> if approved then deploy

While submitting any file and selcting the workflow shows the error as

Invalid Workflow Template: Undefined subroutine &WFtemplate::declare_workflow called at (eval 53) line 416, line 3.

I also attached the wft file and the error screenshot for more details.

Could any one give me a solution for the problem?

Many thanks in advance.

Find more posts tagged with

Comments

Migrateduser

Run the CLT iwjobc agains your workflow - that gives better error messages. Looks like you may have an XML problem in your WFT. I didn't look at it - I'm not that helpful. You'll need to learn some basic debugging skills if you're going to be working with workflows.

ISCBorisB

Undefined subroutine &WFtemplate::declare_workflow called at...

"declare_workflow" is a public Method of OTB TeamSite::WFconstructor module. An error pretty much indicates that WFconstructor
is *not there*. Check if you've declared PM correctly and perhaps if you have issues with the Module itself (it's original, it's readable
by your process etc)

Khateef

Hi,

TeamSite::WFconstructor module is there, and we have declared PM correctly

Initiallay the workflow was working fine, later we installed a few modules thru cpan like DBD and DBI: Smiley Surprised

RACLE and LWP useragent, after that it is giving this error.

all the workflows are having the same issue.

*below is the logfile data*

Invalid Workflow Template:
Too many arguments for Encode::decode_utf8 at /Interwoven/TeamSite/iw-perl/site/lib/HTTP/Message.pm line 275, near "))"
BEGIN not safe after errors--compilation aborted at /Interwoven/TeamSite/iw-perl/site/lib/HTTP/Message.pm line 621.
Compilation failed in require at
/Interwoven/TeamSite/iw-perl/site/lib/HTTP/Request.pm line 3.
Compilation failed in require at
/Interwoven/TeamSite/iw-perl/site/lib/LWP/UserAgent.pm line 10.
BEGIN failed--compilation aborted at
/Interwoven/TeamSite/iw-perl/site/lib/LWP/UserAgent.pm line 10.
Compilation failed in require at
/Interwoven/TeamSite/iw-perl/vendor/lib/XML/DOM.pm line 4269.
BEGIN failed--compilation aborted at
/Interwoven/TeamSite/iw-perl/vendor/lib/XML/DOM.pm line 4269.
Compilation failed in require at
/Interwoven/TeamSite/iw-perl/vendor/lib/TeamSite/WFconstructor.pm line 481.
BEGIN failed--compilation aborted at
/Interwoven/TeamSite/iw-perl/vendor/lib/TeamSite/WFconstructor.pm line 481.
Compilation failed in require at (eval 1) line 44.
BEGIN failed--compilation aborted at (eval 1) line 44.

Adam Stoller

There appears to be some mismatch between the version of of the Encode module that HTTP::Message is expecting to be using, and the version of the Encode module that is being referenced (most likely in iw-perl/vendor/lib) - your choices are:

jagadesh

[QUOTE=ghoti]There appears to be some mismatch between the version of of the Encode module that HTTP::Message is expecting to be using, and the version of the Encode module that is being referenced (most likely in iw-perl/vendor/lib) - your choices are:

As ghoti told, PM modules has version compatibility, install the exact relevant modules then try again

Migrateduser

As ghoti told, PM modules has version compatibility, install the exact relevant modules then try again

This just in from the Department of Redundancy Department....

nipper

This just in from the Department of Redundancy Department....

But still gives you the opportunity to pad your post totals. Me too.

I just need to bread Ghoti;s computer for a few years and I can take over the lead. :-)

Migrateduser

But still gives you the opportunity to pad your post totals. Me too.

I just need to bread Ghoti;s computer for a few years and I can take over the lead. :-)

Come on - that was funny, wasn't it? I loathe "ditto" posts unless they are my own to pad my post count.

A few years indeed....Ghoti is king of the mountain for the foreseeable future...

Adam Stoller

I just need to bread Ghoti;s computer for a few years and I can take over the lead. :-)

"bread" my computer? - You do that and you're toast! (or perhaps you're just a few slices short of a loaf?) :-)

Khateef

Hi All,

Thanks to Ghoti. I got resolved the issue by installing older version of HTTP::Message module. Now workflows are working fine.