From ec50d93884ef49a3f726a7cb866d16f4386b5606 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?= Date: Fri, 4 Sep 2026 18:56:07 -0400 Subject: [PATCH] docs: changelog for the 4-Sep connector work and the ticket assignee change The Power Automate actions, their dynamic dropdowns and the dropped location fields shipped in #31 with no changelog entry. Adds it, together with the list_users filtering from DScope/datascope-rails#2737, which takes the technical accounts out of the user pickers in both connectors. Rebuilds the Zapier 2.1.3 entry from the 2.1.2 and 2.1.3 app definitions. The (FKA Issue) rename, the user and form dropdowns, the renamed signature output labels and the rewritten help text were all missing from it. The trigger and action tables in the three guides now use the current names. Documents that Create Ticket accepts assignees and invitees as a comma-separated string (DScope/datascope-rails#2661, shipped 31-Aug), in the endpoint's parameter table and in its own changelog entry. Co-Authored-By: Claude Opus 5 --- source/index.html.md | 17 +++++++++++++++-- source/zapier/connector_guide_en.html.md | 21 ++++++++++++++++++--- source/zapier/connector_guide_es.html.md | 23 ++++++++++++++++++++--- source/zapier/connector_guide_pt.html.md | 23 ++++++++++++++++++++--- 4 files changed, 73 insertions(+), 11 deletions(-) diff --git a/source/index.html.md b/source/index.html.md index 0dd28f0caf6..46cb27d04b8 100644 --- a/source/index.html.md +++ b/source/index.html.md @@ -2546,8 +2546,8 @@ status | String | Status of ticket. Fallback: `open`. Options: `[open, in_progre priority | String | Status of ticket. Fallback: `medium`. Options: `[low, medium, high, critical]` location_id | Integer | Optional. ID of the location location_name | Integer | Optional. Name of the location in case of unrecognized `location_id` -assignees | Array of Integers or Strings | Required. MobileUser IDs or emails of users to be assigned to the ticket -invitees | Array of Integers or Strings | Optional. MobileUser IDs or emails of users to be invited to the ticket (ignoring already assigned ones) +assignees | Array or String | Required. MobileUser IDs or emails of users to be assigned to the ticket. Send an array, or a comma-separated string if your client cannot send array parameters. Up to 100 entries +invitees | Array or String | Optional. MobileUser IDs or emails of users to be invited to the ticket (ignoring already assigned ones). Send an array, or a comma-separated string if your client cannot send array parameters. Up to 100 entries type | String | Optional. Ticket Type ID or Ticket Type Name. If provided, preset data will be retrieved from this type. Fallback: "Other" (no type assigned). creation_date | String or Datetime | Optional. Date or String with a custom creation date of ticket (YYYY-MM-DD HH:MM) @@ -2565,6 +2565,19 @@ Remember — use your own Authorization header # Changelog +**04-Sep-2026** + +- The user pickers in the [Zapier](#zapier) and [Power Automate](#microsoft-power-automate-beta) connectors no longer list the technical accounts DataScope creates for submissions that have no real user behind them, so they can no longer be selected as an author, an assignee or an invitee. The change is server side and applies to the Zaps and flows you already have +- The [Microsoft Power Automate](#microsoft-power-automate-beta) connector now carries actions, not only triggers: Assign Task, Change Form Status, Modify Form Answer, Send Data (Beta) and Create Ticket. Re-import the definition file to pick them up +- Form, status, user and ticket type fields on those actions offer a dropdown, so there is no need to paste raw ids copied from elsewhere +- Assign Task uses the native date picker for the due date, and no longer exposes the fields that created a Location on the fly +- The English and Portuguese guides now call tickets by their current name, as the Spanish one already did +- Rebuilt the [Zapier](#zapier) changelog entry for app version 2.1.3 from the app definition, covering the ticket trigger and action renames, the new user and form dropdowns, the renamed signature output fields and the rewritten help text. The guides now use the current trigger and action names + +**31-Aug-2026** + +- [Create Ticket](#create-ticket) accepts `assignees` and `invitees` as a comma-separated string, not only as an array, for clients that cannot send array parameters. Up to 100 entries per field. Clients that already send an array are unaffected + **26-Aug-2026** - Added the [Zapier](#zapier) section under Data Export, with a step-by-step guide in English, Spanish and Portuguese covering the connection, every trigger and action, the Locations and Places choice, and the one-Zap-per-form constraint diff --git a/source/zapier/connector_guide_en.html.md b/source/zapier/connector_guide_en.html.md index 1f8f0f6fd18..b68491a1319 100644 --- a/source/zapier/connector_guide_en.html.md +++ b/source/zapier/connector_guide_en.html.md @@ -83,8 +83,8 @@ see in Zapier's trigger list: | Signatures: New Completed Signature | Every signer has signed the document | Optional, pick one | | Signatures: New Rejected Signature | A signer rejects the signature request | Optional, pick one | | Signatures: Updated Signature | The signatures on a document change while some are still pending | Optional, pick one | -| Tickets: New Ticket (FKA Issue) | A ticket is created | Not applicable, account level | -| Tickets: Changed Status (FKA Issue) | A ticket changes status | Not applicable, account level | +| Tickets: New Ticket | A ticket is created | Not applicable, account level | +| Tickets: Changed Status | A ticket changes status | Not applicable, account level | Each trigger delivers the event data as individual fields, ready to map into the following steps of the Zap without having to parse the JSON yourself. For @@ -101,7 +101,7 @@ DataScope instead of only reacting to it: | Forms: Send Data / New Answer [Beta] | Generates a new form answer and its PDF from an existing form used as a template | | Change Form Status | Changes the status of a form answer, found by form name and form code | | Modify Form Answer | Creates or updates a single answer inside an existing form response | -| Tickets: Create Ticket (FKA Issue) | Creates a ticket, optionally taking its defaults from a Ticket Type | +| Tickets: Create Ticket | Creates a ticket, optionally taking its defaults from a Ticket Type | ### Assign Task: V1 or V2 @@ -261,6 +261,21 @@ user or task counts. Add a date only when the release date is known. legacy Locations one. - Adds `Find Location / Place by ID` to `Tasks: Assign Task V2`, so a task can point at an existing location or place by its internal ID. +- Drops the `(FKA Issue)` suffix from the two ticket triggers and from + `Tickets: Create Ticket`. A Zap built on an earlier version still shows the + old name. +- `User Email` on `Tasks: Assign Task V2` and `Form Name` on + `Change Form Status` become dropdowns, so you pick the user or the form from + a list instead of typing it. +- Renames output field labels on `Signatures: New Completed Signature`. + `Signer Rut` is now `Signer National ID`, and `If Signer is a Datascope User` + is now `Signer Is External User`, which is what the field actually reports. + The keys behind the labels do not change, so existing mappings keep working. +- Rewrites the help text on most fields, including every location field on + `Tasks: Assign Task V2`, which now states which module each one applies to. + `Modify Form Answer` gets its `From Code` label fixed to `Form Code`, and + `Tasks: Assign Task V1 [Legacy]` now says in its description that V2 is the + one to use. **2.1.2** (default for new Zaps) diff --git a/source/zapier/connector_guide_es.html.md b/source/zapier/connector_guide_es.html.md index 2c1b277ff97..83d48c434e7 100644 --- a/source/zapier/connector_guide_es.html.md +++ b/source/zapier/connector_guide_es.html.md @@ -85,8 +85,8 @@ que ves en la lista de disparadores de Zapier: | Signatures: New Completed Signature | Todos los firmantes firmaron el documento | Opcional, elige uno | | Signatures: New Rejected Signature | Un firmante rechaza la solicitud de firma | Opcional, elige uno | | Signatures: Updated Signature | Cambian las firmas de un documento y todavía quedan pendientes | Opcional, elige uno | -| Tickets: New Ticket (FKA Issue) | Se crea un ticket | No aplica, es a nivel de cuenta | -| Tickets: Changed Status (FKA Issue) | Un ticket cambia de estado | No aplica, es a nivel de cuenta | +| Tickets: New Ticket | Se crea un ticket | No aplica, es a nivel de cuenta | +| Tickets: Changed Status | Un ticket cambia de estado | No aplica, es a nivel de cuenta | Cada disparador entrega los datos del evento como campos individuales, listos para mapear en los pasos siguientes del Zap sin tener que procesar el JSON @@ -103,7 +103,7 @@ sobre DataScope y no solo reaccionar a sus eventos: | Forms: Send Data / New Answer [Beta] | Genera una nueva respuesta de formulario y su PDF a partir de un formulario existente usado como plantilla | | Change Form Status | Cambia el estado de una respuesta de formulario, identificada por nombre y código de formulario | | Modify Form Answer | Crea o modifica una respuesta puntual dentro de un formulario ya enviado | -| Tickets: Create Ticket (FKA Issue) | Crea un ticket, opcionalmente tomando sus valores por defecto de un Ticket Type | +| Tickets: Create Ticket | Crea un ticket, opcionalmente tomando sus valores por defecto de un Ticket Type | ### Assign Task: V1 o V2 @@ -272,6 +272,23 @@ versión. Agrega una fecha solo si se conoce la fecha de publicación. Locations antigua. - Agrega `Find Location / Place by ID` en `Tasks: Assign Task V2`, para que una tarea pueda apuntar a un lugar existente por su ID interno. +- Saca el sufijo `(FKA Issue)` de los dos disparadores de tickets y de + `Tickets: Create Ticket`. Un Zap creado en una versión anterior sigue + mostrando el nombre antiguo. +- `User Email` en `Tasks: Assign Task V2` y `Form Name` en + `Change Form Status` pasan a ser listas desplegables, así eliges el usuario o + el formulario en vez de escribirlo. +- Renombra etiquetas de campos de salida en + `Signatures: New Completed Signature`. `Signer Rut` ahora es + `Signer National ID`, y `If Signer is a Datascope User` ahora es + `Signer Is External User`, que es lo que el campo realmente informa. Las + claves detrás de las etiquetas no cambian, así que los mapeos existentes + siguen funcionando. +- Reescribe los textos de ayuda de la mayoría de los campos, incluidos todos + los campos de ubicación de `Tasks: Assign Task V2`, que ahora indican a qué + módulo aplica cada uno. En `Modify Form Answer` corrige la etiqueta + `From Code` a `Form Code`, y la descripción de + `Tasks: Assign Task V1 [Legacy]` ahora dice que la V2 es la que hay que usar. **2.1.2** (predeterminada para los Zaps nuevos) diff --git a/source/zapier/connector_guide_pt.html.md b/source/zapier/connector_guide_pt.html.md index ab14316e1ab..c499789343a 100644 --- a/source/zapier/connector_guide_pt.html.md +++ b/source/zapier/connector_guide_pt.html.md @@ -87,8 +87,8 @@ vê na lista de disparadores do Zapier: | Signatures: New Completed Signature | Todos os signatários assinaram o documento | Opcional, escolha um | | Signatures: New Rejected Signature | Um signatário rejeita a solicitação de assinatura | Opcional, escolha um | | Signatures: Updated Signature | As assinaturas de um documento mudam e ainda há pendentes | Opcional, escolha um | -| Tickets: New Ticket (FKA Issue) | Um ticket é criado | Não se aplica, é no nível da conta | -| Tickets: Changed Status (FKA Issue) | Um ticket muda de status | Não se aplica, é no nível da conta | +| Tickets: New Ticket | Um ticket é criado | Não se aplica, é no nível da conta | +| Tickets: Changed Status | Um ticket muda de status | Não se aplica, é no nível da conta | Cada disparador entrega os dados do evento como campos individuais, prontos para mapear nas etapas seguintes do Zap sem precisar processar o JSON @@ -105,7 +105,7 @@ DataScope e não apenas reagir aos seus eventos: | Forms: Send Data / New Answer [Beta] | Gera uma nova resposta de formulário e seu PDF a partir de um formulário existente usado como modelo | | Change Form Status | Muda o status de uma resposta de formulário, identificada por nome e código do formulário | | Modify Form Answer | Cria ou modifica uma resposta pontual dentro de um formulário já enviado | -| Tickets: Create Ticket (FKA Issue) | Cria um ticket, opcionalmente herdando os valores padrão de um Ticket Type | +| Tickets: Create Ticket | Cria um ticket, opcionalmente herdando os valores padrão de um Ticket Type | ### Assign Task: V1 ou V2 @@ -275,6 +275,23 @@ versão. Inclua uma data somente quando a data de publicação for conhecida. Locations antiga. - Adiciona `Find Location / Place by ID` na `Tasks: Assign Task V2`, para que uma tarefa possa apontar para um lugar existente pelo seu ID interno. +- Remove o sufixo `(FKA Issue)` dos dois disparadores de tickets e da + `Tickets: Create Ticket`. Um Zap criado em uma versão anterior continua + mostrando o nome antigo. +- `User Email` na `Tasks: Assign Task V2` e `Form Name` na + `Change Form Status` passam a ser listas suspensas, então você escolhe o + usuário ou o formulário em vez de digitá-lo. +- Renomeia rótulos de campos de saída na + `Signatures: New Completed Signature`. `Signer Rut` agora é + `Signer National ID`, e `If Signer is a Datascope User` agora é + `Signer Is External User`, que é o que o campo realmente informa. As chaves + por trás dos rótulos não mudam, então os mapeamentos existentes continuam + funcionando. +- Reescreve os textos de ajuda da maioria dos campos, incluindo todos os campos + de localização da `Tasks: Assign Task V2`, que agora indicam a qual módulo + cada um se aplica. Na `Modify Form Answer` corrige o rótulo `From Code` para + `Form Code`, e a descrição da `Tasks: Assign Task V1 [Legacy]` agora diz que + a V2 é a que deve ser usada. **2.1.2** (padrão para os Zaps novos)