jumpmind / metl Goto Github PK

The runtime framework should calculate the message statistics so the component developer is not writing boiler plate code constantly, and script code would be simplified. If left to the developer, components may not report statistics, which could mislead troubleshooting issues in flows.

A model can be copied but it's confusing what happens since there is no paste.

Today it creates a second model at the end of the list of models with copy appended to the end of the name.

@erilong suggested calling it "clone" to make the functionality more clear.

Add an examples project that provides flow examples and automatically gets installed

Show all buttons on the button bar for executions, which are Cancel and Remove. If the button does not apply in the current context, then it should be disabled.

The deduper should function for text based messages as well as model based messages. Same functionality regardless of input message type.

Provide an option that automatically creates (and keeps up to date) a database model versus having to maintain it manually.

Get rid of @SettingsDefintion. Resources are the last remaining subsystem that uses them.

Support different join types in the joiner including inner, left outer, right outer and full outer.

Add a component that would allow you to wait for the receipt of 1 or more messages from different components before triggering the next component.

Remove transform functionality from the formatter screens. Transform should be done as a separate step with the transform component.

Provide transactional capabilities across components

/symmetric-is/api/agents/{agent}/deployments/My%20Deployment/invoke

Allow a component to be documented as well as allowing flows to be documented with notes.

The examples project could make good use of this. Allow for token replacement of parameters and possibly entity values.

Show shared components and disabled components with some type of visual indicator on the design flow screen.

Create a component similar to IS1 that collects messages in a logical database and allows messages to be queries from that database with hints.

This would provide an easy way to change record results based off of other records in the logical db.

Example:
Fee Plan records should return Fixed if there is only one stepping schedule on the logical but Stepping if there is more than one record.

Provide lineage capabilities with reporting or other screen functionality.

Disabling a single component in a flow prevents all the connected components from running. It should only prevent that component from initializing and handling messages.

The model edit screen can import from the database, but it is reading types on SQL-Server like "datetime" and importing them as "other".

Sort flows by alphabetical order on design screen