Feature ETP-3486: Add color support documentation#607
Conversation
There was a problem hiding this comment.
Pull request overview
Adds end-user documentation for configuring the Workspace UI color badge system and exposes it in the MkDocs navigation (including Spanish nav label translation).
Changes:
- Added a new “How to Configure Color System Support” guide (EN + ES).
- Updated MkDocs navigation to include the new guide under New UI.
- Extended Spanish nav translations to include the new page title.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 9 comments.
| File | Description |
|---|---|
| mkdocs.yml | Adds the new “How to Configure Color System Support” page to nav and ES nav translations. |
| docs/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md | New English how-to guide describing how the color system is detected and rendered, plus a step-by-step setup example. |
| docs/es/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md | Spanish version of the same how-to guide. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
docs/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md
Outdated
Show resolved
Hide resolved
docs/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md
Outdated
Show resolved
Hide resolved
| ### 2. Apply DB changes and show the column in the window | ||
|
|
||
| After defining the column in the data dictionary, you must materialize it in your database: | ||
| 1. Apply the changes compiling the system via console (e.g., `gradlew smartbuild` or rebuilding the database appropriately). |
There was a problem hiding this comment.
The build command is written as gradlew smartbuild, but the rest of the docs commonly use the Gradle wrapper with ./gradlew smartbuild (or gradlew.bat on Windows). Consider updating this command to match the documented convention and avoid confusion for users running on Unix-like shells.
| 1. Apply the changes compiling the system via console (e.g., `gradlew smartbuild` or rebuilding the database appropriately). | |
| 1. Apply the changes compiling the system via console (e.g., `./gradlew smartbuild` or rebuilding the database appropriately). |
docs/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md
Outdated
Show resolved
Hide resolved
docs/es/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md
Outdated
Show resolved
Hide resolved
docs/es/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md
Outdated
Show resolved
Hide resolved
docs/es/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md
Outdated
Show resolved
Hide resolved
docs/es/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md
Outdated
Show resolved
Hide resolved
docs/es/user-guide/new-ui/how-to-guides/how-to-configure-color-system.md
Outdated
Show resolved
Hide resolved
- Move how-to-configure-color-system.md from user-guide/new-ui to developer-guide/etendo-classic/how-to-guides - Fix style: remove informal tone, fix admonitions, add license footer - Add status: new to frontmatter - Update mkdocs.yml nav in both EN and ES blocks
isaiasb-etendo
left a comment
There was a problem hiding this comment.
Lo moví a un how-to como developer, ya que nada de esto es de usuario.
Falta agregar capturas de pantalla por que esta todo en el aire.
Algunos comentarios que me sugirio claudio y creo que merecen la pena mejorar:
Step 1 — Falta la tabla destino: dice "create a new column... using the module prefix" pero no aclara que esa columna se crea en la tabla master (M_Product_Category), no en la tabla que la referencia. Para una IA esto es crítico.
Step 2 — "add or reload the record in the Field tab" es vago: ¿se crea el field manualmente? No queda claro si se refiere a sincronizar desde la Application Dictionary o a crearlo a mano.
"Verify the Configuration" — no se indica el resultado esperado: el paso 5 termina diciendo "locate the column" pero no dice qué debe verse exactamente (el badge de color). Falta el outcome explícito.
Scope — los ejemplos parecen inventados: Priority_ID y C_Currency_ID probablemente no existen con color configurado por defecto. Puede confundir. hay alguna implementación real en core?
|
Warning Git Police 👮One or more commit messages do not meet the required standards. Please correct them.
|
|
Warning Git Police 👮One or more commit messages do not meet the required standards. Please correct them.
|
|
Warning Git Police 👮One or more commit messages do not meet the required standards. Please correct them.
|
|
Warning Git Police 👮One or more commit messages do not meet the required standards. Please correct them.
|
|
Warning Git Police 👮One or more commit messages do not meet the required standards. Please correct them.
|
|
Warning Git Police 👮One or more commit messages do not meet the required standards. Please correct them.
|
No description provided.