handlers.sync_field_values

class SyncFieldValues(handlers.eventhandler.EventHandler):

Copies a value from one field to another field on the same fact sheet whenever it's updated.
Example: Copy the value of category into the field architectureFsCategory:

"fields": [
    ["category", "architectureFsCategory"]
]
name = 'Sync Fact Sheet Fields'
description = "Copies a value from one field to another field on the same fact sheet whenever it's updated."
supports_initial_sync = True
conditions = {'event_types': ['FactSheetUpdatedEvent'], 'fs_types': ['Architecture']}
config_template = {'fields': [['category', 'architectureFsCategory']]}
def data_requirements(self):

Declare the exact fact-sheet data this handler needs, so the webhook event loop (process_event in workspace/views_module.py) can load a single lean FastFactSheet per event instead of the full fact sheet.

Return a dict: { "fields": [], "relations": [], "subscriptions": bool, # True if handle() reads fs["subscriptions"] "tags": bool, # True if handle() reads tags / has_tag() "documents": bool, "acls": bool, "completion": bool, # True if handle() reads fs["completion"] "base_fields": [], # optional; omit/None = full # default base field set. A list restricts the # base scalars to just those (id and type are # always loaded). Advanced opt-in for max speed. } Fields referenced by this handler's trigger are folded in automatically by the event loop (into "fields"), so only declare what handle() itself needs on top of them.

Return None (the default) to signal "requirements cannot be declared statically" - e.g. handlers that exec/eval config-supplied code. The event loop then loads the full fact sheet for that event, so correctness is always preserved. This is a standalone hook (deliberately not tied to the initial_sync_* hooks, which are slated to migrate onto it later).

def handle(self, event, fs, **kwargs):

Called automatically whenever a FactSheetUpdated event comes in via webhook.