Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Introduction (File Writer) • Introduction (Migration Assistant)
bw:file_writer_tool

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
bw:file_writer_tool [2020/07/28 15:33]
external edit 		bw:file_writer_tool [2022/08/02 15:29] (current)
akoehler
Line 20: Line 20:
 The **Datasource** output option is used to write the input data set as it is received and create the file with data records only. Use the **Custom String** output method if header and footer sections, or custom column headings, are needed as well. No Bizweaver looping is required. The **Datasource** output option is used to write the input data set as it is received and create the file with data records only. Use the **Custom String** output method if header and footer sections, or custom column headings, are needed as well. No Bizweaver looping is required.
  
-{{:bw:fwimage1.png?384x408}}+{{  :bw:fwimage1.png?384x408  }}
  
   - Enter the **Filename** (target folder and file name) for the output file.   - Enter the **Filename** (target folder and file name) for the output file.
Line 50: Line 50:
 </WRAP> </WRAP>
  
-{{:bw:fwimage2.png?384x408}}+{{  :bw:fwimage2.png?384x408  }}
  
   - Enter the **Filename** (target folder and file name) for the output file.   - Enter the **Filename** (target folder and file name) for the output file.
Line 96: Line 96:
 The image below illustrates the record structure. The column headings in yellow are used to obtain the needed data. The image below illustrates the record structure. The column headings in yellow are used to obtain the needed data.
  
-{{:bw:fwimage3.png?576x43}}+{{  :bw:fwimage3.png?576x43  }}
  
   - **ID** is the unique record ID in the table.   - **ID** is the unique record ID in the table.
Line 122: Line 122:
   * The FileContent variable indicates what data is to be written out   * The FileContent variable indicates what data is to be written out
  
-{{:bw:fwimage4.png?384x305}}+{{  :bw:fwimage4.png?384x305  }}
  
 This process occurs for each record passed into the loop. The recreated files are created in the designated folder using their original name. This process occurs for each record passed into the loop. The recreated files are created in the designated folder using their original name.
Line 168: Line 168:
 The image below illustrates the record structure of the “SignatureCapture” table. The column headings in yellow are used to obtain the needed data. The image below illustrates the record structure of the “SignatureCapture” table. The column headings in yellow are used to obtain the needed data.
  
-{{:bw:fwimage5.png}}+{{  :bw:fwimage5.png  }}
  
 The conversion to disk file is then the same as described in Uploaded Versago Data section above. The conversion to disk file is then the same as described in Uploaded Versago Data section above.
Line 174: Line 174:
 ====Option 2==== ====Option 2====
 The signature image can also be converted as needed in a Bizweaver workflow.  In this case a SQLCommand step is used to parse out the signature data using <code sql>substring(Signature,23,999999)</code> on the database column that holds the signature data.  This step feeds into a FileWriter step using the Binary Output option to convert the base64 data back to an image file, which is saved to disk for subsequent use. The signature image can also be converted as needed in a Bizweaver workflow.  In this case a SQLCommand step is used to parse out the signature data using <code sql>substring(Signature,23,999999)</code> on the database column that holds the signature data.  This step feeds into a FileWriter step using the Binary Output option to convert the base64 data back to an image file, which is saved to disk for subsequent use.
 +
 +====File Writer Variables====
 +^Name         ^ Description         
 +| AppendData         | True or False if the append data radio button was selected        |
 +| BinaryData|      The value that was entered in the binary data section if any              |
 +|ColumnID| If create a file for records - grouped by is selected it will display the current record that is being grouped|
 +| CreateFileForAllRecords          | True or False if the create file for all records radio button was selected|
 +| CreateFileForGroupedRecords |True or False if the create a file for grouped records radio button was selected|
 +| CustomSeparator         |Will display the customer separator if any is selected|
 +| DataSourceWorkFlowID          |The source of the data that is being used in the file writer tool|
 +| EnableBinaryData |True or False if the binary data radio button is selected|
 +| EnableColumnHeaders          |True or False if the enable column headers radio button is selected|
 +|EnableDataSource          |True or False if there is a data source used|
 +| EnableStringBuilder |True or False if custom string radio button is selected|
 +| FileName          |The file location where the file that is being created is being saved with extension|
 +| FileType          |The file type that is selected ex. JSON,XML,Comma Seperated|
 +|FormattedStringBody |The value that was entered in the body section of the custom string if any|
 +| FormattedStringFooter         |The value that was entered in the footer section of the custom string if any|
 +| FormattedStringHeader         |The value that was entered in the header section of the custom string if any|
 +| StepMessage|During a failure the reason for failure will be populated here |
 +| StepStatus        |True or False|
 +
bw/file_writer_tool.1595964815.txt.gz · Last modified: 2020/07/28 15:33 by

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki