I have one idea. Let's take a set sample statuses here of (in order) New, Assigned, In Progress, Pending, Resolved, Closed to give ourselves a frame of reference. Let's suppose furthermore that your DDL is called ddlStatus
Depending on the source of your DDL options, one thing you can do is assign a number as the Value for each status. So
Value = 1, Display Name = New
Value = 2, Display Name = Assigned
Value = 3, Display Name = In Progress
Value = 4, Display Name = Pending
Value = 5, Display Name = Resolved
Value = 6, Display Name = Closed
You can set ddlStatus to have a default value of 1, then when you click Update, you can fire an Action Rule that sets ddlStatus.Value to ddlStatus.Value + 1
I'm not 100% sure of what this would look like in code, but the principle should work. Otherwise you have to create some kind of lookup table with values of Current Status and Next Status and God forbid that you need the ability to do something like be able to go from In Progress to either Pending or Resolved! I guess in that case, you have to have some other conditions to know which one you need to go to.
Good luck!
nkstrou
An imprecisely defined requirement has an infinite number of possible solutions. Unfortunately, only about a maxiumum of 3 solutions are actually satisfactory to the end user.