My DB rule is behaving strangely. Sometimes the update actions works sequentially, as written, but sometimes it doesnt.
Here's my rule: When case is created OR When case is modified where Status (*) equals CLOSED AND NOT (Assignment;To person is current) Status=CLOSED,Assignment to Current (Update Data) Assignment;To person set to (Make empty); Assignment;To workgroup set to (Make empty); Assignment;To person set to (Current person); Assignment;To workgroup set to (Make empty)
When a person closes the ticket, I want the Assignment To Person to be set to the person who closed the case.
In some cases, it works fine. In some cases, the Update Data action swaps, once it sets, the n it clears the field.
I think that better is to use UI rule "Before save" for this action instead of DB rule because there could be problem with Current person identification via the function (DB rule is evaluated after save and system couldn't be able to find the actual person who modified the record). But this solution with UI rule could cause problems when you update case via SSP (but there you can customize SSP to fill the currently logged specialist).