Ssk/platgovnetsuite rebrand

docs/platgovnetsuite/agent/agent_clear_incident.md

@@ -11,7 +11,7 @@ Report.
 
 Here is the process to clear/resolve a control incident:
 
-1. Open **Strongpoint** > **Financial Controls** > **Unresolved Control Incidents**
+1. Open **Netwrix** > **Financial Controls** > **Unresolved Control Incidents**
 2. Click on the **Customization** to display the incidents.
 3. Click **Edit** on the Incident record to clear/resolve.
 

docs/platgovnetsuite/agent/agent_creating_preapproved_change_request.md

@@ -12,7 +12,7 @@ implementing your custom form.
 
 Here are the steps to create a pre-approved change request for a control:
 
-1. Open **Strongpoint** > **Financial Controls** > **New Agent Control Approval**
+1. Open **Netwrix** > **Financial Controls** > **New Agent Control Approval**
 
     ![agent_pre_app_not_started](/images/platgovnetsuite/financial_controls/agent_pre_app_not_started.webp)
 

docs/platgovnetsuite/agent/agent_example_set_control.md

@@ -50,7 +50,7 @@ Here is the process to create a control to monitor changes:
 
 You can wait until the next AutoSpider run, or manually create the customization record:
 
-1. Open **Strongpoint** > **Customizations** > **Customization** > **New**
+1. Open **Netwrix** > **Customizations** > **Customization** > **New**
 2. Enter information in the required fields:
 
     - **Custom Form**: Use the **Simplified Form**, or select a different form if you want to add a

docs/platgovnetsuite/agent/agent_example_unresolved_control_incident.md

@@ -13,7 +13,7 @@ be found under **Unresolved Control Incidents**.
 
 To view unresolved control incidents:
 
-1. Open **Strongpoint** > **Financial Controls** > **Unresolved Control Incidents**
+1. Open **Netwrix** > **Financial Controls** > **Unresolved Control Incidents**
 
     ![Viewing Unresolved Control Incidents](/images/platgovnetsuite/financial_controls/agent_unresolved_example1.webp)
 

docs/platgovnetsuite/agent/agent_lookback.md

@@ -12,7 +12,7 @@ a daily run.
 
 The Agent Lookback is accessed from the Customization record for the control.
 
-1. Open **Strongpoint** > **Financial Controls** > **Controls**.
+1. Open **Netwrix** > **Financial Controls** > **Controls**.
 2. **Edit** the control to run.
 3. Open the **Controls** tab.
 

docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-0_release_notes.md

@@ -1,10 +1,10 @@
 ---
-title: "Netwrix Strongpoint for Netsuite 7.0 Release Notes"
-description: "Netwrix Strongpoint for Netsuite 7.0 Release Notes"
+title: "Netwrix Platform Governance for NetSuite 7.0 Release Notes"
+description: "Netwrix Platform Governance for NetSuite 7.0 Release Notes"
 sidebar_position: 40
 ---
 
-# Netwrix Strongpoint for Netsuite 7.0 Release Notes
+# Netwrix Platform Governance for NetSuite 7.0 Release Notes
 
 ## Core 7.0.3
 
@@ -32,12 +32,12 @@ June 23, 2023
 June 16, 2023
 
 - **Autospider**, **Manual Spider** and **ReSpider Now** now support French (both France and Canada)
-  for Strongpoint customers using French in NetSuite.
+  for Netwrix customers using French in NetSuite.
 - **Changed By No HTML** and **Diff No HTML** result options are available for customizing your
   Searches. Specifying these options enable you to export the Change Management Reports with the
   fields in plain text, removing the HTML tags to improve readability.
 
-    - Open **Strongpoint** > **Change Management Reports** > _report_name_ > **Customize**.
+    - Open **Netwrix** > **Change Management Reports** > _report_name_ > **Customize**.
     - Click **Edit this Search**.
     - Open the **Results** tab.
     - Click **Add Multiple**.
