Current release

Highlighted features of the current paxpar version 4.2.37:

template composition

To craft a document we generate PDF from templates.

The template use to be a LibreOffice writer document (.odt extension).

We introduce template composition by adding new template engine and by allowing multiple templates.

As an example you can provide, as usual, a simple template.odt.

Or you can

• tempalte_010_front.svg
• tempalte_020_contract.docx
• tempalte_030_technical.typst
• tempalte_040_details.md
• tempalte_050_extra.docx

portal signature

Each PDF produced is now signed. The signature if different for each portal.

The signature reason is customizable and may contain the current user email.

So it may be use as a cheap way to truthfully get the user who create the document.

Legally it is not as solid as a true signature from the user.

collaborative forge

multiple authors can work edit a checklist collaboratively

web dev environment based on Jupyter Notebook

edit checklist/craft and see them directly in your portal

synchronized to live pp-ref

From a synchronized pp-ref to a live

S3 backend

scrap tool

Generate complex PDF from a single YAML file.

roadmap

Highlighted features of the comming versions:

deleguation

see ticket

deleguer la creation d'un document ex d'un RSI compose de 100 documents, on peut deleguer la creation du document racine lui compose d'autres documents a deleguer et ainsi de suite

In a craft form, where you drop attached documents, you will be able to deleguate a document that will be automatically attached when finalize.

signature providers integration

paxpar supports any signature provider that respect the PAdES standard.

Currently the generated PDF can be signed, externally, by any of those provider.

We plan to integrate the signature process of someof those providers.

see ticket

multi-psc

y-compris signatures legeres (portail)

• Chave Move Digital
• Chambersign
• Lex Community
• any provider that use standard PAdES signature

BPMN representation of the workflow

monorepo

all pp project in a single repo :

• pp-api
• pp-widgets
• pp-front
• pp-front0
• pp-schemas
• pp-test

auto deploy of any branch

faster release

AI integration

See ticket

This is a rolling feature that span over a longer period. We currently use AI for deloppement and authoring only. The paxpar released version does not contain any AI feature.

Here is a sample conversation with the check assistant:

>>> Please tell me if I can trust the document `DSI6746.pdf` ?

The document has been submitted to the energie.qdoc portal.
The checklist `Controle DSI` has been applied and considers the document OK.
Visit the energie.qdoc.pro portal for details.
You can also ask me about the document.

>>> What is the document about ?

The document `RFI6746.pdf` is a *Rapport final d'Intervention*.
It contains 83 attached files for a total of 836 pages.

>>> Who is Paul Legrand and what is his role ?
Paul Legrand is an employee of the company GenElec (see document `OrgaGenElec.pdf`).
He worked on the steps 5, 6, 7 and 11 (see document `DS165.pdf`).

Here is a sample conversation with the craft author assistant:

>>> Please

Here is a sample conversation with the document assistant:

>>> Please

ZKML

See ticket

ZK : Zero Knowledge -> Prouver qu'on dispose d'une info sans la divulguer

TODO

XSD ?

• link to issues
• link to BIM issue
• link to CSTB issue
• link to ZKML issue
• link to Coffee Market issue