Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Purely for concept work on PDF functionality
HtmlToPdf
step to automations${appId}/attachments/${processedFileName}
. This location is not set in stone and is simply convenient for now.Output Directory
- Location on the file system to initially render the PDF.Filename (No Extension)
- Filename to be used by the documentHTML Template
- String HTML template that can also utilise bindings. You can add in custom styles and this version currently supports linking to external media.filePath
- the file id of the pdf in the store.storeSync
- a fully built attachment record ready to be used.Update Row - Sync attachment
Update Row
automation step to allow the updating of attachments (not currently supported).storeSync
response object from theHtmlToPdf
step can be passed toUpdate Row
as long as you structure it as an array e.g[ {{step.4.respose.storeSync }} ]
This may not deploy correctly in the feature branch. A sample app will be added to verify.
Feature branch env
Feature Branch Link