handlers.link_fact_sheet_by_tag_handler
Whenever somebody sets a specific tag, we link this fact sheet to another fact sheet.
Configuration:
fs_type: Fact sheet type of the fact sheets to be linked automatically, e.g. ITComponent.
relation: The relation type that will be used for linking.
mapping: Combinations of the tags and the ids of the fact sheets that should be linked automatically.
Examples:
"EAI": {
"*": "abcdefff-1234-abcd-defa-12345678abcd"
}
Links the fact sheet abcd... if any tag in the group EAI is added.
"EAI": {
"LeanIX Team": "abcdefff-1234-abcd-defa-12345678abcd"
}
Links the fact sheet abcd... if the tag "LeanIX Team" in the tag group "EAI" is added.
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": [
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).
Called automatically whenever a FactSheetUpdated event comes in via webhook.
Inherited Members
- handlers.eventhandler.EventHandler
- EventHandler
- get_trigger
- get_event_types
- get_fs_types
- get
- all
- lx_client
- initial_sync_event
- update_with_uniqueness_check
- facet_matches
- is_tag_key
- SUBSCRIPTION_TYPES
- parse_subscription_key
- get_mapped_subscriptions
- get_notification_users
- get_send_email_for_users
- get_email_callback
- get_due_date