Hans Karlsen (talk | contribs) (Created page with "SysDocBatch is a model pattern recognized by TurnkeyServer and MDrivenServer. The problem it solves are document collections. Normally when you generate a report it will directly download as a odt or ods format file. If a SysSingleton.oclSingleton.CurrentSysDocBatch is found we now instead add a SysDoc to the SysSingleton.oclSingleton.CurrentSysDocBatch.SysDocs association. And on the first added SysDoc we will show the SysDocBatchView viewmodel (rooted in SysDocBat...") |
No edit summary |
||
| (16 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
SysDocBatch is a model pattern recognized by TurnkeyServer and MDrivenServer. | <message>Describe what a SysDoc is and what it does. Explain SysDocBatch further, giving details on how to do the document conversion in steps. </message> | ||
SysDocBatch is a model pattern recognized by TurnkeyServer and WPF-Wecpof (MDrivenServer can zip and convert). | |||
We suggest you keep the SysDocBatch and SysDoc classes transient. | |||
This Pattern is mergable from the GitHub repository: [https://github.com/supportMDriven/MDrivenComponents supportMDriven/MDrivenComponents (github.com)] | |||
The problem it solves is document collections, conversions, zipping and controlled download of reports and other documents. | |||
Normally when you generate a report, it will directly download as an odt or ods formated file. | |||
If a SysSingleton.oclSingleton.CurrentSysDocBatch is found, we now instead add a SysDoc to the SysSingleton.oclSingleton.CurrentSysDocBatch.SysDocs association. | |||
And on the first added SysDoc, we will show the SysDocBatchView ViewModel (rooted in SysDocBatch) as a Modal window. | |||
You can also make use of the new selfVM operators for Zipping and Downloading: | This will enable you to collect a list of many possible documents that you need to print (if your action generates multiple reports, multiple SysDoc objects are created). | ||
The SysDocBatchView ViewModel is a good place to possibly offer to convert documents to pdf or docx (read more on [[Documentation:Use LibreOffice for PDF conversion|Using LibreOffice for this task]]). | |||
You can also make use of the new [[selfVM]] operators for Zipping and Downloading: | |||
vData:=selfVM.SysDocBatchZip( self ) | vData:=selfVM.SysDocBatchZip( self ) | ||
selfVM.Download( 'Somefile.zip' | selfVM.Download( 'Somefile.zip' , vData ) | ||
[[File: | [[File:2024-06-05 11h06 50.png|none|thumb|712x712px]] | ||
Latest revision as of 06:14, 26 June 2024
SysDocBatch is a model pattern recognized by TurnkeyServer and WPF-Wecpof (MDrivenServer can zip and convert).
We suggest you keep the SysDocBatch and SysDoc classes transient.
This Pattern is mergable from the GitHub repository: supportMDriven/MDrivenComponents (github.com)
The problem it solves is document collections, conversions, zipping and controlled download of reports and other documents.
Normally when you generate a report, it will directly download as an odt or ods formated file.
If a SysSingleton.oclSingleton.CurrentSysDocBatch is found, we now instead add a SysDoc to the SysSingleton.oclSingleton.CurrentSysDocBatch.SysDocs association.
And on the first added SysDoc, we will show the SysDocBatchView ViewModel (rooted in SysDocBatch) as a Modal window.
This will enable you to collect a list of many possible documents that you need to print (if your action generates multiple reports, multiple SysDoc objects are created).
The SysDocBatchView ViewModel is a good place to possibly offer to convert documents to pdf or docx (read more on Using LibreOffice for this task).
You can also make use of the new selfVM operators for Zipping and Downloading:
vData:=selfVM.SysDocBatchZip( self ) selfVM.Download( 'Somefile.zip' , vData )
