512
MB. 256 by defaultThe technical notes page gives some technical details about Utility component like changelog.
This component has no trigger functions. This means it will not be accessible to select as a first component during the integration flow design.
Creates attachment from input value
. Output is attachmentId
and attachmentUrl
in message.body
and attachment object in message.attachments
:
encodeToBase64
- if checked encode an input value
using Base64 encode. Than saves encoded value into attachment.Creates string from attachment with provided input attachmentId
which must be either:
decodeFromBase64
- if checked decode attachment content using Base64 decode before output. If content of attachment is malformed or not Base64 encoded string, result will be malformed.Decodes input value
using Base64 decoding to regular string. If malformed input provided or not Base64 encoded string, result will be malformed:
Encodes input value
using Base64 encoding:
Given two timezones and an array of timestamps (without any timezone info) converts the timestamps to the output timezone. The output is a dictionary of oldTimezone -> newTimezone values:
E.g. If converting from UTC to German time then
{timesToConvert: ['2020-01-01T12:00:00', '2020-07-01T12:00:00']}
produces
{
'2020-01-01T12:00:00': '2020-01-01T13:00:00+01:00',
'2020-07-01T12:00:00': '2020-07-01T14:00:00+02:00',
}
This component takes into account that Germany is ahead of UTC 1 hour in Winter and 2 hours in the Summer. The possible format of incoming strings is deliberately broad to account for as large a range of possible timestamps. Epoch time conversion is not supported.
Get your free 14-day elastic.io trial account to use this component.