Forum Discussion
DonLarson
4 years agoQrew Elite
Chris,
What does the architecture of your application look like?
Assuming that you are tracking every Task Status Change
Assume that your Task Status table has values that look like this
1 New
2 Not Started
3 Submitted for Approval
4 Rejected
5 Revisions Needed
6 Approved
I would add a Pipeline that fires when a Record is added to the Task Status Change table where
Related Task Status =4
The Pipeline then adds a record to that table
Related Task = RID from the Task from prior add
Related Task Status = 5
Note = "Rejected by ... Status set to Revisions Needed" or whatever makes sense for your person that has to work on it for the revision.
------------------------------
Don Larson
------------------------------
What does the architecture of your application look like?
Assuming that you are tracking every Task Status Change
Assume that your Task Status table has values that look like this
1 New
2 Not Started
3 Submitted for Approval
4 Rejected
5 Revisions Needed
6 Approved
I would add a Pipeline that fires when a Record is added to the Task Status Change table where
Related Task Status =4
The Pipeline then adds a record to that table
Related Task = RID from the Task from prior add
Related Task Status = 5
Note = "Rejected by ... Status set to Revisions Needed" or whatever makes sense for your person that has to work on it for the revision.
------------------------------
Don Larson
------------------------------