--- title: "Review Converted WebApps" slug: "review-converted-webapps" updated: 2026-03-24T10:48:30Z published: 2026-03-24T13:33:56Z canonical: "skthelp.syniti.com/review-converted-webapps" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Review Converted WebApps ## Overview This article describes the WebApp configuration conversion process from the legacy Construct to Cloud Construct. The conversion process is automated and involves analyzing and validating the WebApp components, resolving configuration and compatibility issues, and ensuring that all configurations are preserved while moving assets to Cloud Construct. This process will be triggered on a tenant-by-tenant basis, and the results will be available afterward on the **System Administration > NextGen Construct Conversion** page. ## Post Conversion Checklist - You can begin validating and updating [page layout](/v1/docs/create-a-construct-page) (container) settings, [Menu Links](/v1/docs/configure-webapp-menu), [WebApp Groups](/v1/docs/configure-webapp-groups), [Events](/v1/docs/construct-events), Datasets and [Fields](/v1/docs/configure-column-properties). > [!NOTE] > Note > > - Not every page in your WebApp will become a page in the Cloud Construct design. Cloud Construct uses a **Container** concept for presentation and layout. > - Header-Detail pages will be converted into a vertically split pair of containers, with the original header page then the original detail page arranged in a top-to-bottom layout. > - Horizontal Views will be converted into **Grid** containers. > - Vertical Views will be converted into **Property Card** containers. > - A page that contains both a horizontal and a vertical view will be converted into a horizontally split container, with the Grid on the left and the Property Card on the right. > - If a WebApp’s data source is not associated with the correct datastore, the WebApp is skipped during the conversion process. - Confirm that the [**Is Key**](/v1/docs/configure-column-properties#column-base-properties) property is toggled on for the correct key fields present in the Dataset. - If a SQL View is used for the Dataset creation, confirm the **Affected Table** value is correct in the Syniti Knowledge Platform’s (SKP) Catalog module. Click the button next to the Dataset list to open it in the SKP Catalog. - Review any List or Combobox fields that may have had dependent Where Clause criteria. Construct Preview does not allow free-text entries for the List Where Clause as the legacy Construct did. Instead, Construct Preview uses defined parameters to specify list filter criteria. - Review the validations and business rules registered for your page events. > [!NOTE] > Note > > - OnValidate events will be renamed to **OnSave**. > - Cloud Construct does not separate validations and business rules as different configuration elements. Each rule is now implemented as a **Task** assigned to the event of a Validation or Business Rule type. > - Cloud Construct uses Task dependencies, instead of Priority values, to determine the order of execution for validations and business rules. > - For converted events, all Validations will be registered with no dependencies and the business rules will be dependent on the successful completion of all validations. - Review Stored Procedure validations that previously used a non-zero Return value to indicate a validation failure. They will need to be updated or replaced per the instructions given [below](/v1/docs/review-converted-webapps#stored-procedure-validations). - Evaluate your events to determine if you had controls, business rules, or validations dependent on the **boaStatus** field. Event status is no longer saved directly to the record. - **Assign Security to Non-Admin Users:** Each WebApp Group converted from legacy Construct will have an new Security Profile created for it in the SKP as part of the automated process. Initially, this security profile will have no User Groups or Roles assigned to it. - On the *NextGen Construct Conversion* page, click the **Security Help** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-PBVYNGQD.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A37%3A51Z&se=2026-11-17T20%3A37%3A51Z&sr=b&sp=r&sig=Os3B98l%2B%2BvNaqFFkDDyTVPY3UHemOGZ56llNcpIv3lU%3D) button to see the newly created security profiles in the NextGen Construct Security Help section. - Click the **User Groups** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-GXYKPF9O.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A37%3A51Z&se=2026-11-17T20%3A37%3A51Z&sr=b&sp=r&sig=SaGZEFbYcXHDZxelLL3%2BgbGUHMQNj%2F7Rjw4MviQk41A%3D) button next to a security profile to see the recommended User Groups that would be needed to match your legacy [Construct Security Role](/v1/docs/security-roles) assignments. - Typically, this involves creating a [User Group](/v1/docs/user-groups) in the SKP Admin module for each Construct Security Role that exists in the legacy Construct. - You can then assign [Roles](/v1/docs/roles) in the SKP to these User Groups and Security Profiles. Refer to the [Assign Roles and Groups to Security Profiles](/v1/docs/security-profiles#assign-roles-and-groups-to-security-profiles) section for more information. - You can also use Build Assist, Syniti’s AI-powered WebApp development assistant, to converse in natural language and configure the WebApp. - Refer to [Methodology Updates in Construct Preview](/v1/docs/methodology-updates-in-construct-preview) for more information on how WebApp configuration and underlying data are referenced and managed in Cloud Construct. ## Re-Running the Conversion If you need to re-run or reset the conversion process to post the latest WebApp configurations, ensure that you first [delete](/v1/docs/create-a-webapp-in-construct#delete-a-webapp) or rename the previously converted WebApp in the WebApp Builder and then review the information given [below](/v1/docs/review-converted-webapps#reset-or-create-the-webapp). ### Prerequisites - Ensure that the WebApp’s [Datasource](/v1/docs/data-sources) is associated with the correct [datastore](/v1/docs/datastores) in the Syniti Knowledge Platform’s (SKP) Catalog module. - It is recommended to select the Profiling and Construct [usages](/v1/docs/set-the-usage-of-a-connection) on the connection used for the datastore and then run a metadata scan on the datastore to retrieve the latest SQL schema and object definitions. ### Reset or Create the WebApp 1. Access **System Administration > WebApps** and select the required WebApp. 2. Select the WebApp’s **vertical menu** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image(884).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A37%3A51Z&se=2026-11-17T20%3A37%3A51Z&sr=b&sp=r&sig=MPjDmjFR3N0gNPaTrLHlFtgwENJQU2%2FdmdqVY0Vn%2BDk%3D) **> Import/Export >** **Convert to Next Gen** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image(889).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A37%3A51Z&se=2026-11-17T20%3A37%3A51Z&sr=b&sp=r&sig=YD1hvLd9kGHaSffRUjmw%2F%2B4QXGJi9aGMq5wlthtnfWI%3D) . The *Conversion Results* page is displayed. This page is similar to the *NextGen Construct Conversion* page, but includes additional functionality to reset and recreate the WebApp. 3. To enable the ability to rerun the conversion process, click the **Reset** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-G3BZ8IJ2.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A37%3A51Z&se=2026-11-17T20%3A37%3A51Z&sr=b&sp=r&sig=TnRGJm1AdUejj2o5giHnlaEojdvgrDYXl3M6oU8qnvg%3D) button only after renaming or deleting the existing WebApp in Cloud Construct. 4. To start the WebApp conversion analysis and process, click the **Create New WebApp** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-DUKCT8S5.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A37%3A51Z&se=2026-11-17T20%3A37%3A51Z&sr=b&sp=r&sig=AJ%2FqU0b9%2BKvo7p443SoYf7O64ca%2BYA6Qiq%2FGsaUnJeQ%3D) button. The Conversion Results report will then be available for your review, and a link to the WebApp Builder for the newly converted WebApp in Cloud Construct will be active. 5. On the *Analysis Results* page, review the component types and their sub-properties that need configuration updates, identify components that are not compatible, and verify those that were converted (in Ready to Move status). > [!NOTE] > Note > > - The Reason column provides a detailed explanation of why a particular component may have encountered a problem and the disposition of the element. > - The Converted status indicates that the components were converted to Cloud Construct while preserving existing configurations, such as column input types, events, validations, link to page criteria, menu links, and other configurations. The WebApp conversion is now successful. > [!NOTE] > Note > > This conversion process is highly dependent on a successful, recent datastore scan of the database hosting the WebApp’s SQL objects. Incorrect or incomplete database schema or SQL objects, such as views and stored procedures, in the datastore scan will require additional configuration work for the new WebApp in Cloud Construct. Click the **WebApp Link** to access the converted WebApp configuration in Cloud Construct. > [!NOTE] > Note > > Only compatible column input types are converted and created as Datasets in Cloud Construct. ## Stored Procedure Validations Instead of a RETURN statement, a stored procedure validation needs to have a THROW statement. Unfortunately, a Stored Procedure Validation can only display (THROW) an error or return (RETURN) an integer value, you may need to create a copy and replace the RETURN statement with a THROW statement as shown in the example below. ```sql CREATE PROCEDURE [dbo].[webCustomerMaster_TAXJURCODE_ConstructPreviewVersionVal]  @ID INT,  @KTOKD NVARCHAR(4) AS BEGIN DECLARE @TaxCode NVARCHAR(255) SELECT @TaxCode = COALESCE(TAXJURCODE, STCD1, STCD2) FROM ttCustomerMaster WHERE ID = @ID AND KTOKD = @KTOKD IF @TaxCode = '' OR @TaxCode IS NULL --RETURN 1 --This is now replaced by a THROW statement. THROW 99999,'Missing Tax Code',1 END ``` ## Related Articles - [Build Assist](/v1/docs/build-assist) - [Catalogs](/v1/docs/catalogs) - [Configure Column Properties](/v1/docs/configure-column-properties) - [Configure WebApp Groups](/v1/docs/configure-webapp-groups) - [Configure WebApp Menu](/v1/docs/configure-webapp-menu) - [Construct Events](/v1/docs/construct-events) - [Data Sources](/v1/docs/data-sources) - [Datasets](/v1/docs/datasets) - [Datastores](/v1/docs/datastores) - [Dictionaries](/v1/docs/dictionaries) - [Methodology Updates in Construct Preview](/v1/docs/methodology-updates-in-construct-preview) - [Security Profiles](/v1/docs/security-profiles) - [Working with the JSON Editor](/v1/docs/working-with-the-json-editor-1)