Skip to content

Add exporting-workflow-data page#73

Open
jonochang wants to merge 2 commits intomainfrom
jc/configurable-zip-internal-file-paths
Open

Add exporting-workflow-data page#73
jonochang wants to merge 2 commits intomainfrom
jc/configurable-zip-internal-file-paths

Conversation

@jonochang
Copy link
Member

@jonochang jonochang self-assigned this Jan 5, 2026
@netlify
Copy link

netlify bot commented Jan 5, 2026

Deploy Preview for highlighter-docs ready!

Name Link
🔨 Latest commit 9f2ca84
🔍 Latest deploy log https://app.netlify.com/projects/highlighter-docs/deploys/695c85d3e5d13000083f101f
😎 Deploy Preview https://deploy-preview-73--highlighter-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 91 (no change from production)
Accessibility: 97 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@jonochang jonochang added the documentation Improvements or additions to documentation label Jan 5, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jonochang, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new, dedicated documentation page that provides users with detailed instructions on how to export workflow-related data, such as CSV results and case files. It aims to centralize and clarify the data export process, making it easier for users to retrieve necessary information from their workflows. The new page is seamlessly integrated into the existing user manual structure through updated navigation links.

Highlights

  • New Documentation Page: A comprehensive new documentation page, 'Exporting Workflow Data', has been added to the user manual. This page details the process of exporting various types of workflow data.
  • Workflow Data Export Instructions: The new page provides step-by-step instructions for exporting CSV results, case files (as ZIP archives with customizable paths), and annotated case files, including available Liquid-style variables for path customization.
  • Documentation Integration: Existing user manual pages, specifically the main 'managing-workflows' index and 'creating-workflow-orders', have been updated to include links to the new 'Exporting Workflow Data' page, improving discoverability.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new documentation page, exporting-workflow-data.md, which details how to export CSV results and case files from a workflow. It also adds links to this new page from the 'Managing Workflows' index and the 'Creating Workflow Orders' page. The new documentation is well-structured and provides useful details on export options, including how to customize ZIP file paths with templates. I have a couple of suggestions to improve clarity for the end-user, particularly around export requirements and template variable definitions.

- `WORKFLOW_ORDER_NAME`: Workflow order name (or workflow name if no order)
- `CASE_ID`: Case database ID
- `CASE_SHORT_ID`: Case short ID
- `CASE_EXTERNAL_ID`: External ID (entity, case, or short ID)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The description for CASE_EXTERNAL_ID is ambiguous as it lists multiple possible IDs ('entity, case, or short ID') without specifying the order of precedence. To help users predict the output of the template, please clarify the fallback logic. For example: '...uses the entity ID if available, otherwise the case ID, and finally the short ID'.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my similar comment in highlighter PR about this text in brackets

@jonochang jonochang requested a review from simon-dev-ml January 5, 2026 10:20
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
draft = false
+++

Export workflow data, including CSV results and case files: [Exporting Workflow Data](/docs/user-manual/managing-workflows/exporting-workflow-data/).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if this is desired results, see this page https://deploy-preview-73--highlighter-docs.netlify.app/docs/user-manual/managing-workflows/ has just this text at the top. All other content is just links

@@ -0,0 +1,73 @@
+++
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is already a page for exporting data from workflows: https://deploy-preview-73--highlighter-docs.netlify.app/docs/user-manual/managing-workflows/exporting-data/, we should integrate this content into it

- `WORKFLOW_ORDER_NAME`: Workflow order name (or workflow name if no order)
- `CASE_ID`: Case database ID
- `CASE_SHORT_ID`: Case short ID
- `CASE_EXTERNAL_ID`: External ID (entity, case, or short ID)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my similar comment in highlighter PR about this text in brackets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants