<?xml version="1.0" encoding="utf-8"?>
<!--RSS generated by Flaimo.com RSS Builder [2026-11-15 23:44:44]-->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"><channel><docs>https://feedback.inlyrastudio.com/</docs><link>https://feedback.inlyrastudio.com/</link><description><![CDATA[Inlyra Studio Feedback - Issues]]></description><title>Inlyra Studio Feedback - Issues</title><image><title>Inlyra Studio Feedback - Issues</title><url>https://feedback.inlyrastudio.com/images/InlyraStudioFeedback_logo.png</url><link>https://feedback.inlyrastudio.com/</link><description><![CDATA[Inlyra Studio Feedback - Issues]]></description></image><language>en</language><category>All Projects</category><ttl>10</ttl><dc:language>en</dc:language><sy:updatePeriod>hourly</sy:updatePeriod><sy:updateFrequency>1</sy:updateFrequency><item><title>0000010: CSV Output Tool wrap data in quotes</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=10</link><description><![CDATA[CSV wrap fields in double quotes.  Right now the outputs are just value, value, value.&lt;br /&gt;
&lt;br /&gt;
It is useful to wrap values in quotes if the data contains commas or whatever delimiter is used.&lt;br /&gt;
&quot;city,state&quot;,&quot;value&quot;,&quot;value&quot;&lt;br /&gt;
&lt;br /&gt;
it could be:&lt;br /&gt;
&quot;some|value&quot;|&quot;value2&quot;|&quot;value3&quot;]]></description><category>Output Tools</category><pubDate>Sun, 27 Sep 2026 20:37:50 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=10</guid><comments>https://feedback.inlyrastudio.com/view.php?id=10#bugnotes</comments></item><item><title>0000046: Add Stored Procedure support to Database Input</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=46</link><description><![CDATA[Goal:&lt;br /&gt;
Allow Inlyra Studio Pro users to execute database stored procedures that return tabular results and use those results as normal workflow input.&lt;br /&gt;
&lt;br /&gt;
Phase 1 scope&lt;br /&gt;
Add a new Stored Procedure mode to Database Input alongside the existing table/view and custom query options.&lt;br /&gt;
Example:&lt;br /&gt;
Source Type&lt;br /&gt;
&lt;br /&gt;
( ) Table / View&lt;br /&gt;
( ) Custom Query&lt;br /&gt;
(•) Stored Procedure&lt;br /&gt;
&lt;br /&gt;
When Stored Procedure is selected:&lt;br /&gt;
1. Use the selected saved database connection.&lt;br /&gt;
2. Discover available stored procedures for that connection/provider.&lt;br /&gt;
3. Let the user choose a procedure from a dropdown.&lt;br /&gt;
4. Discover the procedure’s input parameters where supported.&lt;br /&gt;
5. Display the parameters in a simple grid.&lt;br /&gt;
6. Let the user enter literal/static values for each parameter.&lt;br /&gt;
7. Validate/cast those values to the parameter’s database type.&lt;br /&gt;
8. Execute the procedure.&lt;br /&gt;
9. Use the first returned tabular result set as the Database Input output.&lt;br /&gt;
Proposed UI&lt;br /&gt;
Stored Procedure&lt;br /&gt;
[ dbo.GetDailyMarks ▼ ]&lt;br /&gt;
&lt;br /&gt;
Parameters&lt;br /&gt;
&lt;br /&gt;
Parameter             Type        Value&lt;br /&gt;
@BusinessDate         Date        2026-09-27&lt;br /&gt;
@Desk                 String      ERCOT&lt;br /&gt;
@IncludeInactive      Boolean     false&lt;br /&gt;
&lt;br /&gt;
[ Discover Schema ]   [ Preview (100 rows) ]&lt;br /&gt;
&lt;br /&gt;
Phase 1 parameter behavior&lt;br /&gt;
Parameter values are configured directly in the tool and remain static until the workflow is edited.&lt;br /&gt;
Examples:&lt;br /&gt;
@BusinessDate = 2026-09-27&lt;br /&gt;
@Desk = ERCOT&lt;br /&gt;
@IncludeInactive = false&lt;br /&gt;
&lt;br /&gt;
Dynamic expressions and workflow/system variables are not part of phase 1.&lt;br /&gt;
Result-set behavior&lt;br /&gt;
For the initial implementation:&lt;br /&gt;
- support procedures that return a tabular result set&lt;br /&gt;
- use only the first result set&lt;br /&gt;
- procedures returning no tabular result should produce a clear configuration/execution message&lt;br /&gt;
- multiple result sets are out of scope initially&lt;br /&gt;
- output parameters and procedure return values are out of scope initially&lt;br /&gt;
This keeps the feature compatible with Inlyra’s existing single-table node output model.&lt;br /&gt;
Schema discovery&lt;br /&gt;
Stored procedures may require parameter values before their output schema can be determined.&lt;br /&gt;
Discover Schema / Preview should therefore execute the procedure using the configured parameter values.&lt;br /&gt;
Because stored procedures can contain side effects, the UI/help should clearly state that schema discovery and preview may execute the procedure.&lt;br /&gt;
For phase 1, documentation should recommend using Stored Procedure Input with procedures intended for data retrieval/read-only use.&lt;br /&gt;
Provider rollout&lt;br /&gt;
Recommended first provider:&lt;br /&gt;
Microsoft SQL Server&lt;br /&gt;
SQL Server has straightforward stored-procedure execution and parameter support through ADO.NET.&lt;br /&gt;
After the interaction model is proven, support can be evaluated for:&lt;br /&gt;
- PostgreSQL&lt;br /&gt;
- MySQL&lt;br /&gt;
- MariaDB&lt;br /&gt;
- Oracle&lt;br /&gt;
Provider behavior should remain isolated behind the database-provider abstraction because procedure discovery and execution differ across database systems.&lt;br /&gt;
Future phases&lt;br /&gt;
Later enhancements could add dynamic parameter values such as:&lt;br /&gt;
@BusinessDate = Sys.Today()&lt;br /&gt;
@WorkflowName = Sys.GetWorkflowName()&lt;br /&gt;
&lt;br /&gt;
and user/workflow variables such as:&lt;br /&gt;
@Region = Var.Region&lt;br /&gt;
&lt;br /&gt;
Possible future capabilities:&lt;br /&gt;
- system/runtime variable namespace&lt;br /&gt;
- workflow-defined variables&lt;br /&gt;
- Server-supplied parameters&lt;br /&gt;
- formula/expression-based parameter values&lt;br /&gt;
- output parameters&lt;br /&gt;
- multiple result sets&lt;br /&gt;
- procedure/action execution without tabular output]]></description><category>Input Tools</category><pubDate>Sun, 27 Sep 2026 20:37:32 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=46</guid><comments>https://feedback.inlyrastudio.com/view.php?id=46#bugnotes</comments></item><item><title>0000012: Function Tool: Need a DateAdd function</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=12</link><description><![CDATA[There are no DataAdd functions in the Function Tool.  No ability to add/delete days, months, years.]]></description><category>Formula / Expressions</category><pubDate>Sun, 27 Sep 2026 16:28:33 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=12</guid><comments>https://feedback.inlyrastudio.com/view.php?id=12#bugnotes</comments></item><item><title>0000045: Add ODBC support for generic database connectivity</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=45</link><description><![CDATA[Add ODBC connectivity to Inlyra Studio Pro to support databases and data sources that do not yet have a native Inlyra connector.&lt;br /&gt;
ODBC should be positioned as a broad-compatibility connector, while native database providers remain the preferred option for best performance, provider-specific features, and support.&lt;br /&gt;
Initial implementation should support both Windows DSN-based connections and DSN-less connection strings.&lt;br /&gt;
Proposed functionality:&lt;br /&gt;
- Add ODBC as a supported database connection type.&lt;br /&gt;
- Support:&lt;br /&gt;
  - Windows User DSNs&lt;br /&gt;
  - Windows System DSNs&lt;br /&gt;
  - DSN-less connection strings&lt;br /&gt;
