{% comment %} One question in the import mapping step. Field names are `||`; apps/flows/views_portability.py drops any that do not name a requirement this document actually raises, so a hand-posted field cannot introduce one. {% endcomment %} {% with requirement=resolution.requirement %} {% comment %} `.is-unanswered` is the whole point of this card's styling. The footer counts what is still missing, and before this there was nothing on the page connecting that count to a control: a workspace with no Instagram account saw "1 answer still needed", an untouched dropdown, and no way to tell which of eight questions it meant. The id is what the footer links to. {% endcomment %}

{% if resolution.problem %}Needs an answer{% endif %} {% if requirement.name %}{{ requirement.name }}{% else %}Unnamed {{ kind }}{% endif %} {% if requirement.detail and kind != "custom_field" %} ({{ requirement.detail }}) {% endif %}

{% comment %} Blank for a single-flow file, and flow names rather than the importer's internal coordinates otherwise — see _needed_by in apps/flows/views_portability.py. {% endcomment %} {% if needed_by %}

Needed by {{ needed_by }}

{% endif %}
{% if requirement.in_document %}

Included in this file.

{% elif kind == "whatsapp_template" %}

Make sure {{ requirement.name }} exists in your WhatsApp account.

{% elif kind == "request_header" or kind == "link_handle" or kind == "from_override" or kind == "comment_posts" %} {% comment %} These were removed on export rather than translated — a credential, an account handle, the exporter's own post ids. There is nothing to map to and nothing to create, only a value to supply or leave blank. {% endcomment %} {% elif kind == "platform" %} {% comment %} One control, deliberately. The generic action select plus a connection dropdown had two ways to say "unbound" and one of them — "use an existing one" with nothing picked — was reachable by not finishing the form. An unbound trigger listens on every platform its type supports, so that had to stop being the accidental answer. {% endcomment %} {% comment %} With nothing connected the dropdown holds one real answer and no accounts, which reads as a broken form rather than as a step that has not been done yet. Saying so is not optional politeness: the wide option is still offered, so somebody who does not know an account is missing picks it and imports a trigger far broader than the one the template described. {% endcomment %} {% if not options %}

No {{ requirement.name|default:requirement.key }} account is connected. You can connect one or pick one after importing.

{% endif %} {% if resolution.action == "blank" %}

This trigger will listen on every platform its kind works on, not only {{ requirement.name|default:requirement.key }}.

{% endif %} {% comment %} Always shown. An earlier cut hid this when the picker had no options, to avoid repeating the "no account is connected yet" note above — and that note is grey, informational, and says nothing about being the thing blocking the import. The two say different things now: the note explains the empty dropdown, this says the question is unanswered. {% endcomment %} {% if resolution.problem %}

{{ resolution.problem }}

{% endif %} {% else %} {% comment %} Only the control the chosen answer needs. All three used to show at once — the action, a name box and an existing-thing picker — so every question read as three questions, two of which did nothing. Picking "Create it" left a "Pick one…" dropdown sitting beside it looking unanswered. `x-show`, not a server round trip: the answer is not saved until Save answers, and hiding on the client keeps the field posted (a hidden input still submits) so switching back and forth loses nothing typed. {% endcomment %}
{% if requirement.creatable %} {% endif %} {% if kind == "custom_field" %} {% endif %} {% if kind == "media" %} {% else %} {% endif %}
{% if resolution.problem %}

{{ resolution.problem }}

{% endif %} {% endif %}
{% endwith %}