Home > Forum > General > Process documentation

Process documentation
0

Is it possible to generate process documentation without using Designer Studio?

I have 200 processes and need to generate documentation for each one. Generating them individually is too time-consuming.

Can this be done using an API/script?

MVP

Not at the moment, but with Designer Studio Web Edition coming in Version 2027, there should be a REST API endpoint to generate the documentation.

In the meantime, I'm trying a different approach: I used Claude to build a skill that analyzes the .bpe files and generates PowerShell scripts.
These scripts produce markdown files structured by application and process, and we can integrate them into our build pipeline to publish the markdown to GitHub Pages or other markdown repositories.
The first version was already quite impressive, and we're now tailoring the output to our needs.

In reply to: Markus Jenni

Not at the moment, but with Designer Studio Web Edition coming in Version 2027, there should be a REST API endpoint to generate the documentation.

In the meantime, I'm trying a different approach: I used Claude to build a skill that analyzes the .bpe files and generates PowerShell scripts.
These scripts produce markdown files structured by application and process, and we can integrate them into our build pipeline to publish the markdown to GitHub Pages or other markdown repositories.
The first version was already quite impressive, and we're now tailoring the output to our needs.

Hi,

Documents generation using a kind.of a batch job was also my idea since some time and I am happy to hear the good news from WEBCON experts that an API will be available for that. However, I would see some extension to the documentation generation to make Markdown format available apart from DOCX, XLSX. We try to use WEBCON process documentation as one of data sources for Gemini Notebooks RAG tool to query it using LLM. This works fine, however DOCX documents are heavy what makes Gemini replies take longer. It will work much faster if plain-text markdown / mermaid format is available. I can admit that it is possible to achieve "quasi" vibe code results or very detailed analysis for change requests using this simple approach.

Of course, MCP could help here, but we would need to develop a tool to consume it.