- When DSN mode is selected:&lt;br /&gt;
  - enumerate configured ODBC DSNs on the local machine&lt;br /&gt;
  - display available DSNs in a dropdown&lt;br /&gt;
  - identify User vs System DSNs where possible&lt;br /&gt;
  - provide a Refresh option&lt;br /&gt;
- Allow Username and Password entry when credentials are not stored in the DSN.&lt;br /&gt;
- Provide a Test Connection action.&lt;br /&gt;
- Allow saved ODBC connections to be reused across workflows.&lt;br /&gt;
- Support ODBC Input and ODBC Output operations.&lt;br /&gt;
- Reuse the redesigned database connection-management UI where practical.&lt;br /&gt;
Example workflow:&lt;br /&gt;
Connect to an existing Windows ODBC DSN such as FinanceWarehouse, read a table or supported query, transform the data in Inlyra, and write the results to another supported destination.&lt;br /&gt;
Design considerations:&lt;br /&gt;
- Native connectors such as SQL Server, PostgreSQL, MySQL, and MariaDB should remain preferred when available.&lt;br /&gt;
- ODBC should be treated as a generic compatibility option and may not provide the same performance or provider-specific capabilities as native connectors.&lt;br /&gt;
- Error handling should surface driver and connection errors clearly, since ODBC behavior may vary by installed driver.&lt;br /&gt;
- Consider whether driver architecture differences such as 32-bit vs 64-bit need to be detected or documented.]]></description><category>Database Connections</category><pubDate>Sat, 26 Sep 2026 22:44:46 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=45</guid><comments>https://feedback.inlyrastudio.com/view.php?id=45#bugnotes</comments></item><item><title>0000044: Parallel workflow branch execution implemented and validated</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=44</link><description><![CDATA[Updated workflow execution so independent nodes/branches can run concurrently instead of waiting for unrelated nodes earlier in the execution plan. Each node now waits only for its actual upstream dependencies before becoming eligible to run.&lt;br /&gt;
Parallel execution is bounded to avoid overwhelming the local machine or external databases. Active node executors are limited based on processor count, with a minimum of 2 and maximum of 8 concurrent executions.&lt;br /&gt;
Dependency behavior is preserved:&lt;br /&gt;
- downstream nodes wait for all required predecessors&lt;br /&gt;
- failed branches block only their dependent nodes&lt;br /&gt;
- unrelated branches continue executing&lt;br /&gt;
- cancellation behavior remains supported&lt;br /&gt;
- execution events remain ordered&lt;br /&gt;
- node execution results and exceptions are stored using thread-safe collections&lt;br /&gt;
Regression coverage was added for:&lt;br /&gt;
- independent inputs executing simultaneously&lt;br /&gt;
- Join waiting until both input branches are complete&lt;br /&gt;
- failure isolation between independent branches&lt;br /&gt;
- dependency barriers&lt;br /&gt;
- ordered execution events&lt;br /&gt;
- thread-safe/order-independent tests]]></description><category>Performance</category><pubDate>Sat, 26 Sep 2026 22:22:22 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=44</guid><comments>https://feedback.inlyrastudio.com/view.php?id=44#bugnotes</comments></item><item><title>0000043: Redesign database connection dialog</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=43</link><description><![CDATA[Redesign it to clean up the ux.  Make labels and input text fields on the same row.  Also, move port numbers outside of the advanced options.]]></description><category>Database Connections</category><pubDate>Sat, 26 Sep 2026 16:59:29 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=43</guid><comments>https://feedback.inlyrastudio.com/view.php?id=43#bugnotes</comments></item><item><title>0000037: Expand and Standardize Date/Time Formula Functions</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=37</link><description><![CDATA[Expand Inlyra's Date/Time formula functionality and standardize function naming before the v1.0 release.&lt;br /&gt;
&lt;br /&gt;
As Inlyra is still pre-release, existing date functions should be renamed to use the preferred function naming convention rather than retaining backward-compatible aliases.&lt;br /&gt;
&lt;br /&gt;
Rename existing functions:&lt;br /&gt;
&lt;br /&gt;
DATE_PART()  → DATEPART()&lt;br /&gt;
DATE_DIFF()  → DATEDIFF()&lt;br /&gt;
DATE_TRUNC() → DATETRUNC()&lt;br /&gt;
&lt;br /&gt;
Inlyra function names should generally avoid underscores when a clear and readable name can be used.&lt;br /&gt;
&lt;br /&gt;
New Date Manipulation Functions&lt;br /&gt;
&lt;br /&gt;
DATEADD(interval, amount, date)&lt;br /&gt;
Adds or subtracts an interval from a date or datetime. Negative amounts subtract.&lt;br /&gt;
&lt;br /&gt;
Supported intervals should include:&lt;br /&gt;
&lt;br /&gt;
year&lt;br /&gt;
quarter&lt;br /&gt;
month&lt;br /&gt;
week&lt;br /&gt;
day&lt;br /&gt;
hour&lt;br /&gt;
minute&lt;br /&gt;
second&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
DATEADD('month', -1, [OrderDate])&lt;br /&gt;
DATEADD('day', 30, [OrderDate])&lt;br /&gt;
DATEADD('hour', 2, [Timestamp])&lt;br /&gt;
&lt;br /&gt;
FODATE(interval, date [, weekStart])&lt;br /&gt;
Returns the first date of the calendar period containing the supplied date.&lt;br /&gt;
&lt;br /&gt;
Examples for 8/23/2026:&lt;br /&gt;
&lt;br /&gt;
FODATE('year', [mydate])    → 1/1/2026&lt;br /&gt;
FODATE('quarter', [mydate]) → 7/1/2026&lt;br /&gt;
FODATE('month', [mydate])   → 8/1/2026&lt;br /&gt;
&lt;br /&gt;
EODATE(interval, date [, weekStart])&lt;br /&gt;
Returns the last date of the calendar period containing the supplied date.&lt;br /&gt;
&lt;br /&gt;
Examples for 8/23/2026:&lt;br /&gt;
&lt;br /&gt;
EODATE('year', [mydate])    → 12/31/2026&lt;br /&gt;
EODATE('quarter', [mydate]) → 9/30/2026&lt;br /&gt;
EODATE('month', [mydate])   → 8/31/2026&lt;br /&gt;
&lt;br /&gt;
Month-end calculations must correctly handle different month lengths and leap years.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
EODATE('month', DATE(2024,2,15)) → 2/29/2024&lt;br /&gt;
EODATE('month', DATE(2025,2,15)) → 2/28/2025&lt;br /&gt;
Week Handling&lt;br /&gt;
&lt;br /&gt;
For FODATE('week', ...) and EODATE('week', ...), support an optional third parameter specifying the first day of the week:&lt;br /&gt;
&lt;br /&gt;
1 = Monday&lt;br /&gt;
2 = Tuesday&lt;br /&gt;
3 = Wednesday&lt;br /&gt;
4 = Thursday&lt;br /&gt;
5 = Friday&lt;br /&gt;
6 = Saturday&lt;br /&gt;
7 = Sunday&lt;br /&gt;
&lt;br /&gt;
Default should be Monday when omitted.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
FODATE('week', [mydate], 1)&lt;br /&gt;
EODATE('week', [mydate], 1)&lt;br /&gt;
&lt;br /&gt;
The weekStart argument should only be valid when the interval is week.&lt;br /&gt;
&lt;br /&gt;
Convenience Date/Time Functions&lt;br /&gt;
&lt;br /&gt;
Add commonly used component functions:&lt;br /&gt;
&lt;br /&gt;
YEAR(date)&lt;br /&gt;
QUARTER(date)&lt;br /&gt;
MONTH(date)&lt;br /&gt;
WEEK(date)&lt;br /&gt;
WEEKDAY(date)&lt;br /&gt;
DAY(date)&lt;br /&gt;
&lt;br /&gt;
HOUR(datetime)&lt;br /&gt;
MINUTE(datetime)&lt;br /&gt;
SECOND(datetime)&lt;br /&gt;
&lt;br /&gt;
TIME(hour, minute, second)&lt;br /&gt;
&lt;br /&gt;
These provide simpler alternatives to DATEPART() for common operations.&lt;br /&gt;
&lt;br /&gt;
Resulting Date/Time Formula Family&lt;br /&gt;
&lt;br /&gt;
The intended v1.0 Date/Time API would be:&lt;br /&gt;
&lt;br /&gt;
DATE()&lt;br /&gt;
TIME()&lt;br /&gt;
&lt;br /&gt;
TODAY()&lt;br /&gt;
NOW()&lt;br /&gt;
&lt;br /&gt;
DATEADD()&lt;br /&gt;
DATEDIFF()&lt;br /&gt;
DATEPART()&lt;br /&gt;
DATETRUNC()&lt;br /&gt;
&lt;br /&gt;
FODATE()&lt;br /&gt;
EODATE()&lt;br /&gt;
&lt;br /&gt;
YEAR()&lt;br /&gt;
QUARTER()&lt;br /&gt;
MONTH()&lt;br /&gt;
WEEK()&lt;br /&gt;
WEEKDAY()&lt;br /&gt;
DAY()&lt;br /&gt;
&lt;br /&gt;
HOUR()&lt;br /&gt;
MINUTE()&lt;br /&gt;
SECOND()]]></description><category>Formula / Expressions</category><pubDate>Sat, 26 Sep 2026 16:57:48 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=37</guid><comments>https://feedback.inlyrastudio.com/view.php?id=37#bugnotes</comments></item><item><title>0000042: Redesign About dialog with branded split layout and click-to-dismiss behavior</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=42</link><description><![CDATA[Redesign the About Inlyra Studio dialog to provide a more polished, branded presentation appropriate for the v1.0 release.&lt;br /&gt;
&lt;br /&gt;
The About dialog should use a vertical split layout, approximately 40% information / 60% visual.&lt;br /&gt;
&lt;br /&gt;
The left section should contain the primary product information, such as:&lt;br /&gt;
&lt;br /&gt;
Inlyra Studio product name&lt;br /&gt;
Short product description/tagline&lt;br /&gt;
Installed version&lt;br /&gt;
Current edition where appropriate&lt;br /&gt;
Copyright / TaskNext LLC&lt;br /&gt;
Inlyra Studio website or other relevant product information&lt;br /&gt;
&lt;br /&gt;
The right section should be primarily visual and feature a large Inlyra-branded graphic, logo treatment, or other professional product artwork. Avoid filling this area with additional configuration-style text. The intent is to give the About dialog a stronger visual identity and make it feel like a polished commercial application.&lt;br /&gt;
&lt;br /&gt;
The dialog should also use simplified dismissal behavior:&lt;br /&gt;
&lt;br /&gt;
Clicking anywhere on a non-interactive area of the About dialog should close it.&lt;br /&gt;
No dedicated OK or Close button should be required.&lt;br /&gt;
Esc should also dismiss the dialog.&lt;br /&gt;
The normal window close control should continue to work.&lt;br /&gt;
Interactive elements such as website links should perform their intended action without the click-to-dismiss behavior interfering.&lt;br /&gt;
&lt;br /&gt;
Where practical, reduce unnecessary traditional dialog chrome so the About window feels more like a branded product card than a configuration dialog.&lt;br /&gt;
&lt;br /&gt;
Expected Result:&lt;br /&gt;
Opening Help → About presents a clean, professional Inlyra-branded About screen with product information on the left and prominent visual branding on the right. The user can dismiss it naturally by clicking the dialog, pressing Esc, or closing the window.]]></description><category>User Interface</category><pubDate>Sat, 26 Sep 2026 16:57:30 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=42</guid><comments>https://feedback.inlyrastudio.com/view.php?id=42#bugnotes</comments></item><item><title>0000004: Help -&gt; Check for Updates</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=4</link><description><![CDATA[Add way to check for updates, and prompt, would you like to upgrade click here&lt;br /&gt;
&lt;br /&gt;
The ability for Inlyra to automatically check for updates, maybe have a flag to check automatically.&lt;br /&gt;
Also, go to Help-&gt;Check for Updates menu item.&lt;br /&gt;
&lt;br /&gt;
This will notify the user there's an update available and provide a button/link to download the new version.&lt;br /&gt;
OR&lt;br /&gt;
Provide a way to download and  auto update the application.]]></description><category>User Interface</category><pubDate>Sat, 26 Sep 2026 16:39:09 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=4</guid><comments>https://feedback.inlyrastudio.com/view.php?id=4#bugnotes</comments></item><item><title>0000006: Function Tool, f(x) button is too far to the right</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=6</link><description><![CDATA[Function Tool f(x) button is too far to the right in the tool settings pane.]]></description><category>User Interface</category><pubDate>Mon, 21 Sep 2026 23:25:52 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=6</guid><comments>https://feedback.inlyrastudio.com/view.php?id=6#bugnotes</comments></item><item><title>0000016: Multi-Row Calculation Tool ability to replace existing fields and apply calculation to multiple columns</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=16</link><description><![CDATA[1.	Allow replacing an existing field. Add an Output option that lets the user choose between Create New Field and Replace Existing Field. When replacing, modify the selected source field instead of creating another column. Preserve the existing field's name and appropriate data type. Existing workflows must remain backward compatible. &lt;br /&gt;
2.	Support multiple target fields where the calculation makes sense, particularly Fill Forward and Fill Backward. The user should be able to select multiple fields and apply the operation to all of them in a single Multi-Row Calculation node. For example, after pivoting contract prices into monthly columns, I should be able to select all contract-month columns, choose Fill Forward, select Replace Existing Fields, and fill NULL values down every selected column with one node.]]></description><category>Transform Tools</category><pubDate>Sun, 20 Sep 2026 23:49:22 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=16</guid><comments>https://feedback.inlyrastudio.com/view.php?id=16#bugnotes</comments></item><item><title>0000032: Formula Tool dirty state changes when clicking between tools</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=32</link><description><![CDATA[I selected the Formula tool, and click on a different tool, and the dirty state changed.]]></description><category>Transform Tools</category><pubDate>Sun, 20 Sep 2026 23:48:38 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=32</guid><comments>https://feedback.inlyrastudio.com/view.php?id=32#bugnotes</comments></item><item><title>0000041: Multi-Row Calculation: dynamically apply calculations to all numeric fields</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=41</link><description><![CDATA[Add a dynamic “All numeric fields” target option to the Multi-Row Calculation tool when using Replace Existing Fields.&lt;br /&gt;
&lt;br /&gt;
Currently, users must select individual fields from a fixed checklist. If additional numeric fields appear in the incoming schema later, the user must reopen the tool and select those fields manually.&lt;br /&gt;
&lt;br /&gt;
The new option should evaluate the incoming schema each time the workflow runs and apply the selected calculation independently to every numeric field. This would be particularly useful for datasets containing a changing number of similarly structured columns, such as contract-month prices.&lt;br /&gt;
&lt;br /&gt;
Proposed field-selection options:&lt;br /&gt;
&lt;br /&gt;
• Selected fields&lt;br /&gt;
• All numeric fields&lt;br /&gt;
&lt;br /&gt;
When “All numeric fields” is selected:&lt;br /&gt;
&lt;br /&gt;
• Include Int64, Decimal, and Double fields dynamically at runtime.&lt;br /&gt;
• Automatically include compatible numeric fields added in future runs.&lt;br /&gt;
• Exclude fields selected under Group By.&lt;br /&gt;
• Leave Date, String, and Boolean fields unchanged.&lt;br /&gt;
• Apply the calculation independently to each selected field.&lt;br /&gt;
• Preserve each field’s original name and data type when replacing it.&lt;br /&gt;
• Display an explanation that newly added numeric fields will be included automatically.&lt;br /&gt;
&lt;br /&gt;
Example use case:&lt;br /&gt;
&lt;br /&gt;
A dataset contains one column for each futures contract month. Each contract stops receiving new prices after it expires, and additional contract-month columns are introduced over time. The user selects Fill Forward, Replace Existing Fields, and All Numeric Fields. The node carries each contract’s last known price forward and automatically processes future contract columns without requiring the workflow to be reconfigured.&lt;br /&gt;
&lt;br /&gt;
Acceptance criteria:&lt;br /&gt;
&lt;br /&gt;
1. “All numeric fields” is available with Replace Existing Fields.&lt;br /&gt;
2. The selection is stored as a dynamic rule rather than a fixed list of field names.&lt;br /&gt;
3. New numeric input fields are included automatically during future executions.&lt;br /&gt;
4. Group By fields are excluded from replacement.&lt;br /&gt;
5. Each numeric field is calculated independently.&lt;br /&gt;
6. Existing workflows using individually selected fields remain backward compatible.&lt;br /&gt;
7. Schema preview and execution produce consistent results.]]></description><category>Transform Tools</category><pubDate>Sun, 20 Sep 2026 23:46:54 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=41</guid><comments>https://feedback.inlyrastudio.com/view.php?id=41#bugnotes</comments></item><item><title>0000014: Multi-Row Calculation Tool: when changing source field, output field name doesn't update</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=14</link><description><![CDATA[Multi-Row Calculation Tool – fix when changing Source Field, the Output Field name doesn’t change after the first field was selected.]]></description><category>Transform Tools</category><pubDate>Sun, 20 Sep 2026 23:00:30 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=14</guid><comments>https://feedback.inlyrastudio.com/view.php?id=14#bugnotes</comments></item><item><title>0000018: Basic Email Tool need to design</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=18</link><description><![CDATA[Need to develop Basic Email Tool prior to 1.0 release]]></description><category>Output Tools</category><pubDate>Sun, 20 Sep 2026 22:46:24 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=18</guid><comments>https://feedback.inlyrastudio.com/view.php?id=18#bugnotes</comments></item><item><title>0000013: CSV/Excel Input Tools, fix duplicate column name inputs</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=13</link><description><![CDATA[If the files have multiple columns with the same name, the input tools are not able to handle this.  Tool should be able to rename the column fields to avoid these issues.  Maybe sequentially, Field, Field_2, Field_3.]]></description><category>Input Tools</category><pubDate>Sun, 20 Sep 2026 03:22:51 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=13</guid><comments>https://feedback.inlyrastudio.com/view.php?id=13#bugnotes</comments></item><item><title>0000035: Manage Connections shows "eg Reporting Database" for SMTP server connection input field</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=35</link><description><![CDATA[Manage Connections shows &quot;eg Reporting Database&quot; for SMTP server connection input field]]></description><category>User Interface</category><pubDate>Sun, 20 Sep 2026 03:11:18 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=35</guid><comments>https://feedback.inlyrastudio.com/view.php?id=35#bugnotes</comments></item><item><title>0000034: In light mode, when hovering over the New button, the text turns black</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=34</link><description><![CDATA[In light mode, when hovering over the New button, the text turns black]]></description><category>User Interface</category><pubDate>Sun, 20 Sep 2026 03:09:50 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=34</guid><comments>https://feedback.inlyrastudio.com/view.php?id=34#bugnotes</comments></item><item><title>0000040: Formula Tool: fix Proper function to capitalize hyphenated name</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=40</link><description><![CDATA[How PROPER Treats Hyphens&lt;br /&gt;
- The PROPER function converts text to proper case by capitalizing the first letter of every new word.&lt;br /&gt;
- It treats spaces, hyphens, and other punctuation marks as word separators.&lt;br /&gt;
&lt;br /&gt;
Example: =PROPER(&quot;mary-jane&quot;) results in Mary-Jane.&lt;br /&gt;
Example: =PROPER(&quot;state-of-the-art&quot;) results in State-Of-The-Art (capitalizing minor words incorrectly by standard title-case rules)]]></description><category>Formula / Expressions</category><pubDate>Sun, 20 Sep 2026 03:08:08 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=40</guid><comments>https://feedback.inlyrastudio.com/view.php?id=40#bugnotes</comments></item><item><title>0000039: Add XML Input and Output Tools</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=39</link><description><![CDATA[Add native XML Input and XML Output tools to Inlyra Studio for reading, transforming, and writing XML data.&lt;br /&gt;
&lt;br /&gt;
XML is hierarchical rather than inherently tabular, so the tools should provide a practical method of converting repeating XML elements and attributes into Inlyra workflow rows and columns.&lt;br /&gt;
&lt;br /&gt;
XML Input&lt;br /&gt;
&lt;br /&gt;
The XML Input tool should support:&lt;br /&gt;
&lt;br /&gt;
Reading .xml files.&lt;br /&gt;
Selecting the repeating XML element representing workflow records.&lt;br /&gt;
XPath or similar record-path selection.&lt;br /&gt;
Reading element values.&lt;br /&gt;
Reading XML attributes.&lt;br /&gt;
Nested elements.&lt;br /&gt;
Repeating child elements.&lt;br /&gt;
Field discovery and selection.&lt;br /&gt;
Automatic data-type inference where practical.&lt;br /&gt;
Preview of the resulting dataset.&lt;br /&gt;
Handling optional/missing elements.&lt;br /&gt;
Clear errors for malformed XML.&lt;br /&gt;
&lt;br /&gt;
Example source:&lt;br /&gt;
&lt;br /&gt;
&lt;customer name=&quot;Acme&quot;&gt;&lt;br /&gt;
  &lt;orders&gt;&lt;br /&gt;
    &lt;order id=&quot;1001&quot; amount=&quot;250&quot; /&gt;&lt;br /&gt;
    &lt;order id=&quot;1002&quot; amount=&quot;400&quot; /&gt;&lt;br /&gt;
  &lt;/orders&gt;&lt;br /&gt;
&lt;/customer&gt;&lt;br /&gt;
&lt;br /&gt;
Possible configuration:&lt;br /&gt;
&lt;br /&gt;
Record Path: /customer/orders/order&lt;br /&gt;
&lt;br /&gt;
Fields:&lt;br /&gt;
@id&lt;br /&gt;
@amount&lt;br /&gt;
&lt;br /&gt;
Parent Fields:&lt;br /&gt;
&lt;a href=&quot;mailto:customer/@name&quot;&gt;customer/@name&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Expected output:&lt;br /&gt;
&lt;br /&gt;
customer | id   | amount&lt;br /&gt;
Acme     | 1001 | 250&lt;br /&gt;
Acme     | 1002 | 400&lt;br /&gt;
&lt;br /&gt;
The design should clearly distinguish between:&lt;br /&gt;
&lt;br /&gt;
Elements&lt;br /&gt;
Attributes&lt;br /&gt;
Repeating elements&lt;br /&gt;
Parent/context values&lt;br /&gt;
XML Output&lt;br /&gt;
&lt;br /&gt;
The XML Output tool should support:&lt;br /&gt;
&lt;br /&gt;
Writing .xml files.&lt;br /&gt;
Configurable root element name.&lt;br /&gt;
Configurable row/record element name.&lt;br /&gt;
Writing workflow fields as child elements.&lt;br /&gt;
Proper XML escaping.&lt;br /&gt;
Handling null/missing values.&lt;br /&gt;
Optional formatted/indented output.&lt;br /&gt;
Overwrite behavior consistent with other Inlyra Output tools.&lt;br /&gt;
&lt;br /&gt;
For example, a configuration could specify:&lt;br /&gt;
&lt;br /&gt;
Root Element:   orders&lt;br /&gt;
Record Element: order&lt;br /&gt;
&lt;br /&gt;
and produce:&lt;br /&gt;
&lt;br /&gt;
&lt;orders&gt;&lt;br /&gt;
  &lt;order&gt;&lt;br /&gt;
    &lt;customer&gt;Acme&lt;/customer&gt;&lt;br /&gt;
    &lt;id&gt;1001&lt;/id&gt;&lt;br /&gt;
    &lt;amount&gt;250&lt;/amount&gt;&lt;br /&gt;
  &lt;/order&gt;&lt;br /&gt;
  &lt;order&gt;&lt;br /&gt;
    &lt;customer&gt;Acme&lt;/customer&gt;&lt;br /&gt;
    &lt;id&gt;1002&lt;/id&gt;&lt;br /&gt;
    &lt;amount&gt;400&lt;/amount&gt;&lt;br /&gt;
  &lt;/order&gt;&lt;br /&gt;
&lt;/orders&gt;&lt;br /&gt;
&lt;br /&gt;
Advanced hierarchical XML construction, namespaces, schemas/XSD, and complex parent/child grouping can be considered separately rather than blocking initial XML support.&lt;br /&gt;
&lt;br /&gt;
Design Notes:&lt;br /&gt;
&lt;br /&gt;
JSON and XML should ideally share an internal hierarchical-data mapping architecture where practical. Concepts such as record-path selection, field discovery, flattening, parent/context fields, preview, and type inference should behave consistently between the two formats.]]></description><category>Input Tools</category><pubDate>Sun, 20 Sep 2026 02:30:49 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=39</guid><comments>https://feedback.inlyrastudio.com/view.php?id=39#bugnotes</comments></item><item><title>0000038: Add JSON Input and Output Tools</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=38</link><description><![CDATA[Add native JSON Input and JSON Output tools to Inlyra Studio for reading, transforming, and writing JSON data.&lt;br /&gt;
&lt;br /&gt;
JSON support should accommodate both simple flat JSON structures and nested/hierarchical data commonly encountered in application exports, API responses, configuration data, and data integration workflows.&lt;br /&gt;
&lt;br /&gt;
JSON Input&lt;br /&gt;
&lt;br /&gt;
The JSON Input tool should support:&lt;br /&gt;
&lt;br /&gt;
Reading .json files.&lt;br /&gt;
JSON arrays containing multiple records.&lt;br /&gt;
Single JSON objects.&lt;br /&gt;
Nested objects.&lt;br /&gt;
Nested arrays.&lt;br /&gt;
Selection of a record path identifying which array/object represents workflow rows.&lt;br /&gt;
Field discovery and selection.&lt;br /&gt;
Automatic data-type inference where practical.&lt;br /&gt;
Preview of the resulting tabular dataset before workflow execution.&lt;br /&gt;
Flattening nested objects into columns.&lt;br /&gt;
Expanding arrays/repeating structures into rows where appropriate.&lt;br /&gt;
Handling missing/null properties.&lt;br /&gt;
Clear errors for malformed JSON.&lt;br /&gt;
&lt;br /&gt;
Example source:&lt;br /&gt;
&lt;br /&gt;
{&lt;br /&gt;
  &quot;customer&quot;: &quot;Acme&quot;,&lt;br /&gt;
  &quot;orders&quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &quot;id&quot;: 1001,&lt;br /&gt;
      &quot;amount&quot;: 250&lt;br /&gt;
    },&lt;br /&gt;
    {&lt;br /&gt;
      &quot;id&quot;: 1002,&lt;br /&gt;
      &quot;amount&quot;: 400&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Possible configuration:&lt;br /&gt;
&lt;br /&gt;
Record Path: $.orders&lt;br /&gt;
&lt;br /&gt;
Fields:&lt;br /&gt;
id&lt;br /&gt;
amount&lt;br /&gt;
&lt;br /&gt;
Parent Fields:&lt;br /&gt;
customer&lt;br /&gt;
&lt;br /&gt;
Expected output:&lt;br /&gt;
&lt;br /&gt;
customer | id   | amount&lt;br /&gt;
Acme     | 1001 | 250&lt;br /&gt;
Acme     | 1002 | 400&lt;br /&gt;
JSON Output&lt;br /&gt;
&lt;br /&gt;
The JSON Output tool should support:&lt;br /&gt;
&lt;br /&gt;
Writing .json files.&lt;br /&gt;
Writing workflow rows as a JSON array.&lt;br /&gt;
Configurable pretty/indented vs. compact output.&lt;br /&gt;
Proper handling of strings, numbers, Boolean values, dates, and nulls.&lt;br /&gt;
Correct JSON escaping.&lt;br /&gt;
Optional overwrite behavior consistent with other Inlyra Output tools.&lt;br /&gt;
&lt;br /&gt;
Initial JSON Output can focus on producing a straightforward array of objects:&lt;br /&gt;
&lt;br /&gt;
[&lt;br /&gt;
  {&lt;br /&gt;
    &quot;customer&quot;: &quot;Acme&quot;,&lt;br /&gt;
    &quot;id&quot;: 1001,&lt;br /&gt;
    &quot;amount&quot;: 250&lt;br /&gt;
  },&lt;br /&gt;
  {&lt;br /&gt;
    &quot;customer&quot;: &quot;Acme&quot;,&lt;br /&gt;
    &quot;id&quot;: 1002,&lt;br /&gt;
    &quot;amount&quot;: 400&lt;br /&gt;
  }&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
Advanced construction of deeply nested JSON structures can be considered separately for a later release rather than blocking initial JSON support.&lt;br /&gt;
&lt;br /&gt;
Design Notes:&lt;br /&gt;
&lt;br /&gt;
JSON parsing should be designed with future HTTP/API Input functionality in mind. The same JSON parsing/flattening engine should eventually be reusable for JSON returned by REST APIs rather than being coupled specifically to files.]]></description><category>Input Tools</category><pubDate>Sun, 20 Sep 2026 02:28:25 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=38</guid><comments>https://feedback.inlyrastudio.com/view.php?id=38#bugnotes</comments></item><item><title>0000031: Switching workflow tabs marks selected tool configuration as modified</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=31</link><description><![CDATA[When a configured tool is selected in one workflow, switching to another open workflow and then returning to the original workflow can incorrectly mark the selected tool's configuration as dirty.]]></description><category>Workflow / Canvas</category><pubDate>Sun, 20 Sep 2026 01:49:16 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=31</guid><comments>https://feedback.inlyrastudio.com/view.php?id=31#bugnotes</comments></item><item><title>0000036: Improve tool settings readability and consistency</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=36</link><description><![CDATA[Improve tool settings readability and consistency.  Fix font sizes among other UI/UX clean up.]]></description><category>User Interface</category><pubDate>Sun, 20 Sep 2026 01:37:56 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=36</guid><comments>https://feedback.inlyrastudio.com/view.php?id=36#bugnotes</comments></item><item><title>0000017: Show Tool Help on Hover setting doesn't stick upon restart</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=17</link><description><![CDATA[When the Show Tool Help on Hover setting if unchecked, after restarting Inlyra, the flag comes back on.]]></description><category>User Interface</category><pubDate>Sun, 20 Sep 2026 01:30:53 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=17</guid><comments>https://feedback.inlyrastudio.com/view.php?id=17#bugnotes</comments></item><item><title>0000033: Delete/Backspace only removes one tool when multiple tools are selected</title><author></author><link>https://feedback.inlyrastudio.com/view.php?id=33</link><description><![CDATA[When multiple tools are selected on the workflow canvas using marquee selection or multi-select, pressing Delete or Backspace removes only one tool rather than all selected tools.]]></description><category>Workflow / Canvas</category><pubDate>Sun, 20 Sep 2026 01:30:07 -0400</pubDate><guid>https://feedback.inlyrastudio.com/view.php?id=33</guid><comments>https://feedback.inlyrastudio.com/view.php?id=33#bugnotes</comments></item></channel></rss>
