- You can now schedule orchestrations by table events. Do you want to run an orchestration as soon as a key table gets updated? You can do that now! Please refer to the documentation to help guide you through it.
- When creating a new token you can now restrict its access to the configuration trash bin
- Transformations can now be copied to the same bucket or an other transformation bucket
- Simplified version diffs for scripts
- You will now be given a warning if you cannot extend your sandbox because of required system upgrades
- For notifications, you can now choose from any email of any user that has previously worked on the orchestration or of course enter one of your choosing
- On the orchestrations listing page it will show if the orchestrations were manually triggered, event triggered, or scheduled
SQL Server extractor
- Allows incremental fetching by timestamp data type columns
- A new option to disable use of the fallback driver on failure
- We are now always displaying the documentation link for components, so please make sure that your components have it filled in the Developer Portal. If you have the documentation link then you can remove excess documentation from the long description.