Function Component

[ColtonMcInroy]

Function Component

[petersirka]

@ColtonMcInroy - I do not have an email for you, but try our brand-new product UI Studio. This demo is primarily intended for the Flow as a UI Builder: DEMO (don't change the data there). Let me know your feelings.

Tomorrow I will look into this issue.

[petersirka]

Hi @ColtonMcInroy, I have fixed the Teleport component. It contained a wrong implementation of the Web Component declaration.

I found that it destroys the incoming message

This is not true. The Teleport component does not destroy messages when input/output exists, otherwise it must destroy them to prevent zombie messages.

[ColtonMcInroy]

This is not true. The Teleport component does not destroy messages when input/output exists, otherwise it must destroy them to prevent zombie messages.

@petersirka You are correct, sorry, mixed up that with FlowStream Input/Output/Subscribe/Publish components.

The other feature this implements is very handy though.

The message data at the end of the Output Mode handler is returned to the Input Mode component as the payload of the message it outputs. This way the data is returned to the correct location in a flow. If you used teleport for instance to process logic in another location, you would have to use teleport to send it back. If that logic is to be applied to multiple locations, then this could become problematic. This component takes care of it.

Here is a copy of the html file version of this component
Function.html.tar.gz

[petersirka]

@ColtonMcInroy improve your code in the Function component:

<ui-component name="watcher" config="CONFIG">
    <script type="text/js">

        // IMPORTANT:
        if (!value)
            return;

        component.watcherbackup && component.unwatch(component.watcherbackup);
        var defcolor = '#888';
        var deftext = 'Not configured';