The 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.
Introduce a delay before passing the message to the next step.
Delay behavior
, as two options:
Delay Each
- every incoming message will to delay independent each other, for example: we have 100 messages at the same moment with delay 1 sec, after 1 sec all messages will get to the next step.Delay All
- all incoming message will to delay one by one, new message will go farther only after previous finish, for example: we have 100 messages at the same moment with delay 1 sec, each second a message will go to the next step (from oldest).Delay Time (in seconds)
- Amount of time this component should wait/delay (in seconds) before emiting the message. Negative number will be converted to positive, strings converted to number, if converted failed will set to zero.Data to transfer
- Use this field to transfer data in to another stepsLog the message (and potentially passthrough) into the provided logger at the selected level.
Log Level
- dropdown, the log level at which to store the message, default: Info. To see message in logs, level in config must be higher or equal component Log Level. When you do “Retrieve new sample” log Level set to platform default value - Info.Log All Passthrough
- dropdown, Log only the message body or log all passthrough data, default: message bodyThere are no Input Metadata in this action.
Match the input message metadata
Utility to create a JSON patch
There are no Config Fields in this action.
Origin Object
- Object that we have nowTarget Object
- Object that should be after patch was appliedJSON Patch
- Series of changes to be applied to go from Origin Object to Target ObjectUtility to apply a JSON patch
There are no Config Fields in this action.
Origin Object
- Object that we have nowJSON Patch
- Series of changes to be applied to go from Origin Object to Target ObjectTarget Object
- Object that should be after patch was appliedUseful to diagnose connectivity issues between an eio pod and some endpoint
There is no Config Fields
URL
- Full url to the resource. E.g https://github.com
pingResult
- Result object for ping
nsLookupResult
- Result object for NsLookup
sslCertCheckResult
- Result object for SSL certificate check
Delay All
option from Delay
don’t correctly support Parallel Processing
option in component more then 1Delay Each
option from Delay
in ordinary flow type can handle delay up to 30 sec, if you need more, use real-time typeData to transfer
field for correct transfer data after Delay
component.Click here to learn more about the elastic.io iPaaS