#matdayman-future_requirements
brazen dome
I'm not sure I understand what you mean here -- future requirements is a "preview" of the requirements you'd eventually find in requirements later
the current_deadline tells you when this will move to requirements
Specifically, Future Requirements introduces the future_requirements hash to the Account object. future_requirements is a hash that performs the same function as the requirements hash, but for upcoming requirements that haven’t gone into effect yet. The requirements in future_requirements become active and transition to the requirements hash on the future_requirements[current_deadline].
restive mica
Ahhhh, thank you. We're currently checking the requirements hash to gather information for connect accounts but haven't updated to check for future_requirements yet. So we are trying to leverage whether we should make updates to also check the future_requirements hash in order to submit those "early" or wait until the content of future_requirements becomes available in the requirements hash
If that makes sense
brazen dome
Yea that's reasonable, the future requirements are if you want to look ahead for what to expect later
restive mica
Reason being we received an email that some accounts needed to be updated by January 12th (which implies before), and don't know if there will be some sort of grace period after that date to submit the info. So do you know if the future_requirements moving to requirements will also update the deadline in the requirements hash?
brazen dome
If not collected by future_requirements[current_deadline], these fields will transition to the main requirements hash.
From my reading, the current_deadline value would be the same when the requirements move, so you should provide the information by then or they'd be past_due
restive mica
OK. Thanks for the info! Appreciate it!
brazen dome
NP!