AssistantRemindersMemoryPayload

Assistant RemindersInfrastructure

GoogleApi.ContentWarehouse.V1.Model.AssistantRemindersMemoryPayload

1
out of 10
Minimal
SEO Impact
Since this is stored in BE, any update on this proto needs LGTM by ARIS storage owner

SEO Analysis

AI Generated

Backend infrastructure with indirect SEO impact. This model (Assistant Reminders Memory Payload) contains 2 attributes that define its data structure. Key functionality includes: Whether the reminder created has a referenced_entity attached to it or not(go/hub-memory-payload). Since we plan to set this in Assistant reminder cre...

Actionable Insights for SEOs

  • Understanding this model helps SEOs grasp Google's internal data architecture

Attributes

2
Sort:|Filter:
hasReferencedEntityAtCreationboolean(
Default: nil

Whether the reminder created has a referenced_entity attached to it or not(go/hub-memory-payload). Since we plan to set this in Assistant reminder creation path flow, in case later the referenced_entity is removed from the reminder, then this bit might still remain true. Also in case referenced_entity is later added to reminder(for example when referenced_entity is attached by Server), then also this bit might remain false. This bit will be used to guess if the user has a memory-enabled AGSA, thus we'll surface the "open memory" button on hubpage. This check is not perfect, as the user might have other phones with older AGSA, so this is just a best guess. This field won't be stored in Memory backend, and will not be populated back when retrieving reminders.

recordIdstring
Default: nilFull type: String.t

Id of record that is associated with Reminder. This will be set for all Assistant reminders created after the first launch of the Reminder Memory integration, see go/reminders-memory for more details. Also, this might apply to all other types of reminders.