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 should only have one column to determine the compensation type of an EquityCompensationIssuance.
UPDATE: We actually do have this already -- the old field option_grant_type is marked as DEPRECATED via the $comment field:
"$comment": "DEPRECATION WARNING - This field is being retained for compatibility, but these variations have been incorporated into CompensationType.schema.json enum options"
We should move that $comment into the description field so that it appears in the documentation as so.
We also need a boolean to track ISO eligibility at time of issuance, to support OCX
Why is this Needed?
We cannot support the OCX column "ISO Eligible at Grant Date (Y/N)" without tracking this separately in OCF
Anything else we need to know?
Created while working through the comments sheet attached to issue #507
The text was updated successfully, but these errors were encountered:
jacobyavis
changed the title
[Enhancement]: Consolidate/simplify columns on EquityCompIssuance with regard to ISO eligibility, new boolean to track ISO eligibility at time of issuance
[Enhancement]: New boolean to track ISO eligibility at time of issuance
Sep 16, 2024
Description of Enhancement :
We should only have one column to determine the compensation type of an EquityCompensationIssuance.
UPDATE: We actually do have this already -- the old field
option_grant_type
is marked as DEPRECATED via the $comment field:We should move that $comment into the description field so that it appears in the documentation as so.
We also need a boolean to track ISO eligibility at time of issuance, to support OCX
Why is this Needed?
We cannot support the OCX column "ISO Eligible at Grant Date (Y/N)" without tracking this separately in OCF
Anything else we need to know?
Created while working through the comments sheet attached to issue #507
The text was updated successfully, but these errors were encountered: