Skip to main content

    Filter by idea status

    Filter by product

    859 Ideas

    rory.smith
    TimeXtender Xpert
    rory.smithTimeXtender Xpert

    Add security features to REST EndpointsSUBMITTED

    It is possible to create REST Endpoints for Deliver instances in TimeXtender. This is a really nice feature that makes it possible to share data in- and externally using API calls instead of directly to a database.The current implementation is backed by an IIS instance that uses a machine identity to authenticate to the database backing your Prepare instance. The main drawback of this is that there is one static login/user connecting to your datawarehouse, there are no options for more finegrained security than applying a token or oauth to the endpoint.In my experience many customers would consider using REST to deliver data to third parties. The third parties could be customers or partners that consume parts of a larger dataset. Naturally, this leads to needing to apply table/field or row-level security to filter down the data that can be accessed by a specific token/login.It would be a great addition if a single Deliver instance can be secured such that Power BI, Qlik, Tableau, REST endpoints can enjoy the same security possiblities. Apart from passing through Windows AD / Entra ID / user:pass (SQL Auth), the REST endpoint would need to be able to map database users to tokens / app registrations.The current workaround would be to create a separate Deliver instance for each data / security combination that must be delivered. This will quickly lead to an unmanageable amount of Deliver instances, or for customers to look for other solutions.

    rory.smith
    TimeXtender Xpert
    rory.smithTimeXtender Xpert

    Add Job / Execution package / Task field to all relevant logging dialoguesSUBMITTED

    When checking the status of runs in TimeXtender you need to jump around between different dialogues to get to the bottom of an issue. The UX is rather lacking at the moment and could benefit from some quality-of-life improvements: please add the following fields/columns to logging dialogues across the products:Orchestration package:Orchestration package triggering a Job Job calling an Ingest Task or Package that sets a status Ingest Task or Execution Package triggering a status In case of a task, the Data Source the Task belongs to In case of an Execution Package: the instance (and Data Area) the package belongs to This would make it much easier to narrow down where to look in TDI after checking the logging from the Orchestration side, whether using Exmon DG client or browser or coming from a notification sent by Orchestration.Job:Orchestration package triggering a Job Job calling an Ingest Task or Package Ingest Task or Execution Package triggering a status In case of a task, the Data Source the Task belongs to In case of an Execution Package: the instance (and Data Area) the package belongs to Directly seeing the Task or Package setting a status, makes it much faster to jump to the place where action is required versus needing to read through a load of text to discover where to start looking will save a lot of time. Being able to click any of the fields and have the object open in the interface would really improve this. There are also some issues with the Job log dialogue itself:the dialogue is blocking, making it extra annoying to diagnose issues the error messages are cryptic: Ingest Instance <instance name>: The task <task name> CompletedWithErrors execution. It seems like there is an Enum name being passed directly instead of a descriptive stringExecution package:Orchestration package triggering a Job Job calling an Ingest Task or Package Ingest Task or Execution Package In case of a task, the Data Source the Task belongs to In case of an Execution Package: the instance (and Data Area) the package belongs to Steps within the Ingest Task or Execution PackageSimilarly to Job logging, being able to click a field and jump to the object would much improve the user's experience. As this dialogue is not blocking it is not as disruptive as the Job logging dialogue