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

wfconstructor

Valentine

Should I be using TeamSite::WFconstructor or am I better away with manually coding the *.wft file?

Up until now I was creating wft files straight-up, but looking at the perldoc the WFconstructor looks promising.

What's your experience?

Find more posts tagged with

Comments

jbonifaci

It is a fairly common practice among experienced developers on this forum to use WFconstructor.

~Jeff

dkuntze

That is until TeamSite 6.7.1 introduces the Workflow Modeler... But, I think ultimately the workflow engine will remain the same, and you'll be able to feed it BPMN.

DbDemo.rptdesign

jbonifaci

That is until TeamSite 6.7.1 introduces the Workflow Modeler... But, I think ultimately the workflow engine will remain the same, and you'll be able to feed it BPMN.

I'm still very skeptical about the extent that this will be usable. I saw the presentation at GearUp and it's obviously better than WF Builder, but I believe it will still have limitations. I will more be more than happy to be proven wrong, but I guess we'll have to wait and see.

~Jeff

kaalraa

A lineof thought: More complex and extensible your workflow requirements are, much more easier to code.

Should I be using TeamSite::WFconstructor or am I better away with manually coding the *.wft file?

Up until now I was creating wft files straight-up, but looking at the perldoc the WFconstructor looks promising.

What's your experience?

dkuntze

I'm still very skeptical about the extent that this will be usable. I saw the presentation at GearUp and it's obviously better than WF Builder, but I believe it will still have limitations. I will more be more than happy to be proven wrong, but I guess we'll have to wait and see.

~Jeff

I did a usabilty study with IW on it a couple of months ago. I was using a version that was newer than the one they showed at GearUp, and it was still pretty buggy. But, it is pre-beta...