Replies: 1 comment
-
^^ Info regarding how the fields are used today. I don't think that answers questions, because we will have to establish what each milestone should be, since our lambda is the 'user' setting those fields |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Background
When showing our bi directional capabilities, we've gotten feedback from at least two groups that have expressed a desire to have the seatool clocks filled out by our system.
So in Seatool, a submission has an End Date / 90th Day, as well as 4 Alert Milestones. These are dates based off the initial submission date.
Since we're setting the initial submission date as we write to seatool from our labmda, it stands to reason we could calculate these dates and write them as well.
Detail
^^ These are the fields as they show up in seatool. They each map to a column in State_Plan
Solutioning
On new submission, a lambda fires and writes to seatool. It has access to the initial submission date. We should be able to perform math based on the initial submission date and fill in these fields.
However, it's not clear what the alert milestones should be... 10th day, 15th day, 80th day? That needs to be firmed up
Questions:
This thread is to post information regarding these fields that we discover, and to talk about technical hurdles or different approaches.
Beta Was this translation helpful? Give feedback.
All reactions