Astera 10.5, where precision meets innovation in data governance. Unleash the power of smooth data management with our Governance platform's features: From intuitive UI enhancements to advanced AI-driven data enrichment and profiling.

Astera's Access Management ensures secure data marketplace navigation, while our Business Glossary, generated intelligently by AI, adds clarity to your vocabulary.

Experience a refined user interface, and optimized AI functionalities, setting a new benchmark in data governance.

Elevate your data trek with Astera 10.5 – where efficiency, visibility, and performance converge effortlessly, all within an intuitive drag-and-drop interface.

Data Governance

Data Discoverability

Advanced search and filtering capabilities to find exactly what the user is looking for. The Astera Governance platform offers these features and much more.

Data Enrichment

We've integrated AI to automatically generate business titles, descriptions for assets/artifacts, and field descriptions, enhancing clarity and efficiency in our processes.

Data Profiling

Data profiling refers to the process of examining, analyzing, reviewing, and summarizing data sets. The Astera Governance platform offers advanced functionality that encompasses Data Profiling.

Data Quality

Data quality is a measure of the condition of data based on factors such as accuracy, completeness, consistency, reliability, and whether it's up to date.

Business Glossary (this is also being generated via AI)

A business glossary is a set of data-related terms and definitions. The Astera Governance platform also supports a business glossary, which is generated using AI.

Data Marketplace/Access Management

The Access Management section of the Astera Data Governance platform lets the owner set resources to each of the users, based on their roles.

Improvements

FTP and File Handling Enhancements

Enhancements have been made to the Cloud Browser functionality, refining source parameter usage in FTP List, and improving password handling in the File Transfer Task.

Improvements in user experience include better informative messaging during server downtime and streamlined communication for file uploads/downloads.

User Interface Refinements

User interface improvements encompass enhanced homepage pagination. The Edit Toolbar button has a polished appearance, and project explorer panels feature icons for improved visibility.

The Ask AI feature has been enhanced, and UI improvements contribute to a more user-friendly experience. Forward/back buttons in the Job Progress window have been improved, enhancing usability.

Artificial Intelligence (AI) Enhancements

Improvements in the AI Mapper performance and error handling have been made. The 'Build Using AI' feature has seen refined UI improvements for seamless user interaction.

AI Mapper optimizations enhance performance, and parsing of Functional Groups in EDI Source has been improved.

Other Enhancements

UI improvements for the Build Using AI feature have been made. Cluster repository building now features clearer communication.

Additional Notes

• For existing customers, a repository upgrade and service restart are required. It is recommended that upgrading customers use the Repository Upgrade Utility.

This concludes the Astera 10.5 Release Notes.

Getting Started!

Artifacts

Use Cases

More...

Astera 10.4 revolutionizes data management with Google BigQuery and Azure Data Lake connectors, Excel Worksheet Parameterization, and AI-driven mapping precision.

Furthermore, explore advanced API Management capabilities, Cloud Browser in Scheduler, refined AI features in Astea Report Model, and innovations like GraphQL APIs.

Experience a data revolution with Astera 10.4's user-friendly drag-and-drop interface, simplifying complex tasks without the need for coding. Elevate your data journey as the intuitive design puts advanced management capabilities at your fingertips, ensuring a seamless and efficient process.

Unleash the potential of your data management with this intuitive and transformative release.

Report Worksheet Parameterization

The Worksheet Parameterization feature empowers users to efficiently extract data from specific worksheets in an Excel file through convenient looping mechanisms. When accessing the configuration parameter screen, the option to define the desired worksheet is displayed.

This selection is made flexible and customizable as the worksheet option can be parametrized using variables or a configuration file. This comprehensive feature enhances data retrieval processes, simplifying and optimizing data handling from multiple worksheets in Excel.

AI Automap

In Astera Data Stack, the AI Automapper utilizes semantic relationships to facilitate field mapping. By analyzing the context and meaning of the fields, it intelligently establishes connections and maps them accordingly.

This advanced approach streamlines the process, enhancing accuracy and efficiency in field mapping tasks.

Dataprep

Grid Enhancements

The grid has been made more aligned by making it easier to sort and filter the columns. Connected to an easy interface and to the expression language, this enhancement is a step closer to making it more streamlined.

Connectors

MongoDB Destination

MongoDB is a document-oriented database in which one collection holds different documents. The MongoDB Destination object in Astera Data Stack provides functionality to write data onto it. This component provides functionality to control how data should be written in collections.

Google BigQuery

In Astera Data Stack, users will be able to connect with Google BigQuery as a database source or destination. As a source, both flat and hierarchical data can be read. For destination, flat data can be written to Google BigQuery.

Azure Data Lake (Gen 2)

Azure Data Lake Gen 2 is a cloud-based big data storage and analytics solution provided by Microsoft Azure. It offers scalable and cost-effective storage for structured, semi-structured, and unstructured data.

The Azure Data Lake Gen 2 provider will be present within the Cloud Connector object in Astera.

API Management

Support for raw input in API Client

In Astera API Management, the user can now make API requests in any content type by providing the content type along with its serialized content string.

Support for URL Encoded requests in API Client

In Astera API Management, the user can now make API requests using the application/x-www-form-urlencoded payload content type.

Allowing custom server responses for no data response

Define a custom response for your deployed APIs when the flow processing does not give an output. This gives developers flexibility in designing APIs according to the desired standards.

Core

Cloud Browser support in Scheduler

Improvements have been made to the user-friendliness of the Cloud Browser. Cloud Browser’s support has been added to the Scheduler.

Astera Report Model

AI Feature – Duplication Accuracy Enhancement

After utilizing the AI Feature to generate the layout, we noticed that certain fields were being replicated within the table collection region.

However, through thorough investigation and refining our prompt, we managed to significantly reduce field duplication by around 80% based on our analysis of the enhancements implemented.

AI Feature – Cache in DB

The output generated by our AI Feature used to be stored in a system folder, but there has been a modification to this functionality. Now, the cache is stored in a repository table named AICache.

Sort/Un-Sort Layout Option

We've now incorporated an option to sort or unsort the layout of the model. This enhancement adds a sorting feature accessible through the context menu in various regions. By clicking the new sort button, users can conveniently arrange the created fields in alphabetical order.

These changes will be immediately reflected in the data preview as well, and this sorting functionality is applicable across all types of regions, ensuring a more organized experience.

AI Feature Document Type Support – Account Statement

We have added an additional document type support for our AI Feature to extract data and create report models from Account Statements.

Other Features

GraphQL APIs

GraphQL APIs are a query language and runtime for APIs, enabling clients to request the data they need, reducing over-fetching and under-fetching. They offer a more efficient, flexible, and self-documenting approach to data retrieval and manipulation compared to traditional REST APIs.

Astera API Management now supports the use of GraphQL APIs as the input content type for an API. The feature can be seen within the Input Content Type drop-down menu of the API Client object.

Run OCR for all PDF Files

Astera now provides the functionality to extract data from PDFs that contain scanned documents using Optical Character Recognition. This option has now made scanned documents available for extraction to users, minimizing the effort of manual data entry from such documents.

Users can select the Resolution for OCR, allowing them to get the best result for their documents.

Toast Notification Enhancement

The Toast Notification feature in Astera Data Stack has seen quite a lot of improvement and enhancement, making it more efficient and seamless.

AIMapper Improvement

In Astera Data Stack, the AI mapping approach has been changed. The product is now implementing a Waterfall model for this feature.

Refinements in Server Browser

In Astera 10.4, many bugs have been addressed user experience has been improved by enabling automatic refresh after actions like adding a catalog item. Other than that, manual refresh is no longer required.

RMD Source Support in Catalog

Support for the Report Source object has now been added to the resource catalog.

Azure Authentication

The Azure SQL Database is a fully managed platform as a service (PaaS) database engine that handles most of the database management functions such as upgrading, patching, backups, and monitoring without user involvement.

In Astera 10.4, the Azure SQL Server authentication is available.

This concludes the Astera 10.4 release notes.

Astera Data Stack is built on a client-server architecture. The client is the part of the application which a user can run locally on their machine, whereas the server performs processing and querying requested by the client. In simple words, the client sends a request to the server, and the server, in turn, responds to the request. Therefore, database drivers are installed only on the Astera Data Stack server. This enables horizontal scaling by adding multiple clients to an existing cluster of servers and eliminating the need to install drivers on every machine.

The Astera client and server applications communicate on REST architecture. REST-compliant systems, often called RESTful systems, are characterized by statelessness and separate concerns of the client and server, which means that the implementation of both can be done independently if each side knows what format of messages to send to the other. The server communicates with the client using HTTPS commands, which are encrypted using a certified key/certificate signed by an authority. This saves the data from being intercepted by an attacker as the plaintext is encrypted as a random string of characters.

Astera is proud to unveil version 10.2 of our industry-leading products offering cutting-edge features and capabilities.

Encompassing numerous areas of operation, the features include:

• Microsoft SharePoint functionality, now available via the Cloud Connection object, allows users to easily store and access files, whilst working on the dataflow designer.

• A new OCR (Optical Character Recognition) capability that simplifies data extraction and processing.

Additionally, Astera Data Stack's API area has also been upgraded, offering users an even more streamlined experience. Astera is also a one-stop platform within the Astera umbrella that allows users to consume and manage APIs in a code-free environment.

Finally, Astera 10.2 comes with an updated user interface that includes a wealth of UI improvements and bug fixes, enhancing the overall user experience.

Astera's Report Model Component

The Report Model component in Astera 10.2 has introduced, modified, and enhanced some new and existing features to make the process of data extraction even more flexible and user-friendly.

The highlights of this release include:

• Verification of created fields

• The addition of the pattern bar context menu

• An option to change data region type.

Additionally, we have introduced:

• Optical Character Recognition (OCR)

which allows users to read data from PDFs having scanned documents. These new additions have made the experience of capturing data easier than ever before.

Extracting data from scanned PDFs via OCR

Astera now provides the functionality to extract data from PDFs that contain scanned documents using Optical Character Recognition.

When provided such a PDF, the tool recognizes it as an image PDF and automatically starts the OCR process. This option has now made scanned documents available for extraction to users, minimizing the effort of manual data entry from such documents. Users can select the Resolution for OCR, allowing them to get the best result for their documents.

Additionally, to ensure correct data extraction, as noise elements can cause erroneous data to be extracted, an Edit Mode is also available for the users to clean and tweak the extracted data.

Edit Mode allows you to deal with the data as a text file and make changes accordingly.

Data Field Verification

Report Models now have the functionality to verify if the data fields have been captured properly for all data instances by checking for any non-blank character being adjacent to instances of data fields. This option gives users a one-click check for the data fields they have created.

Additionally, to allow users better visibility of the erroneous fields, navigation between instances of the data field is also provided along with an option to auto-adjust field lengths for all data fields within the selected data region.

Pattern Box Context Menu

Users can now access wildcards and other additional features for patterns in a report model through a context menu by right-clicking on the pattern box.

Append Region and Data Region Interchangeability

Now, if need be, users can change a data region to an append region and vice versa within the Model Layout panel.

This allows users flexibility in changing the model layout as they are creating their extraction template.

Multipart (API Consumption)

The multipart format is a way of structuring data in an API request or response that allows multiple files or data types to be transmitted together as a single unit.

In Astera Data Stack for the consumption side, the multipart format can be used to simplify the process of uploading or downloading large files, or when sending a single request that contains both file data and metadata.

Now, you can consume APIs In Astera using an API client that supports multipart content.

AWS Signature Authentication

AWS Signature authentication is the process of verifying the authenticity of requests made to Amazon Web Services (AWS) using the AWS Signature method.

This authentication process involves calculating a digital signature for each request using the requester’s access key and secret access key, along with details about the request being made. AWS verifies the signature against the user’s access credentials and grants access to the requested resources if the signature is valid.

The AWS Signature authentication method ensures that requests are securely transmitted and that only authorized users can access AWS resources.

NTLM Authentication

NTLM (NT LAN Manager) authentication is a Microsoft proprietary authentication protocol used to authenticate users in a Windows-based network.

It provides secure authentication by using a challenge-response mechanism, where the server sends a challenge to the client, and the client sends a response that is encrypted using a hash of the user’s password.

NTLM authentication is used in various Microsoft products, including Windows, Internet Explorer, and Microsoft Office.

Raw Preview Request/Response

A raw preview request and response feature allows API developers to view the exact request and response payloads being exchanged between clients and servers in their APIs.

This feature provides a detailed look at the headers, body, and metadata of the HTTP request and response, which can help API developers debug issues, test APIs, and optimize performance. By using raw preview request and response capabilities, API developers can gain a deeper understanding of how their APIs are being used and troubleshoot issues quickly and efficiently.

Curl Command

Curl is a command-line tool that can be used to send HTTP requests to APIs and retrieve the respective responses.

It allows API developers and testers to easily interact with APIs and perform tasks such as testing, debugging, and troubleshooting. Curl supports various HTTP methods such as GET, POST, PUT, and DELETE, and can handle HTTP headers, cookies, and authentication.

It is a simple yet powerful tool that is widely used in API development and management.

API Logging

API logging is the process of keeping track of how an application programming interface (API) is being used.

It helps to understand how often the API is being used, how long each request takes, and any errors that occur. API logging can be used for troubleshooting, monitoring performance, and identifying security threats.

The logs can be stored locally or in a cloud-based system, where they can be analyzed to provide insights.

Astera Install Manager

The Install Manager installs the dependencies required for running auto-generate layout (AGL) and optical character recognition (OCR) on your system/machine.

The auto-generate layout option allows for the generation of an extraction template at the click of a button. With optical character recognition, scanned pdfs can be processed by Astera to get extracted data.

AGL was introduced in Astera 10.0, and OCR has been introduced in Astera 10.2.

When you install the client and the server, you’ll see two install managers (one for the client and one for the server) installed.

You can run this from here directly or go inside the client, when it runs under an Admin account, and go to Tools > Run Install Manager and it would run the install manager to install the dependencies.

You can learn more about the install manager and its setup here.

UI Fixes and Improvements

Project

• Project refresh has been greatly improved.

• Project loading times have been improved.

• A new UI has been implemented for the ‘Add New Item’ window in the Project with better-looking icons and a side panel that shows a description.

Jobs

• Improvements in the Job trace window have been made.

Deployment and Scheduling

• Deployment selections have been improved.

• Scheduler refresh has been improved to work more efficiently.

This concludes the release Notes for Astera 10.2.

Astera 10 is a major release and not a direct upgrade of Astera 7.6. This means that migrating from Astera 7.x to Astera 10 won’t require you to uninstall Astera 7 since Astera 10 can be installed side by side with Astera 7 on a system. Astera 10 is backward compatible, and therefore, most of the flows created on Astera 7 can run on Astera 10 without modifications. However, as with the most major release of any complex software, we recommend that you upgrade your lower level environment first, so you have an opportunity to test and verify any existing flows. This will make it possible to identify any migration issues you may encounter early on in the upgrade cycle. In this document, we will cover how you can migrate from Astera 7.x to the all-new Astera 10.

Installing

The installation package for Astera 10 (64-bit) contains two setup (.exe) files:

• AsteraDataIntegrator.exe – for Astera client, and

• IntegrationServer.exe – for Astera Integration Server

The setup files for Astera 10 can be downloaded from the following location:

https://www.astera.com/download-center/

Licensing

Unlike the previous releases of Astera, Astera 10 comes with a single licensing key (for server) rather than two separate keys for Astera server and client. The licensing key for Astera 10 has changed which means you cannot use your Astera 7 key to register Astera 10. The single licensing key for Astera 10 is used to register Astera server and it controls how many clients can connect to the server as well as the functionality available to the connected clients.

Cluster and Server Management in Server Explorer

The Astera 10 client can be configured with multiple different servers, however, it can only connect with one server at a time. The jobs scheduled, queued or running on the other registered server will continue to run without interruption even if the client is not currently connected to the server.

All servers pointing to a single repository database will form a cluster of servers sharing the common workload of queued jobs. A cluster of v10 servers you configure will be up and running and processing jobs in a similar way to 7.6, despite the fact that the v10 client can only connect to and manage one v10 server at a time. You can see which server in the cluster has actually processed a job by right clicking the Cluster and opening Server Jobs window.

Repository

You need to set up a new repository to communicate with the Astera 10 server. While upgrading the previous releases of Astera 7, you would simply go to Server > Upgrade Cluster Database. However, while migrating to Astera 10, you need to set up a repository in a new database from scratch to communicate with the server(s) and store the record of server activity. To set up a repository in Astera 10, go to Server menu > Configure > Build Repository Database and Configure Server.

Manually Migrating Existing Jobs from Astera 7 to Astera 10

Once you have built a cluster repository in Astera 10, the next step is to migrate the scheduled jobs you created in Astera 7.

1. For this, open the Job Scheduler in Astera 7 from Server > Job Schedules.

1. You will see all the scheduled jobs listed in the Scheduler. Select the jobs you want to migrate.

1. Click Export Schedule button in the Scheduler toolbar.

1. Point to the directory and folder where you want to save the scheduled jobs and click OK.

Now Astera will create a separate XML file with ‘.Sched’ extension for each scheduled job and save it in the designated folder.

1. A message window will pop up to notify that your scheduled jobs have been successfully. Click OK.

1. Now you have to import the job files in Astera 10 to complete the migration process. For this, open Astera 10 client and go to Server > Job Schedules.

1. This will open the Scheduler  tab. To import the existing jobs, click the Import Schedule  button in the Scheduler toolbar.

1. Point the path to the directory where you have saved the schedule files. Select all the scheduled jobs you want to import and click Open.

1. You can see that the existing jobs scheduled in Astera 7 have been successfully migrated to Astera 10 and a new Job ID has been assigned to each job.

Migrating Existing Jobs from Astera 7 to Astera 10 Using Pre-Designed Flows

Prior to any upgrade, we strongly recommend that you take a full backup of your repository database. Also, upgrading lower-level environment first (such as QA, UAT, etc.) is recommended prior to upgrading the Production environment. This will make it possible to sort out/resolve any issues before upgrading Production.

Steps to Upgrade:

Using Astera 7 client, run the following dataflow to export existing schedules into a comma-delimited file.

Take note of any existing Cluster Settings. You can check it by right-clicking the cluster in Server Explorer and selecting Cluster Settings in the context menu. These settings will need to be re-configured manually after the upgrade.

It may be helpful to take screenshots of those settings for later reference. The settings include: Staging Directory, Purge Job Frequency Options, Email Notification Setup, and optionally, Server Profiles if a non-default profile was used prior to the upgrade.

Open Astera 10 client. Go to Server menu > Manage > Build Cluster Database. Point it to the database hosting the Astera repository.

Use the dataflow below to import the schedules you exported previously in Astera 7.

The dataflow will look like this:

Once the objects are properly configured, save and run the dataflow.

Next, open Server Explorer, right-click on DEFAULT and select Cluster Settings.

Now, manually re-configure the relevant settings. You can use the screenshots of Cluster Settings you previously took for reference in version 7. Optionally, you can manually reconfigure the Server Profiles setting if a non-default profile was used prior to the upgrade.

Now, restart the Astera server.

This completes the upgrade.

Migration Best Practices:

• When you are starting the migration process, it is recommended to keep Astera 7 and Astera 10 servers running in parallel. This is to avoid any interruption in jobs that are currently running.

• We also recommend you initiate the migration process with a lower-level, testing environment, and then promote your deployment to a higher-level environment as needed. This will help ensure smooth migration process with any flow compatibility issues spotted early in the transition cycle.

Astera 10 is a major release and not a direct upgrade of Astera 9. This means that migrating from Astera 9 to Astera 10 won’t require you to uninstall Astera 9 since Astera 10 can be installed side by side with Astera 9 on a system. Astera 10 is backward compatible, and therefore, most of the flows created on Astera 9 can run on Astera 10 without modifications. However, the deployment archives (*.car files) created with previous versions are not directly compatible with v10.x. All the deployments must be regenerated and deployed again in the latest version. As with most major releases of any complex software, we recommend that you upgrade your lower-level environment first, so you have an opportunity to test and verify any existing flows. This will make it possible to identify any migration issues you may encounter early in the upgrade cycle.

Installing

The installation package for Astera 10 (64-bit) contains two setup (.exe) files:

• AsteraDataIntegrator.exe – for Astera client

• IntegrationServer.exe – for Astera Integration Server

The setup files for Astera 10 can be downloaded from the following location:

Licensing

Like Astera versions 8 and 9, Astera 10 also comes with a single licensing key (for server) rather than two separate keys for Astera server and client. However, the licensing key for Astera 10 has changed which means you cannot use your Astera 9 key to register Astera 10. The single licensing key for Astera 10 is used to register Astera server and it controls how many clients can connect to the server as well as the functionality available to the connected clients.

Cluster and Server Management in Server Explorer

Astera 10 client can be configured with multiple different servers, however, it can only connect with one server at a time. The jobs scheduled, queued, or running on the other registered server will continue to run without interruption even if the client is not currently connected to the server.

All servers pointing to a single repository database will form a cluster of servers sharing the common workload of queued jobs. A cluster of v10 servers you configure will be up and running and processing jobs in a similar way to v9. You can see which server in the cluster has actually processed a job by right clicking the DEFAULT node in Server Explorer and opening the Job Monitor window.

Repository

Upgrading Existing Repository

Astera provides an option to make an in-place repository upgrade which means that if you don’t wish to set up a new repository when you shift to v10, you can just use your existing one from the previous version and upgrade its cluster database. All the jobs scheduled in the repository used in v9 will appear in v10 after the upgrade.

The following steps explain how to upgrade an existing repository for migration from v9 to v10:

1. In Astera 10, go to Server > Manage > Upgrade Cluster Database.

1. Provide credentials of the version 9 repository and click OK:

1. Now go to Server menu > Manage > Server Properties.

1. In the Server Connection Properties tab, click on the ellipsis button next to Cluster DB Info.

1. In the Database Connection window, provide the credentials of the repository you just upgraded and click OK.

After completing this step, we recommend that you restart the Integration service.

Creating a New Repository

If you wish to set up a new repository in Astera 10, go to Server menu > Configure > Build Repository Database and Configure Server.

Manually Migrating Existing Jobs from Astera 9 to Astera 10

In case you chose to build a new cluster repository in Astera 10, your next step is to import all the scheduled jobs created in Astera 9.

1. For this, open the scheduler in Astera 9 from Server > Job Schedules.

1. You will see all the scheduled jobs listed in the scheduler. Select the jobs you want to migrate. To select all jobs, you can also use the shortcut key Ctrl+A.

1. Click on the Export Schedule icon in the Scheduler toolbar.

1. Point to the directory and folder where you want to save the scheduled jobs and click OK.

Now Astera will create a separate XML file with ‘.Sched’ extension for each scheduled job and save it in the designated folder.

1. A message window will pop up to notify that your scheduled jobs have been exported successfully. Click OK.

1. Now you need to import the scheduled jobs in Astera 10 to complete the migration process.

For this, open Astera 10 client and go to Server  >  Job Schedules.

This will open the Scheduler tab. To import the existing jobs, click the ‘Import Schedule’  button in the Scheduler toolbar.

1. Point the path to the directory where you have saved the schedule files. Select all the scheduled jobs you want to import and click ‘Open.’

1. You can see that the existing jobs scheduled in Astera 9 have been successfully migrated to Astera 10 and a new Job ID has been assigned to each job.

Migrating Existing Jobs from Astera 9 to Astera 10 Using Pre-Designed Flows

After building a new cluster repository in Astera 10, an alternate way of shifting all the scheduled jobs from Astera 9 to Astera 10 is to use pre-designed flows.

Prior to any upgrade, we strongly recommend that you take a full backup of your repository database. Also, upgrading a lower-level environment first (such as QA, UAT, etc.) is recommended prior to upgrading the production environment. This will make it possible to sort out/resolve any issues before upgrading production.

Steps to Upgrade:

Using Astera 9 client, run the following dataflow to export existing schedules into a comma-delimited file.

Next, open the downloaded file in Astera 9. The dataflow will look like this:

Once the objects have been configured, run the dataflow. This will create a CSV file containing data of all the schedules that existed in v9.

Next, take note of any existing Cluster Settings. You can check it by right clicking the cluster in the Server Explorer and selecting Cluster Settings in the context menu. These settings will need to be re-configured manually after the upgrade.

It may be helpful to take screenshots of those settings for later reference. The settings include Staging Directory, Purge Job Frequency Options, Email Notification Setup, etc.

Open Astera 10 client. Go to Server menu > Manage > Build Cluster Database. Point it to the database hosting the Astera repository.

Use the dataflow below to import the schedules you exported previously in Astera 9.

The dataflow will look like this:

Once the objects are properly configured, save and run the dataflow.

Next, open Server Explorer, right-click on DEFAULT, and select Cluster Settings.

Now, manually re-configure the relevant settings. You can use the screenshots of Cluster Settings you previously took for reference in version 9. Optionally, you can manually reconfigure the Server Profiles setting if a non-default profile was used prior to the upgrade.

Now, restart the Astera server.

This completes the upgrade.

You can download the flows by clicking on the links below:

Migration Best Practices:

• When you are starting the migration process, it is recommended to keep Astera 9 and Astera 10 servers running in parallel. This is to avoid any interruption in jobs that are currently running.

• We also recommend that you initiate the migration process with a lower-level, testing environment and then promote your deployment to a higher-level environment as needed. This will help ensure smooth migration process with any flow compatibility issues spotted early in the transition cycle.