Updated incorrect URLs (#235)

SamDesmondKing · web-flow · commit 40a55a8045a4 · 2023-03-03T14:59:50.000+05:30
* Updated URL on fields page

* Updated analyze databases page

* Updated analyze source code page

* Updated host discovery page

* Updated servicenow page

* Updated six steps page

* Update pages/user guides/integrating_with_servicenow.md

* Fixed issues with numbering
diff --git a/pages/api/create_interview_questions.md b/pages/api/create_interview_questions.md
@@ -23,7 +23,7 @@ For any additional details regarding the endpoint, checkout the Tidal API docume
 
 # Tools
 
- * [jq](https://stedolan.github.io/jq/) - `jq` is a CLI that allows us quickly parse and filter JSON.
+- [jq](https://stedolan.github.io/jq/) - `jq` is a CLI that allows us quickly parse and filter JSON.
 
 # Creating Interview Questions
 
@@ -33,7 +33,7 @@ Our interview questions are tightly coupled with our application fields. So, bef
 
 ### Create a custom field
 
-You can create a custom field for an application by going to https://[your subdomain].tidal.cloud/#/admin and clicking on the 'New Application Field' button. Note: we don't limit the type of field (dropdown, text, number, currency, checkbox) that can be used in interview questions.
+You can create a custom field for an application by going to https://[your workspace].tidal.cloud/fields/applications and clicking on the 'New Application Field' button. Note: we don't limit the type of field (dropdown, text, number, currency, checkbox) that can be used in interview questions.
 
 ### Get a custom field id
 
@@ -45,7 +45,6 @@ Once we have created a custom field, we need to get its field id. So, to start w
       -H Content-Type\:\ application/json \
       -o fields.json
 
-
 Once we have that, we need to search for our newly created field name. If you have 'jq' installed you can use it to query the json file for your field name
 
     jq '.[] | select(.name=="Your Field Name")' fields.json
@@ -68,7 +67,6 @@ Which should give you an output similiar to
       "field_options": []
     }
 
-
 ## Custom Question
 
 ### Get a question number
@@ -132,7 +130,6 @@ Putting this all together we can then post this request to our API
       -H Content-Type\:\ application/json \
       -d \{\"question\"\:\ \{\ \"text\"\:\ \"How\ many\ users\ does\ this\ application\ have\?\"\,\ \"number\"\:\ 22\,\ \"field_id\"\:\ 1\}\}
 
-
 ### Updating an existing quesiton
 
 If you have an interview question already and you want to change the number or change what field it applies to you can do a put request
diff --git a/pages/tidal tools/analyze_database.md b/pages/tidal tools/analyze_database.md
@@ -45,7 +45,7 @@ For example, in Oracle databases, the Data Dictionary and AWR repository tables
 
 ## Getting Started
 
-1. Before you can analyze a database, You must enable the Database Analysis feature for your account. To do so, go to your workspace Settings/Preferences (https://yourworkspace.tidal.cloud/#/admin/setting). You will find the Database Analysis section at the bottom of the page.
+1. Before you can analyze a database, You must enable the Database Analysis feature for your account. To do so, go to your workspace Settings/Preferences (https://[your workspace].tidal.cloud/preferences). You will find the Database Analysis section at the bottom of the page.
 2. Now that you have activated the Database Analyze feature, You need to install, configure and authenticate via Tidal Tools. Make sure you follow these guides.
   - How to [install](tidal-tools.html#install) Tidal Tools.
   - Install Tidal Tools [dependencies](tidal-tools.html#dependencies).
@@ -65,7 +65,7 @@ For the most part, all supported Database engines share very similar configurati
 
 Your YAML configuration file for Postgres, MySQL, and SQL Server must contain the following information.
 
-  - `id` - The id of the database from your Tidal account. You can find it in the URL bar when looking at a database instance. ex. If you are viewing a database instance in Tidal, the URL will show https://demo2.tidal.cloud/#/database_instances/111 in this case 111 is the database instance ID.
+  - `id` - The id of the database from your Tidal account. You can find it in the URL bar when looking at a database instance. ex. If you are viewing a database instance in Tidal, the URL will show https://[your workspace].tidal.cloud/database_instances/111/overview in this case 111 is the database instance ID.
   - `name` - A common name for your database could be the same or different from db_name, but this value is arbitrary and only for your reference.
   - `engine` - The database vendor, either `SQL Server`, `MySQL`, or `PostgreSQL`, it is not case sensitive.
   - `host` - The hostname of the server that the database is located on and is accessible via a network connection from your current device and location.
@@ -77,7 +77,7 @@ Your YAML configuration file for Postgres, MySQL, and SQL Server must contain th
 
 When analyzing Oracle databases, the attributes in your configuration file must contain the following details.
 
-  - `id` - The id of the database from your Tidal account. You can find it in the URL bar when looking at a database instance. ex. If you are viewing a database instance in Tidal, the URL will show https://demo2.tidal.cloud/#/database_instances/111 in this case 111 is the database instance ID.
+  - `id` - The id of the database from your Tidal account. You can find it in the URL bar when looking at a database instance. ex. If you are viewing a database instance in Tidal, the URL will show https://[your workspace].tidal.cloud/database_instances/111/overview in this case 111 is the database instance ID.
   - `name` - A common name for your database.
   - `analyze_workload` - When set to **true** workload analysis is enabled. Be sure to configure AWR data retention and verify licensing. For more information check the advance configuration [section](#advanced-configuration)
   - `engine` - **Oracle**
diff --git a/pages/tidal tools/sourcecode.md b/pages/tidal tools/sourcecode.md
@@ -7,12 +7,13 @@ sidebar: main_sidebar
 permalink: analyze-source-code.html
 folder: tidaltools
 ---
+
 ## Tidal Analyze Source Code
 
 Not sure how ready you are to move to the cloud? With Tidal you have
 the option to analyze your specified source code associated with the applications.
 The analysis will identify the difficulty to migrate your applications to the
-cloud. 
+cloud.
 
 If you are interested in a deeper dive source code assessment, let us know at
 [info@tidalcloud.com](mailto:info@tidalcloud.com).
@@ -24,12 +25,13 @@ Try it out!
 ## Getting Started
 
 1. Install, configure and authenticate via Tidal Tools. Make sure you follow these guides.
-  - How to [install](tidal-tools.html#install) Tidal Tools.
-  - Install Tidal Tools [dependencies](tidal-tools.html#dependencies).
-  - Make sure you can [connect](tidal-tools.html#connecting-to-the-api) with your workspace using Tidal Tools.
-  - As the last step, You should run the [tidal doctor](troubleshooting.html#tidal-doctor) command to verify that your environment has been configured properly.
 
-2. You will need the ID of the application for which you are going to perform the source code analysis. You can find it in the URL bar when looking at an application. ex. If you are viewing an application in Tidal, the URL will show `https://demo.tidal.cloud/#/apps/111` in this case 111 is the application ID.
+- How to [install](tidal-tools.html#install) Tidal Tools.
+- Install Tidal Tools [dependencies](tidal-tools.html#dependencies).
+- Make sure you can [connect](tidal-tools.html#connecting-to-the-api) with your workspace using Tidal Tools.
+- As the last step, You should run the [tidal doctor](troubleshooting.html#tidal-doctor) command to verify that your environment has been configured properly.
+
+2. You will need the ID of the application for which you are going to perform the source code analysis. You can find it in the URL bar when looking at an application. ex. If you are viewing an application in Tidal, the URL will show `https://[your workspace].tidal.cloud/apps/111/overview` in this case 111 is the application ID.
 
 3. Lastly, you will need a local copy of the source code for the application.
 
@@ -45,15 +47,16 @@ When analyzing a source code (or multiple), you have two options.
 
 1. Perform the source code analysis and upload the result immediately to your workspace. This is Tidal Tools' default behaviour. To do so, all you need to do is run the following command.
 
-    ```bash
-    cd /path/to/source-code
-    tidal analyze code --app-id 111
-    ```
+   ```bash
+   cd /path/to/source-code
+   tidal analyze code --app-id 111
+   ```
 
-    Alternatively, you can pass the location to the source code.
-    ```bash
-    tidal analyze code ~/location/to-source-code/ --app-id 111
-    ```
+   Alternatively, you can pass the location to the source code.
+
+   ```bash
+   tidal analyze code ~/location/to-source-code/ --app-id 111
+   ```
 
 2. Perform the source code analysis and upload the results **at a later time**. The following section will explain how to run database analysis in **offline mode**
 
@@ -63,33 +66,34 @@ There are circumstances in which you need to perform a source code analysis on a
 
 These are the steps you need to follow in order to bypass internet access limitations:
 
-1. On a Machine with internet access, you need to install, and configure Tidal Tools. 
+1. On a Machine with internet access, you need to install, and configure Tidal Tools.
 
 2. Package Tidal Tools and its required docker container images into a tar file. This will allow you to move the archive file into your restricted environment. To do so, run the following command.
 
-    `tidal backup`
+   `tidal backup`
 
-    Once it has finished, you will find (in your current location) a tar file called `tidal-snapshot_DATE.tar`. This is the file you need to transport into your internet restricted environment.
+   Once it has finished, you will find (in your current location) a tar file called `tidal-snapshot_DATE.tar`. This is the file you need to transport into your internet restricted environment.
 
 3. On the machine that has no internet access, you will now restore Tidal Tools using the following command.
 
-    `tidal restore tidal-snapshot_DATE.tar`
+   `tidal restore tidal-snapshot_DATE.tar`
+
+   This will load a docker image and all the existing Tidal Tools configurations from the original machine. You can now run the source code analysis without any external network connectivity.
 
-    This will load a docker image and all the existing Tidal Tools configurations from the original machine. You can now run the source code analysis without any external network connectivity.
+   `tidal analyze code [path/to-directory] --offline --output-dir [directory]`
 
-    `tidal analyze code [path/to-directory] --offline --output-dir [directory]`
+   Note:
 
-    Note:
-    - The `--offline` flag indicates to Tidal Tools that the output needs to be stored in a file instead of being uploaded.
-    - The `--output-dir` flag determines where the output will be located.
+   - The `--offline` flag indicates to Tidal Tools that the output needs to be stored in a file instead of being uploaded.
+   - The `--output-dir` flag determines where the output will be located.
 
-    After the analysis is completed, you will find a zip file called, `result-<DATE>.zip` that can then be transferred into a machine with internet connectivity.
+   After the analysis is completed, you will find a zip file called, `result-<DATE>.zip` that can then be transferred into a machine with internet connectivity.
 
 4. Back to the machine with internet access, you can now upload your results to your workspace with this command.
 
-    `tidal analyze code --app-id [app_id_for_your_application] --upload [file_name]`
+   `tidal analyze code --app-id [app_id_for_your_application] --upload [file_name]`
 
-    You should receive confirmation that the upload has been completed and can navigate to Tidal to see the results.
+   You should receive confirmation that the upload has been completed and can navigate to Tidal to see the results.
 
 {% include tip.html content="Need to run code analysis on a entire set of applications all from one machine? Run [this command and easily create a directory for every application already in Tidal Migrations](https://github.com/tidalmigrations/gists/blob/master/make_source_code_dirs.sh)" %}
 
diff --git a/pages/user guides/discover_nmap.md b/pages/user guides/discover_nmap.md
@@ -35,7 +35,7 @@ By leveraging the power of **Tidal Tools**, you can send the output generated by
     ```
     tidal sync nmap my-network.xml
     ```
-5. Head over to your Tidal account! (https://<<account_name>>.tidal.cloud/#/discover/host_discovery)
+5. Head over to your Tidal account! (https://[your workspace].tidal.cloud/host-discovery)
 
 
 ## Installing Nmap
diff --git a/pages/user guides/integrating_with_servicenow.md b/pages/user guides/integrating_with_servicenow.md
@@ -89,7 +89,7 @@ In order for your Tidal workspace to communicate with your ServiceNow instance,
 
 - Log into your Tidal workspace and head to the ServiceNow integration page.
 
-`` https://<example>.tidal.cloud/#/servicenow ``
+`` https://[your workspace].tidal.cloud/_/#/servicenow ``
 
 - Enter the following information:
     - Instance Name
diff --git a/pages/user guides/six_steps.md b/pages/user guides/six_steps.md
@@ -126,7 +126,7 @@ out.
 
 You can find the `Application ID` in the URL bar when looking at an
 application.  e.g. if I'm loking at an application in Tidal, the URL
-will show `https://demo2.tidal.cloud/#/apps/111`  Here, `111` is my
+will show `https://[your workspace].tidal.cloud/apps/111/overview`  Here, `111` is my
 `Application ID`.
 
 I can now analyze the source code with:
