[sklett]

It’s been a year or so since I last tried to do a workflow in NetSuite for client side logic. It’s actually not mine, but a coworker that isn’t a programmer and needed some assistance. I got all high and might about state machines and how they were misusing SuiteFlow with their current State design and transitions, blah blah blah.

Then reality slapped me in the face, for the 3rd… maybe the 4th time. It appears I had to learn again that field change events don’t trigger state transitions – is this correct? If this is the case, does this not frustrate you all? Or better, am I missing something? Is there a way the WF will trigger on field changes client side?
This is a cached copy. Click here to see the original post.

[k_dunc]

I’m not aware of the ability to transition on a field change. Depending on what you’re physically trying to achieve, could you perhaps run a Workflow Action Script triggered on a Field Change?

[sklett]

Thanks for the suggestion, but it would be easier to just use script. Workflows are another example of NetSuite releasing something and then doing nothing at all to improve it over time.

[Voltron]

Originally posted by sklett

View Post

Thanks for the suggestion, but it would be easier to just use script. Workflows are another example of NetSuite releasing something and then doing nothing at all to improve it over time.

I don’t agree with “nothing at all.” They’ve made some good strides with it. I think it’s foundationally challenged. I’ve felt for years that it will always have it’s place but is far from a substitute for scripting.

And I don’t have an answer to the original question. ha

[sklett]

Technically, they have done some things, though I can only think of the updated graphical editor. In the interest of discussion, what changes since initial launch have they made? I’m really asking, it could be that I have selective memory and am forgetting stuff, in fact I probably am!

[Author]

Posts