@@ -68,7 +68,7 @@ April 21, 2023
 ### **Reset Strongpoint scripts to Low Priority**
 
 This change ensures the Strongpoint scripts do not impact your performance. This change affects both
-new installs and updates to existing Strongpoint for NetSuite installations.
+new installs and updates to existing Platform Governance for NetSuite installations.
 
 There is an exception for customers using the **Agent** module to run **Large Controls**. These
 scripts are set to **Standard** priority. Contact your Customer Success Manager for assistance if
@@ -83,7 +83,7 @@ you are considering changing these associated scripts to a lower priority.
 
 ### **NetSuite Make Copy Creates Content and Resets Status**
 
-Strongpoint ensures the **Make Copy** command found under the **Actions** option only copies the
+Netwrix ensures the **Make Copy** command found under the **Actions** option only copies the
 content, not the status. Copied change requests are set to the **Not Started** status.
 
 ![Make Copy does not copy the status](/images/platgovnetsuite/release_notes/change_request_make_copy.webp)
@@ -113,15 +113,15 @@ Here are the enhancements for the release:
 
 ### Import Customizations from Jira
 
-An **Import Customization** button has been added to the Jira Strongpoint form. You can import an
+An **Import Customization** button has been added to the Jira form. You can import an
 xml file exported from a Jira ticket.
 ![Jira Strongpoint form](/images/platgovnetsuite/release_notes/jira_strongpoint_form.webp)
 
 ### Enable Allow NS to Jira Push
 
 This feature must be enabled before you can create tickets from NetSuite to Jira.
 
-1. Open **Strongpoint** > **Strongpoint Support** > **Installation Settings**
+1. Open **Netwrix** > **Strongpoint Support** > **Installation Settings**
 2. Open the **Jira Integration** tab
 3. Check **Allow NS to Jira Push** to enable pushing NetSuite change requests into Jira.
 
@@ -132,7 +132,7 @@ This feature must be enabled before you can create tickets from NetSuite to Jira
 Create Ticket from NetSuite to Jira must be enabled before you can create tickets from NetSuite to
 Jira.
 
-1. Create or open a change request in Strongpoint.
+1. Create or open a change request in Platform Governance for NetSuite.
 2. Add your information and customizations.
 3. Click **Push to Jira**.
 4. Select your Jira project.

docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-1_release_notes.md

@@ -1,10 +1,10 @@
 ---
-title: "Netwrix Strongpoint for Netsuite 7.1 Release Notes"
-description: "Netwrix Strongpoint for Netsuite 7.1 Release Notes"
+title: "Netwrix Platform Governance for NetSuite 7.1 Release Notes"
+description: "Netwrix Platform Governance for NetSuite 7.1 Release Notes"
 sidebar_position: 30
 ---
 
-# Netwrix Strongpoint for Netsuite 7.1 Release Notes
+# Netwrix Platform Governance for NetSuite 7.1 Release Notes
 
 ## Core 7.1.2.1
 
@@ -27,7 +27,7 @@ November 30, 2023
 
 November 2, 2023
 
-- Removed **People Related to Customization** search from the **Strongpoint** > **Customization**
+- Removed **People Related to Customization** search from the **Netwrix** > **Customization**
   menu.
 - Increased the number of employees and roles for User Provisioning per run. If there are more than
   the limit, multiple runs are processed. The **User Provisioning Error** field reports the Change
@@ -194,7 +194,7 @@ Enable Allow NS to Jira Push
 
 This feature must be enabled before you can create tickets from NetSuite to Jira.
 
-1. Open **Strongpoint** > **Strongpoint Support** > **Installation Settings**
+1. Open **Netwrix** > **Strongpoint Support** > **Installation Settings**
 2. Open the **Jira Integration** tab
 3. Check **Allow NS to Jira Push** to enable pushing NetSuite change requests into Jira.
 

docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-2_release_notes.md

@@ -6,7 +6,7 @@ sidebar_position: 20
 
 # Core 7.2
 
-Netwrix Strongpoint for NetSuite 7.2 Release Notes
+Netwrix Platform Governance for NetSuite 7.2 Release Notes
 
 ## Core 7.2
 

docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-3_release_notes.md

@@ -6,7 +6,7 @@ sidebar_position: 10
 
 # Core 7.3.2
 
-Netwrix Strongpoint for Netsuite 7.3 Release Notes
+Netwrix Platform Governance for NetSuite 7.3 Release Notes
 
 ## Core 7.3.2
 
@@ -37,7 +37,7 @@ March 18, 2024
 - Updated library to SuiteScript 2.x to support customization audit tags.
 - Updated Strongpoint bundle component changes to be flagged as Managed Bundle instead of
   nonmaterial SP Bundle Change.
-- Updated the Search results link for **Strongpoint** > **Change Management Reports** > **Policy
+- Updated the Search results link for **Netwrix** > **Change Management Reports** > **Policy
   Changes** to open **Strongpoint Policy Changes**. This is the same report as the one available in
   the **Reminders** portlet.
 - Updated the Strongpoint _customscript_flo_create_error_proc_issue_ script to be a maximum of 4000

docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup.md

@@ -53,7 +53,7 @@ Menu options are available to access the rules and lists:
 Search Clean Up rules are created by the administrator and used to locate Saved Searches matching
 the rule criteria. Search Clean Up rules are used for both Automatic and Run Now.
 
-To create or edit rules, access **Strongpoint**> **Automated Search Clean Up** > **Search Clean Up
+To create or edit rules, access **Netwrix** > **Automated Search Clean Up** > **Search Clean Up
 Rules**
 
 ![autocleanup](/images/platgovnetsuite/clean_up/autocleanup.webp)
@@ -203,7 +203,7 @@ searches**, **retained searches**, **scheduled to be archived searches** and **a
 
 ## Search Clean Up Status
 
-Open **Strongpoint**> **Search Auto Clean Up** > **Search Clean Up Status** to view current status.
+Open **Netwrix** > **Search Auto Clean Up** > **Search Clean Up Status** to view current status.
 
 - **Job Type**: **Run Now** or **Automatic**.
 - **Status**:

docs/platgovnetsuite/change_management_reports.md

@@ -8,7 +8,7 @@ sidebar_position: 90
 
 To access change management reports:
 
-Open **Strongpoint** > **Change Management Reports** and one of the available reports:
+Open **Netwrix** > **Change Management Reports** and one of the available reports:
 
 - Policy Changes
 - Open Non-Compliant Changes

docs/platgovnetsuite/changemanagement/approving_policy_changes.md

@@ -6,7 +6,7 @@ sidebar_position: 50
 
 # Approving Policy Changes
 
-1. Open **Strongpoint** > **Change Management Tools** > **Policy Change Approval (Beta)
+1. Open **Netwrix** > **Change Management Tools** > **Policy Change Approval
    ![policy_approval_new](/images/platgovnetsuite/change_management/policy_approval_new.webp)**
 2. Enter information into the required **Name**, **Change Overview** and **Policies** fields.
    **Change Type** is preset to **Policy Change Approval**.

docs/platgovnetsuite/changemanagement/comparing_environments.md

@@ -21,7 +21,7 @@ notification that there were more than 1000 records to compare and to restrict t
 Your TBA Credentials only need to be set up once. These are the credentials you need to run Compare
 Environments and to use the **Change Account** feature on a Change Requests.
 
-1. Open **Strongpoint** > **Change Management Tools** > **Compare Environments**
+1. Open **Netwrix** > **Change Management Tools** > **Compare Environments**
 
     ![Set up your TBA Credentials](/images/platgovnetsuite/change_management/tba_cred_1.webp)
 
@@ -54,7 +54,7 @@ Token-based authentication (TBA) is required by NetSuite. Follow the steps in t
 TBA Credentials** section the first time you use this feature.
 :::
 
-1. Open **Strongpoint** > **Change Management Tools** > **Compare Environments**
+1. Open **Netwrix** > **Change Management Tools** > **Compare Environments**
 
     ![Compare Environments](/images/platgovnetsuite/change_management/comp_env.webp)
 
@@ -172,7 +172,7 @@ to ensure the environments are synchronized.
 
 Environment comparison can be used on any Customization Type, including Body Fields.
 
-1. Open **Strongpoint** > **Change Management Tools** > **Compare Environments**.
+1. Open **Netwrix** > **Change Management Tools** > **Compare Environments**.
 2. Enter the **Name**, select the **Source** and **Target** environments and all the required
    credential information.
 3. Select **Body Field** for the **Customization Type**.

docs/platgovnetsuite/changemanagement/completing_validating_change_request.md

@@ -8,7 +8,7 @@ sidebar_position: 130
 
 Once the changes are complete, validate the Change Request and mark it **Complete**.
 
-1. Open **Strongpoint** > **Change Management Tools** > **Change Request** to view the list of
+1. Open **Netwrix** > **Change Management Tools** > **Change Request** to view the list of
    Change Requests.
 2. Locate your Change Request and click **View**
 3. Click **Respider Now** to start the change documentation process.

docs/platgovnetsuite/changemanagement/creating_change_request.md

@@ -23,7 +23,7 @@ request in your sandbox account.
 
 ## Create the Change Request
 
-1. Open **Strongpoint** > **Change Management Tools** > **ITGC Change Request**
+1. Open **Netwrix** > **Change Management Tools** > **ITGC Change Request**
    The status bar displays the stage of the Change Request. A new change request displays _Not
    Started_.
 2. Enter information in the **Main** and **Scope** sections:

docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md

@@ -16,7 +16,7 @@ impacts and the level of change required.
 
 To do this, in your **production** account:
 
-1. Open **Strongpoint** > **Change Management Tools** > **Change Request** > **New**
+1. Open **Netwrix** > **Change Management Tools** > **Change Request** > **New**
 2. Fill in the following fields in the **Main** section of the change request:
 
     - **Name**: Add a name to the change request.

docs/platgovnetsuite/changemanagement/example_sample_change.md

@@ -8,7 +8,7 @@ sidebar_position: 160
 
 ## New Object Compliant Change with a Change Request
 
-1. Open **Strongpoint** > **Change Management Tools** > **Change Request** > **New**
+1. Open **Netwrix** > **Change Management Tools** > **Change Request** > **New**
 2. Enter a **Name** and **Change Overview**.
 3. Click **Lookup Customization**. Enter a sample **Name** and set **Type** to **Entity Field**.
 4. Click **Add Selected Customization** to add the field as a proposed customization.
@@ -32,13 +32,13 @@ sidebar_position: 160
 
 ## Create the Entity Field
 
-1. Open **Strongpoint** > **Customizations** > **Customization** > **New**
+1. Open **Netwrix** > **Customizations** > **Customization** > **New**
 2. Add the **Name** of your proposed entity field customization.
 3. Select **Entity Field** for **Type**.
 4. Click **Save**.
 5. Open the **Change Log** tab to view the change.
 6. Check **Customer** on the **Applies To** tab.
-7. Open **Strongpoint** > **Change Management Tools** > **Change Request**
+7. Open **Netwrix** > **Change Management Tools** > **Change Request**
 8. Select your **Change Request** from the list.
 9. Click **Respider Now**.
 
@@ -64,6 +64,6 @@ This change will be flagged as non-compliant and appear on the report as **Non-C
 
 ## Open the Non-Compliant Changes Report
 
-1. Open **Strongpoint** > **Change Management Reports** > **Open Non-Compliant Changes**
+1. Open **Netwrix** > **Change Management Reports** > **Open Non-Compliant Changes**
 2. Set the **Date Created** to **Today**
 3. Resolve and close non-compliant change.

docs/platgovnetsuite/changemanagement/multi_environment_change_management.md

@@ -27,10 +27,10 @@ least the Strongpoint Developer Role to perform a Change Request Push.
 A best practice is to create change requests in your production account so that they are not lost,
 they have an audit trail and approvals can be shown.
 
-1. Open **Strongpoint** > **Change Management Tools** > **ITGC Change Request**.
+1. Open **Netwrix** > **Change Management Tools** > **ITGC Change Request**.
 2. Enter all required fields and additional approver(s).
 3. Click Pending Approval. Wait until the Change Request is approved.
-4. Open **Strongpoint** > **Change Management Tools** > **ITGC Change Request**.
+4. Open **Netwrix** > **Change Management Tools** > **ITGC Change Request**.
 5. Click **Edit** on the appropriate Change Request.
 6. Open the **Sync Tool** tab on the Change Request.
 7. Set the **Target** environment (where the Change Request will be pushed).
@@ -42,7 +42,7 @@ they have an audit trail and approvals can be shown.
 
 ## Update the Change Request in Testing/Development
 
-1. Open **Strongpoint** > **Change Management Tools** > **Change Request**
+1. Open **Netwrix** > **Change Management Tools** > **Change Request**
 2. Click **Edit** on the Change Request that came from Production.
 
     - Attach **customizations created/updated**.
@@ -59,7 +59,7 @@ they have an audit trail and approvals can be shown.
 
 ## Run Pre-Deployment Environment Comparison
 
-1. Run **Strongpoint** > **Change Management Tools** > **Compare Environments**
+1. Run **Netwrix** > **Change Management Tools** > **Compare Environments**
 2. Enter the login credentials of the **Target** and **Source** Accounts.
 3. Set the **Comparison Type** to **Target Newer than Source**.
 4. Click the **Compare** button.
@@ -72,7 +72,7 @@ record is approved, deploy the customizations listed on the change request.
 
 In your Production environment:
 
-1. Open **Strongpoint** > **Change Management Tools** > **Change Request**
+1. Open **Netwrix** > **Change Management Tools** > **Change Request**
 2. **Edit** your **master** Change Request.
 3. Open **Related Change Records** tab.
 4. Open **Change Request** tab.
@@ -85,7 +85,7 @@ In your Production environment:
 
 ## Run Post-Deployment Environment Comparison
 
-1. Run **Strongpoint** > **Change Management Tools** > **Compare Environments**
+1. Run **Netwrix** > **Change Management Tools** > **Compare Environments**
 2. Enter the login credentials of the **Target** and **Source** Accounts.
 3. Set the **Comparison Type** to **Target Newer than Source**.
 4. Click the **Compare** button.

docs/platgovnetsuite/changemanagement/opportunisticclearance/opportunistic_clearance.md

@@ -10,7 +10,7 @@ Many non-compliant change logs are generated due to one or more related objects
 in a Change Request. You can set up to automatically clear low risk non-compliant changes that meet
 specific criteria. By default, opportunistic clearance is not enabled. To enable it:
 
-1. Open **Strongpoint** > **Strongpoint Support** > **Installation Settings**
+1. Open **Netwrix** > **Strongpoint Support** > **Installation Settings**
 2. Click **Edit** to open **Configuration and Stats**.
 3. Select the **Change Management** tab.
 4. Select **Enable Opportunistic Clearance**.

docs/platgovnetsuite/changemanagement/resolving_non_compliant_changes.md

@@ -8,7 +8,7 @@ sidebar_position: 150
 
 To access the Open Non-Compliant Changes Report:
 
-1. Open **Strongpoint** > **Change Management Reports** > **Open NonCompliant Changes**
+1. Open **Netwrix** > **Change Management Reports** > **Open NonCompliant Changes**
    The Non-Compliant Changes Report gives you a list of the [Change Logs](/docs/platgovnetsuite/changemanagement/using_change_logs.md). You
    can filter the report or sort by the column heads.