I'm working on adding some enhancements to a sales order approval workflow. For some reason a condition that i am setting for a popup message is not being evaluated correctly, yet when display those fields in my condition, they appear to be correct. Also, transitions using the same or similar logic works. I've tried to trigger the condition "Before User Edit", "After Field Edit" and "After Field Sourcing" and it still doesn't work. Note one of the fields in my condition is a sourced field. Below are a few screen shots.

Looks like your fields are calculated fields?

@KevinJ of Kansas thanks. that would be ideal, but i need to include it in an existing workflow. By wrapping these fields in nlapi calls, it now works. So i'm using the following condition instead: nlapiGetFieldValue('overallbalance') + nlapiGetFieldValue('overallunbilledorders')) > nlapiGetFieldValue('custbody_veecreditlimitsourced')

Here's what the Help Guide says:

SQL functions execute on the server, while JavaScript and SuiteScript execute on the client. Therefore, use SQL functions with server triggers on workflow definitions, actions, and transitions; use JavaScript and SuiteScript functions with client triggers on actions. You cannot use client triggers with workflow definitions or transitions.