Descripción
El addon GravityBoard – Visual Workflow Management convierte envíos de Gravity Forms en tarjetas Kanban arrastrables, organizando entradas por estado, prioridad o responsable directamente en el panel de WordPress. Diseñado para equipos que manejan cada formulario como ticket, pedido o tarea, el complemento conecta el motor de GravityKit al flujo visual de tableros, listas y columnas personalizables, eliminando herramientas externas de gestión de proyectos.
Características Principales
- Tableros Kanban por formulario
Renderiza entradas de Gravity Forms como tarjetas en columnas de estado configurables. - Arrastrar y soltar entre etapas
Mueve entradas entre columnas actualizando el campo de estado en tiempo real. - Columnas personalizables
Define etapas del flujo de trabajo basadas en cualquier campo desplegable, radio o casilla de verificación. - Filtros y búsquedas avanzadas
Segmenta tarjetas por responsable, plazo, prioridad o cualquier metadato del formulario. - Integración nativa con GravityKit
Aprovecha permisos, vistas y configuraciones ya definidas en el ecosistema GravityKit.
Beneficios del GravityBoard – Visual Workflow Management
- Visión clara del pipeline
Sustituye hojas de cálculo y listas estáticas por un panel visual con el estado de cada entrada. - Menor dependencia de herramientas externas
Centraliza la gestión de tareas en el mismo WordPress, sin Trello, Asana o ClickUp paralelos. - Respuesta más rápida a envíos
El equipo identifica cuellos de botella y prioridades sin abrir cada entrada individualmente. - Estandarización del flujo de trabajo
Define etapas fijas que cada envío debe recorrer hasta la conclusión.
¿Para Quién Está Indicado?
- Equipos de soporte que manejan cada envío de formulario como ticket a resolver.
- Agencias que gestionan briefings, pedidos de presupuesto y solicitudes de clientes.
- Equipos internos que usan Gravity Forms para registrar tareas, demandas y procesos administrativos.
Para quienes ya dependen de Gravity Forms como motor de captura de datos, GravityBoard transforma el acto de recibir entradas en un flujo visualmente gestionable, con tarjetas moviéndose entre etapas y responsables siguiendo el progreso de cada envío. Está indicado para operaciones en que cada formulario enviado dispara un proceso interno que debe ser rastreado hasta la finalización.
Preguntas frecuentes
¿El plugin GravityBoard – Visual Workflow Management es GPL?
Sí. GravityBoard – Visual Workflow Management se distribuye bajo la licencia GPL (GNU General Public License). Puedes usarlo, modificarlo y redistribuirlo legalmente en todos los sitios que quieras.
¿Puedo usar el plugin GravityBoard – Visual Workflow Management en más de un sitio?
Sí. Puedes instalar GravityBoard – Visual Workflow Management en todos los sitios que quieras. Solo las actualizaciones automáticas con Ultrapack Auto Updater tienen límite: de 3 a 80 sitios, según el plan.
¿Cuánto cuesta el plugin GravityBoard – Visual Workflow Management en Ultrapack?
GravityBoard – Visual Workflow Management cuesta US$ 2,99 en la compra individual, y también está incluido en los planes de suscripción desde US$12/mes (VIP I).
¿El plugin GravityBoard – Visual Workflow Management incluye actualizaciones?
Sí. La versión actual de GravityBoard – Visual Workflow Management es la 1.5.0, publicada en Ultrapack el 26/09/2026. Los suscriptores actualizan directamente desde el panel de WordPress con UAU (Ultrapack Auto Updater).
¿Es seguro descargar e instalar el plugin GravityBoard – Visual Workflow Management en mi WordPress?
Sí. Cada versión de GravityBoard – Visual Workflow Management pasa por un análisis de malware (ClamAV y reglas YARA, en UltraHub) antes de publicarse.
¿Cuáles son los requisitos del plugin GravityBoard – Visual Workflow Management?
Requiere WordPress 6.2 o superior y PHP 7.4 o superior. Probado hasta WordPress 7.1.
Qué cambió en esta versión
Versión 1.5.0
- This update makes boards easier to use with a keyboard and screen reader, keeps card saves from changing unmodified fields, and fixes issues with attachments, mention emails and large boards. It also improves security.
- 🔒 Security
- Card notes no longer show images loaded from other sites. Such an image could report the IP address and browser of everyone who read the note to whoever added it.
- ✨ Improved
- Large boards render faster: cards that are scrolled out of view in a lane are drawn when they come into view.
- A board holding more cards than it can show now says how many of them it is showing, and sets that number by the server's available memory.
- A board whose lane field has no choices now guides users how to fix instead of showing an empty space.
- Non-editable fields are shown read-only in the card.
- Conditional logic in the board settings works better with a keyboard and screen reader.
- Saving a card changed fields nobody edited
- A title or description containing characters such as `&` or `'` was rewritten
- Assignees were cleared on boards with assignees turned off
- A field holding `0` was shown as blank and saved blank
- Editing a Label mapped to the same field as the lanes moved the card without the board's lane-change notifications.
- Saving only a card's assignees failed on PHP 8 and left an "unsaved changes" warning. On PHP 7 it did not send "Card Edited" notifications.
- The card editor
- An optional drop down could not be set back to empty
- A radio field showed no choice selected when its stored value was a number
- The due date could not be set with the keyboard, and it was shown in month/day order even on sites that use day/month
- Saving a note without changing its text showed an error
- A file dropped on an existing card was uploaded only with the separate Upload Files button.
- Attachments
- The user who uploaded attachemnts was shown as "User #" and a number instead of by name
- Uploading a file larger than the server allows showed "No file uploaded." or another unclear message. Such a file is now refused as soon as it is picked, with the maximum upload size
- Deleting an attachment required "Who Can Add Attachments", and without it the attachment stayed listed after its file was deleted
- Deleting an attachment now also requires permission to view attachments, and a refused delete says which permission is missing.
- Mention emails
- Turning off "Enable Mention Notifications" did not stop them
- Boards created by an import or another plugin did not send them
- A note mentioning several people sent each of them the email written for the first person, with that person's links. Each person now gets their own.
- Boards created by an import or MCP ignored the feed defaults until manually updated: nobody could be assigned, @mentions listed nobody, and only administrators had access.
- Assignee merge tags such as `{gravityboard_assignees:names}` showed names containing characters such as `&` incorrectly.
- Keyboard and screen reader use
- Shortcuts such as "?" and "/" did not work until the board had been clicked
- Arrow keys and J/K did not move between cards
- The card menu ignored the arrow keys, Home and End, and closing it with Escape lost your place
- "/" left focus on the filter panel's Close button, and F did not move focus into the fullscreen board
- Enter or Space on a vote button opened the card instead of voting
- Tags could not be added or removed with the keyboard
- Space did not start renaming a lane
Versión 1.4.5
- This update strengthens how board permissions are enforced, improves data handling when creating and updating cards, and fixes notification handling.
- 🔒 Security
- Improved how permissions are enforced when a card is viewed or changed, and when entry notes and attachments are turned off. All users are advised to update.
- ✨ Improved
- Checkbox and multiselect fields on a card are now edited with multi-value controls. They previously rendered as a single-choice control.
- Multiple bugs associated with data loss when editing and creating cards.
- Checklist editing not working for users who had the capability, based on board configuration.
- Issues around due dates
- A card due today showing as "Overdue" too early
- "Due in the next day" matching only cards due today, leaving out tomorrow's
- "Due in the next week" and "Due in the next month" now better cover the periods described.
- Assignee notification issues
- Notifications set to "Assignee(s) Added", "Assignee(s) Removed" and "Assignee(s) Updated" never sending when a card's assignees changed
- `{gravityboard_assignee_email}` and `{gravityboard_assignee:display_name}` merge tags arriving as literal text.
- Notifications continuing to send after a board's "Trigger Form Notifications" setting was turned off.
- Errors uploading files while creating a new card will keep the form open, making it possible to try again.
- A required checkbox or multiselect field with nothing selected passed validation.
- Pressing Escape while editing a field on a card closed the whole card instead of the field, and in Safari the unsaved-changes prompt could flash and disappear without being answered. Escape now leaves the field and puts the cursor back on it.
- Embedding more than one board on a page would not show anything for the second board. Administrators are now shown a message that only one board can be rendered per page.
- A board whose form has been deleted didn't show a notice.
Versión 1.4.4
- This update brings the GravityBoard block up to date with the current WordPress editor, and restores the Active toggle on the All Boards screen.
- ✨ Improved
- The GravityBoard block now previews inside the WordPress editor's iframed canvas, and the editor no longer logs a deprecation warning for it. Pages saved with earlier GravityBoard versions keep working unchanged.
- The Active/Inactive toggle on the All Boards screen displayed as a plain, unstyled button.
Versión 1.4.3
- This update fixes boards failing to load on sites that optimize JavaScript, card edits being reported as saved when validation failed, and several display and messaging issues.
- Boards failing to load on sites that minify JavaScript through a caching or optimization plugin — the board's script and stylesheet now ship as `.min` files, which those plugins pass through instead of re-minifying and corrupting.
- Editing a card reporting success when a field failed validation, leaving the entry unchanged — the card now marks the fields that need attention.
- Validation messages showing `%d` in place of the number of fields that need attention when a single field fails.
- Cards showing a choice's stored value instead of its label, so a drop-down, radio button, or checkbox field with separate values now displays "GravityMath" rather than "gravitymath".
- The icon on the board's loading screen appearing to the left of the text instead of centered above it on themes that render SVGs as blocks.
- A "translation loading was triggered too early" notice on WordPress 6.7 and newer, caused by the voting fields loading their translations during plugin bootstrap.
- 💻 Developer Updates
- `PATCH gravityboard/v1/boards/{feed_id}/cards/{entry_id}` now responds with a `400` and a `validation_failed` error when a mapped field fails validation, instead of a `200` with a success message.
- `Checklist::validate` now returns a `WP_Error` when the checklist holds an item that is not a `ChecklistItem`, instead of raising an argument-count error on PHP 8.
Versión 1.4.2
- This release fixes an issue where deleting attachments from a card could fail with an invalid file path error on sites with custom upload directories, symlinks, or multisite configurations.
- Card attachments cannot be deleted when the site's upload directory uses a custom path, lives under a symlink, runs on multisite, or surfaces paths with mixed `/` and `\` separators.
Notas de versión publicadas por el desarrollador.
Cómo instalar
Actualización automática: este ítem se actualiza con el Ultrapack Auto Updater. Con él instalado, la versión nueva aparece en tu panel como cualquier otra actualización de WordPress (cómo configurarlo).
- Descarga el archivo
gravityboard.zip. - En el panel de WordPress, ve a Plugins > Añadir nuevo > Subir plugin.
- Selecciona el archivo
gravityboard.zipy haz clic en Instalar ahora. - Haz clic en Activar.
Requisitos: Requiere WordPress 6.2 o superior y PHP 7.4 o superior. Probado hasta WordPress 7.1.
¿Te trabaste en algún paso? Abre un ticket diciendo en cuál te detuviste.

UAU Ready