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 specific problem?
Admin UI support for fields added in #4227, #4245 - expose them in edit/view forms for systems.
System fields:
cookie_max_age_seconds: Optional[int]
uses_cookies: bool, default=False
cookie_refresh: bool, default=False
uses_non_cookie_access: bool, default=False
legitimate_interest_disclosure_url: Optional[str]
PrivacyDeclaration fields:
flexible_legal_basis_for_processing: Optional[bool] -- don't default to anything if Compass gives you null/None update here @TheAndrewJackson Compass isn't really capable of giving you a null/None for this field, i don't think, so i'd ignore any special handling for now, please treat this as a normal boolean! we probably need to revisit this a bit from the BE/data modeling POV across the stack, but i don't think there's any need to go out of your way in the FE code for now 👍
Describe the solution you'd like
These fields should show up in the System and PrivacyDeclaration forms, and they should also get populated from Compass, which will now be serving them as fields in its response
Describe alternatives you've considered, if any
Need to look further into Optional[bool] to see if this is really viable...
Is your feature request related to a specific problem?
Admin UI support for fields added in #4227, #4245 - expose them in edit/view forms for systems.
System
fields:cookie_max_age_seconds
:Optional[int]
uses_cookies
:bool, default=False
cookie_refresh
:bool, default=False
uses_non_cookie_access
:bool, default=False
legitimate_interest_disclosure_url
:Optional[str]
PrivacyDeclaration
fields:flexible_legal_basis_for_processing
:Optional[bool]
--don't default to anything if Compass gives youupdate here @TheAndrewJackson Compass isn't really capable of giving you anull
/None
null
/None
for this field, i don't think, so i'd ignore any special handling for now, please treat this as a normal boolean! we probably need to revisit this a bit from the BE/data modeling POV across the stack, but i don't think there's any need to go out of your way in the FE code for now 👍Describe the solution you'd like
These fields should show up in the
System
andPrivacyDeclaration
forms, and they should also get populated from Compass, which will now be serving them as fields in its responseDescribe alternatives you've considered, if any
Need to look further into
Optional[bool]
to see if this is really viable...Additional context
https://ethyca.atlassian.net/browse/PROD-1147
https://github.com/ethyca/fides/issues/4269 is a followup that covers the flexible logic for legal basis, which is not being done as part of the current unit of work
The text was updated successfully, but these errors were encountered: