Renaming of Task Step, Endpoint, and Schema Column Without Loss of Mapping
The next significant config enhancement in this version of our platform is the ability to rename task steps, endpoints, and schema columns without any loss of mapping. In the previous version, renaming these essential elements led to the loss of crucial data mappings, causing configuration headaches and elongated processes.
What's New?
In the past, users faced the challenge of maintaining their task step input data mapping or endpoint input and output mappings when renaming task steps, endpoints, or schema columns. This limitation created unnecessary obstacles and disrupted configuration work.
Solving the Configuration Pain Point
Thanks to our newly implemented internal logic for mapping formats, we have fully eliminated this pain point. You can now freely rename task steps, endpoints, and schema columns according to your specific needs without any negative consequences.
Key Benefits
Streamlined config work: No more time-consuming workarounds and complex procedures when renaming task steps, endpoints, or schema columns.
Data Integrity
Be assured that your data mappings remain intact, ensuring data accuracy and consistency throughout the platform.
Enhanced Flexibility
Adapt your configurations to evolving requirements effortlessly, without compromising on the quality of your mappings.
This update marks a significant step toward improving the user experience and making your configuration process smoother and more efficient.