You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To support the generation of one PDF per sub form, we need a mechanism for naming PDFs to avoid name collision and to have a semantic domain-related name to easily be distinguished from others.
We should expose the naming rules to the Service Owner app developers. Could be done with expressions.
With PDF as its own taskExtension taskType, we could include a pdfConfig section which could include PdfName, something like this:
The file name is determined by app-lib-dotnet, based on the appName in text resources currently it seems. So maybe this issue belongs there? Unless there is a way for app-frontend to expose this in the PDF file? Though, I suspect there is not, as we currently cannot even set the document title #196
HauklandJ
changed the title
Need ability to specify name for generated PDFs (with expressions)
Need ability to specify name for generated PDFs
Jun 21, 2024
Part of the Underskjema Epic
To support the generation of one PDF per sub form, we need a mechanism for naming PDFs to avoid name collision and to have a semantic domain-related name to easily be distinguished from others.
We should expose the naming rules to the Service Owner app developers. Could be done with expressions.
With PDF as its own taskExtension taskType, we could include a pdfConfig section which could include PdfName, something like this:
TasksToInclude: hvis det er server task så vil det ikke være noe layout set, så frontend vil ikke rendre noe.
The text was updated successfully, but these errors were encountered: