Skip to main content

    Filter by idea status

    Filter by product

    863 Ideas

    bas.hopstaken
    TimeXtender Xpert
    bas.hopstakenTimeXtender Xpert

    Support for Additional Connections in TDISUBMITTED

    In TimeXtender Classic (v20.10), it is possible to add additional connections. This is a very powerful feature that many of our customers are using.It is especially useful when you have many similar data sources (such as NAV/BC or Exact software). In our customer base, it is often the case that there is a separate database for each country, region, or office. Some of these customers frequently acquire new companies or open new offices. In such cases, these data sources can easily be added to the main data source connection. The transformations then also apply to these sources, all the way up to the semantic layers.In TDI, we do not have this option, even though it is a very powerful feature. For some of our customers, this is the only reason holding them back from migrating from Classic to TDI.A possible workaround in TDI could be to clone the data sources and adjust some settings. However, in that case, all tables still need to be mapped to the Prepare instance. You then have two options:Manually map all tables: You can use smart mapping, but it still requires a lot of work. Use mapping sets: This can be a very powerful feature, but in the current setup, you need to manually synchronize all mapping sets for all tables.An option to synchronize all mapping sets at once could also be a solution. Alternatively, and perhaps preferably, it would be great to have the ability to create additional connections in TDI as well.

    Ability to link multiple processes to a single process map.SUBMITTED

    Hi! Current state:When using orchestration , it's possible to link and synchronize a process with a process map. This is a great feature for monitoring and controlling a process!Problem:However, when building an overview of dependent processes (e.g. two or more processes that run within the same schedule), it would be very helpful to link multiple processes directly to a single process map. This would allow us to monitor and control them together from one central place.Workaround/ Solution finding:Our current workaround is to create an extra process that contains the individual processes as sub-steps, and then link that wrapper process to the process map (without scheduling it). While this technically works, it becomes messy over time and requires maintaining the same logic in multiple places. This increases the risk of errors and makes orchestration harder to manage.I did notice that within the process map builder, there is an option to add a process map to another process map (so nested maps). However, the task status indicators (success, warning, failed) do not reflect the actual status of the nested process map (see screenshots down below). Because of this, it's not reliable for monitoring or controlling multiple processes from a single map.Feature suggestion:Managing multiple processes from a single map would be easier if one of the following changes were implemented: Allow linking multiple processes directly to a single process map. Nested process maps reflect accurate status indicators for monitoring and control. Screenshots:Web interface (deployed):Nested map is always (even with failed tasks) a single green check. Redirects on click to the nested map.Editor view:From editor view it seems like it should show a list of indicators connected to the nested map.