We have a process for Extra Duty time approvals. There are several projects that can fall into our Curriculum / Training Additional Job code. Because this is a big bucket that encompasses many projects, we needed a way of verifying approved projects, which requires an employee to include a note on their time entry. When they don't, time is rejected. When they go back to include the note AFTER the pay cycle is locked, this does not take the "rejected" status away so that the time can now be approved and pushed forward to the next pay cycle. Can Red Rover be programed so that IF we RESTART the workflow on these individual time entries, the rejected status goes away AND the time entry is PUSHED forward to the NEXT OPEN pay cycle? If we don't want it pushed forward, we would leave it rejected. So, this seems to make sense as a solution to the issue. We don't really want the "edit" or "addition" of a note itself to trigger a change because we do add notes to approved timesheets for various reasons (clarity, etc).