User_KC8S1 Red Ribbon

try using expression syntax where you will have access to the "old" macro (or whatever you want call it) For example: {old.salesrep.id} != {salesrep.id}

I know it's Beta, I should have just waited until it was out of Beta I guess. As I said in my email: When I see “All fields supported” in release notes I will try again. Looking forward to it.

Seems to be working well. However, for some reason, it doesn't do anything if the field in Old Record was blank and the field is then populated or vice versa. Kinda weird since NULL is not equal to NOT NULL. That is odd because that is not the behavior I am experiencing. My WF is detecting CREATE or UPDATE operations and…

Oh God am I happy to hear about such a project! PLEASE do the same for SuiteScript, please.

Evan, confused what you mean by this: One of our next projects is to make sure all of those fields are represented in search All WHAT fields? Let's say you have Sales Order. You are saying that 2010.2 should have ALL the Sales Order body fields. (great) But then what do you mean "represented in search" - a WorkFlow search?…

Trial and Error!!!!!!!! :) {id} is null or {old.assigned.id} != {assigned.id} Now.... if you're like me then you may be wondering why the FU&$ isn't it {internalid} like it is in script and just about everywhere else. I don't know but my joy of making this work is briefly overpowering my instinct to complain. Briefly.

sure, I think that would work. The first Transition would dump to the end, or delay and transition back into the same state or something and the next one would take me to the next State. Good idea, thanks for the help.

ALRIGHT! Thanks for the info.

It's odd that the "braces" syntax works on the subject line though?

It's been almost a day and it has not transitioned yet ;) Case #1210951 Update : Delayed Transition is not executing

It looks like this does not work. I don't know if it's because I have a misunderstanding about the system or if it's because something is not working correctly. Seems like a Transition set to Trigger on Entry with a 1 hour delay should be executed in one hour and do it's job but the record is still in that State.

I guess I'll have to wait for 2011.1. Thanks for the update. Yikes, you don't need to wait that long. Just use a custom action and script it, then you can keep going with your plans.

It IS possible although it appears the visual builder can't support it. If I enter the following custom formula {old.assigned.id} != {assigned.id} then change to the Visual Builder it clears the field because I assume it can't parse the expression. It it DID support it I think it would look like this Old Record : Assigned…

Your response would be valuable in the Help, hopefully someone is monitoring this thread. OK, so it looks like what we are missing is a WorkFlow-specific preference field. If I have a workflow and I want to configure 10 options on the WorkFlow definition page it sounds like I can't do that. If I use Class fields they will…

Sorry for the spam. I just though I would share the final solution in case anyone is interested in doing something like this. I ended up creating two transitions from Entry that each had a condition to determine if the record is new or if the assignee had changed. Here is what it looks like:…

I also entered an ER request to expose Name and Description fields on the Actions list on a State. I haven't received the ER# yet, but here is a mockup of what I would like to see (supplied with the ER request to NS): http://picasaweb.google.com/SteveKlett/NSUGStuff#5520500330274911234

It just drives me nuts when they obviously overlook adding support for something as basic as the notes field, then when you alert them to the problem it gets dropped into the bottomless abyss of enhancements. Seems very inefficient: [LIST] [*]you've got unhappy customers [*]support taking calls and creating enhancements…

Just a quick note that SYSDATE (and other DB functions) do not require brackets. If the formula parser sees brackets it will try to resolve to a field with that id (and fail)

Do you link the Contact with the Transaction? I don't think you would, but of you did and if you ALSO start the "new order email" with the same words then you could create a Contact search filtered on: MessageFields.Title "doesn't start with" "Thanks for the order" Transaction.Type = SalesOrder Transaction.ItemOnAnyLine =…

It looks like a generic Contact join is not exposed in the Transaction search. If you start with a Contact search it looks like you have the Role filter and the Transaction join but you won't be able to Trigger on Sales Order creation. You could create a custom scripted Action to pull the Contact you want and return to a…

I'm still not familiar enough with Workflows to easily grasp the whole picture here. I understand what you are suggesting and can see it as a viable alternative to a custom transition. Please confirm if I have this correct: [LIST=1] [*]A Workflow's active state is persistent, that is it remembers it's active state during…

I stopped working with Workflows for about 4 months or so and just started again Tonight. I created a scheduled workflow and noticed this in the log! Claim Crossover Verification Monitor Complete 9/20/2010 9:32 pm 9/20/2010 9:32 pm Claim Crossover Verification Monitor Balance Paid 9/20/2010 9:32 pm 9/20/2010 9:32 pm Claim…

Can you explain what you mean by the standard transitions not being enough... Sure, what I mean is that they aren't flexible enough for some use cases. Let's say I have a workflow that will approve a purchase order when a commodity price drops below a certain point. I have a web service which will supply me global…

OK, that makes total sense. I still propose a warning popup or something. It's an easy option to overlook and not terribly obvious when troubleshooting non-invocation issues.

I gave up and didn't check back on it. I plan to soon so we'll see! ;)

Wait, hold on... I jumped the gun again. It's Thursday night they do the updates, not Thursday morning so maybe there is still hope this feature will be working in a day!

It ran again on the same record but this time it ran 42 times!! It also didn't run for over 1.5 hours after the previous run. Help says it should be every ~30 minutes. Now I remember why I put WorkFlows down for 4 months :( Your Customer Care Case # is 1210218.

I ended up doing this with a script so my Workflow isn't testable right now but I will assume from btanenholtz response that it is indeed working. This is great because I have other workflows planned that will need this functionality. Did you fix it out of cycle or was it part of the last eFix? Either way, thanks!

Thanks for the response. In your example I wouldn't call that a formula because there is no processing being done, it's just simple field substitution. I really hope that the SetField Action is not limited to this. I look forward to what else you may find out.

OK, it apparently ran a little bit ago. This is strange. "Beta" might be pushing it a bit... feels pretty random and quirky so far. It's cool and exciting... but quirky