You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
If a repeater is moved or changed enough to require re-coordination, there is currently no process in place to facilitate this.
Describe the solution you'd like
When a user changes a repeater's metadata outside of the deviation allowances, they should be prompted that the repeater will need to be re-coordinated because of the changes. After they approve, then workflows should be created for the coordination. Need to ensure that new logic is added to ignore the repeater being changed when automated approvals. (Perhaps a new status of "Re-coordination pending".)
Describe alternatives you've considered
None
Additional information
None
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
If a repeater is moved or changed enough to require re-coordination, there is currently no process in place to facilitate this.
Describe the solution you'd like
When a user changes a repeater's metadata outside of the deviation allowances, they should be prompted that the repeater will need to be re-coordinated because of the changes. After they approve, then workflows should be created for the coordination. Need to ensure that new logic is added to ignore the repeater being changed when automated approvals. (Perhaps a new status of "Re-coordination pending".)
Describe alternatives you've considered
None
Additional information
None
The text was updated successfully, but these errors were encountered: