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
We need to be able to edit timelines in work manager. That includes:
Changing the timeline template
Changing the start/end of a phase and possibly moving the gantt
We had this in the UI before and had the functionality there, and everything worked fine in v5. It was when it was sync'd back to legacy that there was a problem. If i remember correctly, the issue was the v4 API wouldn't allow for that level of editing.
I believe what needs to happen is we need to move the legacy-challenge-processor almost completely away from using the v4 api, and manipulate challenge information using informix directly. The problem here is that legacy still needs all the components and stuff created.
I think the steps then would be:
When a challenge is changed from New to Draft, CREATE the challenge using v4/challenges api
When a challenge is edited/updated, use Informix directly.
Background
The things we're currently relying on legacy to do is:
Add the default terms to a challenge (review phase terms, etc)
Autopilot move the phases along
Handle review
Manage payment
Default terms, we should create a mechanism in the terms api (?) to map track-type-phase -> terms? (not sure about this or where it should live to be managed) ((we also have to assess if we need terms attached at the phase level))
Autopilot v5 is being discussed.
Review and Payment happen later in the cycle
All this means that we should be very close to getting away from keeping legacy in lock step with challenge edits.
We need to be able to edit timelines in work manager. That includes:
We had this in the UI before and had the functionality there, and everything worked fine in v5. It was when it was sync'd back to legacy that there was a problem. If i remember correctly, the issue was the v4 API wouldn't allow for that level of editing.
I believe what needs to happen is we need to move the
legacy-challenge-processor
almost completely away from using the v4 api, and manipulate challenge information using informix directly. The problem here is that legacy still needs all the components and stuff created.I think the steps then would be:
Background
The things we're currently relying on legacy to do is:
All this means that we should be very close to getting away from keeping legacy in lock step with challenge edits.
Related Issues
The text was updated successfully, but these errors were encountered: