diff --git a/learn/app-development/services/database-services/working-stored-procedures.md b/learn/app-development/services/database-services/working-stored-procedures.md index 271f5cfb6..bb09f69b1 100644 --- a/learn/app-development/services/database-services/working-stored-procedures.md +++ b/learn/app-development/services/database-services/working-stored-procedures.md @@ -162,7 +162,7 @@ For all queries and procedures, there will be a Rest API generated with the Serv Both _Request_ and _Response_ POJO classes are generated as: `Request/Response` -1. These classes are generated in a package: `.models.procedure` 2. Response classes generated for all procedures having at least one return property i.e OUT parameter or cursor. **Example**: a procedure with name `getEmployees` will generate `GetEmployeesResponse` class with the returned columns. diff --git a/learn/app-development/services/database-services/working-with-queries.md b/learn/app-development/services/database-services/working-with-queries.md index 657fd4521..c1ac7b8cc 100644 --- a/learn/app-development/services/database-services/working-with-queries.md +++ b/learn/app-development/services/database-services/working-with-queries.md @@ -176,7 +176,7 @@ For all queries and procedures, there will be a Rest API generated with the Serv ### Models Both _Request_ and _Response_ POJO classes are generated as: `Request/Response` -- These classes are generated in a package: .models.query +- These classes are generated in a package: `.models.query` - Response class is generated only for SELECT queries. The return type for Non-Select queries will be integer hence POJO class is not generated. **Example**: query with name **getAllEmployees** will generate **GetAllEmployeesResponse** class with all returned columns. diff --git a/learn/app-development/services/db-services/working-with-queries.md b/learn/app-development/services/db-services/working-with-queries.md index 19a9bf7b6..3bcc36641 100644 --- a/learn/app-development/services/db-services/working-with-queries.md +++ b/learn/app-development/services/db-services/working-with-queries.md @@ -159,7 +159,7 @@ For all queries and procedures, there will be a Rest API generated with the Serv **Understanding generated Code** _File structure_ [![](/learn/assets/queryproc_files.png)](/learn/assets/queryproc_files.png)_Models_: Both _Request_ and _Response_ POJO classes are generated as: <queryName> Request/Response -- These classes are generated in a package: .models.query +- These classes are generated in a package: `.models.query` - Response class is generated only for SELECT queries. The return type for Non-Select queries will be integer hence POJO class is not generated. Eg: query with name **getAllEmployees** will generate **GetAllEmployeesResponse** class with all returned columns. - For HQL queries existing Model classes will be used if possible, else a Response model similar to Native queries will be generated. - Eg: query `from Employee;` @@ -170,7 +170,7 @@ For all queries and procedures, there will be a Rest API generated with the Serv _Services_: This layer exposes the methods related to the configured query and procedures. Controller layer uses these methods to complete the user requests. We recommend using methods from this layer in custom Java services. -- Class with name QueryExecutorService is generated in the package .service For eg: for Service **hrdb**, class name will be **HrdbQueryExecutorService** +- Class with name QueryExecutorService is generated in the package `.service` For eg: for Service **hrdb**, class name will be **HrdbQueryExecutorService** - Method with name **execute<queryName>** will be generated for all configured queries - For SELECT and DELETE queries, all parameters are configured as arguments for that method. In the case of Paginated request Pageable argument is added to the method signature. - For INSERT and UPDATE queries, **<queryName>Request** is the argument. @@ -181,7 +181,7 @@ _Services_: This layer exposes the methods related to the configured query and p [![](/learn/assets/query_files_service.png)](/learn/assets/query_files_service.png)_Controllers_: -- Separate controller classes are generated for query and procedures with names as **QueryExecutorController** and **ProcedureExecutorController** respectively in package **.controller**. +- Separate controller classes are generated for query and procedures with names as **QueryExecutorController** and **ProcedureExecutorController** respectively in package **`.controller`**. - Rest API is generated for each configured query and procedure. Generated method signature will be same as service layer method signature. - For methods returning INT type, controller layer returns **IntegerWrapper**. diff --git a/website/blog/2021-12-13-zero-day-vulnerability.md b/website/blog/2021-12-13-zero-day-vulnerability.md index 1dfa62068..0fab2890b 100644 --- a/website/blog/2021-12-13-zero-day-vulnerability.md +++ b/website/blog/2021-12-13-zero-day-vulnerability.md @@ -42,7 +42,7 @@ WaveMaker Enterprise users should continue to follow the risk mitigation provide A zero-day vulnerability is an unintentional software security flaw identified in the application, poses a zero-day threat. -A new [zero-day vulnerability](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228) was reported in the Log4j2 library on 9th Dec 2021, **affecting the library versions >=2.0-beta9 and <=2.14**. It has the potential to allow an attacker to execute the code remotely. Log4j has provided the fix by releasing the 2.15.0 version on the same day. Plus, Log4j has released a newer 2.17.0 version, which is available for production now. For more information, see [LOG4J changes report](https://logging.apache.org/log4j/2.x/changes-report.html#a2.17.0). +A new [zero-day vulnerability](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228) was reported in the Log4j2 library on 9th Dec 2021, **affecting the library versions `>=2.0-beta9` and `<=2.14`**. It has the potential to allow an attacker to execute the code remotely. Log4j has provided the fix by releasing the 2.15.0 version on the same day. Plus, Log4j has released a newer 2.17.0 version, which is available for production now. For more information, see [LOG4J changes report](https://logging.apache.org/log4j/2.x/changes-report.html#a2.17.0). diff --git a/website/blog/2022-01-10-cordova-android-change-in-webview-url.md b/website/blog/2022-01-10-cordova-android-change-in-webview-url.md index 97c29fbc3..eccd2e5ae 100644 --- a/website/blog/2022-01-10-cordova-android-change-in-webview-url.md +++ b/website/blog/2022-01-10-cordova-android-change-in-webview-url.md @@ -24,7 +24,7 @@ By default, this methodology gets implemented in all projects. If the hostname p ## Changes to note -In Android Apps, location.href now has the server domain as the host. All local app files are served at path **https://${server_domain}/_www**. +In Android Apps, location.href now has the server domain as the host. All local app files are served at path `https://${server_domain}/_www`. ## Additional Info diff --git a/website/blog/2022-03-24-saml-library-upgrade.md b/website/blog/2022-03-24-saml-library-upgrade.md index 9be55c01f..afab2f6ed 100644 --- a/website/blog/2022-03-24-saml-library-upgrade.md +++ b/website/blog/2022-03-24-saml-library-upgrade.md @@ -23,10 +23,10 @@ The new SAML library provided by spring suggests the metadata, audience url, SSO | URL Type | spring-security-saml2-core (Existing) | saml2-service-provider (New) | |---|---|---| -| Metadata | {app-url}/saml/metadata | {app-url}/saml2/service-provider-metadata/saml | -| Audience | {app-url}/saml/metadata | {app-url}/saml2/service-provider-metadata/saml | -| SSO | {app-url}/saml/SSO | {app-url}/login/saml2/sso/saml | -| SLO | {app-url}/saml/SingleLogout | {app-url}/logout/saml2/slo | +| Metadata | \{app-url}/saml/metadata | \{app-url}/saml2/service-provider-metadata/saml | +| Audience | \{app-url}/saml/metadata | \{app-url}/saml2/service-provider-metadata/saml | +| SSO | \{app-url}/saml/SSO | \{app-url}/login/saml2/sso/saml | +| SLO | \{app-url}/saml/SingleLogout | \{app-url}/logout/saml2/slo | Here app-url can be preview or deployed URL. diff --git a/website/blog/2022-08-02-Monitoring-performance-and-health-of-deployed-WaveMaker-app.md b/website/blog/2022-08-02-Monitoring-performance-and-health-of-deployed-WaveMaker-app.md index 068d802db..ba7d8f1b4 100644 --- a/website/blog/2022-08-02-Monitoring-performance-and-health-of-deployed-WaveMaker-app.md +++ b/website/blog/2022-08-02-Monitoring-performance-and-health-of-deployed-WaveMaker-app.md @@ -68,15 +68,15 @@ Here Zipkin server should be accessible to the tomcat server. Navigate to the maven `pom.xml` file to add following dependencies code snippet `$WMAPP_HOME---->pom.xml` - - - - io.opentelemetry - opentelemetry-sdk - 1.11.0 - - - +```xml + + + io.opentelemetry + opentelemetry-sdk + 1.11.0 + + +``` Navigate to the `project-user-spring.xml` in the below path and add the given snippet diff --git a/website/blog/2023-09-05-xml-to-java-configuration-migration.md b/website/blog/2023-09-05-xml-to-java-configuration-migration.md index c3777f56c..fbf1c1141 100644 --- a/website/blog/2023-09-05-xml-to-java-configuration-migration.md +++ b/website/blog/2023-09-05-xml-to-java-configuration-migration.md @@ -28,6 +28,6 @@ As a part of release 11.4, the following profile property names have been auto-m |Old Property Name| New Property Name| |----|----| | security.providers | security.activeProviders | -| security.general.cors.{pathEntryName}.allowedOrigins | security.general.cors.pathEntries.{pathEntryName}.allowedOrigins | +| security.general.cors.\{pathEntryName}.allowedOrigins | security.general.cors.pathEntries.\{pathEntryName}.allowedOrigins | | security.providers.ad.groupSearchDisabled | security.providers.ad.roleMappingEnabled | | security.providers.ldap.groupSearchDisabled | security.providers.ldap.roleMappingEnabled | diff --git a/website/blog/2024-09-25-addressing-accessibility-issues.md b/website/blog/2024-09-25-addressing-accessibility-issues.md index 57d863cf7..37c21f9a6 100644 --- a/website/blog/2024-09-25-addressing-accessibility-issues.md +++ b/website/blog/2024-09-25-addressing-accessibility-issues.md @@ -31,7 +31,9 @@ In this new version, the component tree is significantly flattened, enabling aut For example, consider two scenarios: in one, we set the maximum depth level to 33 using Expo 50 and React Native 0.73, and in the second, we set it to 150 using Expo 51 and React Native 0.74. -
Expo 50 and React Native 0.73 +
+ +Expo 50 and React Native 0.73 ![Expo 50 and React Native 0.73](/learn/assets/expo50-reactnative-73.png) @@ -41,7 +43,9 @@ Beyond this level, Appium encounters a limitation, unable to expand or interact
-
Expo 51 and React Native 0.74 +
+ +Expo 51 and React Native 0.74 ![Expo 51 and React Native 0.74](/learn/assets/expo51-reactnative-74.png) diff --git a/website/blog/2024-10-11-11-9-migration.md b/website/blog/2024-10-11-11-9-migration.md index bfbbe3af9..c968c617d 100644 --- a/website/blog/2024-10-11-11-9-migration.md +++ b/website/blog/2024-10-11-11-9-migration.md @@ -42,7 +42,7 @@ In one of our previous release, we introduced a **parent POM** structure to mana * **Default App Runtime Dependencies:** Many default dependencies your application relies on are already included in the parent POM. During the 11.9 migration, any duplicate dependencies in your application POM that are also present in the parent POM will be removed to avoid redundancy. For instance, if Apache Commons Lang3 is declared in the application POM, it will be removed since it's already included in the parent POM. -* **Dependency Version Management:** If a dependency version is declared in the parent POM, both the version and any overrides using placeholders or properties will be removed from the application POM. This ensures that the application inherits the correct version from the parent POM. For example, if spring-security-oauth2-client has its version set through a property like ${spring.security.version}, both the version tag and the property will be removed, allowing the dependency to inherit the latest version from the parent POM. +* **Dependency Version Management:** If a dependency version is declared in the parent POM, both the version and any overrides using placeholders or properties will be removed from the application POM. This ensures that the application inherits the correct version from the parent POM. For example, if spring-security-oauth2-client has its version set through a property like `${spring.security.version}`, both the version tag and the property will be removed, allowing the dependency to inherit the latest version from the parent POM. **Before Migration** diff --git a/website/versioned_docs/version-v10.14/app-development/app-security/authentication.md b/website/versioned_docs/version-v10.14/app-development/app-security/authentication.md index 33d1a6908..2a72d1487 100755 --- a/website/versioned_docs/version-v10.14/app-development/app-security/authentication.md +++ b/website/versioned_docs/version-v10.14/app-development/app-security/authentication.md @@ -160,7 +160,7 @@ WaveMaker allows you to authenticate your apps with OpenID. Setting the Security ### Service Provider Information - **Redirect URL** is pre-populated by WaveMaker and is not editable. You need to copy this link and use it to as the callback URL in Provider app settings page when you register the app. - If the application is deployed outside of WaveMaker then the redirect URL for the deployed applications will be in the below format. - **"https:////oauth2/code/{providerid}"**. + `https:////oauth2/code/{providerid}`. ### Integration Information - Client Credentials issued once your app is registered with the Provider. It will be in the form of **Client ID** and **Client Secret**. diff --git a/website/versioned_docs/version-v10.14/app-development/app-security/saml-integration.md b/website/versioned_docs/version-v10.14/app-development/app-security/saml-integration.md index 57a24f909..f92f18bc3 100755 --- a/website/versioned_docs/version-v10.14/app-development/app-security/saml-integration.md +++ b/website/versioned_docs/version-v10.14/app-development/app-security/saml-integration.md @@ -129,31 +129,31 @@ During the app development in WaveMaker, application URLs like Metadata, Audienc - the **Metadata URL** during development would look like this: - https://wavemakeronline.com/studio/services/saml/metadata + `https://wavemakeronline.com/studio/services/saml/metadata` whereas, for deployment app, the URL should typically look like: - (http/https)://{hostname}/{appname}/saml/metadata + `(http/https)://{hostname}/{appname}/saml/metadata` - the **Audience URL** during development would look like this: - https://wavemakeronline.com/{tenantid}/{appname}/saml/SSO + `https://wavemakeronline.com/{tenantid}/{appname}/saml/SSO` whereas, for deployment app, the URL should typically look like: - (http/https)://{hostname}/{appname}/saml/SSO + `(http/https)://{hostname}/{appname}/saml/SSO` - the Single Signout URL during development would look like this: - https://wavemakeronline.com/studio/services/saml/SingleLogout + `https://wavemakeronline.com/studio/services/saml/SingleLogout` whereas, for deployment app, the URL should typically look like: - (http/https)://{hostname}/{appname}/saml/SingleLogout + `(http/https)://{hostname}/{appname}/saml/SingleLogout` :::note -You can get the {hostname} by looking at the URL of any deployed app from your account. It will typically be of the format: `tenant_id.cloud.wavemakeronline.com` for apps deployed to WaveMaker Cloud (ref [Managed Deployed App](/learn/app-development/deployment/manage-deployed-apps/) for details). +You can get the `{hostname}` by looking at the URL of any deployed app from your account. It will typically be of the format: `tenant_id.cloud.wavemakeronline.com` for apps deployed to WaveMaker Cloud (ref [Managed Deployed App](/learn/app-development/deployment/manage-deployed-apps/) for details). ::: ## Collaboration in Application that is configured with SAML diff --git a/website/versioned_docs/version-v10.14/app-development/dev-integration/developer-collaboration.md b/website/versioned_docs/version-v10.14/app-development/dev-integration/developer-collaboration.md index f62ef28ed..d967cce9f 100755 --- a/website/versioned_docs/version-v10.14/app-development/dev-integration/developer-collaboration.md +++ b/website/versioned_docs/version-v10.14/app-development/dev-integration/developer-collaboration.md @@ -33,7 +33,7 @@ One need not be on the same email domain to collaborate on the project. ## Change Roles - Once the user is added as Project Admin/Contributor, the role can be changed. To change the role of the existing member, click on More options and select Add as Project Admin/Add as Contributor option. -- It opens a  confirmation dialog saying `` role will be changed from `` to in ``. Click OK button to confirm. +- It opens a  confirmation dialog saying `` role will be changed from `` to `` in ``. Click OK button to confirm. [Refer here](/learn/app-development/wavemaker-overview/project-user-management/#roles) to know more about the Roles. diff --git a/website/versioned_docs/version-v10.14/app-development/services/database-services/orm-artifacts.md b/website/versioned_docs/version-v10.14/app-development/services/database-services/orm-artifacts.md index bd3566169..72c78da55 100755 --- a/website/versioned_docs/version-v10.14/app-development/services/database-services/orm-artifacts.md +++ b/website/versioned_docs/version-v10.14/app-development/services/database-services/orm-artifacts.md @@ -268,9 +268,9 @@ Supported value expression types are listed in below table | equals | = | Number or String | Values that equals to given value | - `empId=1` - `firstname=’Eric’` | | not equals | `!=` (or) `< >` | Number or String | Values that are not equal to given value | - `zip!=02127` - `jobTitle< >‘Engineer’` | | between | between | Date or Number | Values between given range | - birthdate between '1973-10-21' and '1986-06-18' (using date format - YYYY-MM-DD) - zip between 14231 and 15922 | -| less than | < | Number | Values less than given value | - empId<6 | +| less than | < | Number | Values less than given value | - empId<6 | | greater than | > | Number | Values greater than given value | - deptId>10 | -| less than or equal to | <= | Number | Values less or equal to given value | - empId<=4 | +| less than or equal to | <= | Number | Values less or equal to given value | - empId<=4 | | greater than or equal to | >= | Number | Values greater than or equal to given value | - zip>=11 | | pattern matching | like | String | Values matching the given pattern |- street like ‘4%Houston%’ | | starts with | like | String | Values starting with the given string | - firstname like ‘E%’ | diff --git a/website/versioned_docs/version-v10.14/app-development/services/database-services/temporal-support.md b/website/versioned_docs/version-v10.14/app-development/services/database-services/temporal-support.md index 5dc44509a..beab9897a 100755 --- a/website/versioned_docs/version-v10.14/app-development/services/database-services/temporal-support.md +++ b/website/versioned_docs/version-v10.14/app-development/services/database-services/temporal-support.md @@ -92,7 +92,7 @@ _periods_ This API returns the history data for the temporal table by applying g 5. q [optional]: query to filter the history data. 6. Pageable [optional]: pagination information.  -- _/periods/{id} (or) /periods/composite-id_ This Api returns the history data for given id and by applying given filters. +- _/periods/\{id} (or) /periods/composite-id_ This Api returns the history data for given id and by applying given filters. ### Method: GET Parameters 1. Id columns information as specified for normal findById API. diff --git a/website/versioned_docs/version-v10.14/app-development/services/database-services/working-stored-procedures.md b/website/versioned_docs/version-v10.14/app-development/services/database-services/working-stored-procedures.md index f539610e0..8933caff2 100755 --- a/website/versioned_docs/version-v10.14/app-development/services/database-services/working-stored-procedures.md +++ b/website/versioned_docs/version-v10.14/app-development/services/database-services/working-stored-procedures.md @@ -138,7 +138,7 @@ For all queries and procedures, there will be a Rest API generated with the Serv Both _Request_ and _Response_ POJO classes are generated as: `Request/Response` -1. These classes are generated in a package: `.models.procedure` 2. Response classes generated for all procedures having at least one return property i.e OUT parameter or cursor. **Example**: diff --git a/website/versioned_docs/version-v10.14/app-development/services/database-services/working-with-queries.md b/website/versioned_docs/version-v10.14/app-development/services/database-services/working-with-queries.md index 1c5a378b8..2a7552a36 100755 --- a/website/versioned_docs/version-v10.14/app-development/services/database-services/working-with-queries.md +++ b/website/versioned_docs/version-v10.14/app-development/services/database-services/working-with-queries.md @@ -176,7 +176,7 @@ For all queries and procedures, there will be a Rest API generated with the Serv ### Models Both _Request_ and _Response_ POJO classes are generated as: `Request/Response` -- These classes are generated in a package: .models.query +- These classes are generated in a package: `.models.query` - Response class is generated only for SELECT queries. The return type for Non-Select queries will be integer hence POJO class is not generated. **Example**: query with name **getAllEmployees** will generate **GetAllEmployeesResponse** class with all returned columns. diff --git a/website/versioned_docs/version-v10.14/app-development/services/db-services/orm-artifacts.md b/website/versioned_docs/version-v10.14/app-development/services/db-services/orm-artifacts.md index a3b777fcb..446991be7 100755 --- a/website/versioned_docs/version-v10.14/app-development/services/db-services/orm-artifacts.md +++ b/website/versioned_docs/version-v10.14/app-development/services/db-services/orm-artifacts.md @@ -53,24 +53,24 @@ Import or creation of database within a WaveMaker app results in the auto-genera ### CRUD APIs 1. **CREATE** Inserts a record into the table _URL_: / _Request Type_: POST _Path Variables_: None _Request Parameter_: None _Request Body_: object in JSON format _Method Name Example_: createEmployee [![](/learn/assets/db_apis_create.png)](/learn/assets/db_apis_create.png) -2. **READ (primary key based)** Retrieves the data associated with given ID value _URL_: /{id} _Request Type_: GET _Path Variables_: primary key column value _Request Parameter_: None _Request Body_: none _Method Name Example_: getEmployee [![](/learn/assets/db_apis_readpk.png)](/learn/assets/db_apis_readpk.png) -3. **READ (unique key based)** Retrieves the data associated with given unique key value _URL_: /[UNIQUE_KEY]/{unique_key_value} _Request Type_: GET _Path Variables_: unique key column value _Request Parameter_: None _Request Body_: none _Method Name Example_: getByDeptCode (unique key for department entity) [![](/learn/assets/db_apis_readuk.png)](/learn/assets/db_apis_readuk.png) -4. **READ (foreign key based)** Retrieves the data associated with given ID value from the related table _URL_: /{id..+}/[relation_field] _Request Type_: GET _Path Variables_: primary key column value _Request Parameter_: +2. **READ (primary key based)** Retrieves the data associated with given ID value _URL_: /\{id} _Request Type_: GET _Path Variables_: primary key column value _Request Parameter_: None _Request Body_: none _Method Name Example_: getEmployee [![](/learn/assets/db_apis_readpk.png)](/learn/assets/db_apis_readpk.png) +3. **READ (unique key based)** Retrieves the data associated with given unique key value _URL_: /[UNIQUE_KEY]/\{unique_key_value} _Request Type_: GET _Path Variables_: unique key column value _Request Parameter_: None _Request Body_: none _Method Name Example_: getByDeptCode (unique key for department entity) [![](/learn/assets/db_apis_readuk.png)](/learn/assets/db_apis_readuk.png) +4. **READ (foreign key based)** Retrieves the data associated with given ID value from the related table _URL_: /\{id..+}/[relation_field] _Request Type_: GET _Path Variables_: primary key column value _Request Parameter_: - Page, - Size, - Sort _Request Body_: none _Method Name_: findAssociatedEmployees (employee foreign key for department entity) [![](/learn/assets/db_apis_readfk.png)](/learn/assets/db_apis_readfk.png) -5. **READ (foreign key based - self-referential)** Retrieves the data associated with given ID value _URL_: /{id..+}/[relation_field] _Request Type_: GET _Path Variables_: primary key column value _Request Parameter_: +5. **READ (foreign key based - self-referential)** Retrieves the data associated with given ID value _URL_: /\{id..+}/[relation_field] _Request Type_: GET _Path Variables_: primary key column value _Request Parameter_: - Page, - Size, - Sort _Request Body_: none _Method Name_: findAssociatedEmployeesForManagerId (foreign key) [![](/learn/assets/db_apis_readsr.png)](/learn/assets/db_apis_readsr.png) -6. **UPDATE** Updates entity record associated with the given id value _URL_: /{id} _Request Type_: PUT _Path Variables_: primary key column value _Request Parameter_: None _Request Body_: object in JSON format _Method Name Example_: editEmployee [![](/learn/assets/db_apis_update.png)](/learn/assets/db_apis_update.png) -7. **DELETE** Deletes entity record associated with the given id _URL_: /{id} _Request Type_: DELETE _Path Variables_: primary key column value _Request Parameter_: None _Request Body_: None _Method Name Example_: deleteEmployee [![](/learn/assets/db_apis_delete.png)](/learn/assets/db_apis_delete.png) +6. **UPDATE** Updates entity record associated with the given id value _URL_: /\{id} _Request Type_: PUT _Path Variables_: primary key column value _Request Parameter_: None _Request Body_: object in JSON format _Method Name Example_: editEmployee [![](/learn/assets/db_apis_update.png)](/learn/assets/db_apis_update.png) +7. **DELETE** Deletes entity record associated with the given id _URL_: /\{id} _Request Type_: DELETE _Path Variables_: primary key column value _Request Parameter_: None _Request Body_: None _Method Name Example_: deleteEmployee [![](/learn/assets/db_apis_delete.png)](/learn/assets/db_apis_delete.png) ### Query APIs @@ -95,7 +95,7 @@ Import or creation of database within a WaveMaker app results in the auto-genera - ExportOptions (Body) - custom query (optional, see here for [query syntax](#custom-query-syntax)), - - fields list (optional): [{ “header”:””, “field”:””, “expression”:”” (eg: (${field_name} (or) <any string>)) }] + - fields list (optional): `[{ “header”:””, “field”:””, “expression”:”” (eg: (${field_name} (or) <any string>)) }]` - exportType - data format for export can be EXCEL or CSV - fileName: exported file name. @@ -149,7 +149,7 @@ The APIs generated by WaveMaker for all the imported tables will have methods th | | less than | < | Number | Values less than given value | -- empId<6 +- empId<6 | | greater than | > | Number | Values greater than given value | @@ -157,9 +157,9 @@ The APIs generated by WaveMaker for all the imported tables will have methods th - deptId>10 | -| less than or equal to | <= | Number | Values less or equal to given value | +| less than or equal to | <= | Number | Values less or equal to given value | -- empId<=4 +- empId<=4 | | greater than or equal to | >= | Number | Values greater than or equal to given value | diff --git a/website/versioned_docs/version-v10.14/app-development/services/db-services/working-with-queries.md b/website/versioned_docs/version-v10.14/app-development/services/db-services/working-with-queries.md index ba51e908b..3947efd81 100755 --- a/website/versioned_docs/version-v10.14/app-development/services/db-services/working-with-queries.md +++ b/website/versioned_docs/version-v10.14/app-development/services/db-services/working-with-queries.md @@ -159,7 +159,7 @@ For all queries and procedures, there will be a Rest API generated with the Serv **Understanding generated Code** _File structure_ [![](/learn/assets/queryproc_files.png)](/learn/assets/queryproc_files.png)_Models_: Both _Request_ and _Response_ POJO classes are generated as: <queryName> Request/Response -- These classes are generated in a package: .models.query +- These classes are generated in a package: `.models.query` - Response class is generated only for SELECT queries. The return type for Non-Select queries will be integer hence POJO class is not generated. Eg: query with name **getAllEmployees** will generate **GetAllEmployeesResponse** class with all returned columns. - For HQL queries existing Model classes will be used if possible, else a Response model similar to Native queries will be generated. - Eg: query `from Employee;` @@ -170,18 +170,18 @@ For all queries and procedures, there will be a Rest API generated with the Serv _Services_: This layer exposes the methods related to the configured query and procedures. Controller layer uses these methods to complete the user requests. We recommend using methods from this layer in custom Java services. -- Class with name QueryExecutorService is generated in the package .service For eg: for Service **hrdb**, class name will be **HrdbQueryExecutorService** +- Class with name QueryExecutorService is generated in the package `.service` For eg: for Service **hrdb**, class name will be **HrdbQueryExecutorService** - Method with name **execute<queryName>** will be generated for all configured queries - For SELECT and DELETE queries, all parameters are configured as arguments for that method. In the case of Paginated request Pageable argument is added to the method signature. - For INSERT and UPDATE queries, **<queryName>Request** is the argument. - - For all SELECT queries **<queryName>Response** object is returned. In case of Paginated, returns **Page<<queryName>Response>**. + - For all SELECT queries **<queryName>Response** object is returned. In case of Paginated, returns **Page<queryName>Response**. - In the case of HQL query and queries returning existing types, the return type will be the existing type. - For non-select queries, it returns INT. - Export API is added for queries which will return Paginated data. Method name will be **export<queryName>** and which takes same arguments as execute method (as mentioned above). [![](/learn/assets/query_files_service.png)](/learn/assets/query_files_service.png)_Controllers_: -- Separate controller classes are generated for query and procedures with names as **QueryExecutorController** and **ProcedureExecutorController** respectively in package **.controller**. +- Separate controller classes are generated for query and procedures with names as **QueryExecutorController** and **ProcedureExecutorController** respectively in package **`.controller`**. - Rest API is generated for each configured query and procedure. Generated method signature will be same as service layer method signature. - For methods returning INT type, controller layer returns **IntegerWrapper**. diff --git a/website/versioned_docs/version-v10.14/app-development/services/web-services/web-services/working-with-soap-services.md b/website/versioned_docs/version-v10.14/app-development/services/web-services/web-services/working-with-soap-services.md index 5f27c679d..d0ed652d5 100755 --- a/website/versioned_docs/version-v10.14/app-development/services/web-services/web-services/working-with-soap-services.md +++ b/website/versioned_docs/version-v10.14/app-development/services/web-services/web-services/working-with-soap-services.md @@ -87,7 +87,7 @@ By default package name is set to the project base package name by the platform Name collisions happen while code generation when there is more than one schema definition with the same name that can be from two different external schema files. Following example depicts the collision of element “root”, because this element is defined twice in two different namespaces: - +```xml - +``` These collisions can be avoided either by implicit handling by the platform or manual handling using an xjb file. **Implicit handling of name collisions** @@ -132,11 +132,11 @@ In manual handling, you have to write an _xjb_ file which defines the customizat **Writing XJB files** -XJB bindings can be customized by defining separate element for each namespace, which selects the node with given targetNamespace within the WSDL document. - - element should define which describes customization of package names/class names in code generation for selected node: +XJB bindings can be customized by defining separate `` element for each namespace, which selects the node with given targetNamespace within the WSDL document. +```xml + +``` +Inside the `` element should define which describes customization of package names/class names in code generation for selected node: 1. Suffixing all the classes generated from the schema ``` diff --git a/website/versioned_docs/version-v10.14/app-development/variables/crud-variable.md b/website/versioned_docs/version-v10.14/app-development/variables/crud-variable.md index e0c2dca5f..1226181b2 100755 --- a/website/versioned_docs/version-v10.14/app-development/variables/crud-variable.md +++ b/website/versioned_docs/version-v10.14/app-development/variables/crud-variable.md @@ -222,7 +222,7 @@ This method can also be used to set all the specified key-value pairs as input f #### `delete.setInput(object)` #### Parameters -- **Object**: key-value pairs {“key”: “value”,…} +- **Object**: key-value pairs `{“key”: “value”,…}` #### Return Value - Updated `inputFields` object diff --git a/website/versioned_docs/version-v10.14/app-development/variables/database-crud.md b/website/versioned_docs/version-v10.14/app-development/variables/database-crud.md index 380e1c0b9..f80afa057 100755 --- a/website/versioned_docs/version-v10.14/app-development/variables/database-crud.md +++ b/website/versioned_docs/version-v10.14/app-development/variables/database-crud.md @@ -300,7 +300,7 @@ This method makes a call to the Live Service to delete the passed record in the **Parameters**: -- **options**(object): This object can have optional fields as row - record object to be deleted as {"key":"value"} +- **options**(object): This object can have optional fields as row - record object to be deleted as `{"key":"value"}` - **successCallback**(method): callback method called on successful invocation of the variable. - **errorCallback**(method): callback method called if an error is encountered while invocation. @@ -377,7 +377,7 @@ var lv = Page.Variables.HrdbEmployeeData; This method can also be used to set all the specified key-value pairs as input fields in the variable. -**Parameters**: inputData(object) object or key-value pairs {“key”: “value”,…} +**Parameters**: inputData(object) object or key-value pairs `{“key”: “value”,…}` **Return Value**: Updated inputFields object @@ -414,7 +414,7 @@ var lv = Page.Variables.HrdbEmployeeData; This method can also be used to set all the specified key-value pairs as filter fields in the variable. -**Parameters**: inputData(object) object or key-value pairs {“key”: “value”,…} +**Parameters**: inputData(object) object or key-value pairs `{“key”: “value”,…}` **Return Value**: Updated filterFields object diff --git a/website/versioned_docs/version-v10.14/app-development/variables/java-services.md b/website/versioned_docs/version-v10.14/app-development/variables/java-services.md index 44c1d76ab..e600f75e0 100755 --- a/website/versioned_docs/version-v10.14/app-development/variables/java-services.md +++ b/website/versioned_docs/version-v10.14/app-development/variables/java-services.md @@ -162,7 +162,7 @@ var sv = Page.Variables.[variable_name]; This method can also be used to set all the specified key-value pairs as input fields in the variable. -**Parameters**: inputData(object) object or key-value pairs {“key”: “value”,…} +**Parameters**: inputData(object) object or key-value pairs `{“key”: “value”,…}` **Return Value**: Updated inputFields object diff --git a/website/versioned_docs/version-v10.14/app-development/variables/security-service.md b/website/versioned_docs/version-v10.14/app-development/variables/security-service.md index fd24d50cf..08fa6bfcd 100755 --- a/website/versioned_docs/version-v10.14/app-development/variables/security-service.md +++ b/website/versioned_docs/version-v10.14/app-development/variables/security-service.md @@ -146,7 +146,7 @@ var sv = Page.Variables.[variable_name]; This method can also be used to set all the specified key-value pairs as input fields in the variable. -**Parameters**: inputData(object) object or key-value pairs {“key”: “value”,…} +**Parameters**: inputData(object) object or key-value pairs `{“key”: “value”,…}` **Return Value**: Updated inputFields object diff --git a/website/versioned_docs/version-v10.14/app-development/variables/timer-action.md b/website/versioned_docs/version-v10.14/app-development/variables/timer-action.md index 6876ba772..42ae7e742 100755 --- a/website/versioned_docs/version-v10.14/app-development/variables/timer-action.md +++ b/website/versioned_docs/version-v10.14/app-development/variables/timer-action.md @@ -46,13 +46,13 @@ Once a Timer Action is triggered, if it is Page scoped, then the action (and its 1. Call a Variable that fetches the updates from Employee database with the latest after every 30 seconds. [![](/learn/assets/var_timer_props.png)](/learn/assets/var_timer_props.png) [![](/learn/assets/var_timer_event.png)](/learn/assets/var_timer_event.png) 2. A Variable that gives Facebook-like feeds after a certain timestamp. Assign Javascript to the onTimerFire event and write following logic. Once the Timer Action is triggered, if repeating property is set, then the variable will be invoked after every delay milliseconds. - +```js Page.timerAction1onTimerFire = function(variable, data){ // set the dynamic input on the variable Page.Variables.WebServiceVariabe.setInput('timestamp', Date.now()); Page.Variables.WebServiceVariabe.invoke(); }; - +```   # Methods diff --git a/website/versioned_docs/version-v10.14/app-development/widgets/datalive/datatable/events-methods.md b/website/versioned_docs/version-v10.14/app-development/widgets/datalive/datatable/events-methods.md index 694af907e..ee1d4296a 100755 --- a/website/versioned_docs/version-v10.14/app-development/widgets/datalive/datatable/events-methods.md +++ b/website/versioned_docs/version-v10.14/app-development/widgets/datalive/datatable/events-methods.md @@ -12,6 +12,7 @@ Live Form behavior can be customized with the help of the call-back events. The | --- | --- | | On before service call | This event will be called on saving the live form. Any validation checks can be performed here. Returning false from the script will stop the live form save. | | | +```js Page.liveform1Beforeservicecall = function($event, $operation, $data) { //$operation: Current operation being performed - INSERT or UPDATE or DELETE //$data has the data of the all widgets inside the live form. This data can be modified and validated before sending the request. @@ -27,37 +28,37 @@ Page.liveform1Beforeservicecall = function($event, $operation, $data) { } return isValidData($data) }; - +``` | | On result | This event will be called after the live form is saved and API returns a response. The event is triggered in both success and failure cases. | | | - +```js Page.liveform1Result = function($event, $operation, $data) { //$operation: operation performed - INSERT or UPDATE or DELETE //$data has the response returned from the API. console.log("server response:", $data); }; - +``` | | On success | This event will be called after the live form is saved and API returns a success response. | | | - +```js Page.liveform1Success = function($event, $operation, $data) { //$operation: operation performed - INSERT or UPDATE or DELETE //$data has the response returned from the API. console.log("The inserted/updated/deleted data:", $data); }; - +``` | | On error | This event will be called after the live form is saved and API returns a failure response. | | | - +```js Page.liveform1Error = function($event, $operation, $data) { //$operation: operation performed - INSERT or UPDATE or DELETE //$data has the error message returned from the API. console.log("Error returned from server:", $data); }; - +``` | # Methods @@ -68,23 +69,23 @@ For the following script samples, we are considering the _hrdb_ _Employee_ table - To delete a record: - Page.Widgets.EmployeeForm.delete(); //Deletes the current record that is bound to EmployeeForm. + `Page.Widgets.EmployeeForm.delete();` //Deletes the current record that is bound to EmployeeForm. - To update a record: - Page.Widgets.EmployeeForm.save(); //Updates the current record bound + `Page.Widgets.EmployeeForm.save();` //Updates the current record bound - To add a new record: - Page.Widgets.EmployeeForm.new(); //Adds a new record to dataset that is bound to EmployeeForm. + `Page.Widgets.EmployeeForm.new();` //Adds a new record to dataset that is bound to EmployeeForm. - To reset a form: - Page.Widgets.EmployeeForm.reset(); //Resets the form to initial state. + `Page.Widgets.EmployeeForm.reset();` //Resets the form to initial state. - To cancel an edit operation: - Page.Widgets.EmployeeForm.cancel(); //Cancels the form edit. + `Page.Widgets.EmployeeForm.cancel();` //Cancels the form edit.   diff --git a/website/versioned_docs/version-v10.14/app-development/widgets/datalive/form.md b/website/versioned_docs/version-v10.14/app-development/widgets/datalive/form.md index 0817d7133..c3395061b 100755 --- a/website/versioned_docs/version-v10.14/app-development/widgets/datalive/form.md +++ b/website/versioned_docs/version-v10.14/app-development/widgets/datalive/form.md @@ -57,7 +57,7 @@ Set the alignment of the form. You can choose from the left, center, right, and #### Position -Set the position of the input field and label placement as shown in the image above: {label: field}, {field: label}, {label: field below}. +Set the position of the input field and label placement as shown in the image above: `{label: field}`, `{field: label}`, `{label: field below}`. #### Layout Style diff --git a/website/versioned_docs/version-v10.14/app-development/widgets/datalive/form/select-locale.md b/website/versioned_docs/version-v10.14/app-development/widgets/datalive/form/select-locale.md index 7e4f5f975..c34dd329c 100755 --- a/website/versioned_docs/version-v10.14/app-development/widgets/datalive/form/select-locale.md +++ b/website/versioned_docs/version-v10.14/app-development/widgets/datalive/form/select-locale.md @@ -10,9 +10,9 @@ There are three ways that Localization comes into effect: 1. WaveMaker automatically detects the user's preferred locales (from the browser) and renders the application with the locale of the user's preference if the application supports. If not, displays the application in the default language configured in application settings. 2. The user can be given a choice to select the language using the Select Locale widget. 3. You can also choose to trigger the language switch through user events like button click from JavaScript, the following snippet changes language to English: - +```js App.changeLocale({'datavalue': 'en'}) - +``` ## Properties diff --git a/website/versioned_docs/version-v10.14/app-development/widgets/modal-dialogs/modal-windows-dialogs.md b/website/versioned_docs/version-v10.14/app-development/widgets/modal-dialogs/modal-windows-dialogs.md index b8148f934..4a5b41df3 100755 --- a/website/versioned_docs/version-v10.14/app-development/widgets/modal-dialogs/modal-windows-dialogs.md +++ b/website/versioned_docs/version-v10.14/app-development/widgets/modal-dialogs/modal-windows-dialogs.md @@ -72,18 +72,18 @@ Page Dialog is a popup window that displays page content and can be dismissed by **Dialog** widget in your project can be accessed by associating the open and _close_ properties of the dialog with an event of any other widget. The dialog can be accessed through scripting by adding _DialogService_ to the _page controller_ and adding the code for _open_ and _close_ as shown below, here we are displaying an alert dialog on click of a button: Click event of the button should trigger the following JavaScript code: - +```js Page.button3Click = function($event, widget) { Page.Widgets.alertdialog1.open(); } - +``` For hiding dialog: - +```js /** function called on button1 click **/ Page.button1Click = function($event, widget) { Page.Widgets.alertdialog1.close(); }; - +``` ## Properties & Events ### **Alert Dialog Properties** diff --git a/website/versioned_docs/version-v10.14/how-tos/aws-s3-connector.md b/website/versioned_docs/version-v10.14/how-tos/aws-s3-connector.md index 955f565a2..e22cc3c1e 100755 --- a/website/versioned_docs/version-v10.14/how-tos/aws-s3-connector.md +++ b/website/versioned_docs/version-v10.14/how-tos/aws-s3-connector.md @@ -19,7 +19,7 @@ This connector exposes api to interact with AWS S3 from WaveMaker application. ## Step 2: Configure aws-s3-connector properties in profiles 1. By default externalized connector properties are added in the project profiles [Know More](/learn/connectors/connectors-import#externalizing-connector-properties). -2. Connector externalized properties are prefixed with **connector.${connectorName}** +2. Connector externalized properties are prefixed with `connector.${connectorName}` ```Java connector.aws-s3-connector.default.aws.accessKey= diff --git a/website/versioned_docs/version-v10.14/how-tos/azure-file-storage-connector.md b/website/versioned_docs/version-v10.14/how-tos/azure-file-storage-connector.md index 7f083c73c..2936a6a8d 100755 --- a/website/versioned_docs/version-v10.14/how-tos/azure-file-storage-connector.md +++ b/website/versioned_docs/version-v10.14/how-tos/azure-file-storage-connector.md @@ -31,7 +31,7 @@ The process shows how to upload, download or delete file in storage account: ## Step 2: Configure azurefilestorage properties in profiles 1. By default externalized connector properties are added in the project profiles [Know More](/learn/connectors/connectors-import#externalizing-connector-properties). -2. Connector externalized properties are prefixed with **connector.${connectorName}** +2. Connector externalized properties are prefixed with `connector.${connectorName}` ` connector.azurefilestorage.default.azure.connectionString= diff --git a/website/versioned_docs/version-v10.14/how-tos/capturing-card-items.md b/website/versioned_docs/version-v10.14/how-tos/capturing-card-items.md index e8c9394bc..c6c7fce47 100755 --- a/website/versioned_docs/version-v10.14/how-tos/capturing-card-items.md +++ b/website/versioned_docs/version-v10.14/how-tos/capturing-card-items.md @@ -4,18 +4,18 @@ id: "capturing-card-items" --- 1. **currentItem & currentItemWidgets**: These bind objects can be used to bind the current item of the list to any form widget placed within the list template. The currentItemWidgets can be accessed as the fourth argument of the events for widgets within the List. For example, button click event within List will result in the following code will capture the caption property of the Name label within a List: - +```js Page.button1Click = function($event, widgets, item, currentItemWidgets) { alert(currentItemWidgets.Name.caption); }; - +``` 2. **selecteditem & selectedItemWidgets**: These bind objects can be used to capture the selected item of the list when selection is enabled for the List. The return type would be array in case of multi-select List. Both selecteditem and selectedItemWidgets can be accessed through the script as follows, the click of a button will capture the selected item firstname and the caption of widget Name: - +```js Page.button1Click = function($event, widgets, item, currentItemWidgets) { alert(Page.Widgets.livelist1.selecteditem.firstname); alert(Page.Widgets.livelist1.selectedItemWidgets.Name.caption); }; - +``` [![list_bind](/learn/assets/list_bind.png)](/learn/assets/list_bind.png) diff --git a/website/versioned_docs/version-v10.14/how-tos/combining-columns-data-table.md b/website/versioned_docs/version-v10.14/how-tos/combining-columns-data-table.md index 03729af11..8e4af049c 100755 --- a/website/versioned_docs/version-v10.14/how-tos/combining-columns-data-table.md +++ b/website/versioned_docs/version-v10.14/how-tos/combining-columns-data-table.md @@ -19,9 +19,9 @@ You can combine two or more columns to be displayed in a single column in a Data 1. Go to Advanced Settings of the Data Table from the Properties panel 2. From the Columns tab, add two new columns - H1 and H2 3. In the View Mode section, enter the following for Value Expression: - +```js {{row.getProperty('q1') + row.getProperty('q2')}} - +``` This will add the content from columns q1 and q2 and set it as the content for H1 column. [![](/learn/assets/dt_ve_1.png)](/learn/assets/dt_ve_1.png) diff --git a/website/versioned_docs/version-v10.14/how-tos/data-table-actions.md b/website/versioned_docs/version-v10.14/how-tos/data-table-actions.md index 63b399b31..b372d0645 100755 --- a/website/versioned_docs/version-v10.14/how-tos/data-table-actions.md +++ b/website/versioned_docs/version-v10.14/how-tos/data-table-actions.md @@ -7,11 +7,11 @@ id: "data-table-actions" - We will add a Row Action in a Data Table to display an alert message on click. - The Action will be a JS function as shown below. Here we have written a function to display an alert dialog. **The name of the function is the action field entry in the custom button created.** - +```js Page.EmployeeTable1_customRowAction = function($event, row) { alert('hello'); }; - +``` diff --git a/website/versioned_docs/version-v10.14/how-tos/data-table-styling.md b/website/versioned_docs/version-v10.14/how-tos/data-table-styling.md index 7d8d8b324..3b1a722df 100755 --- a/website/versioned_docs/version-v10.14/how-tos/data-table-styling.md +++ b/website/versioned_docs/version-v10.14/how-tos/data-table-styling.md @@ -10,7 +10,7 @@ id: "data-table-styling" - Row to be displayed as warning when the value is New York _(row.city=='New York')_ The following style classes have been defined from the Style tab: - +```css .pink { background-color: #F8E0E0; } @@ -20,7 +20,7 @@ The following style classes have been defined from the Style tab: .green { background-color: #D8F6CE; } - +``` [Data Table Use Cases](/learn/app-development/widgets/datalive/datatable/data-table-use-cases/) diff --git a/website/versioned_docs/version-v10.14/how-tos/dynamic-data-tables.md b/website/versioned_docs/version-v10.14/how-tos/dynamic-data-tables.md index 41ce06d19..522fd7ef6 100755 --- a/website/versioned_docs/version-v10.14/how-tos/dynamic-data-tables.md +++ b/website/versioned_docs/version-v10.14/how-tos/dynamic-data-tables.md @@ -31,7 +31,7 @@ Here we will see how to create a dynamic grid based on the metadata returned fro 5. Rename the Data Table to “SVGrid” or any other valid name as per your scenario (this name is used in the JavaScript code later). [![](/learn/assets/dynamic_grid3.png)](/learn/assets/dynamic_grid3.png) 6. For the buttons placed on the canvas, navigate to the Events tab from the properties panel and choose JavaScript as operation for the **on Click** event. 7. Below is an example code snippet to change the grid dataset’s dynamically at runtime. - +```js Page.button1Click = function ($event, widget) { Page.Widgets.SVGrid.dataset = Page.Variables.DeptData.dataSet; }; @@ -39,7 +39,7 @@ Here we will see how to create a dynamic grid based on the metadata returned fro Page.button2Click = function ($event, widget) { Page.Widgets.SVGrid.dataset = Page.Variables.UserData.dataset; }; - +``` [![](/learn/assets/dynamic_grid4.png)](/learn/assets/dynamic_grid4.png) Using the above implementation steps, you will be able to successfully change the Data Table at runtime using multiple services. diff --git a/website/versioned_docs/version-v10.14/how-tos/fetch-default-number100-records-database.md b/website/versioned_docs/version-v10.14/how-tos/fetch-default-number100-records-database.md index 6d0976333..56cb2c7e2 100755 --- a/website/versioned_docs/version-v10.14/how-tos/fetch-default-number100-records-database.md +++ b/website/versioned_docs/version-v10.14/how-tos/fetch-default-number100-records-database.md @@ -17,7 +17,7 @@ To fetch greater than 100 records for the deployed application, you will need to We do not recommend fetching large number of records in a single call from server during development mode i.e., run-mode of the app for optimized performance. However, in case you would like to view the changes in the select widget in run mode, please follow the approach below: -1. Open File explorer --> --> profiles --> development.properties file. 2. Set db.datbaseName.maxPageSize to the required number. +1. Open File explorer --> `` --> profiles --> development.properties file. 2. Set db.datbaseName.maxPageSize to the required number. [![](/learn/assets/developmentprofile.png)](/learn/assets/developmentprofile.png)**Disclaimer:** It's not advised to change the number of records from development.properties file. **Recommendation:** It's recommended to use search widget with autocomplete instead of select widget. diff --git a/website/versioned_docs/version-v10.14/how-tos/generate-pdf-file-using-jasper-reports.md b/website/versioned_docs/version-v10.14/how-tos/generate-pdf-file-using-jasper-reports.md index 0b0059b71..b7ec575ea 100755 --- a/website/versioned_docs/version-v10.14/how-tos/generate-pdf-file-using-jasper-reports.md +++ b/website/versioned_docs/version-v10.14/how-tos/generate-pdf-file-using-jasper-reports.md @@ -203,7 +203,7 @@ id: "generate-pdf-file-using-jasper-reports" ``` :::note - Here Qualifier name is ${databaseServiceName}DataSource + Here Qualifier name is `${databaseServiceName}DataSource` ::: 6. Java service code to generate Jasper Report PDF from hrdb Employee table @@ -466,7 +466,7 @@ id: "generate-pdf-file-using-jasper-reports" ``` - 3. Design a jasper report for the above data. The following is a sample report file. Which we need to import into the project using [Import Resource](/learn/app-development/services/3rd-party-libraries) to the **${Service}/src/** folder. + 3. Design a jasper report for the above data. The following is a sample report file. Which we need to import into the project using [Import Resource](/learn/app-development/services/3rd-party-libraries) to the `${Service}/src/` folder. ```xml diff --git a/website/versioned_docs/version-v10.14/how-tos/get-validation-messages-form.md b/website/versioned_docs/version-v10.14/how-tos/get-validation-messages-form.md index 4ef92a0e0..bc8af098f 100755 --- a/website/versioned_docs/version-v10.14/how-tos/get-validation-messages-form.md +++ b/website/versioned_docs/version-v10.14/how-tos/get-validation-messages-form.md @@ -33,7 +33,9 @@ In the following use case, the employee form contains a few required fields. The - Step-5: Create another Model variable to design the validation messages. - Step-6: On the page created in step-2, drag and drop Button Widget. - Step-7: On the button click, select JavaScript from the Events tab properties, and write the following lines of code. This will bind to the Model variable created for the validation messages. - - Page.button1Click = function($event, widget) { Page.Variables.validationMessagesInfo.dataSet = Page.Widgets.employeeInfoForm1.validationMessages; }; + ```js + Page.button1Click = function($event, widget) { Page.Variables.validationMessagesInfo.dataSet = Page.Widgets.employeeInfoForm1.validationMessages; }; + ``` - Step-8: Drag and drop a Card widget and select a business template. - Step-9: Bind the Card widget to the Model variable to show the validation messages. By doing this, the incorrect information gets highlighted when you submit the wrong information. - Step-10: diff --git a/website/versioned_docs/version-v10.14/how-tos/integrating-junit-tests-for-wavemaker-application.md b/website/versioned_docs/version-v10.14/how-tos/integrating-junit-tests-for-wavemaker-application.md index 4b0cc103e..530abd486 100755 --- a/website/versioned_docs/version-v10.14/how-tos/integrating-junit-tests-for-wavemaker-application.md +++ b/website/versioned_docs/version-v10.14/how-tos/integrating-junit-tests-for-wavemaker-application.md @@ -74,7 +74,7 @@ JUnit is a unit testing framework for the Java programming language. JUnit has b ``` -6. Go to folder src/test/java and create a package namely com/{appName}/test/core +6. Go to folder src/test/java and create a package namely `com/{appName}/test/core` 7. Add a file with name BaseTest.java 8. Add code snippet to the file diff --git a/website/versioned_docs/version-v10.14/how-tos/list-item-access.md b/website/versioned_docs/version-v10.14/how-tos/list-item-access.md index ea0804b18..d02316ca3 100755 --- a/website/versioned_docs/version-v10.14/how-tos/list-item-access.md +++ b/website/versioned_docs/version-v10.14/how-tos/list-item-access.md @@ -4,26 +4,26 @@ id: "list-item-access" --- 1. **currentItem & currentItemWidgets**: The _currentItem_ bind object can be used to bind the current item of the list to any form widget placed within the list template. The currentItemWidgets can be accessed as the fourth argument of the events for widgets within the List. For example, button click event within List will result in the following code will capture the caption property of the Name label within a List: - +```js Page.button1Click = function($event, widget, item, currentItemWidgets) { alert(currentItemWidgets.Name.caption); }; - +``` 2. **selecteditem & selectedItemWidgets**: The _selecteditem_ bind object can be used to capture the selected item of the list when selection is enabled for the List. The return type would be array in case of multi-select List. _selecteditem_ and _selectedItemWidgets_ can be accessed through the script as follows, the click of a button will capture the selected item firstname and the caption of widget Name: - +```js Page.button1Click = function($event, widget, item, currentItemWidgets) { alert(Page.Widgets.livelist1.selecteditem.firstname); alert(Page.Widgets.livelist1.selectedItemWidgets.Name.caption); }; - +``` [![](/learn/assets/list_bind.png)](/learn/assets/list_bind.png)We have used the following JavaScript for the onSelect event of the List: - +```js Page.select1Change = function ($event, widget, item, currentItemWidgets, newVal, oldVal) { Page.Variables.NorthwindProducttestData.setFilter('subcategory', currentItemWidgets.select1.datavalue); Page.Variables.NorthwindProducttestData.update(); }; - +``` [List Use Cases](/learn/app-development/widgets/datalive/list/list-use-cases/) diff --git a/website/versioned_docs/version-v10.14/how-tos/list-multi-grouped.md b/website/versioned_docs/version-v10.14/how-tos/list-multi-grouped.md index d7c98b04b..d8d728956 100755 --- a/website/versioned_docs/version-v10.14/how-tos/list-multi-grouped.md +++ b/website/versioned_docs/version-v10.14/how-tos/list-multi-grouped.md @@ -14,7 +14,7 @@ We will see how List items can be grouped by multiple fields. We will We have used the following code snippets: - JSON file for list of months static variable: - +```json { "0": "Jan", "1": "Feb", @@ -29,9 +29,9 @@ We have used the following code snippets: "10": "Nov", "11": "Dec" } - +``` - JavaScript for the OnBeforeDatasetReady event: - +```js Page.EmployeeVaronBeforeDatasetReady = function(variable, data) { var dataByMonth = _.groupBy(data, function(datum) { //getting the employees grouped by their birth month @@ -47,7 +47,7 @@ We have used the following code snippets: }); return data; }; - +``` diff --git a/website/versioned_docs/version-v10.14/how-tos/localization-error-messages.md b/website/versioned_docs/version-v10.14/how-tos/localization-error-messages.md index 9552645d3..eaa72cb16 100755 --- a/website/versioned_docs/version-v10.14/how-tos/localization-error-messages.md +++ b/website/versioned_docs/version-v10.14/how-tos/localization-error-messages.md @@ -12,7 +12,7 @@ Ensure that the error message returned by the web service server meets the follo - It is mandatory that the error message contains error object, _JSON object_, with the errors object, as shown in the example below. - _messageKey_ is the key value that should be defined in the i18n file as shown in the steps below. - _id_, _message_ and _parameters_ are optional and can be sent for detailed logging of exception. - +```js { "errors": { "error": [ @@ -27,7 +27,7 @@ Ensure that the error message returned by the web service server meets the follo ] } } - +``` **Steps** 1. The _messageKey_ sent in the above error format needs to be added in the localization i.e., i18n dialog diff --git a/website/versioned_docs/version-v10.14/how-tos/radioset-filter-list.md b/website/versioned_docs/version-v10.14/how-tos/radioset-filter-list.md index 54cbe51c1..55634e806 100755 --- a/website/versioned_docs/version-v10.14/how-tos/radioset-filter-list.md +++ b/website/versioned_docs/version-v10.14/how-tos/radioset-filter-list.md @@ -11,7 +11,7 @@ WaveMaker offers three ways of allowing user to choose from given options: Here we will see how to Filter a List using a Radioset Widget The following is the JavaScript function used as the callback event for on before update: - +```js Page.NorthwindProductsDataonBeforeUpdate = function(variable, data) { data.standardCost = { 'value': Page.Widgets.radioset1.datavalue, @@ -19,5 +19,5 @@ The following is the JavaScript function used as the callback event for on befor 'type': 'INTEGER' } }; - +``` diff --git a/website/versioned_docs/version-v10.14/how-tos/sliding-leftnav-mobile-app.md b/website/versioned_docs/version-v10.14/how-tos/sliding-leftnav-mobile-app.md index 46d32f5c0..608b24389 100755 --- a/website/versioned_docs/version-v10.14/how-tos/sliding-leftnav-mobile-app.md +++ b/website/versioned_docs/version-v10.14/how-tos/sliding-leftnav-mobile-app.md @@ -37,7 +37,7 @@ Hence, the markup should look as follows: ``` 4. Navigate to the Style tab of the properties panel and set the Class Name property for this grid column as “hidden”. [![](/learn/assets/sliding_leftnav3.png)](/learn/assets/sliding_leftnav3.png) 5. Open the Style tab of the Main page [![](/learn/assets/sliding_leftnav5.png)](/learn/assets/sliding_leftnav5.png) and write the following style snippet: - +```css @media only screen and (max-width: 480px) and (min-width: 299px) { .leftnavcolumn { display: none !important; @@ -56,7 +56,7 @@ Hence, the markup should look as follows: width: 100% !important; } } - +``` 6. Open the topnav partial page and add an anchor widget. Specify the icon Class as “wi wi-list-ol” for the newly added anchor. [![](/learn/assets/sliding_leftnav6.png)](/learn/assets/sliding_leftnav6.png) [![](/learn/assets/sliding_leftnav7.png)](/learn/assets/sliding_leftnav7.png) 7. Choose the newly added anchor from the topnav and navigate to the properties panel. [![](/learn/assets/sliding_leftnav8.png)](/learn/assets/sliding_leftnav8.png) 8. For the onClick event of the anchor, choose JavaScript as operation. For the function generated in the Script tab of the page, place the below mentioned code snippet: diff --git a/website/versioned_docs/version-v10.14/how-tos/synchronizing-wavemaker-apps-ides-beta.md b/website/versioned_docs/version-v10.14/how-tos/synchronizing-wavemaker-apps-ides-beta.md index 109699afd..5f9dbf083 100755 --- a/website/versioned_docs/version-v10.14/how-tos/synchronizing-wavemaker-apps-ides-beta.md +++ b/website/versioned_docs/version-v10.14/how-tos/synchronizing-wavemaker-apps-ides-beta.md @@ -40,7 +40,7 @@ mvn wavemaker-workspace:init - Username & Password which would require: - **user email** - WaveMaker account which has access to the required project and - **password** of the WaveMaker account. - - Token - For this, you need to have an active WaveMaker session. Use the URL to obtain + - Token - For this, you need to have an active WaveMaker session. Use the URL `` to obtain token value and enter it at the prompt. Do not logout of the WaveMaker session till you complete the synchronization. [![](/learn/assets/InitFlow.jpg)](/learn/assets/InitFlow.jpg) diff --git a/website/versioned_docs/version-v10.14/how-tos/synchronizing-wavemaker-apps-ides.md b/website/versioned_docs/version-v10.14/how-tos/synchronizing-wavemaker-apps-ides.md index bd31ed7db..db7f3a06d 100755 --- a/website/versioned_docs/version-v10.14/how-tos/synchronizing-wavemaker-apps-ides.md +++ b/website/versioned_docs/version-v10.14/how-tos/synchronizing-wavemaker-apps-ides.md @@ -37,7 +37,7 @@ Git has to be installed on your local machine where you want to run this plugin. - Username & Password which would require: - **user email** - WaveMaker account which has access to the required project and - **password **of the WaveMaker account. - - Token - For this, you need to have an active WaveMaker session. Use the URL to obtain + - Token - For this, you need to have an active WaveMaker session. Use the URL `` to obtain token value and enter it at the prompt. Do not log out of the WaveMaker session till you complete the complete the synchronization. **[![](/learn/assets/InitFlow.jpg)](/learn/assets/InitFlow.jpg)** diff --git a/website/versioned_docs/version-v10.14/how-tos/twilio-connector.md b/website/versioned_docs/version-v10.14/how-tos/twilio-connector.md index a76a5e7e0..8b7776db6 100755 --- a/website/versioned_docs/version-v10.14/how-tos/twilio-connector.md +++ b/website/versioned_docs/version-v10.14/how-tos/twilio-connector.md @@ -20,7 +20,7 @@ This connector exposes api to send messages to and receive messages from Twilio ## Step 2: Configure twilio configurable properties in profiles 1. By default externalized connector properties are added in the project profiles [Know More](/learn/connectors/connectors-import#externalizing-connector-properties). -2. Connector externalized properties are prefixed with **connector.${connectorName}** +2. Connector externalized properties are prefixed with **connector.$\{connectorName}** ```Java connector.twilio-connector.default.twilio.account.SID= diff --git a/website/versioned_docs/version-v10.14/how-tos/using-cascading-select-within-live-form.md b/website/versioned_docs/version-v10.14/how-tos/using-cascading-select-within-live-form.md index 536f656df..63e78f0d9 100755 --- a/website/versioned_docs/version-v10.14/how-tos/using-cascading-select-within-live-form.md +++ b/website/versioned_docs/version-v10.14/how-tos/using-cascading-select-within-live-form.md @@ -10,12 +10,12 @@ We will see how to configure cascading selects for Live Form fields using the on 3. Update of rows in Live form with form data mapped to current item of the list. We will be using the following JavaScript function: - +```js Page.liveform1_categorytestChange = function($event, widget, item, currentItemWidgets, newVal, oldVal) { Page.Variables.selectsubcategory.setInput('type', newVal.category); Page.Variables.selectsubcategory.update(); }; - +``` [Live Form Use Cases](/learn/app-development/widgets/datalive/live-form/liveform-use-cases/) diff --git a/website/versioned_docs/version-v10.14/how-tos/using-function-evaluating-conditions.md b/website/versioned_docs/version-v10.14/how-tos/using-function-evaluating-conditions.md index afe303582..cd0c58a6f 100755 --- a/website/versioned_docs/version-v10.14/how-tos/using-function-evaluating-conditions.md +++ b/website/versioned_docs/version-v10.14/how-tos/using-function-evaluating-conditions.md @@ -15,10 +15,10 @@ Show/Hide an image (say, tick image) in a page based on the condition. You can e 2. Select “**Use expression**” tab. Type function “_isShowTick(item)_” where “item” is passed as argument. 3. Click on the script tab. 4. Add following script - + ```javascript //function to show the tick $scope.isShowTick = function(item) { return item.actioncount > 0 ? true:(item.note_text ? (item.note_text !== '' ? true : false) : false); } - + ``` 5. Run the application to test diff --git a/website/versioned_docs/version-v10.14/hybrid-mobile/offline-data-support-implementation.md b/website/versioned_docs/version-v10.14/hybrid-mobile/offline-data-support-implementation.md index b5ce53c45..26aeb5465 100755 --- a/website/versioned_docs/version-v10.14/hybrid-mobile/offline-data-support-implementation.md +++ b/website/versioned_docs/version-v10.14/hybrid-mobile/offline-data-support-implementation.md @@ -74,11 +74,11 @@ By default, three variables **networkInfo**, **datasyncPush** and **datasyncPul | **Operation** | **Behavior** | **Input Data** | **Events** | **Description** | | --- | --- | --- | --- | --- | -| getOfflineChanges | none | none | On Success On Error | to fetch the changes made when the app was offline Return Values: {**'total'**: 0 **'pendingToSync'**: changeLogSet **'failedToSync'**: changeLogSet} | -| lastPullInfo | Spinner Context and Message - to be displayed while pull is in progress | none | On Success On Error | get the last pull info Return Values: {'**databases**' : [{ '**name**' : 'datbaseName', '**entities**': [{ '**entityName**': '**entityName**', '**pulledRecordCount**': 0 }], '**pulledRecordCount**' : 0 }], '**totalPulledRecordCount**' : 0, '**startTime**' : Date, '**endTime**' : Date} | -| lastPushInfo | Spinner Context and Message - to be displayed while pull is in progress | none | On Success On Error | get the last push info Return Values: {**'completedTaskCount'**: 0 **'endTime'**: 0 **'failedTaskCount'**: 0 **'startTime'**: 0 **'successfulTaskCount'**: 0 **'totalTaskCount'**: 0} | -| pull | Request data on page load - to pull the data when the page is loaded Clear offline data before pull - to delete the whole offline data (other than BUNDLED data) before the pull Spinner Context and Message - to be displayed while pull is in progress | none | On Success On Error On Progress On Before | get the data from the server Return Values: {**'completedTaskCount'**: 0 **'inProgress'**: 0 **'totalTaskCount'**: 0} | -| push | Spinner Context and Message - to be displayed while push is in progress | none | On Success On Error On Progress On Before | send the data to server Return Values: {**'completedTaskCount'**: 0 **'failedTaskCount'**: 0 **'inProgress'**: 0 **'successfulTaskCount'**: 0 **'totalTaskCount'**: 0} | +| getOfflineChanges | none | none | On Success On Error | to fetch the changes made when the app was offline Return Values: \{**'total'**: 0 **'pendingToSync'**: changeLogSet **'failedToSync'**: changeLogSet} | +| lastPullInfo | Spinner Context and Message - to be displayed while pull is in progress | none | On Success On Error | get the last pull info Return Values: \{'**databases**' : [\{ '**name**' : 'datbaseName', '**entities**': [\{ '**entityName**': '**entityName**', '**pulledRecordCount**': 0 }], '**pulledRecordCount**' : 0 }], '**totalPulledRecordCount**' : 0, '**startTime**' : Date, '**endTime**' : Date} | +| lastPushInfo | Spinner Context and Message - to be displayed while pull is in progress | none | On Success On Error | get the last push info Return Values: \{**'completedTaskCount'**: 0 **'endTime'**: 0 **'failedTaskCount'**: 0 **'startTime'**: 0 **'successfulTaskCount'**: 0 **'totalTaskCount'**: 0} | +| pull | Request data on page load - to pull the data when the page is loaded Clear offline data before pull - to delete the whole offline data (other than BUNDLED data) before the pull Spinner Context and Message - to be displayed while pull is in progress | none | On Success On Error On Progress On Before | get the data from the server Return Values: \{**'completedTaskCount'**: 0 **'inProgress'**: 0 **'totalTaskCount'**: 0} | +| push | Spinner Context and Message - to be displayed while push is in progress | none | On Success On Error On Progress On Before | send the data to server Return Values: \{**'completedTaskCount'**: 0 **'failedTaskCount'**: 0 **'inProgress'**: 0 **'successfulTaskCount'**: 0 **'totalTaskCount'**: 0} | | exportDB (ver 9.3) | Spinner Context and Message to display during this operation | none | On Success On Error | Offline database is saved as zip in ‘Downloads’ folder in Android. In IOS, zip is stored into ‘Documents’ folder so that one can export from iPhone via iTunes. For the file to be visible in iTunes, File sharing needs to be enabled for the app in iOS preferences. Location of the file is exposed as an outbound property on this variable. | | importDB diff --git a/website/versioned_docs/version-v10.14/on-premise/aws/install/apply-license.md b/website/versioned_docs/version-v10.14/on-premise/aws/install/apply-license.md index 6818cdf70..fd2ee2669 100755 --- a/website/versioned_docs/version-v10.14/on-premise/aws/install/apply-license.md +++ b/website/versioned_docs/version-v10.14/on-premise/aws/install/apply-license.md @@ -7,7 +7,7 @@ sidebar_label: "Apply License" ### Applying license from Launchpad -- Go to +- Go to `` - At license section, select the upload key bunch. - After uploading file select upload keys to apply the license key. diff --git a/website/versioned_docs/version-v10.14/on-premise/aws/install/initilize-setup.md b/website/versioned_docs/version-v10.14/on-premise/aws/install/initilize-setup.md index ee7b88e3c..83b1bbf74 100755 --- a/website/versioned_docs/version-v10.14/on-premise/aws/install/initilize-setup.md +++ b/website/versioned_docs/version-v10.14/on-premise/aws/install/initilize-setup.md @@ -49,4 +49,4 @@ For WaveMaker user, follow the steps below: [![privellaged user setup initialization](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg)](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg) - After successful initialization, the script will display a URL to perform the rest of the WME setup. -- Go to as directed by the above command output to do the WME setup. +- Go to `` as directed by the above command output to do the WME setup. diff --git a/website/versioned_docs/version-v10.14/on-premise/aws/install/setup-using-cw.md b/website/versioned_docs/version-v10.14/on-premise/aws/install/setup-using-cw.md index c2657f843..0a21aa2fc 100755 --- a/website/versioned_docs/version-v10.14/on-premise/aws/install/setup-using-cw.md +++ b/website/versioned_docs/version-v10.14/on-premise/aws/install/setup-using-cw.md @@ -7,7 +7,7 @@ sidebar_label: "Setup Using ConfigPortal" ### WME Setup on ConfigPortal -- Open WaveMaker ConfigPortal by +- Open WaveMaker ConfigPortal by `` - Setup password for the WaveMaker setup portal. This password is system level. All command line operations are authenticated by this Password. Subsequent operations like upgrades needs this password. - Password must contain 8-20 characters, with at least one lower case alphabet, one upper case alphabet, one digit and a special character (underscore(_), at(@), dot(.)) @@ -35,4 +35,4 @@ sidebar_label: "Setup Using ConfigPortal" [![apply-license](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg)](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg) - Click on launchpad for further operations. -- Map with the Domain name given in ur DNS or put an host entry in ur machine. +- Map `` with the Domain name given in ur DNS or put an host entry in ur machine. diff --git a/website/versioned_docs/version-v10.14/on-premise/aws/launching-instances-in-aws.md b/website/versioned_docs/version-v10.14/on-premise/aws/launching-instances-in-aws.md index 4ce68fa7d..d881df711 100755 --- a/website/versioned_docs/version-v10.14/on-premise/aws/launching-instances-in-aws.md +++ b/website/versioned_docs/version-v10.14/on-premise/aws/launching-instances-in-aws.md @@ -55,7 +55,7 @@ sidebar_label: "Prepare Infrastructure" ## Launch Platform Instance -- Open the Amazon EC2 console at +- Open the Amazon EC2 console at `` - Choose Launch Instance, choose an ubuntu 16.04 Amazon Machine Image (AMI), or if you have any ubuntu 16.04 AMI, select it. [![ami](/learn/assets/wme-setup/wme-setup-in-aws/selecting-ami.png)](/learn/assets/wme-setup/wme-setup-in-aws/selecting-ami.png) @@ -95,7 +95,7 @@ sidebar_label: "Prepare Infrastructure" ## Launch Studio Workspace Instance / AppDeployment Instance -- Open the Amazon EC2 console at +- Open the Amazon EC2 console at `` - Choose Launch Instance, choose an ubuntu 16.04 Amazon Machine Image (AMI), or if you have any ubuntu 16.04 AMI, select it. [![ami](/learn/assets/wme-setup/wme-setup-in-aws/selecting-ami.png)](/learn/assets/wme-setup/wme-setup-in-aws/selecting-ami.png) diff --git a/website/versioned_docs/version-v10.14/on-premise/azure/install/apply-license.md b/website/versioned_docs/version-v10.14/on-premise/azure/install/apply-license.md index 6818cdf70..fd2ee2669 100755 --- a/website/versioned_docs/version-v10.14/on-premise/azure/install/apply-license.md +++ b/website/versioned_docs/version-v10.14/on-premise/azure/install/apply-license.md @@ -7,7 +7,7 @@ sidebar_label: "Apply License" ### Applying license from Launchpad -- Go to +- Go to `` - At license section, select the upload key bunch. - After uploading file select upload keys to apply the license key. diff --git a/website/versioned_docs/version-v10.14/on-premise/azure/install/initilize-setup.md b/website/versioned_docs/version-v10.14/on-premise/azure/install/initilize-setup.md index ba738465b..7d262d0e5 100755 --- a/website/versioned_docs/version-v10.14/on-premise/azure/install/initilize-setup.md +++ b/website/versioned_docs/version-v10.14/on-premise/azure/install/initilize-setup.md @@ -49,4 +49,4 @@ For WaveMaker user, follow the steps below: [![privellaged user setup initialization](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg)](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg) - After successful initialization, the script will display a URL to perform the rest of the WME setup. -- Go to as directed by the above command output to do the WME setup. +- Go to `` as directed by the above command output to do the WME setup. diff --git a/website/versioned_docs/version-v10.14/on-premise/azure/install/setup-using-cw.md b/website/versioned_docs/version-v10.14/on-premise/azure/install/setup-using-cw.md index c2657f843..0a21aa2fc 100755 --- a/website/versioned_docs/version-v10.14/on-premise/azure/install/setup-using-cw.md +++ b/website/versioned_docs/version-v10.14/on-premise/azure/install/setup-using-cw.md @@ -7,7 +7,7 @@ sidebar_label: "Setup Using ConfigPortal" ### WME Setup on ConfigPortal -- Open WaveMaker ConfigPortal by +- Open WaveMaker ConfigPortal by `` - Setup password for the WaveMaker setup portal. This password is system level. All command line operations are authenticated by this Password. Subsequent operations like upgrades needs this password. - Password must contain 8-20 characters, with at least one lower case alphabet, one upper case alphabet, one digit and a special character (underscore(_), at(@), dot(.)) @@ -35,4 +35,4 @@ sidebar_label: "Setup Using ConfigPortal" [![apply-license](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg)](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg) - Click on launchpad for further operations. -- Map with the Domain name given in ur DNS or put an host entry in ur machine. +- Map `` with the Domain name given in ur DNS or put an host entry in ur machine. diff --git a/website/versioned_docs/version-v10.14/on-premise/gcp/install/apply-license.md b/website/versioned_docs/version-v10.14/on-premise/gcp/install/apply-license.md index 6818cdf70..fd2ee2669 100755 --- a/website/versioned_docs/version-v10.14/on-premise/gcp/install/apply-license.md +++ b/website/versioned_docs/version-v10.14/on-premise/gcp/install/apply-license.md @@ -7,7 +7,7 @@ sidebar_label: "Apply License" ### Applying license from Launchpad -- Go to +- Go to `` - At license section, select the upload key bunch. - After uploading file select upload keys to apply the license key. diff --git a/website/versioned_docs/version-v10.14/on-premise/gcp/install/initilize-setup.md b/website/versioned_docs/version-v10.14/on-premise/gcp/install/initilize-setup.md index ba738465b..7d262d0e5 100755 --- a/website/versioned_docs/version-v10.14/on-premise/gcp/install/initilize-setup.md +++ b/website/versioned_docs/version-v10.14/on-premise/gcp/install/initilize-setup.md @@ -49,4 +49,4 @@ For WaveMaker user, follow the steps below: [![privellaged user setup initialization](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg)](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg) - After successful initialization, the script will display a URL to perform the rest of the WME setup. -- Go to as directed by the above command output to do the WME setup. +- Go to `` as directed by the above command output to do the WME setup. diff --git a/website/versioned_docs/version-v10.14/on-premise/gcp/install/setup-using-cw.md b/website/versioned_docs/version-v10.14/on-premise/gcp/install/setup-using-cw.md index c2657f843..0a21aa2fc 100755 --- a/website/versioned_docs/version-v10.14/on-premise/gcp/install/setup-using-cw.md +++ b/website/versioned_docs/version-v10.14/on-premise/gcp/install/setup-using-cw.md @@ -7,7 +7,7 @@ sidebar_label: "Setup Using ConfigPortal" ### WME Setup on ConfigPortal -- Open WaveMaker ConfigPortal by +- Open WaveMaker ConfigPortal by `` - Setup password for the WaveMaker setup portal. This password is system level. All command line operations are authenticated by this Password. Subsequent operations like upgrades needs this password. - Password must contain 8-20 characters, with at least one lower case alphabet, one upper case alphabet, one digit and a special character (underscore(_), at(@), dot(.)) @@ -35,4 +35,4 @@ sidebar_label: "Setup Using ConfigPortal" [![apply-license](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg)](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg) - Click on launchpad for further operations. -- Map with the Domain name given in ur DNS or put an host entry in ur machine. +- Map `` with the Domain name given in ur DNS or put an host entry in ur machine. diff --git a/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/apply-license.md b/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/apply-license.md index 6818cdf70..fd2ee2669 100755 --- a/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/apply-license.md +++ b/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/apply-license.md @@ -7,7 +7,7 @@ sidebar_label: "Apply License" ### Applying license from Launchpad -- Go to +- Go to `` - At license section, select the upload key bunch. - After uploading file select upload keys to apply the license key. diff --git a/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/initilize-setup.md b/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/initilize-setup.md index ba738465b..7d262d0e5 100755 --- a/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/initilize-setup.md +++ b/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/initilize-setup.md @@ -49,4 +49,4 @@ For WaveMaker user, follow the steps below: [![privellaged user setup initialization](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg)](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg) - After successful initialization, the script will display a URL to perform the rest of the WME setup. -- Go to as directed by the above command output to do the WME setup. +- Go to `` as directed by the above command output to do the WME setup. diff --git a/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/setup-using-cw.md b/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/setup-using-cw.md index c2657f843..0a21aa2fc 100755 --- a/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/setup-using-cw.md +++ b/website/versioned_docs/version-v10.14/on-premise/hyper-v/install/setup-using-cw.md @@ -7,7 +7,7 @@ sidebar_label: "Setup Using ConfigPortal" ### WME Setup on ConfigPortal -- Open WaveMaker ConfigPortal by +- Open WaveMaker ConfigPortal by `` - Setup password for the WaveMaker setup portal. This password is system level. All command line operations are authenticated by this Password. Subsequent operations like upgrades needs this password. - Password must contain 8-20 characters, with at least one lower case alphabet, one upper case alphabet, one digit and a special character (underscore(_), at(@), dot(.)) @@ -35,4 +35,4 @@ sidebar_label: "Setup Using ConfigPortal" [![apply-license](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg)](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg) - Click on launchpad for further operations. -- Map with the Domain name given in ur DNS or put an host entry in ur machine. +- Map `` with the Domain name given in ur DNS or put an host entry in ur machine. diff --git a/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/apply-license.md b/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/apply-license.md index 6818cdf70..fd2ee2669 100755 --- a/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/apply-license.md +++ b/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/apply-license.md @@ -7,7 +7,7 @@ sidebar_label: "Apply License" ### Applying license from Launchpad -- Go to +- Go to `` - At license section, select the upload key bunch. - After uploading file select upload keys to apply the license key. diff --git a/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/initilize-setup.md b/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/initilize-setup.md index ba738465b..7d262d0e5 100755 --- a/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/initilize-setup.md +++ b/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/initilize-setup.md @@ -49,4 +49,4 @@ For WaveMaker user, follow the steps below: [![privellaged user setup initialization](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg)](/learn/assets/wme-setup/wme-setup-with-privillaged-user.jpg) - After successful initialization, the script will display a URL to perform the rest of the WME setup. -- Go to as directed by the above command output to do the WME setup. +- Go to `` as directed by the above command output to do the WME setup. diff --git a/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/setup-using-cw.md b/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/setup-using-cw.md index c2657f843..0a21aa2fc 100755 --- a/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/setup-using-cw.md +++ b/website/versioned_docs/version-v10.14/on-premise/vmware-esxi/install/setup-using-cw.md @@ -7,7 +7,7 @@ sidebar_label: "Setup Using ConfigPortal" ### WME Setup on ConfigPortal -- Open WaveMaker ConfigPortal by +- Open WaveMaker ConfigPortal by `` - Setup password for the WaveMaker setup portal. This password is system level. All command line operations are authenticated by this Password. Subsequent operations like upgrades needs this password. - Password must contain 8-20 characters, with at least one lower case alphabet, one upper case alphabet, one digit and a special character (underscore(_), at(@), dot(.)) @@ -35,4 +35,4 @@ sidebar_label: "Setup Using ConfigPortal" [![apply-license](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg)](/learn/assets/wme-setup/wme-portal-setup/apply-license.jpg) - Click on launchpad for further operations. -- Map with the Domain name given in ur DNS or put an host entry in ur machine. +- Map `` with the Domain name given in ur DNS or put an host entry in ur machine.