From 350829d5c554607f91e6cc05c7d7e245ef13e331 Mon Sep 17 00:00:00 2001 From: aleksander-tyrnov_nwx Date: Thu, 30 Apr 2026 22:19:14 +0200 Subject: [PATCH 01/27] update(accessanalyzer): replace curl-pipe installer with binary download steps Updates installation commands in install-commands.md and quickinstall.md to use the new dspm-installer binary download approach instead of the deprecated curl-pipe-to-bash pattern. Hides superseded content sections with HTML comments. Generated with AI Co-Authored-By: Claude Code --- .../2601/install/install-commands.md | 34 +++++++++++++++---- .../2601/install/quickinstall.md | 18 +++++++--- 2 files changed, 41 insertions(+), 11 deletions(-) diff --git a/docs/accessanalyzer/2601/install/install-commands.md b/docs/accessanalyzer/2601/install/install-commands.md index b63e417280..06fc1e88da 100644 --- a/docs/accessanalyzer/2601/install/install-commands.md +++ b/docs/accessanalyzer/2601/install/install-commands.md @@ -32,8 +32,16 @@ Your license key authenticates access to the Netwrix package registry. Don't sha # Set the Keygen license key variable export LICENSE_KEY='[YOUR_LICENSE_KEY]' -# Run installation -curl -sLfo - "https://raw.pkg.keygen.sh/v1/accounts/netwrix/artifacts/dspm-install.sh?auth=license:$LICENSE_KEY" | bash - +# Download and install the DSPM installer binary for your Linux system architecture (x86_64 or ARM64) using your license key. +ARCH=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/') +TMP_FILE=$(mktemp) +curl -sLf -o "$TMP_FILE" "https://raw.pkg.keygen.sh/v1/accounts/netwrix/artifacts/dspm-installer-linux-$ARCH?auth=license:$LICENSE_KEY" +sudo install -m 0755 "$TMP_FILE" "/usr/local/bin/dspm-installer" +rm -f "$TMP_FILE" + +# Launches the installation wizard +sudo dspm-installer --license-key '$LICENSE_KEY' +Use "dspm-installer [command] --help" for more information about a command. ``` **To pin to a specific release** — recommended when you want to control when upgrades happen during your organization's patching cycle — export the version before running the same curl command: @@ -45,8 +53,18 @@ export LICENSE_KEY='[YOUR_LICENSE_KEY]' # Pin to a specific release version export DSPM_TARGET_REVISION='[VERSION]' -# Run installation -curl -sLfo - "https://raw.pkg.keygen.sh/v1/accounts/netwrix/artifacts/dspm-install.sh?auth=license:$LICENSE_KEY" | bash - +# Download and install the DSPM installer binary for your Linux system architecture (x86_64 or ARM64) using your license key. +ARCH=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/') +TMP_FILE=$(mktemp) +curl -sLf -o "$TMP_FILE" "https://raw.pkg.keygen.sh/v1/accounts/netwrix/artifacts/dspm-installer-linux-$ARCH?auth=license:$LICENSE_KEY" +sudo install -m 0755 "$TMP_FILE" "/usr/local/bin/dspm-installer" +rm -f "$TMP_FILE" + +# Launches the installation wizard +sudo dspm-installer --license-key '$LICENSE_KEY' + +Use "dspm-installer [command] --help" for more information about a command. + ``` Version strings control which release is installed and what auto-upgrades apply: @@ -106,6 +124,8 @@ When you run the curl command, the installer automatically: Installation typically takes 15–30 minutes depending on network speed and hardware. +--- + ## If the Installer Stops with Warnings By default, the installer stops when a preflight warning is detected. In some cases you may know the warning is acceptable for your environment. Use `--accept-warnings` to allow installation to continue: ```bash -curl -sLfo - "https://raw.pkg.keygen.sh/v1/accounts/netwrix/artifacts/dspm-install.sh?auth=license:$LICENSE_KEY" | bash -s -- --accept-warnings +sudo dspm-installer --accept-warnings ``` Before using this option, identify which warning is being reported and review the guidance below: diff --git a/docs/accessanalyzer/2601/install/quickinstall.md b/docs/accessanalyzer/2601/install/quickinstall.md index 9e44397475..9f5002ab21 100644 --- a/docs/accessanalyzer/2601/install/quickinstall.md +++ b/docs/accessanalyzer/2601/install/quickinstall.md @@ -244,10 +244,20 @@ For most deployments, either omit this variable to stay on the latest release, o Download the installer: ```bash -curl -sLfo /tmp/dspm-install.sh \ - "https://raw.pkg.keygen.sh/v1/accounts/netwrix/artifacts/dspm-install.sh?auth=license:${LICENSE_KEY}" -``` +# Download and install the DSPM installer binary for your Linux system architecture (x86_64 or ARM64) using your license key. +ARCH=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/') +TMP_FILE=$(mktemp) +curl -sLf -o "$TMP_FILE" "https://raw.pkg.keygen.sh/v1/accounts/netwrix/artifacts/dspm-installer-linux-$ARCH?auth=license:$LICENSE_KEY" +sudo install -m 0755 "$TMP_FILE" "/usr/local/bin/dspm-installer" +rm -f "$TMP_FILE" + +# Launches the installation wizard +sudo dspm-installer --license-key '$LICENSE_KEY' + +Use "dspm-installer [command] --help" for more information about a command. +``` + ### Step 4: Verify the installation After the installer completes, confirm all pods are healthy: From 1ff495efc4667dbe38e5de8c1a204b4cf53dc50c Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Thu, 30 Apr 2026 20:29:16 +0000 Subject: [PATCH 02/27] fix(dale): auto-fix documentation issues (AI-assisted) --- docs/accessanalyzer/2601/install/install-commands.md | 4 ++-- docs/accessanalyzer/2601/install/quickinstall.md | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/accessanalyzer/2601/install/install-commands.md b/docs/accessanalyzer/2601/install/install-commands.md index 06fc1e88da..a2f7383cb5 100644 --- a/docs/accessanalyzer/2601/install/install-commands.md +++ b/docs/accessanalyzer/2601/install/install-commands.md @@ -67,7 +67,7 @@ Use "dspm-installer [command] --help" for more information about a command. ``` -Version strings control which release is installed and what auto-upgrades apply: +Version strings control which release the installer installs and what auto-upgrades apply: | Value | Behavior | | --- | --- | @@ -253,7 +253,7 @@ By default, the installer stops when a preflight warning is detected. In some ca sudo dspm-installer --accept-warnings ``` -Before using this option, identify which warning is being reported and review the guidance below: +Before using this option, identify which warning the installer reports and review the following: | Warning | What it means | Recommended action | |---|---|---| diff --git a/docs/accessanalyzer/2601/install/quickinstall.md b/docs/accessanalyzer/2601/install/quickinstall.md index 9f5002ab21..9943008e87 100644 --- a/docs/accessanalyzer/2601/install/quickinstall.md +++ b/docs/accessanalyzer/2601/install/quickinstall.md @@ -54,7 +54,7 @@ See [TLS Certificate Requirements](system/certificates.md) for the full specific - **Application TLS certificate** (PEM). The Subject Alternative Name (SAN) list must include `DSPM_HOSTNAME` **in lowercase** and the server's IP address. - **Private key** paired with the certificate (PEM). Must be readable by the OS user running the installer, not just `root`. -- **CA bundle** (PEM). Must contain the CA that signed the application certificate. If using AD authentication, it must also contain the CA that signed the domain controller's LDAPS certificate. If these are different CAs, concatenate them: +- **CA bundle** (PEM). Must contain the CA that signed the application certificate. For AD authentication, the CA bundle must also contain the CA that signed the domain controller's LDAPS certificate. If these are different CAs, concatenate them: ```bash cat app-ca.crt ldaps-ca.crt > ca-bundle.crt @@ -120,7 +120,7 @@ Ports the Access Analyzer server must be able to reach on your data sources and - **Outbound** from the Access Analyzer server to the target source/host — **required** for all connectors. - **Inbound** at the target source/host from the Access Analyzer server — **required** (the target must accept the connection on the listed port). -- **Two-way communication** between the Access Analyzer server and the target — **optional**. Can be configured for environments that require it, but not required for any connector. +- **Two-way communication** between the Access Analyzer server and the target — **optional**. You can configure it for environments that require it, but no connector requires it. | Connector | Port | Protocol | Notes | | --- | --- | --- | --- | @@ -318,7 +318,7 @@ The installer seeds a bootstrap account, `admin@dspm.local`, with the **User Adm 5. Pre-provision each user who should be able to sign in. For each user: - Click **+ Add User**. - Enter the Name and Email. The email must match the user's AD `mail` attribute exactly, **including case**. - - Assign a role (see [Roles](#roles) below). + - Assign a role (see [Roles](#roles)). Assign at least one user the **Administrator** role — the bootstrap account can't access system configuration, so someone needs to. Assign at least one additional user the **User Admin** role if you want a non-bootstrap user to manage accounts going forward. From e6418e814c792885a43bf1a00262d744b7caab72 Mon Sep 17 00:00:00 2001 From: AleksNWX Date: Mon, 4 May 2026 13:36:49 +0200 Subject: [PATCH 03/27] Apply suggestion from @markis Co-authored-by: Markis Taylor --- docs/accessanalyzer/2601/install/install-commands.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/accessanalyzer/2601/install/install-commands.md b/docs/accessanalyzer/2601/install/install-commands.md index a2f7383cb5..eb56d2e91e 100644 --- a/docs/accessanalyzer/2601/install/install-commands.md +++ b/docs/accessanalyzer/2601/install/install-commands.md @@ -40,7 +40,7 @@ sudo install -m 0755 "$TMP_FILE" "/usr/local/bin/dspm-installer" rm -f "$TMP_FILE" # Launches the installation wizard -sudo dspm-installer --license-key '$LICENSE_KEY' +sudo dspm-installer Use "dspm-installer [command] --help" for more information about a command. ``` From 1957b428f3909b0a7db6a5aff36ffdcfa5e81d1f Mon Sep 17 00:00:00 2001 From: AleksNWX Date: Mon, 4 May 2026 13:37:39 +0200 Subject: [PATCH 04/27] Apply suggestion from @markis Co-authored-by: Markis Taylor --- docs/accessanalyzer/2601/install/install-commands.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/accessanalyzer/2601/install/install-commands.md b/docs/accessanalyzer/2601/install/install-commands.md index eb56d2e91e..7d149943dd 100644 --- a/docs/accessanalyzer/2601/install/install-commands.md +++ b/docs/accessanalyzer/2601/install/install-commands.md @@ -61,7 +61,7 @@ sudo install -m 0755 "$TMP_FILE" "/usr/local/bin/dspm-installer" rm -f "$TMP_FILE" # Launches the installation wizard -sudo dspm-installer --license-key '$LICENSE_KEY' +sudo dspm-installer Use "dspm-installer [command] --help" for more information about a command. From 62dd651ba49928b45892a583c340724ac1aa3ff4 Mon Sep 17 00:00:00 2001 From: AleksNWX Date: Mon, 4 May 2026 13:37:53 +0200 Subject: [PATCH 05/27] Apply suggestion from @markis Co-authored-by: Markis Taylor --- docs/accessanalyzer/2601/install/quickinstall.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/accessanalyzer/2601/install/quickinstall.md b/docs/accessanalyzer/2601/install/quickinstall.md index 9943008e87..c8f2256d71 100644 --- a/docs/accessanalyzer/2601/install/quickinstall.md +++ b/docs/accessanalyzer/2601/install/quickinstall.md @@ -253,7 +253,7 @@ sudo install -m 0755 "$TMP_FILE" "/usr/local/bin/dspm-installer" rm -f "$TMP_FILE" # Launches the installation wizard -sudo dspm-installer --license-key '$LICENSE_KEY' +sudo dspm-installer Use "dspm-installer [command] --help" for more information about a command. ``` From 754dbd77cfa71745ab1d3c6b4c3a37481eeee342 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Mon, 4 May 2026 11:43:56 +0000 Subject: [PATCH 06/27] fix(vale): auto-fix style issues (Vale + Dale) --- docs/accessanalyzer/2601/install/quickinstall.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/accessanalyzer/2601/install/quickinstall.md b/docs/accessanalyzer/2601/install/quickinstall.md index c8f2256d71..6614dd8e1b 100644 --- a/docs/accessanalyzer/2601/install/quickinstall.md +++ b/docs/accessanalyzer/2601/install/quickinstall.md @@ -6,7 +6,7 @@ sidebar_position: 5 # Quick Install -This guide walks through installing Access Analyzer on a fresh Linux VM with **Active Directory** as the identity provider. +This guide covers installing Access Analyzer on a fresh Linux VM with **Active Directory** as the identity provider. For the CLI-flag reference, see [Configure Identity Provider](identity-provider.md). @@ -53,7 +53,7 @@ If running on a hypervisor, configure **static memory allocation** (not dynamic/ See [TLS Certificate Requirements](system/certificates.md) for the full specification. At a minimum you need: - **Application TLS certificate** (PEM). The Subject Alternative Name (SAN) list must include `DSPM_HOSTNAME` **in lowercase** and the server's IP address. -- **Private key** paired with the certificate (PEM). Must be readable by the OS user running the installer, not just `root`. +- **Private key** paired with the certificate (PEM). The OS user running the installer must be able to read it, not just `root`. - **CA bundle** (PEM). Must contain the CA that signed the application certificate. For AD authentication, the CA bundle must also contain the CA that signed the domain controller's LDAPS certificate. If these are different CAs, concatenate them: ```bash @@ -219,7 +219,7 @@ export LDAP_EMAIL_ATTRIBUTE="mail" | `LICENSE_KEY` | Netwrix license key | `NWRX-XXXX-XXXX-XXXX` | | `DSPM_HOSTNAME` | Fully qualified domain name. Must be lowercase and match the cert SAN | `aa2601.corp.example.com` | | `TLS_CERT_FILE` | Full path to PEM server certificate | `/opt/dspm-tls/aa2601.crt` | -| `TLS_KEY_FILE` | Full path to PEM private key. Must be readable by the install user | `/opt/dspm-tls/aa2601.key` | +| `TLS_KEY_FILE` | Full path to PEM private key. The install user must be able to read this file | `/opt/dspm-tls/aa2601.key` | | `TLS_CA_BUNDLE_FILE` | Full path to CA bundle (application CA + LDAPS DC CA) | `/opt/dspm-tls/ca-bundle.crt` | | `IDP_TYPE` | Identity provider type | `ad` | | `IDP_ALIAS` | Login button label. Letters, digits, hyphens, underscores, dots only | `active-directory` | From 3502e538770d12a456dc159c963db1cc43a13601 Mon Sep 17 00:00:00 2001 From: AleksNWX Date: Mon, 4 May 2026 14:19:53 +0200 Subject: [PATCH 07/27] Update install-commands.md --- .../2601/install/install-commands.md | 21 +++++++++++-------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/docs/accessanalyzer/2601/install/install-commands.md b/docs/accessanalyzer/2601/install/install-commands.md index 7d149943dd..8b35f6fc8a 100644 --- a/docs/accessanalyzer/2601/install/install-commands.md +++ b/docs/accessanalyzer/2601/install/install-commands.md @@ -15,10 +15,10 @@ You install Access Analyzer using a single curl command that downloads and runs Export your license key as an environment variable before running any installer command. This keeps the key out of your shell history and makes it available to the installer automatically. ```bash -export LICENSE_KEY='[YOUR_LICENSE_KEY]' +export LICENSE_KEY="[YOUR_LICENSE_KEY]]" ``` -Replace `[YOUR_LICENSE_KEY]` with the license key provided by Netwrix. All examples on this page assume you have exported this variable. +Replace "[YOUR_LICENSE_KEY]" with the license key provided by Netwrix. All examples on this page assume you have exported this variable. :::warning Your license key authenticates access to the Netwrix package registry. Don't share it, commit it to version control, or leave it visible in script files. @@ -41,17 +41,18 @@ rm -f "$TMP_FILE" # Launches the installation wizard sudo dspm-installer -Use "dspm-installer [command] --help" for more information about a command. ``` +Use "dspm-installer [command] --help" for more information about a command. + **To pin to a specific release** — recommended when you want to control when upgrades happen during your organization's patching cycle — export the version before running the same curl command: ```bash # Set the Keygen license key variable -export LICENSE_KEY='[YOUR_LICENSE_KEY]' +export LICENSE_KEY='[Y]' # Pin to a specific release version -export DSPM_TARGET_REVISION='[VERSION]' +export TARGET_REVISION='[VERSION]' # Download and install the DSPM installer binary for your Linux system architecture (x86_64 or ARM64) using your license key. ARCH=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/') @@ -62,16 +63,16 @@ rm -f "$TMP_FILE" # Launches the installation wizard sudo dspm-installer +``` Use "dspm-installer [command] --help" for more information about a command. -``` Version strings control which release the installer installs and what auto-upgrades apply: | Value | Behavior | | --- | --- | -| (unset) | Installs the latest release; auto-upgrades to the latest version with no limit | +| (unset) | Defaults to 1.* — auto-upgrades within the 1.x line; a future 2.x release will not be installed automatically | | `1.0.8` | Pinned to exactly 1.0.8 — no auto-upgrade | | `1.*` | Auto-upgrades to any 1.x version | @@ -87,7 +88,7 @@ Export the variables before running the installer. When you set the same option | --- | --- | --- | | `LICENSE_KEY` | `--license-key` | `NWRX-XXXX-XXXX-XXXX` | | `DSPM_HOSTNAME` | `--hostname` | `aa2601.corp.example.com` | -| `DSPM_TARGET_REVISION` | `--target-revision` | `1.0.8` (pinned) or omit for latest | +| `TARGET_REVISION` | `--target-revision` | `1.0.8` (pinned) or omit for latest | | `SIZE` | `--size` | `1` (default), `2`, up to `10` | | `TLS_CERT_FILE` | `--tls-cert` | `/opt/dspm-tls/aa2601.crt` | | `TLS_KEY_FILE` | `--tls-key` | `/opt/dspm-tls/aa2601.key` | @@ -191,6 +192,8 @@ curl -sLfo - "https://raw.pkg.keygen.sh/v1/accounts/netwrix/artifacts/dspm-insta ``` The installer writes the log to `/var/log/dspm-installer.log`. Accepted values are `debug`, `info`, `warn`, and `error`. The default is `info`. Terminal progress output isn't affected — only the log file verbosity changes. + +END HIDDEN --> --- ## Identity Provider Flags @@ -244,7 +247,7 @@ The installer checks the following before installation begins. The installer wri A **FAIL** result stops the installer. Resolve it before retrying. A **WARN** result also stops the installer by default — see [If the Installer Stops with Warnings](#if-the-installer-stops-with-warnings). For the full list of required network domains, see [Network and Port Requirements](/docs/accessanalyzer/2601/install/system/network). -END HIDDEN --> + ## If the Installer Stops with Warnings By default, the installer stops when a preflight warning is detected. In some cases you may know the warning is acceptable for your environment. Use `--accept-warnings` to allow installation to continue: From 9dd27b00f88774657f6b2b65e6fbc470ab46ef14 Mon Sep 17 00:00:00 2001 From: AleksNWX Date: Mon, 4 May 2026 14:21:22 +0200 Subject: [PATCH 08/27] Update quickinstall.md --- docs/accessanalyzer/2601/install/quickinstall.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/accessanalyzer/2601/install/quickinstall.md b/docs/accessanalyzer/2601/install/quickinstall.md index 6614dd8e1b..69bca88e56 100644 --- a/docs/accessanalyzer/2601/install/quickinstall.md +++ b/docs/accessanalyzer/2601/install/quickinstall.md @@ -227,7 +227,7 @@ export LDAP_EMAIL_ATTRIBUTE="mail" | `LDAP_BIND_DN` | Distinguished name of the read-only service account | `CN=svc-dspm,OU=ServiceAccounts,DC=corp,DC=example,DC=com` | | `LDAP_USERS_DN` | Base DN for the OU containing user accounts | `CN=Users,DC=corp,DC=example,DC=com` | | `LDAP_EMAIL_ATTRIBUTE` | LDAP attribute storing the user's email address | `mail` | -| `DSPM_TARGET_REVISION` | (Optional) Controls which version is installed and auto-upgraded to. Omit to stay on the latest release. | `1.0.8` | +| `TARGET_REVISION` | (Optional) Controls which version is installed and auto-upgraded to. Omit to stay on the latest release. | `1.0.8` | **Version syntax for `DSPM_TARGET_REVISION`:** @@ -254,9 +254,9 @@ rm -f "$TMP_FILE" # Launches the installation wizard sudo dspm-installer - -Use "dspm-installer [command] --help" for more information about a command. ``` + +Use "dspm-installer [command] --help" for more information about a command. --- ## Identity Provider Flags -The following table lists every IdP flag the installer accepts. For end-to-end examples, see one of these walkthroughs: +The following table lists every identity provider (IdP) flag the installer accepts. For end-to-end examples, see one of these walkthroughs: - [Quick Install](quickinstall.md) — Active Directory deployment using environment variables (recommended for most customers) - [Configure Identity Provider](identity-provider.md) — example commands for Active Directory and LDAP, plus recovery with `--configure-idp-only` diff --git a/docs/accessanalyzer/2601/install/quickinstall.md b/docs/accessanalyzer/2601/install/quickinstall.md index feb29ef2a7..2b54e5f910 100644 --- a/docs/accessanalyzer/2601/install/quickinstall.md +++ b/docs/accessanalyzer/2601/install/quickinstall.md @@ -440,7 +440,7 @@ This table is also published at [Configuration > Identity Provider > Roles](../c | **User Admin** | User and role management rights only: create, edit, activate, deactivate, and delete users; assign roles; pre-provision federated users. Does **not** have system configuration rights. The installer assigns this role to the bootstrap `admin@dspm.local` account. | | **Viewer** | Read-only access to data and reports. No configuration or user management rights. | -The **User Admin** role exists to provide a dedicated account for user management with no system configuration access — useful for delegating user administration separately from system configuration. The installer seeds the bootstrap `admin@dspm.local` account as User Admin — you'll use it to pre-provision the rest of your users, including your first Administrator. +The **User Admin** role provides a dedicated account for user management with no system configuration access — useful for delegating user administration separately from system configuration. The installer seeds the bootstrap `admin@dspm.local` account as User Admin — you'll use it to pre-provision the rest of your users, including your first Administrator. From 0ecf1921d5312eb9c54426ccdc3ab59f0fcfe870 Mon Sep 17 00:00:00 2001 From: aleksander-tyrnov_nwx Date: Mon, 4 May 2026 15:11:07 +0200 Subject: [PATCH 11/27] fix(accessanalyzer): apply PR #838 review corrections to installer docs - Replace `sudo dspm-installer --license-key '$LICENSE_KEY'` with `sudo dspm-installer` (env var read automatically; single-quotes prevent expansion) - Remove cobra help text line from bash fences (binary output, not a shell command) - Rename `DSPM_TARGET_REVISION` to `TARGET_REVISION` throughout both files - Rename `LDAP_BIND_CREDENTIAL` to `LDAP_BIND_PASSWORD` to match `--ldap-bind-password` flag - Fix "(unset)" version table row to reflect actual `1.*` default behavior - Fix hidden comment boundary in install-commands.md so Identity Provider Flags, Configuration File, and Preflight Check Requirements sections are visible - Add LDAP password prompt note after Step 3 code block in quickinstall.md - Update wording from "same curl command" to "downloading and running the installer" Generated with AI Co-Authored-By: Claude Code --- docs/accessanalyzer/2601/install/install-commands.md | 7 ++++--- docs/accessanalyzer/2601/install/quickinstall.md | 8 +++++--- 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/docs/accessanalyzer/2601/install/install-commands.md b/docs/accessanalyzer/2601/install/install-commands.md index 6b0554ee47..2a7464cadb 100644 --- a/docs/accessanalyzer/2601/install/install-commands.md +++ b/docs/accessanalyzer/2601/install/install-commands.md @@ -45,7 +45,7 @@ sudo dspm-installer Run `dspm-installer [command] --help` to view usage and available options for any command. -**To pin to a specific release** — recommended when you want to control when upgrades happen during your organization's patching cycle — export the version before running the same curl command: +**To pin to a specific release** — recommended when you want to control when upgrades happen during your organization's patching cycle — export the version before downloading and running the installer: ```bash # Set the Keygen license key variable @@ -99,7 +99,7 @@ Export the variables before running the installer. When you set the same option | `LDAP_BIND_DN` | `--ldap-bind-dn` | `CN=svc-dspm,OU=ServiceAccounts,DC=example,DC=com` | | `LDAP_USERS_DN` | `--ldap-users-dn` | `CN=Users,DC=example,DC=com` | | `LDAP_EMAIL_ATTRIBUTE` | `--ldap-email-attribute` | `mail` (default) | -| `LDAP_BIND_CREDENTIAL` | (secret — see Quick Install) | (see Quick Install) | +| `LDAP_BIND_PASSWORD` | (secret — see Quick Install) | (see Quick Install) | | `POSTGRES_DATA_DIR` | `--postgres-data-dir` | `/mnt/ssd/postgres` | | `CLICKHOUSE_DATA_DIR` | `--clickhouse-data-dir` | `/mnt/nvme/clickhouse` | | `ACCEPT_WARNINGS` | `--accept-warnings` | `true` | @@ -110,7 +110,7 @@ Export the variables before running the installer. When you set the same option | `DRY_RUN` | `--dry-run` | `true` | :::note -`LDAP_BIND_CREDENTIAL` is the only secret environment variable, and the installer doesn't actually honor it — the installer always reads the bind password via an interactive prompt or piped stdin, overwriting any exported value. See [Quick Install — Step 3](quickinstall.md#step-3-download-and-run-the-installer) for the two supported ways to provide the password. +`LDAP_BIND_PASSWORD` is the only secret environment variable, and the installer doesn't actually honor it — the installer always reads the bind password via an interactive prompt or piped stdin, overwriting any exported value. See [Quick Install — Step 3](quickinstall.md#step-3-download-and-run-the-installer) for the two supported ways to provide the password. ::: ## Running the Installer @@ -195,6 +195,7 @@ The installer writes the log to `/var/log/dspm-installer.log`. Accepted values a END HIDDEN --> --- + ## Identity Provider Flags The following table lists every identity provider (IdP) flag the installer accepts. For end-to-end examples, see one of these walkthroughs: diff --git a/docs/accessanalyzer/2601/install/quickinstall.md b/docs/accessanalyzer/2601/install/quickinstall.md index 2b54e5f910..47b6748cf5 100644 --- a/docs/accessanalyzer/2601/install/quickinstall.md +++ b/docs/accessanalyzer/2601/install/quickinstall.md @@ -198,7 +198,7 @@ sudo update-ca-certificates Paste and customize the following at the top of your terminal session. Every subsequent command references these variables. ```bash -# export DSPM_TARGET_REVISION="1.0.8" # optional — omit to stay on latest; see version syntax below +# export TARGET_REVISION="1.0.8" # optional — omit to stay on latest; see version syntax below export LICENSE_KEY="" export DSPM_HOSTNAME="" export TLS_CERT_FILE="/opt/dspm-tls/.crt" @@ -229,11 +229,11 @@ export LDAP_EMAIL_ATTRIBUTE="mail" | `LDAP_EMAIL_ATTRIBUTE` | LDAP attribute storing the user's email address | `mail` | | `TARGET_REVISION` | (Optional) Controls which version is installed and auto-upgraded to. Omit to stay on the latest release. | `1.0.8` | -**Version syntax for `DSPM_TARGET_REVISION`:** +**Version syntax for `TARGET_REVISION`:** | Value | Behavior | | --- | --- | -| (unset) | Installs the latest release; auto-upgrades to the latest version with no limit | +| (unset) | Defaults to `1.*` — installs the latest 1.x release and auto-upgrades within 1.x | | `1.0.8` | Pinned to exactly 1.0.8 — no auto-upgrade | | `1.*` | Auto-upgrades to any 1.x version | @@ -256,6 +256,8 @@ rm -f "$TMP_FILE" sudo dspm-installer ``` +When prompted, enter the password for the service account specified in `LDAP_BIND_DN`. + Run `dspm-installer [command] --help` to view usage and available options for any command. -This table is also published at [Configuration > Identity Provider > Roles](../configurations/identity-provider.md#roles). This guide duplicates it here so it reads top-to-bottom. +This table also appears at [Configuration > Identity Provider > Roles](../configurations/identity-provider.md#roles). This guide duplicates it here so it reads top-to-bottom. | Role | Description | | --- | --- | From 65030fbb88278b08010349f860257671ed2659a3 Mon Sep 17 00:00:00 2001 From: aleksander-tyrnov_nwx Date: Mon, 4 May 2026 15:23:26 +0200 Subject: [PATCH 13/27] fix(accessanalyzer): correct double bracket typo in LICENSE_KEY export example Generated with AI Co-Authored-By: Claude Code --- docs/accessanalyzer/2601/install/install-commands.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/accessanalyzer/2601/install/install-commands.md b/docs/accessanalyzer/2601/install/install-commands.md index 0e785891e0..f10d6e6706 100644 --- a/docs/accessanalyzer/2601/install/install-commands.md +++ b/docs/accessanalyzer/2601/install/install-commands.md @@ -15,7 +15,7 @@ You install Access Analyzer using a single curl command that downloads and runs Export your license key as an environment variable before running any installer command. This keeps the key out of your shell history and makes it available to the installer automatically. ```bash -export LICENSE_KEY="[YOUR_LICENSE_KEY]]" +export LICENSE_KEY="[YOUR_LICENSE_KEY]" ``` Replace "[YOUR_LICENSE_KEY]" with the license key Netwrix provided. All examples on this page assume you have exported this variable. From 6a7f083adc8bf5b3b944450ba75d9e4cc8f1aba0 Mon Sep 17 00:00:00 2001 From: jth-nw Date: Mon, 4 May 2026 17:06:52 -0500 Subject: [PATCH 14/27] fix(platgovnetsuite): resolve Vale style issues across all docs Fixes heading capitalization, passive voice, banned terms, and other Netwrix style rule violations across 126 files. 17 remaining warnings are confirmed false positives on UI element names (e.g., "Do Not ReSpider Automatically") that cannot be changed. Generated with AI Co-Authored-By: Claude Code --- .../agent/agent_clear_incident.md | 6 +-- .../agent/agent_example_set_control.md | 2 +- .../agent/agent_getting_started.md | 2 +- docs/platgovnetsuite/agent/agent_lookback.md | 8 +-- docs/platgovnetsuite/agent/agent_overview.md | 10 ++-- ..._strongpoint_netsuite_7-0_release_notes.md | 20 ++++---- ..._strongpoint_netsuite_7-1_release_notes.md | 32 ++++++------ ..._strongpoint_netsuite_7-2_release_notes.md | 12 ++--- ..._strongpoint_netsuite_7-3_release_notes.md | 8 +-- .../automated_search_cleanup.md | 42 ++++++++-------- ...automated_search_cleanup_considerations.md | 14 +++--- .../bundleremoval/bundle_removal_overview.md | 15 +++--- .../categorizing_customizations.md | 6 +-- .../creating_custom_list_and_fields.md | 2 +- .../creating_four_mass_updates.md | 14 +++--- .../exporting_information_to_excel.md | 2 +- .../bundleremoval/final_tasks.md | 6 +-- .../change_management_reports.md | 6 +-- .../approving_change_request.md | 4 +- .../change_and_approval_policy.md | 8 +-- .../change_management_overview.md | 8 +-- .../changing_deactivating_policies.md | 4 +- .../comparing_environments.md | 20 ++++---- .../completing_validating_change_request.md | 2 +- .../creating_change_request.md | 24 ++++----- .../creating_change_request_from_case.md | 4 +- .../creating_change_request_old_form.md | 16 +++--- .../changemanagement/example_sample_change.md | 2 +- .../multi_environment_change_management.md | 14 +++--- .../opportunistic_clearance.md | 12 ++--- .../resolving_non_compliant_changes.md | 2 +- .../setting_up_multi_stream_approval.md | 2 +- .../changemanagement/setting_up_policies.md | 34 ++++++------- .../setting_up_subsidiary_policies.md | 2 +- .../changemanagement/use_custom_cr_forms.md | 4 +- .../changemanagement/user_provisioning.md | 8 +-- .../changemanagement/using_change_logs.md | 14 +++--- .../platgovnetsuite/cleanup/archive_fields.md | 2 +- .../cleanup_customizations_no_active_owner.md | 8 +-- .../cleanup/cleanup_overview.md | 36 +++++++------ .../cleanup/cleanup_unused_customizations.md | 26 +++++----- .../platgovnetsuite/cleanup/date_last_used.md | 26 +++++----- .../platgovnetsuite/cleanup/restore_fields.md | 2 +- .../cleanup/set_up_archive_folder.md | 4 +- .../update_field_description_and_help.md | 2 +- .../customization/customization_overview.md | 4 +- .../identify_impacted_objects.md | 18 +++---- .../customization/integration_record.md | 2 +- .../understanding_customization_record.md | 4 +- .../customization/using_erd.md | 8 +-- docs/platgovnetsuite/faq.md | 37 +++++++------- docs/platgovnetsuite/index.md | 19 ++++--- .../installation/features_by_license_type.md | 2 +- .../installation/go_live_faq.md | 34 ++++++------- .../installation/installation_overview.md | 2 +- .../installation_settings_report.md | 25 +++++----- .../installation/installing_strongpoint.md | 6 +-- .../installation/license_manager.md | 8 +-- .../installation/managing_menus.md | 2 +- .../installation/redeploy_scripts_sandbox.md | 4 +- .../installation/running_the_spider.md | 16 +++--- .../setting_strongpoint_tab_access.md | 6 +-- .../setting_up_auto_spider_alerts.md | 6 +-- .../integrations/integration_mapping.md | 8 +-- .../integrations/integrations.md | 2 +- .../platgovnetsuite/navigating_strongpoint.md | 10 ++-- .../reportabug/list_segments_not_editable.md | 8 +-- .../reportabug/mobile_devices.md | 2 +- .../reportabug/report_a_bug.md | 5 +- .../reportabug/saved_search_times_out.md | 2 +- .../reportabug/spider_page_not_found.md | 2 +- .../reportabug/spider_spins.md | 6 +-- .../system_maintenance_period_error.md | 2 +- .../analyzing_script_performance.md | 37 +++++++------- .../reviewing_script_performance_errors.md | 4 +- .../scriptmgmt/script_mgmt_overview.md | 47 +++++++++-------- .../sod/approving_exceptions_sod_rules.md | 4 +- ...ng_role_with_preapproved_change_request.md | 4 +- ...approved_change_request_clear_violation.md | 6 +-- .../sod/creating_sod_approval_request.md | 8 +-- .../platgovnetsuite/sod/creating_sod_rules.md | 20 ++++---- docs/platgovnetsuite/sod/sod_clean_up.md | 2 +- docs/platgovnetsuite/sod/sod_notifications.md | 2 +- docs/platgovnetsuite/sod/sod_overview.md | 35 +++++++------ docs/platgovnetsuite/sod/sod_reports.md | 8 +-- .../sod/sod_test_case_scenarios.md | 20 ++++---- docs/platgovnetsuite/sod/sod_testing.md | 4 +- .../apioverview/api_overview.md | 8 +-- .../add_update_change_request.md | 4 +- .../delete_customizations_change_request.md | 4 +- .../changerequestapi/get_change_request.md | 2 +- .../apioverview/changerequestapi/get_erd.md | 2 +- .../changerequestapi/get_impact_analysis.md | 4 +- .../changerequestapi/push_change_request.md | 2 +- .../jiraforgeintegration/jira_forge_faq.md | 20 ++++---- .../jira_forge_integration.md | 10 ++-- .../jiraforgeintegration/jira_forge_set_up.md | 46 +++++++++-------- .../jira_forge_walkthrough.md | 50 +++++++++---------- .../jiraintegration/jira_integration.md | 22 ++++---- .../jira_upload_addon_not_showing.md | 2 +- .../jira_walkthrough_example.md | 34 ++++++------- .../ticketingintegrations/process_issues.md | 22 ++++---- .../servicenow_create_ticket.md | 6 +-- .../servicenow_install_configure_netsuite.md | 16 +++--- .../servicenow_integration.md | 6 +-- .../ticketing_integrations.md | 2 +- .../zendeskintegration/zendesk_integration.md | 8 +-- .../zendesk_walkthrough_example.md | 22 ++++---- docs/platgovnetsuite/uar/access_app.md | 6 +-- .../add_reviewer_membership_reviews.md | 4 +- .../add_reviewer_overview.md | 2 +- .../add_reviewer_uar_list.md | 14 +++--- .../uar/adminoverview/admin_overview.md | 2 +- .../uar/adminoverview/admin_owner_list.md | 18 +++---- .../admin_pending_assignments.md | 10 ++-- .../uar/adminoverview/admin_uar_list.md | 24 ++++----- .../adminoverview/owner_membership_reviews.md | 8 +-- .../adminoverview/owner_permission_reviews.md | 8 +-- .../uar/adminoverview/uar_history.md | 6 +-- .../uar/auditoroverview/auditor_overview.md | 2 +- docs/platgovnetsuite/uar/install_app.md | 2 +- .../uar/owneroverview/owner_overview.md | 2 +- .../uar/owneroverview/owner_uar_list.md | 16 +++--- docs/platgovnetsuite/uar/uar_overview.md | 4 +- .../what_does_strongpoint_document.md | 36 ++++++------- docs/platgovnetsuite/what_is_a_spider.md | 24 ++++----- 126 files changed, 711 insertions(+), 717 deletions(-) diff --git a/docs/platgovnetsuite/agent/agent_clear_incident.md b/docs/platgovnetsuite/agent/agent_clear_incident.md index aedacf95be..c3c4516eee 100644 --- a/docs/platgovnetsuite/agent/agent_clear_incident.md +++ b/docs/platgovnetsuite/agent/agent_clear_incident.md @@ -12,7 +12,7 @@ Report. Here is the process to clear/resolve a control incident: 1. Open **Strongpoint** > **Financial Controls** > **Unresolved Control Incidents** -2. Click on the **Customization** to display the incidents. +2. Click the **Customization** to display the incidents. 3. Click **Edit** on the Incident record to clear/resolve. ![Clearing a Control Incident](/images/platgovnetsuite/financial_controls/agent_clear_incident.webp) @@ -26,8 +26,8 @@ The incident moves from **Unresolved Control Incident Log** to **Resolved Contro Alternatively, you can complete this process by inline editing of the Unresolved Control Incidents Report:: -1. Click on **EDIT** in the report tool bar. When enabled, it is green with a check mark. -2. Click on the red pencil icon in the column head. Columns without the pencil icon cannot be +1. Click **EDIT** in the report tool bar. When enabled, it is green with a check mark. +2. Click the red pencil icon in the column head. Columns without the pencil icon can't be edited. 3. Click in the column to open a text box. diff --git a/docs/platgovnetsuite/agent/agent_example_set_control.md b/docs/platgovnetsuite/agent/agent_example_set_control.md index d20e76c76b..fdc8f34c33 100644 --- a/docs/platgovnetsuite/agent/agent_example_set_control.md +++ b/docs/platgovnetsuite/agent/agent_example_set_control.md @@ -86,7 +86,7 @@ From the customization record: effectively perform a double join to filter your data and eliminate false positives. For example, a script to create an invoice from the user interface is saved to be run as administrator. A user creates the invoice from the interface as part of their work flow. Running a search for - administrator-touched transactions causes false positives as the user is not an administrator. + administrator-touched transactions causes false positives as the user isn't an administrator. Using cross match, the first Saved Search is for all transactions by an administrator. The second Saved Search is an employee search using the administrator role. Cross Match returns the intersection of those two searches, showing only the transactions performed by administrators. diff --git a/docs/platgovnetsuite/agent/agent_getting_started.md b/docs/platgovnetsuite/agent/agent_getting_started.md index e54c76b8ef..507c860eba 100644 --- a/docs/platgovnetsuite/agent/agent_getting_started.md +++ b/docs/platgovnetsuite/agent/agent_getting_started.md @@ -23,4 +23,4 @@ controls / searches you need. | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Record Control | Tracks all changes to the record (Customer, Vendor, Employee, Item)
Any changes trigger a violation record / alert. | | Record Field Control | Tracks changes to specified fields in a record.
Changes on the specified fields trigger a violation record / alert. | -| Transactional Data Control | Tracks changes to transaction records and events
Search types may be Journal entries, Checks, Bills, etc.
This data type can be monitored as a whole (i.e. any changes
additions, modifications, deletions), or specified (e.g. only Journal entries that have been modified after being approved, or journal entries entered and approved by the same user, or list of ad-hoc checks only etc). | +| Transactional Data Control | Tracks changes to transaction records and events
Search types may be Journal entries, Checks, Bills, and so on.
This data type can be monitored as a whole (i.e. any changes
additions, modifications, deletions), or specified (e.g. only Journal entries that have been modified after being approved, or journal entries entered and approved by the same user, or list of ad-hoc checks only, and so on). | diff --git a/docs/platgovnetsuite/agent/agent_lookback.md b/docs/platgovnetsuite/agent/agent_lookback.md index 2cdd9549fa..fae3d0eeba 100644 --- a/docs/platgovnetsuite/agent/agent_lookback.md +++ b/docs/platgovnetsuite/agent/agent_lookback.md @@ -20,7 +20,7 @@ The Agent Lookback is accessed from the Customization record for the control. 4. Set **Control Type** to **Lookback Control** or **Lookback Control with Admin Verification**. 5. Click **Go to Record**. -6. In the **Filter** drop down, select **User Fields**. Select a date such as **Date Created**. The +6. In the **Filter** dropdown, select **User Fields**. Select a date such as **Date Created**. The first date in the filter becomes the lookback start date. 7. Add the details and click **Set**. 8. Click **Add** . @@ -34,7 +34,7 @@ The Agent Lookback is accessed from the Customization record for the control. Administrators can initiate and cancel Lookback Runs from the **Controls** tab on a Customization record. The control search must have at least one date filter set to be used by the Lookback run. -Controls cannot be grouped by run. +Controls can't be grouped by run. ![Schedule or initiate a Lookback run.](/images/platgovnetsuite/financial_controls/lookback_run.webp) @@ -47,8 +47,8 @@ Controls cannot be grouped by run. Run** box (edit). - **Last Action** displays the last user action. -- **Start Date** is the beginning date to use for the lookback run. Future dates are not allowed. -- **End Date** is the ending date for the lookback run. Future dates are not allowed. +- **Start Date** is the beginning date to use for the lookback run. Future dates aren't allowed. +- **End Date** is the ending date for the lookback run. Future dates aren't allowed. - **Next Date** is a reference field displaying the last lookup date of the lookback run. The Lookback run checks for existing Control logs to avoid log duplication. The Control record, diff --git a/docs/platgovnetsuite/agent/agent_overview.md b/docs/platgovnetsuite/agent/agent_overview.md index 6df7a599b7..7e9598a89f 100644 --- a/docs/platgovnetsuite/agent/agent_overview.md +++ b/docs/platgovnetsuite/agent/agent_overview.md @@ -6,7 +6,7 @@ sidebar_position: 130 # Agent Overview -Agent allows you to monitor and manage the creation, deletion, or change of key records and fields +Use Agent to monitor and manage the creation, deletion, or change of key records and fields associated with transactional and master data as well as system critical settings by: - Filling in the gaps left by Segregation of Duties (SoD) by providing monitoring and documentation @@ -29,7 +29,7 @@ associated with transactional and master data as well as system critical setting Check out Netwrix University for helpful tutorials. [Sign in to your Netwrix account](https://www.netwrix.com/my_training.html) to access the NS3-2 -Agent Financial Controls series. Contact your Customer Success Manager if you do not have access to +Agent Financial Controls series. Contact your Customer Success Manager if you don't have access to Netwrix University. ## Agent Control Categories @@ -50,17 +50,17 @@ Pre-Approved Control Incidents ## Agent FAQ -##### Can you create multiple pre-approved Change Requests for a single Control? +##### Creating multiple pre-approved Change Requests for a single Control Yes, Agent goes through the list of multiple Change Requests it is associated with until it finds a match for the control incident result. -##### Can you use a single Change Request for multiple Controls? +##### Using a single Change Request for multiple Controls Yes, the Change Request’s Customization field can accommodate multiple Control records. All of the controls listed under the Customization field are associated with the Change Request. -##### How does Agent handle Pre-approvals when the control results are grouped? (i.e. Group Results In Alert checkbox is marked in the Control setting) +##### How Agent handles Pre-approvals when the control results are grouped (i.e. Group Results In Alert checkbox is marked in the Control setting) When the results are grouped, all results must match the Change Request Control filters for the Change Log to be a pre-approved incident. diff --git a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-0_release_notes.md b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-0_release_notes.md index d5b0871ea8..b15a3a1024 100644 --- a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-0_release_notes.md +++ b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-0_release_notes.md @@ -34,7 +34,7 @@ June 16, 2023 - **Autospider**, **Manual Spider** and **ReSpider Now** now support French (both France and Canada) for Strongpoint 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 + Searches. Specifying use these options 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**. @@ -53,11 +53,11 @@ June 16, 2023 May 16, 2023 - Updated handling of system changes due to a NetSuite change in user base permissions. System - changes are now handled as platform changes, and do not generate non-compliant change logs for + changes are now handled as platform changes, and don't generate non-compliant change logs for user roles. - You must manually resolve any of the non-compliant changes system generated prior to this - release. This update is not retroactive. + You must manually resolve any of the non-compliant changes system generated before this + release. This update isn't retroactive. - Added a **Print** button to all Change Request screens. @@ -67,7 +67,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 +This change ensures the Strongpoint scripts don't impact your performance. This change affects both new installs and updates to existing Strongpoint for NetSuite installations. There is an exception for customers using the **Agent** module to run **Large Controls**. These @@ -86,7 +86,7 @@ you are considering changing these associated scripts to a lower priority. Strongpoint 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) +![Make Copy doesn't copy the status](/images/platgovnetsuite/release_notes/change_request_make_copy.webp) ## Jira 1.2.14 @@ -99,17 +99,17 @@ content, not the status. Copied change requests are set to the **Not Started** s Here are the enhancements for the release: - Change customization name to allow Single quotes ('). -- Added **Location** to the **Type** drop down on the **Add Proposed Customization** form. +- Added **Location** to the **Type** dropdown on the **Add Proposed Customization** form. ## Jira 1.2.11 Here are the enhancements for the release: - Import Customizations from Jira -- Enable Allow NS to Jira Push (must be done prior to creating a ticket from NetSuite to Jira) +- Enable Allow NS to Jira Push (must be done before creating a ticket from NetSuite to Jira) - Create Ticket from NetSuite to Jira - Change customization name to allow Single quotes ('). -- Added **Group** to the **Type** drop down on the **Add Proposed Customization** form. +- Added **Group** to the **Type** dropdown on the **Add Proposed Customization** form. ### Import Customizations from Jira @@ -151,7 +151,7 @@ Jira. Here are the enhancements for the release: -- Credentials are now persistent, and do not need to be entered every time. +- Credentials are now persistent, and don't need to be entered every time. - Strongpoint Settings page added to Jira ### Strongpoint Settings for Jira diff --git a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-1_release_notes.md b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-1_release_notes.md index 8398343708..c0da088f07 100644 --- a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-1_release_notes.md +++ b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-1_release_notes.md @@ -13,14 +13,14 @@ November 30, 2023 - Support links are changing December 1st, the new link is [https://www.netwrix.com/support.html](https://www.netwrix.com/support.html) - NetSuite changes, such a moving an account to a different datacenter, are now treated as a - Platform change. They do not create a non-compliant Change Log record. + Platform change. They don't create a non-compliant Change Log record. - Improved handling of custom employee center roles across the Strongpoint spiders. - Bundle updates were enabling **Automatic Synchronization** between Strongpoint and Jira, changing settings where **Automatic Synchronization** was disabled. **Automatic Synchronization** defaults to enabled for new installations. Refer to [Jira](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) topic for more information. - Enhanced handling of nonmaterial changes for fields using html coding. Special symbols ( < > & " ) - in fields do not generate non-compliant change logs. + in fields don't generate non-compliant change logs. - Improved handling of the **Date Last Used** script to avoid time limit errors. ## Core 7.1.2 @@ -40,7 +40,7 @@ November 2, 2023 - Removed the Token Based Authentication Setup note link from **Environment Compare**. - Improved ReSpider Now to prevent duplicated change logs. - Improved handling of Non-material change workflow instances. -- Improved handling of platform changes on the Record type. Non-compliant change logs are not +- Improved handling of platform changes on the Record type. Non-compliant change logs aren't generated for permissions and links sublists it the **permittedrole** or **linkcenter** is empty. The change is noted in the log. @@ -50,7 +50,7 @@ October 16, 2023 - **Change Log Evaluation**: Change logs related to workflows were labeled with a **Scripted Object** change type. The labeling caused discrepancies in the change log evaluation. -- **Search Functionality**: The **Execute as Admin Workflows** search was not displaying data, even +- **Search Functionality**: The **Execute as Admin Workflows** search wasn't displaying data, even when executed workflows were present. ## Core 7.1.1 @@ -58,7 +58,7 @@ October 16, 2023 September 20, 2023 - Added **Refresh Changed By** button to refresh change information on Change Logs. If the **Actual - Change Date** is empty or **Change By** is set to **Could Not Be Determined** or **Pending + Change Date** is empty or **Change By** is set to **Couldn't Be Determined** or **Pending Autospider**, a **Refresh Changed By** button is available. When clicked, it populates **Actual Change Date** and **Change By** fields. @@ -68,13 +68,13 @@ September 20, 2023 ![Refresh Changed By](/images/platgovnetsuite/change_management/change_log_refresh.webp) - Removed extraneous Customization record link in Search Clean Up notification emails. - Non-Strongpoint users receive the notification and cannot use the link. + Non-Strongpoint users receive the notification and can't use the link. ## Core 7.1 August 23, 2023 -Every release may contain enhancements behind the scenes and customer-specific bug fixes to keep +Every release may contain enhancements internally and customer-specific bug fixes to keep Strongpoint running smoothly. **NetSuite Release 2023.2 Support** @@ -82,7 +82,7 @@ Strongpoint running smoothly. The Strongpoint Searches have been updated to support NetSuite's change of **Formula (Text) Fields** to the new **Formula (HTML) Fields**. This is a NetSuite security enhancement. -Strongpoint 7.1 must be installed prior to the NetSuite 2023.2 release to ensure a smooth upgrade: +Strongpoint 7.1 must be installed before the NetSuite 2023.2 release to ensure a smooth upgrade: 1. Install Strongpoint 7.1 in your Sandbox August 15th. 2. Test Strongpoint 7.1 before August 22nd. Contact your Customer Success Manager if you have @@ -127,7 +127,7 @@ NetSuite Release 2023.2 Support The Strongpoint Searches have been updated to support NetSuite's change of **Formula (Text) Fields** to the new **Formula (HTML) Fields**. This is a NetSuite security enhancement. -Strongpoint 7.1 and SoD 1.6 must be installed prior to the NetSuite 2023.2 release to ensure a +Strongpoint 7.1 and SoD 1.6 must be installed before the NetSuite 2023.2 release to ensure a smooth upgrade: 1. Install Strongpoint 7.1 and SoD 1.6 in your Sandbox August 15th. @@ -150,14 +150,14 @@ September 27, 2023 - Improved handling of the Jira Token field. It is now stored as an API Secret in NetSuite. Refer to [https://suiteanswers.custhelp.com/app/answers/detail/a_id/98285](https://suiteanswers.custhelp.com/app/answers/detail/a_id/98285) - for more information. + for details on NetSuite API Secrets. - Improved handling of the Change Request owner assignment. **Owner** is now the person who pushed the ticket into NetSuite. ## Jira 1.2.15 - Replaced the persistent popup message in the Strongpoint Jira integration when project restricted - access is in effect. You see a static note in the tab if you do not have access, instead of a more + access is in effect. You see a static note in the tab if you don't have access, instead of a more intrusive popup message requiring interaction. (Jira On-prem was updated August 2023, Jira Cloud updated November 2023) @@ -172,17 +172,17 @@ September 27, 2023 Here are the enhancements for the release: - Change customization name to allow Single quotes ('). -- Added **Location** to the **Type** drop down on the **Add Proposed Customization** form. +- Added **Location** to the **Type** dropdown on the **Add Proposed Customization** form. ## Jira 1.2.11 Here are the enhancements for the release: - Import Customizations from Jira -- Enable Allow NS to Jira Push (must be done prior to creating a ticket from NetSuite to Jira) +- Enable Allow NS to Jira Push (must be done before creating a ticket from NetSuite to Jira) - Create Ticket from NetSuite to Jira - Change customization name to allow Single quotes ('). -- Added **Group** to the **Type** drop down on the **Add Proposed Customization** form. +- Added **Group** to the **Type** dropdown on the **Add Proposed Customization** form. Import Customizations from Jira @@ -224,7 +224,7 @@ Jira. Here are the enhancements for the release: -- Credentials are now persistent, and do not need to be entered every time. +- Credentials are now persistent, and don't need to be entered every time. - Strongpoint Settings page added to Jira Strongpoint Settings for Jira @@ -268,7 +268,7 @@ October 13, 2023 - Added a **GL Impact** field and a **Permission Risk Severity** dropdown to the Permission record. **GL Impact** field is a **Y/N** choice. - **Permission Risk Severity** can be **High**, **Medium**, **Low** or **Null** (default). + **Permission Risk Severity** can be **High**, **Medium**, **Low**, or **Null** (default). - Added **GL Impact** and **Permission Risk Severity** filters to the Permission Revews lists. - Added **GL Impact** and **Permission Risk Severity** columns to the Permission Review. diff --git a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-2_release_notes.md b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-2_release_notes.md index 259df30a22..c20398a2fa 100644 --- a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-2_release_notes.md +++ b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-2_release_notes.md @@ -15,8 +15,8 @@ December 22, 2023 **New:** **Strongpoint Integration API** Strongpoint is excited to release an [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) to enable your -developers to support your ticketing systems! Customers enthusiastically embraced our Strongpoint -pre-built integrations for Jira, ServiceNow and Zendesk. The API makes this integration +developers to support your ticketing systems! Customers enthusiastically embraced the Strongpoint +pre-built integrations for Jira, ServiceNow, and Zendesk. The API makes this integration functionality available to everyone. Integrating your systems with your Strongpoint account helps you make the most of your change management and ticketing strategies. @@ -24,7 +24,7 @@ Here are the API highlights: - **Customizations** can be retrieved from your NetSuite account and can be added and removed from your Change Requests. -- **Change Requests** can be created, updated, retrieved and deleted. +- **Change Requests** can be created, updated, retrieved, and deleted. - **ERD** and **Impact Analysis** tools are available. - API commands are documented in the [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) section of this guide. @@ -35,7 +35,7 @@ Here are the API highlights: NetSuite has removed the scheduled status on scripts after a sandbox is refreshed. This stops the Strongpoint scripts required for environment compares, change requests built to push to production, -and other activities. This suitelet enables you to automatically reset all of your Strongpoint +and other activities. Use this suitelet to automatically reset all of your Strongpoint scripts. If you have scheduled custom scripts in your sandbox, you must manually set the status after a sandbox refresh. @@ -51,7 +51,7 @@ after a sandbox refresh. ![Open the Deployment tab](/images/platgovnetsuite/release_notes/script_deploy_tab.webp) 6. Click the Suitelet name: **Strongpoint Reset Schedule Deployments**. -7. Click on the Script **URL**. +7. Click the Script **URL**. ![Click the Script URL](/images/platgovnetsuite/release_notes/script_deploy_url.webp) @@ -62,7 +62,7 @@ December 19, 2023 - Changed the format of the **Reason for Exemption** column on the **Strongpoint SoD Change Requests (List)** report to **Formula Text**. Due to NetSuite 2023.2 changes, HTML tags were displaying in the report. Refer to NetSuite Release 2023.2 Support for more details on the NetSuite change. -- Improved handling of inline edits on Employee names. Making an inline name change does not affect +- Improved handling of inline edits on Employee names. Making an inline name change doesn't affect open SoD Exemptions for the employee. **NetSuite Release 2023.2 Support** diff --git a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-3_release_notes.md b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-3_release_notes.md index f2251601ec..04bf64de0f 100644 --- a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-3_release_notes.md +++ b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-3_release_notes.md @@ -59,13 +59,13 @@ New: **Formula Update in Searches** The **Strongpoint Open Noncompliant Changes**, **Strongpoint What Changed**, and **Open Noncompliant Changes - Audit** searches criteria has been updated. -As part of an ongoing effort to minimize non-material change logs and save time on reporting, we -have reviewed and updated some of the filters in our non-compliant and what changed compliance +As part of an ongoing effort to minimize non-material change logs and save time on reporting, Netwrix +has reviewed and updated some of the filters in the non-compliant and what changed compliance reports. A filter was discovered in the search criteria that could cause change logs to be excluded. This filter was used during the implementation of change detection through the autospider portlet, to -filter out duplicate logs caused by late reconciliation of changes done by our processes. With the +filter out duplicate logs caused by late reconciliation of changes done by the scheduling processes. With the improved process scheduling, the filter is no longer needed. For some accounts, this may result in additional change logs from previous periods in these reports. @@ -84,7 +84,7 @@ These issues have been resolved in this release: - _New Fields not detected by scheduled spiders_. A usage limit error was fixed so the new fields are now documented. -- _Change log for Role changes are showing as Could Not Be Determined_. An error was occurring if +- _Change log for Role changes are showing as Couldn't Be Determined_. An error was occurring if the access history was blank for an employee. ## SoD 1.6.5 diff --git a/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup.md b/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup.md index 879178526e..3f58b12eff 100644 --- a/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup.md +++ b/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup.md @@ -11,7 +11,7 @@ and manage Saved Searches. Accumulated searches contribute to inefficiency in Ne :::note Review the [Automated Search Clean Up Considerations](/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup_considerations.md) -prior to using this feature. +before using this feature. ::: Saved Searches are powerful customizations used throughout NetSuite and interconnected to other @@ -59,16 +59,16 @@ Rules** ![autocleanup](/images/platgovnetsuite/clean_up/autocleanup.webp) - **Name** is the assigned name for the **Search Clean Up Rule Record**. -- **Rule Owner(s)** is the administrator or owners for the rule record. +- **Rule Owners** is the administrator or owners for the rule record. - **Description** is the purpose of the rule record. An informative description helps administrators easily maintain and identify rules. -- **Notify Search Owners Prior to Archive** check to send email to search owners prior to archive. +- **Notify Search Owners Before Archive** check to send email to search owners before archive. Default is checked. -- **Notify Search Users Prior to Archive** check to send email to search users prior to archive. +- **Notify Search Users Before Archive** check to send email to search users before archive. Default is checked. - **Notify Supervisor for Inactive Owners** check to send email to an inactive owner's supervisor. Default is checked. -- **Automatic** is used to include the rule in the automated search. This option is not available +- **Automatic** is used to include the rule in the automated search. This option isn't available until the **Preview** function has been used. - **Inactive** check to exclude this Search Clean Up Rule from the automated search. - **Filter Summary** displays all of the current filters for the rule. @@ -83,7 +83,7 @@ This section is available when **Automatic** is checked. - **Weekly Event**: check and enter the **Repeat** frequency to schedule clean up weekly. - **Monthly Event**: check and enter the **Repeat** frequency to schedule clean up monthly. - **Yearly Event**: check to schedule a yearly run. -- **Next Run Date**: this field is populated by the system, and cannot be edited. The date is added +- **Next Run Date**: this field is populated by the system, and can't be edited. The date is added when the schedule is saved. - **End By**: pick a date to stop running automatic clean up. - **No End Date**: check to never stop the scheduled clean up. @@ -114,16 +114,16 @@ This section is available when **Automatic** is checked. **Advanced Filters** -- **Search Owner(s)** filters searches by matching selected owners or if **Exclude Owner(s)** is +- **Search Owners** filters searches by matching selected owners or if **Exclude Owners** is checked, to exclude matching owners for the rule. Multiple owners can be selected. Default is blank and unchecked. -- **Owner's Department(s)** filters searches by matching departments to the rule or if **Exclude - Department(s)** is checked, to exclude matching departments for the rule. Multiple departments can +- **Owner's Departments** filters searches by matching departments to the rule or if **Exclude + Departments** is checked, to exclude matching departments for the rule. Multiple departments can be selected. Default is blank and unchecked. - **Owner's Subsidiary** filters searches by matching subsidiaries to the rule or if **Exclude Subsidiary** is checked, to exclude matching subsidiaries for the rule. Multiple subsidiaries can be selected. Default is blank and unchecked. -- **Inactive Owner(s)** filters searches by matching inactive owners. Default is blank. +- **Inactive Owners** filters searches by matching inactive owners. Default is blank. - **All Inactive Owners** filters searches by all inactive owners. Default is unchecked. A maximum of 1000 inactive users are loaded. A warning is displayed if there are additional inactive users. @@ -158,10 +158,10 @@ If a Saved Search matches the Clean Up Rule: 2. Immediate notice to all search owners and search users with their searches that are about to be archived. Notifications include a **Retain this Search** link. A **Preview** link is available for the user to view the Search. -3. If the **Retain Search** link is not used and the Saved Search has not been used, final +3. If the **Retain Search** link isn't used and the Saved Search has not been used, final notifications are sent to all search owners and search users seven calendar days after the **Run Now** option was used. The notification includes the date the search is to be archived. -4. If the **Retain Search** link is not used and the Saved Search has not been used by the archive +4. If the **Retain Search** link isn't used and the Saved Search has not been used by the archive date: - Saved Search is archived. @@ -180,19 +180,19 @@ searches**, **retained searches**, **scheduled to be archived searches** and **a - Notification is emailed to the rule owner. The Saved Search is also included in the summary notification to the rule owner. - Notifications are sent the first closest Sunday since the rule was marked **Automatic**. - - Notification is emailed to the search owners unless **Notify Search Owners Prior to Archive** + - Notification is emailed to the search owners unless **Notify Search Owners Before Archive** is turned off for the rule. - - Notification is emailed to the search users unless **Notify Search Users Prior to Archive** is + - Notification is emailed to the search users unless **Notify Search Users Before Archive** is turned off for the rule. - All email notifications include a **Retain this Search** link. A **Preview** link is available for the user to view the Search. - Saved Search is added to the **Automated Search Clean Up** > **Searches To Be Archived (Auto)** list. -2. If the **Retain Search** link is not used and the Saved Search has not been used, second +2. If the **Retain Search** link isn't used and the Saved Search has not been used, second notifications are sent the following Sunday after the first notification date. The notification includes the date the search is to be archived. -3. If the **Retain Search** link is not used and the Saved Search has not been used by the archive +3. If the **Retain Search** link isn't used and the Saved Search has not been used by the archive date: - Saved Search is archived. @@ -256,7 +256,7 @@ The Retain process: ## Auto Archiving a Search -If search owners or users do not click on **Retain this search** in the email notifications, the +If search owners or users don't click **Retain this search** in the email notifications, the search is archived. The Archive process: - Archives the search. @@ -283,10 +283,10 @@ owner and administrators. ### Limitations to Restoring Auto Archived Searches Items from the **Criteria** and **Results** tabs are restored with the exception of **Public** -searches with the **Period** filter. Auto archiving does not occur with **Private** searches with -the **Period** filter, as they cannot be deleted or archived. +searches with the **Period** filter. Auto archiving doesn't occur with **Private** searches with +the **Period** filter, as they can't be deleted or archived. -The following check boxes on the Search form are not restored if they were checked: +The following check boxes on the Search form aren't restored if they were checked: - Available as List View - Available as Dashboard View @@ -294,7 +294,7 @@ The following check boxes on the Search form are not restored if they were check - Available for Reminders - Show in Menu -Items from the following tabs on the Search form are not retained when an auto archived search is +Items from the following tabs on the Search form aren't retained when an auto archived search is restored: - Highlighting diff --git a/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup_considerations.md b/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup_considerations.md index 3c362aeb8a..b75090caa5 100644 --- a/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup_considerations.md +++ b/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup_considerations.md @@ -11,20 +11,20 @@ This list describes some of the special cases encountered when using the 1. When an archived search contains **Date** filters, you must have the same date format preference as the Company’s date preference to accurately restore the filter. -2. SuiteScript cannot delete **Pricing** searches. Pricing searches are not displayed in the Clean +2. SuiteScript can't delete **Pricing** searches. Pricing searches aren't displayed in the Clean Up preview and are excluded from the Automated Search Clean Up. -3. Private searches with a **Period** filter cannot be deleted. SuiteScript returns an **Unexpected +3. Private searches with a **Period** filter can't be deleted. SuiteScript returns an **Unexpected Error** when trying to temporarily set the search as public to delete it. -4. Searches with **Period** filter cannot be fully restored. Only public searches can be deleted for +4. Searches with **Period** filter can't be fully restored. Only public searches can be deleted for searches with **Period** filter. ### Limitations to Restoring Auto Archived Searches Items from the **Criteria** and **Results** tabs are restored with the exception of **Public** -searches with the **Period** filter. Auto archiving does not occur with **Private** searches with -the **Period** filter, as they cannot be deleted or archived. +searches with the **Period** filter. Auto archiving doesn't occur with **Private** searches with +the **Period** filter, as they can't be deleted or archived. -The following check boxes on the Search form are not restored if they were checked: +The following check boxes on the Search form aren't restored if they were checked: - Available as List View - Available as Dashboard View @@ -32,7 +32,7 @@ The following check boxes on the Search form are not restored if they were check - Available for Reminders - Show in Menu -Items from the following tabs on the Search form are not retained when an auto archived search is +Items from the following tabs on the Search form aren't retained when an auto archived search is restored: - Highlighting diff --git a/docs/platgovnetsuite/bundleremoval/bundle_removal_overview.md b/docs/platgovnetsuite/bundleremoval/bundle_removal_overview.md index c0a2e0a6e6..663ef9f433 100644 --- a/docs/platgovnetsuite/bundleremoval/bundle_removal_overview.md +++ b/docs/platgovnetsuite/bundleremoval/bundle_removal_overview.md @@ -6,16 +6,15 @@ sidebar_position: 80 # Bundle Removal Overview -We can help you remove bundles from NetSuite in the safest and best possible manner by using mass -updates and saved searches, leaving you with an efficient use of time and effort. By following the -bundle removal process, the current functionality in your account keeps working as expected. +Platform Governance for NetSuite helps you remove bundles from NetSuite safely and efficiently using mass +updates and saved searches. By following the bundle removal process, the current functionality in your account keeps working as expected. Customizations that are built on top of a bundle can cause issues or break when the bundle is -removed. We help you determine what could cause issues or break if you remove the bundle by: +removed. Platform Governance for NetSuite helps you determine what could cause issues or break if you remove the bundle by: - Safely and easily recognizing which customizations are built on top of the bundle. - Seeing how customizations relate to different components. -- Detecting all the components that do not connect to any object in your NetSuite account. +- Detecting all the components that don't connect to any object in your NetSuite account. - Identifying and separating objects that have the possibility of breaking. - Creating an alternative for how your account would function when you remove the bundle. @@ -30,10 +29,10 @@ To remove a bundle: **Resources**: **Project Manager**: You should appoint a project manager, you can assign an internal technical resource if available or NetSuite can provide you with a Technical Account Manager (TAM). There - is a cost for hiring a TAM if it is not included in your NetSuite support package. You may need - more than one TAM resource depending on how heavily customized your bundle is. If a TAM is not + is a cost for hiring a TAM if it isn't included in your NetSuite support package. You may need + more than one TAM resource depending on how heavily customized your bundle is. If a TAM isn't available, NetSuite can also provide you with a resource from professional services. When - possible, it is recommended that you find a TAM resource that is familiar with Platform + possible, find a TAM resource that is familiar with Platform Governance for NetSuite as well as is familiar with the bundle type that you are trying to remove. **Developer and/or Administrator**: Depending on how your business processes are built around diff --git a/docs/platgovnetsuite/bundleremoval/categorizing_customizations.md b/docs/platgovnetsuite/bundleremoval/categorizing_customizations.md index 9eef06d612..59fa9927a4 100644 --- a/docs/platgovnetsuite/bundleremoval/categorizing_customizations.md +++ b/docs/platgovnetsuite/bundleremoval/categorizing_customizations.md @@ -10,8 +10,8 @@ Part of the bundle removal process is to categorize all the customizations in yo completed with saved searches and csv imports and exports (due to some limitations with mass updates). -Bundle components that do not have relationships outside the bundle or customizations that are not -related to the bundle need to be flagged with CSV imports/exports since mass updates do not have +Bundle components that don't have relationships outside the bundle or customizations that aren't +related to the bundle need to be flagged with CSV imports/exports since mass updates don't have summary criteria for this type of search. ## Create First Saved Search @@ -85,7 +85,7 @@ summary criteria for this type of search. 1. Open **Lists** > **Search** > **Saved Searches** 2. Find the **In bundle with no outside relationships** saved search. -3. Under the **Criteria** tab, click on **Standard** and add the following filters: +3. Under the **Criteria** tab, click **Standard** and add the following filters: | | Filter | Description | | --- | --- | --- | diff --git a/docs/platgovnetsuite/bundleremoval/creating_custom_list_and_fields.md b/docs/platgovnetsuite/bundleremoval/creating_custom_list_and_fields.md index 2de4461d34..94ccb85cb7 100644 --- a/docs/platgovnetsuite/bundleremoval/creating_custom_list_and_fields.md +++ b/docs/platgovnetsuite/bundleremoval/creating_custom_list_and_fields.md @@ -29,7 +29,7 @@ belongs to and six different check boxes, one for each scenario. ## Create Custom Fields 1. Open **Customization** > **Lists, Records, & Fields** > **Record Types** -2. Click on **Customization** in the record type list. +2. Click **Customization** in the record type list. 3. Click **New Field** on the **Fields** tab. 4. Add the new Field information: diff --git a/docs/platgovnetsuite/bundleremoval/creating_four_mass_updates.md b/docs/platgovnetsuite/bundleremoval/creating_four_mass_updates.md index 026fd7899f..07f17506e4 100644 --- a/docs/platgovnetsuite/bundleremoval/creating_four_mass_updates.md +++ b/docs/platgovnetsuite/bundleremoval/creating_four_mass_updates.md @@ -6,8 +6,8 @@ sidebar_position: 40 # Creating Four Mass Updates -Once you have created the first two mass updates and the two saved searches, you need to follow a -similar process to make sure the rest of the objects have been included for the bundle removal. +After you have created the first two mass updates and the two saved searches, you need to follow a +similar process to ensure the rest of the objects have been included for the bundle removal. ## Mass Update Scenario 3 @@ -29,7 +29,7 @@ This mass update captures all the outside bundle components referenced by inside 5. Open the **Mass Update Fields** tab. 6. Scroll down and check the box for **Removal Scenario** -7. Choose **Outside bundle referenced by inside** from the drop down menu. +7. Choose **Outside bundle referenced by inside** from the dropdown menu. 8. Check the box for **Removal Scenario 3** 9. Click **Save** @@ -50,7 +50,7 @@ This mass update captures all the bundle objects that are referencing non bundle 5. Open the **Mass Update Fields** tab. 6. Scroll down and check the box for **Removal Scenario** -7. Select **In bundle referencing record outside** from the drop down menu. +7. Select **In bundle referencing record outside** from the dropdown menu. 8. Check the box for **Removal Scenario 4** 9. Click **Save** @@ -67,13 +67,13 @@ This mass update flags all Non bundle components dependent on bundle components. | --- | :---: | --- | --- | :---: | --- | | Filter 1 | | Inactive | Is false | | and | | Filter 2 | | Clean-Up Status | Is Under Investigation | | and | -| Filter 3 | ( | Data Source(s): Clean-Up Status | Is To Be Cleaned Up | | or | +| Filter 3 | ( | Data Sources: Clean-Up Status | Is To Be Cleaned Up | | or | | Filter 4 | | List: Clean-Up Status | Is To Be Cleaned Up | | or | | Filter 5 | | Parent: Clean-Up Status | Is To Be Cleaned Up | ) | | 5. Open the **Mass Update Fields** tab. 6. Scroll down and check the box for **Removal Scenario** -7. Choose **Outside bundle referencing inside** from the drop down menu. +7. Choose **Outside bundle referencing inside** from the dropdown menu. 8. Check the box for **Removal Scenario 5** 9. Click **Save** @@ -94,7 +94,7 @@ This mass update captures all the bundle components referenced by non bundle com 5. Open the **Mass Update Fields** tab. 6. Scroll down and check the box for **Removal Scenario** -7. In **bundle referenced by outside** from the drop down menu. +7. In **bundle referenced by outside** from the dropdown menu. 8. Check the box for **Removal Scenario 6** 9. Click **Save** diff --git a/docs/platgovnetsuite/bundleremoval/exporting_information_to_excel.md b/docs/platgovnetsuite/bundleremoval/exporting_information_to_excel.md index 4928b0df45..3e70e3730f 100644 --- a/docs/platgovnetsuite/bundleremoval/exporting_information_to_excel.md +++ b/docs/platgovnetsuite/bundleremoval/exporting_information_to_excel.md @@ -19,7 +19,7 @@ and 6 to find affected customizations. To export the results to Excel: 1. Select **View** on **Removal Scenarios 5 and 6**. -2. Click on the **Excel** icon. +2. Click the **Excel** icon. 3. Export **Removal Scenario 5** and **Scenario 6** to Excel. 4. Choose the record you want to investigate. (for example, **custom open task default**) 5. Each record shows all its relationships (both inside and outside bundle). diff --git a/docs/platgovnetsuite/bundleremoval/final_tasks.md b/docs/platgovnetsuite/bundleremoval/final_tasks.md index 70cbb34b64..34a140fb8f 100644 --- a/docs/platgovnetsuite/bundleremoval/final_tasks.md +++ b/docs/platgovnetsuite/bundleremoval/final_tasks.md @@ -9,14 +9,14 @@ sidebar_position: 70 ## Reviewing Critical and Non Critical Sheets **Critical sheets** include all customizations that make use of the bundle components. You should -make sure you are aware of what these bundle components are doing and analyze the risks of removing +ensure you are aware of what these bundle components are doing and analyze the risks of removing them. Specifically, you should review the customizations from scenarios 3 and 6: Scenario 3: are non-bundle components that are used by bundle components, so there may be fields that are set by -scripts, workflows or searches that belong to the bundle. Scenario 6: are non-bundle components that +scripts, workflows, or searches that belong to the bundle. Scenario 6: are non-bundle components that use at least one bundle component for something, so their functionality and/or display may be broken. -**Non critical sheets** include all the customizations from scenarios 1, 2, 4 and 5. +**Non critical sheets** include all the customizations from scenarios 1, 2, 4, and 5. ## Testing diff --git a/docs/platgovnetsuite/change_management_reports.md b/docs/platgovnetsuite/change_management_reports.md index f32952c777..da9cc35fd7 100644 --- a/docs/platgovnetsuite/change_management_reports.md +++ b/docs/platgovnetsuite/change_management_reports.md @@ -131,7 +131,7 @@ The criteria for this report excludes: ## Non-Material Changes This report displays changes to non-material objects. **Non-Material Object Changes** are changes -detected in the object definition not caused by human intervention and do not have any functional +detected in the object definition not caused by human intervention and don't have any functional impact. Examples include NetSuite internal IDs, object XML structure or JSON representation or reordering values in a list. @@ -146,7 +146,7 @@ The criteria for this report excludes: Here is the criteria for non-material changes: - System generated changes. -- XML changes that do not directly affect the object definition. For example, Script Deployment +- XML changes that don't directly affect the object definition. For example, Script Deployment where it shows all related scripts that are deployed to the same record. - Customization record changes that sets references to other customizations but there is no change in actual record definition. For example, the list customization is added as dependency to the @@ -156,7 +156,7 @@ Here is the criteria for non-material changes: record on bundle updates. This **Internal Id** change is flagged as non-material because a deletion log is created. - Initial setting of **Bundle Id** to a customization record because some customizations (for - example, **custom record field**) do not have the bundle information within their metadata. + example, **custom record field**) don't have the bundle information within their metadata. - **Scripting/Workflow to Field Update** when a script/workflow is added as reference in the field customization record. The valid change is documented on the **Script** or **Workflow** instead of the field. diff --git a/docs/platgovnetsuite/changemanagement/approving_change_request.md b/docs/platgovnetsuite/changemanagement/approving_change_request.md index 4d393fb125..993ba4530d 100644 --- a/docs/platgovnetsuite/changemanagement/approving_change_request.md +++ b/docs/platgovnetsuite/changemanagement/approving_change_request.md @@ -31,10 +31,10 @@ NetSuite users and have the correct :::note Administrators can approve a Change Request. The status is set to **Approved (Override)** and the -administrator's name is displayed in the **Approval Override By** field. If the **Block Approval of Own Change Request** is enabled, Administrators cannot override their own change requests. +administrator's name is displayed in the **Approval Override By** field. If the **Block Approval of Own Change Request** is enabled, Administrators can't override their own change requests. ::: :::note -Once the Change Request is approved, you cannot change the customizations attached to the Change +After the Change Request is approved, you can't change the customizations attached to the Change Request. ::: diff --git a/docs/platgovnetsuite/changemanagement/change_and_approval_policy.md b/docs/platgovnetsuite/changemanagement/change_and_approval_policy.md index 28a13ee4cd..0692993939 100644 --- a/docs/platgovnetsuite/changemanagement/change_and_approval_policy.md +++ b/docs/platgovnetsuite/changemanagement/change_and_approval_policy.md @@ -22,7 +22,7 @@ analyzed. The change policy that applies is identified based on the IT risk from Record and the process risk from the Process Records. The Change and Approval Policy also determines the change level required for any detected changes to -be compliant. This ensures that even changes that do not go through the planned change management +be compliant. This ensures that even changes that don't go through the planned change management process are analyzed against the policy for compliance. For example, a company may have multiple policies. For example: @@ -47,14 +47,14 @@ custom form. ## Non-Material Changes -Non-material changes are changes detected in objects that are not performed by a human and do not +Non-material changes are changes detected in objects that aren't performed by a human and don't have functional impact. You can review these changes on the [Non-Material Changes report](/docs/platgovnetsuite/change_management_reports.md). Here is the criteria for non-material changes: - System generated changes. -- XML changes that do not directly affect the object definition. For example, Script Deployment +- XML changes that don't directly affect the object definition. For example, Script Deployment where it shows all related scripts that are deployed to the same record. - Customization record changes that sets references to other customizations but there is no change in actual record definition. For example, the list customization is added as dependency to the @@ -64,7 +64,7 @@ Here is the criteria for non-material changes: record on bundle updates. This **Internal Id** change is flagged as non-material because a deletion log is created. - Initial setting of **Bundle Id** to a customization record because some customizations (for - example, **custom record field**) do not have the bundle information within their metadata. + example, **custom record field**) don't have the bundle information within their metadata. - **Scripting/Workflow to Field Update** when a script/workflow is added as reference in the field customization record. The valid change is documented on the **Script** or **Workflow** instead of the field. diff --git a/docs/platgovnetsuite/changemanagement/change_management_overview.md b/docs/platgovnetsuite/changemanagement/change_management_overview.md index 7f883adecf..9a02aa72c7 100644 --- a/docs/platgovnetsuite/changemanagement/change_management_overview.md +++ b/docs/platgovnetsuite/changemanagement/change_management_overview.md @@ -10,7 +10,7 @@ Closed Loop Change Management and Compliance is an enhanced change management sy NetSuite accounts using the Platform Governance for NetSuite automated documentation and change management system. -We extend your current change management system to enable you to: +Platform Governance for NetSuite extends your current change management system so you can: - Establish change management policies for different types of objects and processes. - Route changes for approval within NetSuite. @@ -25,7 +25,7 @@ are multiple open change requests referencing the same object, any changes to th the change log being associated with the oldest of the approved change requests. ::: -## Plan, Approve and Deploy Changes +## Plan, Approve, and Deploy Changes ### Initiate with a Process Issue @@ -68,12 +68,12 @@ The **Advanced Change Management** Module provides additional functionality: :::note Change Management can be integrated with other change tracking systems using the External Change Request Number field. It is beneficial to use the change records since they can be linked to -processes, customizations and clean up activities. +processes, customizations, and clean up activities. ::: ### Confirm with a Deployment Record -When tracking Full Software Development Lifecycle changes, the Deployment Record enables you to +When tracking Full Software Development Lifecycle changes, use the Deployment Record to track deployment approvals. Once a Change Request is approved, this documents a change is ready for development. At this point, a new change request with the Stage Deployment Record can be created and tracked. diff --git a/docs/platgovnetsuite/changemanagement/changing_deactivating_policies.md b/docs/platgovnetsuite/changemanagement/changing_deactivating_policies.md index d6e3b4a7b0..ac67baef56 100644 --- a/docs/platgovnetsuite/changemanagement/changing_deactivating_policies.md +++ b/docs/platgovnetsuite/changemanagement/changing_deactivating_policies.md @@ -7,7 +7,7 @@ sidebar_position: 40 # Changing or Deactivating Policies Policy records determine the non compliance level of changes. Given that changes to these records -has a direct impact on the compliance levels, it is important to document and approve any +has a direct impact on the compliance levels, document, and approve any modifications. You can deactivate or modify policies with an open and approved change request. This diagram shows the overall process of what happens when you update a policy: @@ -31,7 +31,7 @@ To change an existing policy: ## Deactivate a Policy -Policies cannot be deleted; however you can deactivate the policy. +Policies can't be deleted; however you can deactivate the policy. To deactivate a policy: diff --git a/docs/platgovnetsuite/changemanagement/comparing_environments.md b/docs/platgovnetsuite/changemanagement/comparing_environments.md index 0a7fba7223..5e1529c9f8 100644 --- a/docs/platgovnetsuite/changemanagement/comparing_environments.md +++ b/docs/platgovnetsuite/changemanagement/comparing_environments.md @@ -32,8 +32,8 @@ Environments and to use the **Change Account** feature on a Change Requests. 3. Enter the information for the environment: - **Name** enter the environment name. - - **Account ID** enter the account ID. If it is a Sandbox account, make sure **\_SB1** is - appended. Do not use -sb1. + - **Account ID** enter the account ID. If it is a Sandbox account, ensure **\_SB1** is + appended. Don't use -sb1. - **Consumer Key** enter the consumer key. - **Consumer Secret** enter the consumer secret. - **Token ID** enter your token ID. @@ -77,7 +77,7 @@ obtain new values. - **Source**: Select source environment. - **Target**: Select target environment. -Once you enter the source and targets, the following information is populated: +After you enter the source and targets, the following information is populated: - **Account ID Source**: ID for the source environment account . - **Source Consumer Key**: Consumer Key of the Integration Record from the source account. @@ -99,7 +99,7 @@ Once you enter the source and targets, the following information is populated: clicked Run Compare from a Change Request, the number is automatically populated. This filter is advised when deploying a bundle of changes from one account to another. - **Get Items from Search**: Compares objects identified by the criteria in a Customization Saved - Search. Create the Saved Search prior to running the comparison. Within the Saved Search, you must + Search. Create the Saved Search before running the comparison. Within the Saved Search, you must have the **Script ID** in the **Results** column. This filter is advised when comparing changes in a bundle or other criteria that you can use for a saved search. - **Comparison Type**: This a mandatory field. There are two predefined comparison types. @@ -113,8 +113,8 @@ Once you enter the source and targets, the following information is populated: - **Quick Add**: Add individual customization records you want to compare. - **Include Children**: Check to include Children in your comparison. - **Display Non-Material Changes Results**: Check to include non-material changes between the - environments. This does not affect functionality. **Non-Material Object Changes** are changes - detected in the object definition not caused by human intervention and do not have any functional + environments. This doesn't affect functionality. **Non-Material Object Changes** are changes + detected in the object definition not caused by human intervention and don't have any functional impact. Examples include NetSuite internal IDs, object XML structure or JSON representation or reordering values in a list. - **Exclude Managed Bundle/App Components**: Check to exclude all Managed Bundle or App @@ -126,7 +126,7 @@ Once you enter the source and targets, the following information is populated: included/excluded, separating them with commas. :::note -When using filters, it is recommended that you only use one filter at a time. An exception is using +When using filters, use only one filter at a time. An exception is using **Customization Type** and **Get Items from Search** together. ::: @@ -135,13 +135,13 @@ When using filters, it is recommended that you only use one filter at a time. An ### Pre-Deployment :::note -If you are migrating new objects, they will not exist in your target account. +If you are migrating new objects, they won't exist in your target account. ::: To determine what to compare pre-deployment: 1. Create a **New Change Request** in Production (so it survives any Refreshes). -2. Attach the **Customization Record(s)** to the Change Request. +2. Attach the **Customization Records** to the Change Request. 3. Wait for Approval (if required). 4. On the **Change Request** open **Deployment Validation** > **Run Compare Tool** 5. Select the environments for the **Target** and **Source** Accounts. @@ -154,7 +154,7 @@ To determine what to compare pre-deployment: To determine what to compare post-deployment: 1. Use the **Change Request** from the pre-deployment or create a new one. -2. If creating a new one, attach the **Customization Record(s)** to the Change Request. +2. If creating a new one, attach the **Customization Records** to the Change Request. 3. On the **Change Request** go to > **Deployment Validation** > **Run Compare Tool** 4. Select the environments for the **Target** and **Source** Accounts. 5. Set the **Comparison Type** to **Diff**. diff --git a/docs/platgovnetsuite/changemanagement/completing_validating_change_request.md b/docs/platgovnetsuite/changemanagement/completing_validating_change_request.md index 579691b053..b84519ab54 100644 --- a/docs/platgovnetsuite/changemanagement/completing_validating_change_request.md +++ b/docs/platgovnetsuite/changemanagement/completing_validating_change_request.md @@ -6,7 +6,7 @@ sidebar_position: 130 # Completing and Validating a Change Request -Once the changes are complete, validate the Change Request and mark it **Complete**. +After 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 Change Requests. diff --git a/docs/platgovnetsuite/changemanagement/creating_change_request.md b/docs/platgovnetsuite/changemanagement/creating_change_request.md index 879ee428b8..4ef803fc88 100644 --- a/docs/platgovnetsuite/changemanagement/creating_change_request.md +++ b/docs/platgovnetsuite/changemanagement/creating_change_request.md @@ -6,7 +6,7 @@ sidebar_position: 70 # Creating a Change Request -Before making any changes, it is important to understand the scope of the planned change, potential +Before making any changes, understand the scope of the planned change, potential impacts and the level of change required. Documentation is also available if you are using the old [Change Request](/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md) form. Refer to [Setting Preferred Forms](/docs/platgovnetsuite/customization/setting_preferred_forms.md) for information on @@ -32,7 +32,7 @@ request in your sandbox account. - **Name**: Add a name to the change request. - **Stage**: Select the type of change you want to make. - - **Change Overview**: Add a summary of the desired change. + - **Change Overview**: Add a summary of the change. - **Lookup Customization** launches a window where you can search for customizations in the current account or a different account: - Click **Change Account** to log into another account or sandbox and look up @@ -50,7 +50,7 @@ request in your sandbox account. - **Select User** from the list to search all customizations **Modified By** selected user. This uses the **Change By** field in the change logs. The list is updated if the source account is changed. The **User Not Determined** option is for logs without system notes, - where the user cannot be identified. **User Not Determined** can be used with the **From** + where the user can't be identified. **User Not Determined** can be used with the **From** and **To** filters to search on the log creation date instead of the actual change date. - Select dates in the **From** and/or **To** fields to search all customizations that were changed on or after the **From** date or on or before the **To** date. Use both fields to @@ -64,7 +64,7 @@ request in your sandbox account. - Click the box(es) to select one or more customizations. Check in the **Name** header to toggle **Selecting** or **Deselecting All**. - Click **Add Selected Customizations**. If the Customization (based on Script ID) exists in the current account it is added to the - **Customizations**. If it does not exist, it is added to the **Proposed Customizations**. After the action completes, all checkboxes are cleared and a green confirmation message appears + **Customizations**. If it doesn't exist, it is added to the **Proposed Customizations**. After the action completes, all checkboxes are cleared and a green confirmation message appears indicating that the customizations were added successfully. - To add other customization types, update the filters and repeat the process. - Click **Close** to exit **Lookup Customization**. @@ -81,13 +81,13 @@ request in your sandbox account. Click **Choose File** and navigate to your SDF zipped file. - **Do Not ReSpider Automatically**: when unchecked, an Automatic ReSpider occurs when the Change Request status is set to **Completed**. - The ReSpider ensures that all change logs are complete prior to changing the status. If + The ReSpider ensures that all change logs are complete before changing the status. If automatic ReSpidering is turned off, there is a risk of changes being marked as non-compliant - if the change logs are not complete when the user changes the status to **Completed**. The + if the change logs aren't complete when the user changes the status to **Completed**. The default for the **Do Not ReSpider Automatically** is set on the [Configuration and Stats Change Management](/docs/platgovnetsuite/installation/installation_settings_report.md) tab. - - **Proposed Customizations**: Use this field when you are adding customizations that do not yet + - **Proposed Customizations**: Use this field when you are adding customizations that don't yet exist in your account. You can add multiple Script IDs by separating them with commas. Can be used in conjunction with customizations that already exist. New **Entry** and **Transaction** forms can be pre-approved by adding the Script ID of the @@ -98,7 +98,7 @@ request in your sandbox account. | Proposed Customization | Change Level | | --- | --- | - | customworkflow, customscript, customdeploy or anything with extensions: .js .ssp .ss | Script Object Changes | + | customworkflow, customscript, customdeploy, or anything with extensions: .js .ssp .ss | Script Object Changes | | customsearch, customreport | Searches and Reports | | customrole | User Role Changes | | Files with extensions: .html .txt | Web-Related Changes | @@ -107,11 +107,11 @@ request in your sandbox account. - **Affected Process(es)**: Select any processes affected by this Change Request. Select **Import From Processes** to automatically import affected processes. - **Affected Bundle ID/APP ID**: Use this field to specify a bundle ID or SuiteApp ID. Separate - multiple IDs with commas. Note, this does not run the Impact Analysis. To run the Impact + multiple IDs with commas. Note, this doesn't run the Impact Analysis. To run the Impact Analysis, use the Lookup Customization feature with a **Bundle ID**. 3. Click **In Progress** in the status bar to indicate you are working on the Change Request. -4. **Save** the Change Request. New sections and tabs are available once you save: +4. **Save** the Change Request. New sections and tabs are available after you save: 1. **Push to Jira** button is available if the [Jira integration](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) is available, and @@ -137,10 +137,10 @@ request in your sandbox account. | List referenced by a search related field (in a filter or formula) | Formula Objects | Critical Searches | There are three categories for customizations: Review any warnings or issues with the - impacted customization record(s) before you make a change. + impacted customization records before you make a change. - Can Be Safely Deleted or Modified - - Cannot Be Safely Deleted or Modified + - Can't Be Safely Deleted or Modified - Inactive Customizations (Already Deleted) 5. The **ERD** tab opens the visual Entity Relationship Diagram where you can easily review the diff --git a/docs/platgovnetsuite/changemanagement/creating_change_request_from_case.md b/docs/platgovnetsuite/changemanagement/creating_change_request_from_case.md index a87a33ee6e..a728ba0f36 100644 --- a/docs/platgovnetsuite/changemanagement/creating_change_request_from_case.md +++ b/docs/platgovnetsuite/changemanagement/creating_change_request_from_case.md @@ -18,6 +18,6 @@ The Change Request is created, populating the fields specified in the [Case to Change Request Field Mapping](/docs/platgovnetsuite/installation/installation_settings_report.md) set up. The Change Request status is set to **Not Started**. -If the **Create Change Request** button is not visible on the Case, the +If the **Create Change Request** button isn't visible on the Case, the [Enable Case to Change Request Workflow](/docs/platgovnetsuite/installation/installation_settings_report.md) -is not enabled. Contact your system administrator. +isn't enabled. Contact your system administrator. diff --git a/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md b/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md index 1ae781f206..60d19acd32 100644 --- a/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md +++ b/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md @@ -11,7 +11,7 @@ These are the steps to create a Change Request using the old form. Refer to [Setting Preferred Forms](/docs/platgovnetsuite/customization/setting_preferred_forms.md) for information on designating your preferred Change Request form. -Before making any changes, it is important to understand the scope of the planned change, potential +Before making any changes, understand the scope of the planned change, potential impacts and the level of change required. To do this, in your **production** account: @@ -33,12 +33,12 @@ To do this, in your **production** account: 3. Fill in the following fields in the **Scope** section of the change request: - - **Change Overview**: Add a summary of the desired change. + - **Change Overview**: Add a summary of the change. - To add customizations you can use the Customization field and/or the Proposed Customization field or you can add the Affected Bundle ID: - **Customizations**: Use this field if you are changing objects that already exist in your account. (Can be used in conjunction with proposed customizations.) - - **Proposed Customizations**: Use this field when you are adding customizations that do not + - **Proposed Customizations**: Use this field when you are adding customizations that don't yet exist in your account. You can add multiple Script IDs by separating them with commas. (Can be used in conjunction with customizations that already exist.) - **Affected Bundle ID**: If you are using a bundle to move objects from sandbox to @@ -55,11 +55,11 @@ To do this, in your **production** account: are safe to change. - **Change Request:** you are planning on changing objects that require approval to change. -6. Click on **Impact Analysis**. This will show you how objects are connected to other things. -7. Scroll down to the bottom of the page and click on the **Impact Analysis** tab.This shows you - which customization record(s) can or cannot be safely modified as well as customizations that are - inactive. You see a list of the customization record(s) that have been included, and warnings for - impacted customization record(s) that need to be investigated before you make a change. +6. Click **Impact Analysis**. This will show you how objects are connected to other things. +7. Scroll down to the bottom of the page and click the **Impact Analysis** tab.This shows you + which customization records can or can't be safely modified as well as customizations that are + inactive. You see a list of the customization records that have been included, and warnings for + impacted customization records that need to be investigated before you make a change. ![impactanalysissubtab](/images/platgovnetsuite/change_management/impactanalysissubtab.webp) diff --git a/docs/platgovnetsuite/changemanagement/example_sample_change.md b/docs/platgovnetsuite/changemanagement/example_sample_change.md index 276f756fc9..efe1335957 100644 --- a/docs/platgovnetsuite/changemanagement/example_sample_change.md +++ b/docs/platgovnetsuite/changemanagement/example_sample_change.md @@ -16,7 +16,7 @@ sidebar_position: 160 6. Click **Save**. The Change Level Required, Current Stage and Change Policy are displayed. 7. For this example: - If you are not an **Approver**: + If you aren't an **Approver**: 1. Click **Edit**. 2. Select yourself as an **Additional Approver**. diff --git a/docs/platgovnetsuite/changemanagement/multi_environment_change_management.md b/docs/platgovnetsuite/changemanagement/multi_environment_change_management.md index 508396c0ec..6259bce5cb 100644 --- a/docs/platgovnetsuite/changemanagement/multi_environment_change_management.md +++ b/docs/platgovnetsuite/changemanagement/multi_environment_change_management.md @@ -10,7 +10,7 @@ Multi-Environment Change Management helps you manage changes between your Produc Development/Testing accounts. The design is based on: - Changes to production accounts go through appropriate development and testing in separate NetSuite - accounts to ensure that the performance and data in production are not compromised. + accounts to ensure that the performance and data in production aren't compromised. - Documenting the process of transitioning changes through these accounts is critical to ensure that the process is followed to manage the risks associated with changes in NetSuite. - Change Requests and Deployment Records, along with Environment Comparison enable the documentation @@ -24,17 +24,17 @@ least the Strongpoint Developer Role to perform a Change Request Push. ## Create a Master Change Request in Production -A best practice is to create change requests in your production account so that they are not lost, +A best practice is to create change requests in your production account so that they aren't lost, they have an audit trail and approvals can be shown. 1. Open **Strongpoint** > **Change Management Tools** > **ITGC Change Request**. -2. Enter all required fields and additional approver(s). +2. Enter all required fields and additional approvers. 3. Click Pending Approval. Wait until the Change Request is approved. 4. Open **Strongpoint** > **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). -8. Set the Target login credentials: **Target Email and Target Password**. +8. Set the Target log in credentials: **Target Email and Target Password**. 9. Set the **Account ID Target** (this is automatically loaded upon selecting Target account). 10. Set the **Account Target Role**. 11. Click **Push**. @@ -60,14 +60,14 @@ they have an audit trail and approvals can be shown. ## Run Pre-Deployment Environment Comparison 1. Run **Strongpoint** > **Change Management Tools** > **Compare Environments** -2. Enter the login credentials of the **Target** and **Source** Accounts. +2. Enter the log in credentials of the **Target** and **Source** Accounts. 3. Set the **Comparison Type** to **Target Newer than Source**. 4. Click the **Compare** button. Refer to [Comparing Environments](/docs/platgovnetsuite/changemanagement/comparing_environments.md) for more details. ## Create the Deployment Record -Once you have compared your environments, get the deployment record approved. When your deployment +After you have compared your environments, get the deployment record approved. When your deployment record is approved, deploy the customizations listed on the change request. In your Production environment: @@ -86,7 +86,7 @@ In your Production environment: ## Run Post-Deployment Environment Comparison 1. Run **Strongpoint** > **Change Management Tools** > **Compare Environments** -2. Enter the login credentials of the **Target** and **Source** Accounts. +2. Enter the log in credentials of the **Target** and **Source** Accounts. 3. Set the **Comparison Type** to **Target Newer than Source**. 4. Click the **Compare** button. Refer to [Comparing Environments](/docs/platgovnetsuite/changemanagement/comparing_environments.md) for more details. diff --git a/docs/platgovnetsuite/changemanagement/opportunisticclearance/opportunistic_clearance.md b/docs/platgovnetsuite/changemanagement/opportunisticclearance/opportunistic_clearance.md index 2fd8e8efce..c4221dd87e 100644 --- a/docs/platgovnetsuite/changemanagement/opportunisticclearance/opportunistic_clearance.md +++ b/docs/platgovnetsuite/changemanagement/opportunisticclearance/opportunistic_clearance.md @@ -8,7 +8,7 @@ sidebar_position: 180 Many non-compliant change logs are generated due to one or more related objects not being included 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: +specific criteria. By default, opportunistic clearance isn't enabled. To enable it: 1. Open **Strongpoint** > **Strongpoint Support** > **Installation Settings** 2. Click **Edit** to open **Configuration and Stats**. @@ -38,7 +38,7 @@ Deployment or library script changes must meet these rules to be automatically c If all rules are met, the Change Request is attached to the Change Log and the log is compliant. The **Resolution Description** in the Change Log is set to **Automatically cleared in existing Open Approved CR via related customization [**_Object Name_**(**_ScriptID_**)]**. The _Object Name_ and _ScriptID_ are inserted from the original Change Request. The deployment or library script -does not need to be present in any Open Approved Change Request. +doesn't need to be present in any Open Approved Change Request. [Example Script Use Case](/docs/platgovnetsuite/changemanagement/opportunisticclearance/example_deploy_script_related_approved_change.md) ### Field Changes related to an Approved Record Change @@ -53,7 +53,7 @@ Field changes must meet these rules to be automatically cleared: If all rules are met, the Change Request is attached to the Change Log and the log is compliant. The **Resolution Description** in the Change Log is set to **Automatically cleared in existing Open Approved CR via related customization [**_Field Name_**]**. The _Field Name_ is inserted from the -original Change Request. The field does not need to be present in any Open Approved Change Request. +original Change Request. The field doesn't need to be present in any Open Approved Change Request. [Example Field Change Use Case](/docs/platgovnetsuite/changemanagement/opportunisticclearance/example_field_changes_related_approved_change.md) ### Record Changes related to an Approved Field Change @@ -68,7 +68,7 @@ Record changes must meet these rules to be automatically cleared: If all rules are met, the Change Request is attached to the Change Log and the log is compliant. The **Resolution Description** in the Change Log is set to **Automatically cleared in existing Open Approved CR via related customization [**_Record Name_**]**. The _Record Name_ is inserted from -the original Change Request. The record does not need to be present in any Open Approved Change +the original Change Request. The record doesn't need to be present in any Open Approved Change Request. [Example Record Change Use Case](/docs/platgovnetsuite/changemanagement/opportunisticclearance/example_record_changes_related_approved_change.md) ### Search Changes related to an Approved Workflow Change @@ -77,11 +77,11 @@ Approved Workflow changes must meet these rules to be automatically cleared: - Customization is a search with an Open Approved Change Request, or **all** of the following: - Search is used in a workflow. - - Search is not used by any script. + - Search isn't used by any script. - Related Workflow has an Open Approved Change Request. - Change Request **Stage** meets the required [Policy Change Level](/docs/platgovnetsuite/changemanagement/setting_up_policies.md). If all rules are met, the Change Request is attached to the Change Log and the log is compliant. The **Resolution Description** in the Change Log is set to **Automatically cleared in existing Open Approved CR via related customization [**_Search Name_**]**. The _Search Name_ is inserted -from the original Change Request.The search does not need to be present in any Open Approved Change +from the original Change Request.The search doesn't need to be present in any Open Approved Change Request.[ Example Search Change Use Case](/docs/platgovnetsuite/changemanagement/opportunisticclearance/example_search_changes_related_approved_change.md) diff --git a/docs/platgovnetsuite/changemanagement/resolving_non_compliant_changes.md b/docs/platgovnetsuite/changemanagement/resolving_non_compliant_changes.md index fe162baabe..ddf4dacaea 100644 --- a/docs/platgovnetsuite/changemanagement/resolving_non_compliant_changes.md +++ b/docs/platgovnetsuite/changemanagement/resolving_non_compliant_changes.md @@ -22,7 +22,7 @@ To access the Open Non-Compliant Changes Report: 1. Create a New [Change Request](/docs/platgovnetsuite/changemanagement/creating_change_request.md) or open an existing one. 2. Set it to **Pending Approval**. - 3. Once it is approved and complete, set the **Status** of the Change Request to **Complete**. + 3. After it is approved and complete, set the **Status** of the Change Request to **Complete**. 4. **Edit** the Change Log from the report. 5. Enter the **Related Change Request**. 6. Enter the **Related Process Issue** if applicable. diff --git a/docs/platgovnetsuite/changemanagement/setting_up_multi_stream_approval.md b/docs/platgovnetsuite/changemanagement/setting_up_multi_stream_approval.md index aff63810e9..6cce676c08 100644 --- a/docs/platgovnetsuite/changemanagement/setting_up_multi_stream_approval.md +++ b/docs/platgovnetsuite/changemanagement/setting_up_multi_stream_approval.md @@ -42,7 +42,7 @@ Change Request, where the mandated approvers are included. Only**. 3. Set the Change Levels on the **Change Controls** tab. 4. Leave the fields blank on the **IT Policies** tab. -5. Make sure **Require Affected Process Approval** is selected on the **Process Policies** tab. +5. Ensure **Require Affected Process Approval** is selected on the **Process Policies** tab. 6. Click **Save**. Leave the new policy open and continue with the next steps. ![multi_stream_new_policy](/images/platgovnetsuite/change_management/multi_stream_new_policy.webp) diff --git a/docs/platgovnetsuite/changemanagement/setting_up_policies.md b/docs/platgovnetsuite/changemanagement/setting_up_policies.md index 92b5cb934a..a42a99e1e4 100644 --- a/docs/platgovnetsuite/changemanagement/setting_up_policies.md +++ b/docs/platgovnetsuite/changemanagement/setting_up_policies.md @@ -28,14 +28,14 @@ sidebar_position: 20 Change Policy picking process with **Global Object Level Policy** _enabled_: - If customizations or customization processes are attached to specific policies, pick the most stringent policy. - - If there are no object-specific policies, look for policies that are not attached to any + - If there are no object-specific policies, look for policies that aren't attached to any customization or process. Compare the change level among all resulting policies and the Default Policy, then pick the most stringent policy. -- **Parent Policy**: Parent policy information to help organize policies, does not impact the - process. This field is not available when editing the Default Policy. For child policies, it can +- **Parent Policy**: Parent policy information to help organize policies, doesn't impact the + process. This field isn't available when editing the Default Policy. For child policies, it can be changed when the policy is edited. - **Owner**: Person who created the policy. -- **Inactive**: Checked if the policy is not active. +- **Inactive**: Checked if the policy isn't active. - **Log XML Only Change**: Checked to track online changes that occur in the XML, such as NetSuite internal changes.Recommended to leave this unchecked due to the volume of false positives you would need to manage. @@ -64,7 +64,7 @@ required for changes to the objects to be compliant with this policy. ### Change Levels **No Logs Created**: changes to these objects update the customization documentation is updated but -does not create change logs. A warning text is displayed when the Administrator sets the change +doesn't create change logs. A warning text is displayed when the Administrator sets the change level to **No Logs Created**. **Log Changes Only**: changes to these objects are automatically marked compliant. @@ -88,11 +88,11 @@ To add new change levels, select **New** or use the **+** next to a field when e #### Complex Objects -- **Scripted Objects**: Scripts, Workflows and any object upon with a script or workflow dependency. +- **Scripted Objects**: Scripts, Workflows, and any object upon with a script or workflow dependency. Default: Log Changes Only - **Formula Objects**: Fields used in Formulas. Default: Sandbox Development & Testing - **Workflows and Related Objects**: Changes to Workflows, or any objects used by a Workflow. When - an object is used by a Script and a Workflow, we use the higher level between Scripted Objects, + an object is used by a Script and a Workflow, Platform Governance for NetSuite uses the higher level between Scripted Objects, and Workflows and Related Objects change controls. Default: Change Request - **Integration Objects**: Changes to External Records, External Fields, External Systems, and Integrations. Default: Log Changes Only @@ -167,7 +167,7 @@ of 1 approval. Once each group has approved, the policy moves on to the **Final - **No Order Required**: check the box if approvers can approve in any order. If not checked, approvers must approve in the order specified in the **Approvers** entry. - **Min # of Approvals Required**: select the minimum number of approvers for the group. This option - is not available if **No Order Required** is not checked. + isn't available if **No Order Required** isn't checked. - **Add Row**: click to add another ITGC Approver Group. Click the red **X** to delete an existing group. @@ -190,12 +190,12 @@ Process Policies are only applicable if you implement Manage Process Risk. Request. Default is checked. - **Include Process Editors as Alternates**: Check to include Process Editors as alternate approvers. Process Editors are specified on the **Continuous** **Improvement** tab of the - **Process** record. Default is not checked. + **Process** record. Default isn't checked. - **Require Impacted Process Approval**: Check to require approval from process owners of related - objects. Often these owners are not specifically listed in the Change Request. Default is not + objects. Often these owners aren't specifically listed in the Change Request. Default isn't checked. - **Require Parent Process Owner Approval**: Owners of processes at or above the parent level must - approve. Default is not checked. + approve. Default isn't checked. - **New Process**: Launches the new Process form. ## Customization Policies @@ -203,9 +203,9 @@ Process Policies are only applicable if you implement Manage Process Risk. Customization Policies specifies the objects affected by the policy. - **Require Object Owner Approval**: Owner of the customization record. Likely the person who - created the object. Default is not checked. Recommend checking this box. + created the object. Default isn't checked. Recommend checking this box. - **Require Impacted Customization Approval**: Owner of any impacted customization record in - NetSuite. Default is not checked. + NetSuite. Default isn't checked. - **View** and **Customization**: Select a View and navigate to a Customization. Click **Attach** to add the selected customization to the Policy. - **New Customization**: Launches the new Customization form. @@ -216,7 +216,7 @@ Customization Policies specifies the objects affected by the policy. Control Policies specify controls for this policy. - **Control Assignee Approval**: Checked if there is a control assignee in Control Policies. -- **Process Owner(s)**: Checked if there are any process owners in Control Policies. +- **Process Owners**: Checked if there are any process owners in Control Policies. - **Control Owner**: Checked if there is a control owner in Control Policies. ## SoD Policies @@ -231,7 +231,7 @@ Segregation of Duties Policies specify the approvers for this policy. ## Set Up Additional Policies -In some cases, you may want stricter controls on certain objects. For example, many of our public +In some cases, you may want stricter controls on certain objects. For example, many public companies create a specific policy for SOX related searches, since they want it tighter than Log Only for those objects. To set up object specific policies, the initial spider must be complete, so you can attach the Customization Record to the policy. @@ -256,7 +256,7 @@ To set up additional policies: policies applied to specific objects, the higher change level is selected to keep the change compliant. -- Change the **View** to help locate the desired customization. +- Change the **View** to help locate the customization you want. - Enter all of part of the customization in **Customization**, or click the double down arrow icon to select the **List** option. - Select the customization. @@ -265,7 +265,7 @@ To set up additional policies: 9. Click **Save** when you are finished adding customizations to the Policy. Another method to add customization is through NetSuite's **Mass Update**. Here is the basic -process. Refer to the NetSuite help for more information on Mass Update. +process. See the NetSuite help for details on Mass Update. 1. Open **Lists** > **Mass Updates** 2. Expand **General Updates** > **Custom Records** > **Customization** diff --git a/docs/platgovnetsuite/changemanagement/setting_up_subsidiary_policies.md b/docs/platgovnetsuite/changemanagement/setting_up_subsidiary_policies.md index bc9652aabb..7c4a25198c 100644 --- a/docs/platgovnetsuite/changemanagement/setting_up_subsidiary_policies.md +++ b/docs/platgovnetsuite/changemanagement/setting_up_subsidiary_policies.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Setting Up Subsidiary Policies -Subsidiary Approval enables you to set subsidiary-specific policies based on the employees using a +Use Subsidiary Approval to set subsidiary-specific policies based on the employees using a customization. Once an administrator sets up a change policy for a subsidiary, the subsidiary approvers are set for the process, and the process is attached to the policy. Subsidiary Processes are automatically created by the spider. Employees using customizations are evaluated and Employee diff --git a/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md b/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md index dbfa4c70a6..7c5867a60a 100644 --- a/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md +++ b/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md @@ -7,7 +7,7 @@ sidebar_position: 80 # Using Custom Change Request Forms You can create custom change request forms for ITGC, Agent Pre-Approval, SoD Rule Change, SoD -Approval, Policy Approval and User Provisioning. Once you have created your custom forms, modify the +Approval, Policy Approval and User Provisioning. After you have created your custom forms, modify the Script Deployment Parameters to use your forms. 1. Open **Customization** > **Scripting** > **Scripts** @@ -17,7 +17,7 @@ Script Deployment Parameters to use your forms. 3. Click **Menu: customdeploy_flow_display_cr > Edit** 4. Open the **Parameters** tab. -5. Select your custom forms from the drop down lists for each type of Change Request +5. Select your custom forms from the dropdown lists for each type of Change Request ![Select your custom forms](/images/platgovnetsuite/change_management/custom_cr2.webp) diff --git a/docs/platgovnetsuite/changemanagement/user_provisioning.md b/docs/platgovnetsuite/changemanagement/user_provisioning.md index 697f615078..6d151920e6 100644 --- a/docs/platgovnetsuite/changemanagement/user_provisioning.md +++ b/docs/platgovnetsuite/changemanagement/user_provisioning.md @@ -12,7 +12,7 @@ remove access, or grant temporary access. You can specify the access by **Affect **Affected Roles**. The existing approval process is used. :::note -The **administrator** role cannot be automatically provisioned. +The **administrator** role can't be automatically provisioned. ::: The new form is accessed from **Strongpoint** > **Change Management Tools** > **User Provisioning @@ -58,8 +58,8 @@ custom form. 6. **Save** the change request. 7. Click **Pending Approval** in the status bar. -Once the request is approved, the roles are automatically added if you enabled -**Auto-Provisioning**. The change request status is shown as **Complete**. Otherwise, once the +After the request is approved, the roles are automatically added if you enabled +**Auto-Provisioning**. The change request status is shown as **Complete**. Otherwise, after the request is approved, you need to manually add the roles and update the status. A compliant Change Log is generated: @@ -91,7 +91,7 @@ The **Values** tab shows the details of the role changes. 10. **Save** the change request. 11. Click **Pending Approval** in the status bar. -Once the request is approved, the roles are automatically removed at the specified time if you +After the request is approved, the roles are automatically removed at the specified time if you enabled **Auto-Role Removal**. The change request status is shown as **Complete**. Otherwise, once the request is approved, you need to manually remove the roles and update the status. diff --git a/docs/platgovnetsuite/changemanagement/using_change_logs.md b/docs/platgovnetsuite/changemanagement/using_change_logs.md index a935036916..6a25e73828 100644 --- a/docs/platgovnetsuite/changemanagement/using_change_logs.md +++ b/docs/platgovnetsuite/changemanagement/using_change_logs.md @@ -6,7 +6,7 @@ sidebar_position: 140 # Using Change Logs -Change Logs allow you to see the type of change, who made the change and view the system notes of +Use Change Logs to see the type of change, who made the change, and view the system notes of the NetSuite record. Change Logs are accessed from the [Change Management Reports](/docs/platgovnetsuite/change_management_reports.md). @@ -32,7 +32,7 @@ fields can be retrieved. :::note -Some Object types do not produce System Notes or History Notes for changes. In this case the **Actual Change Date** is empty and the **Change By** is set to **Could Not Be Determined**. +Some Object types don't produce System Notes or History Notes for changes. In this case the **Actual Change Date** is empty and the **Change By** is set to **Could Not Be Determined**. ::: @@ -49,7 +49,7 @@ Change Logs are different based on the type of change. These are the major field **Actual Change Date**: Date of the system note entry reflecting the change date. There must be an available system note to display the date. -**Customization**: Linked customization(s) that have changed. +**Customization**: Linked customizations that have changed. **Deleted Customization**: Name of the deleted customization. Used with deleted Script Deployments. @@ -91,7 +91,7 @@ analysis of a non-compliant change. **Non-Material Clearance Reason**: Used when a change is evaluated as non-material. **Non-Material Object Changes** are changes detected in the object definition not caused by human intervention and -do not have any functional impact. Examples include NetSuite internal IDs, object XML structure or +don't have any functional impact. Examples include NetSuite internal IDs, object XML structure or JSON representation or reordering values in a list. **Non-Material Checked**: Indicates if the change log has been evaluated as non-material. @@ -123,10 +123,10 @@ When you want to find out who has made changes, you can run any of the Change Re made a change in the **Change By** column. The **Change By** and **Actual Date** of the change logs are retrieved using System Notes Search for -supported record types. If a System Note is not available, **Change By** displays **Could Not Be +supported record types. If a System Note isn't available, **Change By** displays **Could Not Be Determined** in the Report List. -Recorded types that are not supported can be retrieved from the AutoSpider. +Recorded types that aren't supported can be retrieved from the AutoSpider. | Supported Records for System Notes Search | Change By retrieved from the AutoSpider | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | @@ -143,7 +143,7 @@ Deployment, and Script. In an open Change Log: -1. Click on a linked **Customization** to open the Customization Record. **Strongpoint Return Jira +1. Click a linked **Customization** to open the Customization Record. **Strongpoint Return Jira Ticket Info (Suitelet Script)** in this example. ![Change Log Customization link](/images/platgovnetsuite/change_management/change_log_customization_link.webp) diff --git a/docs/platgovnetsuite/cleanup/archive_fields.md b/docs/platgovnetsuite/cleanup/archive_fields.md index 9fb099fb7d..644839f5ad 100644 --- a/docs/platgovnetsuite/cleanup/archive_fields.md +++ b/docs/platgovnetsuite/cleanup/archive_fields.md @@ -28,7 +28,7 @@ To create a change request: ![archivefields1](/images/platgovnetsuite/clean_up/archivefields1.webp) -6. Click on the **Archive Customizations** if you find your customizations under **Cannot Be Safely +6. Click the **Archive Customizations** if you find your customizations under **Cannot Be Safely Deleted or Modified** and under **Warning it says Not Archived** ![archivefields2](/images/platgovnetsuite/clean_up/archivefields2.webp) diff --git a/docs/platgovnetsuite/cleanup/cleanup_customizations_no_active_owner.md b/docs/platgovnetsuite/cleanup/cleanup_customizations_no_active_owner.md index 81c9dc1dc9..4c696f2e6c 100644 --- a/docs/platgovnetsuite/cleanup/cleanup_customizations_no_active_owner.md +++ b/docs/platgovnetsuite/cleanup/cleanup_customizations_no_active_owner.md @@ -9,16 +9,16 @@ sidebar_position: 20 Ownership of the customizations is important for clean up and accountability in the system. Owners can become inactive if they quit using the system, or if their licenses have been marked [Inactive](/docs/platgovnetsuite/installation/managing_users.md). The report criteria excludes Customization -types where owner does not apply. +types where owner doesn't apply. 1. Open **Strongpoint** > **Clean Up** > **Inactive Owner** -2. Click **Edit** next to each Customization to change. You can right-click on **Edit** and select +2. Click **Edit** next to each Customization to change. You can right-click **Edit** and select Open link in a new tab or window to keep your results page available. 3. Select a new **Owner**. 4. Click **Save** :::note -Using multi-line direct list editing does not update the actual customization record. Best practice -is to edit the customization record so your changes are not overwritten during the next spider +Using multi-line direct list editing doesn't update the actual customization record. Best practice +is to edit the customization record so your changes aren't overwritten during the next spider process. ::: diff --git a/docs/platgovnetsuite/cleanup/cleanup_overview.md b/docs/platgovnetsuite/cleanup/cleanup_overview.md index 09043c3822..3b273a8be1 100644 --- a/docs/platgovnetsuite/cleanup/cleanup_overview.md +++ b/docs/platgovnetsuite/cleanup/cleanup_overview.md @@ -8,7 +8,7 @@ sidebar_position: 50 Clean up involves some or all of the following steps: -1. Identify and remove unused customizations (searches, records, fields, scripts): +1. Identify and remove unused customizations (searches, records, fields, and scripts): - Completely unused - Useless or inefficient @@ -18,7 +18,7 @@ Clean up involves some or all of the following steps: 3. Describe each object (search, field, script,workflow). 4. Assign true and meaningful owners. 5. Assign customizations to high-level processes. -6. Optimize scripts, workflows and processes. +6. Optimize scripts, workflows, and processes. ### Clean Up Tools @@ -49,14 +49,14 @@ There are many clean up and documentation tools available such as: - Inactive Owner - Default ID -Unused fields and unused fields by form do not include fields that do not store a value since there +Unused fields and unused fields by form don't include fields that don't store a value since there is no Date Last Used for those objects. -All the “Unused” tools with the exception of Unused Bundles do not include customizations from -bundles. For example, even if a field is not used, it is highly unlikely that you will delete a +All the “Unused” tools with the exception of Unused Bundles don't include customizations from +bundles. For example, even if a field isn't used, it is highly unlikely that you will delete a field from a bundle. You would likely want to analyze the bundle usage as a whole when cleaning up. -Consider deleting unused customizations, such as fields that have not been used in years and are not +Consider deleting unused customizations, such as fields that haven't been used in years and aren't used by any other customization, before moving onto other clean up activities. ### Analyze the Results @@ -68,19 +68,19 @@ based on the type of clean up. Sample Result: -- **Edit/View:** enables you to edit or view the Customization Record for that customization. +- **Edit/View:** Use this to edit or view the Customization Record for that customization. - **Name**: the name of the customization. - **Type**: type of customization if showing multiple types. - **Parent**: the parent of the customization if applicable. - **Clean Up Classification:** The clean up status. - **Process/Steps**: processes or steps linked to the customization. -- **Quick Add Process:** enables you to link the customization to a process through direct list +- **Quick Add Process:** Use this to link the customization to a process through direct list editing. Multiple customizations can be added to processes in bulk. Other columns may include: - **Owner**: owner of that customization. If the owner is “Default Strongpoint User,” this means - that the owner is no longer active in the NetSuite account, so could not be linked to that + that the owner is no longer active in the NetSuite account, so couldn't be linked to that customization. - **Link**: takes you to the actual customization. - **ScriptID**: shows you the Script ID. @@ -96,7 +96,7 @@ greatly reduces the risk of things breaking as a result of your changes. Change Requests can be created and managed through: -- **Create Change Request**: enables you to create a new change request with a link to the +- **Create Change Request**: Use this to create a new change request with a link to the customization or customization selected. - **Related Change Requests**: displays the change requests that the customization is linked to. @@ -105,15 +105,15 @@ Change Requests can be created and managed through: The results can be sorted and filtered and are required to group and manage the output for subsequent steps. You may chose to clean up based on process or record type. -Every Customization record has a Clean-Up Status field that enables us to track the status of the +Every Customization record has a Clean-Up Status field to track the status of the clean-up process for that object. The statuses are: -- **To Be Cleaned Up**: We are planning to clean this up, but aren’t doing so yet. +- **To Be Cleaned Up**: Planned for cleanup, but not yet in progress. - **Send Request Info Emails**: This status triggers an email warning that the customization is about to be deleted. -- **Under Investigation**: A holdings status when we are deciding what to do. +- **Under Investigation**: A holding status while deciding what to do. - **Disabled/Hidden**:Tracks that the customization has been disabled. - **Archive**: Tracks that the data / set-up was archived. - **Deleted**: Tracks that the customization has been deleted. The doc will be inactivated. @@ -126,11 +126,11 @@ You can report on these statuses to organize your work. ### Create Change Requests (if required) -Some changes such as deletion, changes to scriptID and Help impact the customization itself. For -these types of changes we recommend creating a Change Request. +Some changes such as deletion, changes to scriptID, and Help impact the customization itself. For +these types of changes, create a Change Request. However, for Clean Up, you can create new change requests and assign them to the customizations. In -the results view, “Create Change Request” creates a new change request. Once that is added to that +the results view, “Create Change Request” creates a new change request. After it is added to that customization it will appear under “Related Change Requests”. You can have multiple customizations assigned to multiple change requests as appropriate. @@ -138,9 +138,7 @@ assigned to multiple change requests as appropriate. ### Manage the Change or Clean Up as Appropriate -You can find more information about how to use the Change Request under Change Management. Once the -appropriate investigations are conducted and approvals are obtained the customization can be changed -as appropriate based on company policies and procedures. +See [Change Management](/docs/platgovnetsuite/changemanagement/change_management_overview.md) for information about creating and managing change requests. After the appropriate investigations are conducted and approvals are obtained, the customization can be changed based on company policies and procedures. Some of the items being changed, such as the description or owner, can be direct list edited or bulk edited like any other NetSuite data directly in a view such as Unused Fields. diff --git a/docs/platgovnetsuite/cleanup/cleanup_unused_customizations.md b/docs/platgovnetsuite/cleanup/cleanup_unused_customizations.md index 077063661d..5938d0364e 100644 --- a/docs/platgovnetsuite/cleanup/cleanup_unused_customizations.md +++ b/docs/platgovnetsuite/cleanup/cleanup_unused_customizations.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Clean Up Unused Customizations -Platform Governance for NetSuite has powerful tools to analyze, organize and delete unused +Platform Governance for NetSuite has powerful tools to analyze, organize, and delete unused customizations in a safe and secure manner. Cleaning up fields has a direct impact on system performance. Larger records load slower than small @@ -24,7 +24,7 @@ order: - **Bundles**: Removing unused bundles eliminates large groups of records and other customizations - **Records**: Removing records eliminates large groups of customizations -- **Forms/Scripts**: Depending on your requirements, you can move unused forms, scripts, fields and +- **Forms/Scripts**: Depending on your requirements, you can move unused forms, scripts, fields, and associated customizations to progress through your account Cleaning up fields makes the account more understandable and reduces the likelihood of confusion. @@ -34,7 +34,7 @@ The basic clean up process: 1. Analyze Unused Customizations and Identify Dependencies 2. Create Change Requests 3. Archive Field Data -4. Back Up Searches, Scripts and Workflows +4. Back Up Searches, Scripts, and Workflows 5. Delete Customizations 6. Close the Change Request @@ -44,18 +44,18 @@ The basic clean up process: 2. Enter filtering information to streamline your search. Searching on all unused customizations can take a long time to load and can time out. - ![Enter criteria prior to searching for unused customizations](/images/platgovnetsuite/clean_up/customizations_cleanup_unused_filters.webp) + ![Enter criteria before searching for unused customizations](/images/platgovnetsuite/clean_up/customizations_cleanup_unused_filters.webp) 3. Click **Search**. The results are coded with a flag in the first column and the text either blue (Inactive owner) or black. ![Cleanup Key](/images/platgovnetsuite/clean_up/customizations_cleanup_key.webp) - You can hover over the flag for more information. If the text is blue, **Inactive Owner** is + You can hover over the flag to see the flag description. If the text is blue, **Inactive Owner** is displayed regardless of the flag color. ![customizations_cleanup_list](/images/platgovnetsuite/clean_up/customizations_cleanup_list.webp) -4. Click **View** next to each Customization to investigate. You can right-click on **View** and +4. Click **View** next to each Customization to investigate. You can right-click **View** and select **Open in a new tab or window** to keep your results page available. ![View the Customization Record](/images/platgovnetsuite/clean_up/customizations_cleanup_view_record.webp) @@ -86,7 +86,7 @@ warnings and status for each customization attached to the Change Request. The **Impact Analysis** tab has the following elements: **Can be safely deleted or modified**: A list of the customizations linked to the change request -that do not trigger any of the warnings below. +that don't trigger any of the warnings below. **Archiving Status**: Users can set the archiving status for fields to be deleted. Archive status can have the following values: @@ -102,8 +102,8 @@ that have triggered one of the following warnings: - **Active Processes**: this customization is linked to an active process. - **Critical Searches:** this customization is used in a formula or filter of a search and could cause the search to break if modified or deleted. Fields that are only in criteria or results of - searches do not trigger this warning since the search would still function. Searches that haven’t - been used in over a year do not trigger this warning. + searches don’t trigger this warning since the search would still function. Searches that haven’t + been used in over a year don’t trigger this warning. - **Dependent Scripts**: this customization is used in a script. - **Recently Used**: this customization has been used in the last 6 months. - **Dependent Workflows**: this customization is used in a workflow. @@ -122,15 +122,15 @@ clicked, any fields in the change request are archived and stored in the **File The status of those fields changes to **Archived**. The customization moves to the **Can Be Safely Deleted or Modified** tab. -## Back Up Searches, Scripts and Workflows +## Back Up Searches, Scripts, and Workflows -While there is no mass un-delete functionality, critical information about scripts, searches and +While there is no mass un-delete functionality, critical information about scripts, searches, and workflows are preserved in the Customization Record. -- **Searches**: All fields, filters, criteria and other search elements are documented in the +- **Searches**: All fields, filters, criteria, and other search elements are documented in the Searches tab. - **Scripts:** A script archive file is attached to the customization record. -- **Workflow:** Workflow actions, states, fields, conditions and other elements are documented in +- **Workflow:** Workflow actions, states, fields, conditions, and other elements are documented in the Related Workflows tab. The customization record of deleted customizations are inactive and accessible for future reference. diff --git a/docs/platgovnetsuite/cleanup/date_last_used.md b/docs/platgovnetsuite/cleanup/date_last_used.md index 30109fcfc7..831151d73c 100644 --- a/docs/platgovnetsuite/cleanup/date_last_used.md +++ b/docs/platgovnetsuite/cleanup/date_last_used.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Date Last Used -Date Last Used (DLU) enables you to see what customizations have not been used recently and could be +Use Date Last Used (DLU) to see what customizations haven't been used recently and could be deleted. Date Last Used (DLU) is captured for changes triggered by users or other customizations. Platform @@ -15,12 +15,12 @@ Searches and Records. DLU values are intended to be reasonably accurate. Complet objects would require excessive processing. :::note -DLU is not available for display only fields. +DLU isn't available for display only fields. ::: -DLU is not reliable for fields with no parent record. -DLU is not reliable in sandbox accounts as fields do not get actively used. -DLU is not reliable until the initial spider is complete, including the Make Joins. +DLU isn't reliable for fields with no parent record. +DLU isn't reliable in sandbox accounts as fields don't get actively used. +DLU isn't reliable until the initial spider is complete, including the Make Joins. Date Last Used is intended to be used for clean up and is set up to be accurate within a month. Higher levels of accuracy would require significantly more processing capacity. **The Last Used @@ -30,9 +30,9 @@ Status** displays additional information: | -------------------------------------- | ----------------------------------------------------------------------------------------- | | Use Not Checked Yet | Initial Value when a script has not yet run for a new customization. | | Managed Bundle Object | Customization is from a Managed Bundle, not monitored in the Unused Customization Report. | -| Use Date Not Supported for This Object | DLU cannot be determined because of API limitations. | +| Use Date Not Supported for This Object | DLU can't be determined because of API limitations. | | Used in the last 6 months | Retrieved DLU is on or after last 6 months. | -| No Use Detected | Retrieved DLU is prior to last 6 months. | +| No Use Detected | Retrieved DLU is before the last 6 months. | Date Last Used for customizations is calculated in a number of different ways: @@ -43,13 +43,13 @@ Used field. - Either the actual date of the last write to that field or date last modified of the last record that has this populated. Can search all fields that don’t store the value. -- If it cannot find a date for a field anywhere in the database, it puts in a default date +- If it can't find a date for a field anywhere in the database, it puts in a default date (12/31/1969) to show that this was checked. This makes searching easier - Periodically it checks all fields that have no date last used or a date last used of more than 1 month ago and updates the date with an approximate date based on the date last modified of the last record with that field used. -- DLU for fields should not be blank, so a blank DLU indicates that some scripts may not have run or - Platform Governance for NetSuite was unable to retrieve the missing data. Please contact Netwrix +- DLU for fields shouldn't be blank, so a blank DLU indicates that some scripts may not have run or + Platform Governance for NetSuite was unable to retrieve the missing data. Contact Netwrix Support. **Searches**: @@ -58,13 +58,13 @@ Used field. - Blank DLU indicates a search that have not been used since the time when NetSuite started capturing in 2009. - Search “Date Last Used” are checked depending upon the Time To Live specified for searches. -- Searches run in Dashboard Portlets does not update the DLU. DLU cannot be determined for searches +- Searches run in Dashboard Portlets doesn't update the DLU. DLU can't be determined for searches only used through Portlets. **Scripts:** -- For scripts the DLU is the last execution date as determined by audit, error or debug logs in - server execution log. In order to get accurate data while maximizing performance, Netwrix +- For scripts the DLU is the last execution date as determined by audit, error, or debug logs in + server execution log. To get accurate data while maximizing performance, Netwrix recommends setting all deployments to AUDIT logging status and setting at least one Audit tag. See [Script Management](/docs/platgovnetsuite/scriptmgmt/script_mgmt_overview.md) for details. - Blank DLU for scripts indicates that it has not been used since Platform Governance for NetSuite diff --git a/docs/platgovnetsuite/cleanup/restore_fields.md b/docs/platgovnetsuite/cleanup/restore_fields.md index 64a30f2f3b..12fa9d04b6 100644 --- a/docs/platgovnetsuite/cleanup/restore_fields.md +++ b/docs/platgovnetsuite/cleanup/restore_fields.md @@ -6,7 +6,7 @@ sidebar_position: 80 # Restore Fields -There is not a direct restore tool for fields, however you can get your archived fields back using +There isn't a direct restore tool for fields, however you can get your archived fields back using **Import Assistant** and the CSV file created for archiving. ## Import Assistant diff --git a/docs/platgovnetsuite/cleanup/set_up_archive_folder.md b/docs/platgovnetsuite/cleanup/set_up_archive_folder.md index ebd4e0afc6..2ab9655d04 100644 --- a/docs/platgovnetsuite/cleanup/set_up_archive_folder.md +++ b/docs/platgovnetsuite/cleanup/set_up_archive_folder.md @@ -12,7 +12,7 @@ process. An archive folder must be created before the Clean Up process. ## Create the Archive Folder 1. Open **NetSuite Home** > **Set Preferences** -2. Under **Defaults**, make sure **Show Internal IDS** is checked on the **General** tab. +2. Under **Defaults**, ensure **Show Internal IDS** is checked on the **General** tab. 3. Click **Save** 4. Open **Documents** > **Files** > **File Cabinet** > **New** 5. Name the folder **Strongpoint Archived Data Files**. @@ -35,7 +35,7 @@ To assign the internal ID to a deployed script: ![scripts-1](/images/platgovnetsuite/clean_up/scripts-1.webp) 4. Open the **Deployments** tab. -5. Click on **Strongpoint Auto Archive – OD**. +5. Click **Strongpoint Auto Archive – OD**. ![scripts-2](/images/platgovnetsuite/clean_up/scripts-2.webp) diff --git a/docs/platgovnetsuite/cleanup/update_field_description_and_help.md b/docs/platgovnetsuite/cleanup/update_field_description_and_help.md index 1979e45bcc..84b98c056a 100644 --- a/docs/platgovnetsuite/cleanup/update_field_description_and_help.md +++ b/docs/platgovnetsuite/cleanup/update_field_description_and_help.md @@ -17,7 +17,7 @@ changed_. The Change Log is closed. You can filter the results by **Name**, **Script Id**, **Type** or check the **Description/Help is Empty** checkbox to automatically hide rows with populated description and help from the **Field List**. - You can also click on a column heading in the **Field List** to sort the list by the selected column. + You can also click a column heading in the **Field List** to sort the list by the selected column. :::note The column with the arrow up or arrow down is the column used for sorting. (Ascending or Descending Order) ::: diff --git a/docs/platgovnetsuite/customization/customization_overview.md b/docs/platgovnetsuite/customization/customization_overview.md index 61cfee1b6b..e6a290a4a5 100644 --- a/docs/platgovnetsuite/customization/customization_overview.md +++ b/docs/platgovnetsuite/customization/customization_overview.md @@ -7,7 +7,7 @@ sidebar_position: 40 # Customizations Overview Customization records are documentation about each customization. They are automatically built and -maintained by the Spiders. They enable you to search customizations and attach them to processes. +maintained by the Spiders. Use them to search customizations and attach them to processes. Customization records contain the following information: @@ -16,7 +16,7 @@ Customization records contain the following information: 3. Which customizations are being used. 4. What the joins are between customizations. 5. What detailed automated documentation exists, including search filters and formulas, related - fields, scripts, searches and records. + fields, scripts, searches, and records. For Change Management and Compliance, the joins between customizations are critical to determine the IT risk of making changes to the system. For example, they warn you if changing a search could break diff --git a/docs/platgovnetsuite/customization/identify_impacted_objects.md b/docs/platgovnetsuite/customization/identify_impacted_objects.md index 2dfb34758b..029929c49c 100644 --- a/docs/platgovnetsuite/customization/identify_impacted_objects.md +++ b/docs/platgovnetsuite/customization/identify_impacted_objects.md @@ -20,13 +20,13 @@ You can find impacted objects in several ways: The customization list provides a complete list of all the customization records. -It enables you to: +Use it to: - Filter the view. - Access the Customization Record. - Access the actual customization record by clicking on the **Link** column on the right. -Changing the view enables you to access many clean up tools, which can also be accessed by going to +Changing the view gives you access to many clean up tools, which can also be accessed by going to **Clean Up** located under the **Strongpoint** tab. To access the customization list: @@ -42,13 +42,13 @@ To access a customization quick search, open **Strongpoint** > **Customizations* Quick Search** You can search using several factors and submit. When looking up by **Name**, using **Contains** -helps if you do not have the exact name. +helps if you don't have the exact name. ![custquicksearch](/images/platgovnetsuite/customizations/custquicksearch.webp) ## ERD View -The ERD provides a way to look at customizations by record type. A left click on the customization +The ERD provides a way to look at customizations by record type. A left click the customization name brings up the customization record. 1. Open **Strongpoint**> **Customizations** > **ERD View** @@ -58,10 +58,10 @@ name brings up the customization record. - **Field Name Filter**: enter all or part of a field name to filter the results. - **Date Last Used Filter**: enter a date range to filter the results. - **Hide standard fields without relationships**: check this box to hide all standard fields - that do not have relationships from the results. + that don't have relationships from the results. - **Hide all standard fields**: check this box to hide all standard fields from the results. - **Hide all fields without custom relationships**: check this box to hide all unused fields - that do not have custom relationships from the results. + that don't have custom relationships from the results. - **Hide Unused fields**: check this box to hide all unused fields from the results, based on the DLU. @@ -69,7 +69,7 @@ name brings up the customization record. ![erd-view](/images/platgovnetsuite/customizations/erd-view.webp) -5. Click on any item to expand the view. For large lists, click **More** to see the additional +5. Click any item to expand the view. For large lists, click **More** to see the additional items. External sources headers are highlighted in green. @@ -79,7 +79,7 @@ name brings up the customization record. ## ERD Search Form -The ERD search form enables you to search by different record types. You can also use it to create a +Use the ERD search form to search by different record types. You can also use it to create a Process Issue or a Change Request. Refer to [Enabling the ERD Search](/docs/platgovnetsuite/customization/using_erd.md). From the ERD Search Form, you can search by: @@ -92,7 +92,7 @@ From the ERD Search Form, you can search by: ![erdsearchform-2](/images/platgovnetsuite/customizations/erdsearchform-2.webp) -Once you have finished your search, you can create a Process Issue or a Change Request from the +After you have finished your search, you can create a Process Issue or a Change Request from the results. ![erdsearchform-3](/images/platgovnetsuite/customizations/erdsearchform-3.webp) diff --git a/docs/platgovnetsuite/customization/integration_record.md b/docs/platgovnetsuite/customization/integration_record.md index 48dcd4159e..9c9200db4d 100644 --- a/docs/platgovnetsuite/customization/integration_record.md +++ b/docs/platgovnetsuite/customization/integration_record.md @@ -17,7 +17,7 @@ Quick Search** to locate an integration record. The main section of the Integration Record summarizes the key information, including Application ID, name, description, state, and change history. -The **Authentication** tab enables you to specify additional authorization for the integration: +The **Authentication** tab is where you specify additional authorization for the integration: ![Integration record example](/images/platgovnetsuite/customizations/integration_record.webp) diff --git a/docs/platgovnetsuite/customization/understanding_customization_record.md b/docs/platgovnetsuite/customization/understanding_customization_record.md index 7275525515..1367e2891b 100644 --- a/docs/platgovnetsuite/customization/understanding_customization_record.md +++ b/docs/platgovnetsuite/customization/understanding_customization_record.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Understanding the Customization Record Customization records are the documentation about each customization. They are normally built and -maintained by the Spiders. They enable you to search the customizations and attach them to +maintained by the Spiders. Use them to search the customizations and attach them to processes. Customization records tell you: @@ -65,7 +65,7 @@ The tabs provide detailed information about the customization: customizations include States, Actions, and Workflow Fields not applicable when viewing Field customizations. - **ERD**: Displays the Entity-Relationship Diagram centered around this customization. -- **Clean Up**: Comments, classification and clean up status associated with the customization. +- **Clean Up**: Comments, classification, and clean up status associated with the customization. Search records have additional fields for Automated Search Clean Up alerts, rules, and status. - **Change Log**: Displays the change log for the customization. - **Related Change Log**: Displays any related change logs for the customization. diff --git a/docs/platgovnetsuite/customization/using_erd.md b/docs/platgovnetsuite/customization/using_erd.md index d00b06e690..3574d072e9 100644 --- a/docs/platgovnetsuite/customization/using_erd.md +++ b/docs/platgovnetsuite/customization/using_erd.md @@ -13,7 +13,7 @@ can easily review the relationships and dependencies. The ERD is easily accessi - ERD Search, refer to [Enabling the ERD Search on the Dashboard](#enabling-the-erdsearch-on-the-dashboard) - Tabs on various pages, for example, Customization record, Change Requests, and Process Issues. -The ERD provides a way to look at customizations by record type. A left click on the customization +The ERD provides a way to look at customizations by record type. A left click the customization name brings up the customization record. 1. Open **Strongpoint**> **Customizations** > **ERD View** @@ -23,10 +23,10 @@ name brings up the customization record. - **Field Name Filter**: enter all or part of a field name to filter the results. - **Date Last Used Filter**: enter a date range to filter the results. - **Hide standard fields without relationships**: check this box to hide all standard fields - that do not have relationships from the results. + that don't have relationships from the results. - **Hide all standard fields**: check this box to hide all standard fields from the results. - **Hide all fields without custom relationships**: check this box to hide all unused fields - that do not have custom relationships from the results. + that don't have custom relationships from the results. - **Hide Unused fields**: check this box to hide all unused fields from the results, based on the DLU. @@ -34,7 +34,7 @@ name brings up the customization record. ![erd-view](/images/platgovnetsuite/customizations/erd-view.webp) -5. Click on any item to expand the view. For large lists, click **More** to see the additional +5. Click any item to expand the view. For large lists, click **More** to see the additional items. External sources headers are highlighted in green. diff --git a/docs/platgovnetsuite/faq.md b/docs/platgovnetsuite/faq.md index 9f57a7690e..24f80205c9 100644 --- a/docs/platgovnetsuite/faq.md +++ b/docs/platgovnetsuite/faq.md @@ -8,38 +8,37 @@ sidebar_position: 200 Platform Governance for NetSuite is a stress-free change management and compliance software for NetSuite and Salesforce. It helps companies manage change in their systems, enabling them to drive -growth with confidence and certainty. Here are answer to Frequently Asked Questions: +growth with confidence and certainty. Here are answers to frequently asked questions: - [Can Platform Governance for NetSuite provide a SOC1 Report?](#can-platform-governance-for-netsuite-provide-a-soc1-report) -- [Can I install Platform Governance for NetSuite in the Sandbox or Release Preview?](#can-i-install-platform-governance-for-netsuite-in-the-sandbox-or-release-preview) +- [Can Platform Governance for NetSuite be installed in the Sandbox or Release Preview?](#can-platform-governance-for-netsuite-be-installed-in-the-sandbox-or-release-preview) -- [Is our private data being transmitted or shared in any way?](#is-our-private-data-being-transmitted-or-shared-in-any-way) +- [Is private data transmitted or shared in any way?](#is-private-data-transmitted-or-shared-in-any-way) - [What is the time or effort required to use Platform Governance for NetSuite?](#what-is-the-time-or-effort-required-to-use-platform-governance-for-netsuite) - [Who needs a Platform Governance for NetSuite License? What is the difference between an editor and a viewer?](#who-needs-a-platform-governance-for-netsuite-license-what-is-the-difference-between-an-editor-and-a-viewer) -#### Can Platform Governance for NetSuite provide a SOC1 Report? +#### Can Platform Governance for NetSuite provide a SOC1 Report Contact your Account Manager to request a SOC1 type 2 report. Reports are available by the end of January. A bridge letter can be provided if necessary. -Platform Governance for NetSuite does not presently issue SOC2 reports. +Platform Governance for NetSuite doesn't issue SOC2 reports. Platform Governance for NetSuite for NetSuite is built on NetSuite. Platform Governance for NetSuite -does not have access to or store any of your data outside of your NetSuite platform. +doesn't have access to or store any of your data outside of your NetSuite platform. -#### Can I install Platform Governance for NetSuite in the Sandbox or Release Preview? +#### Can Platform Governance for NetSuite be installed in the Sandbox or Release Preview -Many of our customers install Platform Governance for NetSuite in their sandbox before installing it -in production. Your license covers both sandbox and production instances. We currently do not have -the ability to have the bundle installed in release previews. +Many customers install Platform Governance for NetSuite in their sandbox before installing it +in production. The license covers both sandbox and production instances. The bundle can't be installed in release previews. -#### Is our private data being transmitted or shared in any way? +#### Is private data transmitted or shared in any way -Platform Governance for NetSuite is completely contained within NetSuite and Salesforce. It utilizes -the platform’s custom records and APIs to create and manage documentation. No data leaves the system +Platform Governance for NetSuite is completely contained within NetSuite and Salesforce. It uses +the platform's custom records and APIs to create and manage documentation. No data leaves the system at anytime to ensure compliance with data security requirements for critical system and process data. All code and key tools are locked to ensure consistent processes within the application. Access to records can be restricted by role or user using standard NetSuite and Salesforce access @@ -49,22 +48,22 @@ management for specific processes or objects. All documentation can be printed, rendered as flat HTML or exported to an external repository and can be reimported and retained for archiving purposes by an authorized user. -#### What is the time or effort required to use Platform Governance for NetSuite? +#### What is the time or effort required to use Platform Governance for NetSuite -A lot less than you would expect. The first phase is to get your complete customization +A lot less than you would expect. The first phase is to get a complete customization documentation library. All this requires is for the Administrator to install the bundle, press -“Start Spider” and let the system run. After a few nights, the system documentation is complete and +"Start Spider" and let the system run. After a few nights, the system documentation is complete and you can review the results in the Status Report. -We have User Guides and online videos to walk you through Clean Up, Script Analysis and other +User guides and online videos are available to walk you through Clean Up, Script Analysis and other capabilities. Because Platform Governance for NetSuite creates complete documentation and updates on an ongoing basis with your NetSuite and Salesforce records, you can use the pre-built searches or create your own to get instant visibility into your account. While Platform Governance for NetSuite greatly reduces the amount of time to find information and identify interdependencies, the NetSuite -and Salesforce Administrators will still need to do the appropriate due diligence and analysis to +and Salesforce Administrators still need to do the appropriate due diligence and analysis to ensure their actions are appropriate and safe. -#### Who needs a Platform Governance for NetSuite License? What is the difference between an editor and a viewer? +#### Who needs a Platform Governance for NetSuite License — what is the difference between an editor and a viewer Licenses are only required for editors of Platform Governance for NetSuite (i.e. people who create or edit processes or view customization documentation). No license is required for users who merely diff --git a/docs/platgovnetsuite/index.md b/docs/platgovnetsuite/index.md index 170a462623..c9f9911ef3 100644 --- a/docs/platgovnetsuite/index.md +++ b/docs/platgovnetsuite/index.md @@ -13,9 +13,9 @@ to date. By implementing Platform Governance for NetSuite you can: -- Automatically catalog all custom fields, scripts, forms, searches, records and workflows. -- Visually browse standard and custom fields, lists and records to find all related scripts, - searches, users and departments. +- Automatically catalog all custom fields, scripts, forms, searches, records, and workflows. +- Visually browse standard and custom fields, lists, and records to find all related scripts, + searches, users, and departments. - Capture and search script comments and identify poorly commented code. - Automatically track changes to your customizations using the change logs, so you can see what customizations were changed, how they were changed, when they were changed and who changed them. @@ -25,7 +25,7 @@ Check out Netwrix University for helpful tutorials. ## Installation and Initial Scan -Once you install Platform Governance for NetSuite, you simply click the **Start Spider** button and +After you install Platform Governance for NetSuite, click the **Start Spider** button and your customizations are documented over the course of 4-5 days with minimal impact on system performance. Once completed, you have a searchable database of all your customizations. @@ -36,18 +36,17 @@ have your account both fully documented and optimized. ### Clean Up -Use the end to end documentation of custom objects and our Clean Up Tools to: +Use the end to end documentation of custom objects and the Clean Up Tools to: -- Identify unused fields, searches and other custom objects. +- Identify unused fields, searches, and other custom objects. - Quickly identify dependencies to reduce the risk of breaking things in your account (i.e. see if a search is being used in a script or workflow). - Use Change Requests to keep your changes organized and capture approvals. ### Script Management -Critical Script Analysis enables you to determine how healthy your scripts are and what areas you -can fix to improve your account. With our tools and the Critical Script Analysis methodology you -can: +Critical Script Analysis lets you determine how healthy your scripts are and what areas you +can fix to improve your account. With the Critical Script Analysis methodology you can: - Identify high priority scripts based on usage. - Identify people and departments triggering scripts to focus on scripts that could be @@ -93,7 +92,7 @@ Agent automates IT and financial controls and critical change practices to ensur master data are compliant. It can: - Check for process problems regularly without user event scripts. -- Automatically generate and assign tasks, cases or process issues for each detected problem. +- Automatically generate and assign tasks, cases, or process issues for each detected problem. - Automatically alert key stakeholders. - Log control violations for clearance. - Store relevant data as a CSV to create a snapshot for compliance or troubleshooting purposes. diff --git a/docs/platgovnetsuite/installation/features_by_license_type.md b/docs/platgovnetsuite/installation/features_by_license_type.md index 2f6e9675c9..279f392702 100644 --- a/docs/platgovnetsuite/installation/features_by_license_type.md +++ b/docs/platgovnetsuite/installation/features_by_license_type.md @@ -44,7 +44,7 @@ Menus and items not available for your license type are automatically hidden. 1 **Non-Material Object Changes** are changes detected in the object definition not caused by human -intervention and do not have any functional impact. Examples include NetSuite internal IDs, object +intervention and don't have any functional impact. Examples include NetSuite internal IDs, object XML structure or JSON representation or reordering values in a list. | **Optional Menus** | **Menu Items** | diff --git a/docs/platgovnetsuite/installation/go_live_faq.md b/docs/platgovnetsuite/installation/go_live_faq.md index 14aa854854..49bdf30d7f 100644 --- a/docs/platgovnetsuite/installation/go_live_faq.md +++ b/docs/platgovnetsuite/installation/go_live_faq.md @@ -18,15 +18,15 @@ Here is a list of common questions customers have asked after they Go Live. > > _About_: [Approval Overrides](#approval-overrides) > -> _Help_: [Change By Field Showing AutoSpider or Could Not Be Determined](#change-by-field-showing-autospider-or-could-not-be-determined) +> _Help_: [Change By Field Showing AutoSpider or Couldn't Be Determined](#change-by-field-showing-autospider-or-couldnt-be-determined) > > _Help_: [New Script Deployments on Non-Compliant Changes Report](#new-script-deployments-on-non-compliant-changes-report) > > _Help_: [Change Logs Attached to the Wrong Change Request](#change-logs-attached-to-the-wrong-change-request) > -> _Help_: [Managed Bundle changes showing up as non-compliant changes?](#managed-bundle-changes-showing-up-as-non-compliant-changes) +> _Help_: [Managed Bundle changes showing up as non-compliant changes?](#managed-bundle-changes-showing-as-non-compliant-changes) > -> _Help_: [You do not have a Valid License Message](#you-do-not-have-a-valid-license-message) +> _Help_: [You don't have a Valid License Message](#you-dont-have-a-valid-license-message) ## Create a Change Request for Role Assignment @@ -40,7 +40,7 @@ For a Role Assignment (or any role change), you create a Change Request: 6. Click **Add Selection Customization** 7. Click **Pending Approval** on the Approval Status bar. -Once the Change Request is approved, you add the employee: +After the Change Request is approved, you add the employee: 1. In the NetSuite **Search** box, enter **emp:** and start typing the employee's name. Click **Edit** by the employee in the Search results. @@ -48,15 +48,15 @@ Once the Change Request is approved, you add the employee: 3. Open the **Access** tab and assign the new role, or delete an existing role. 4. Click **Save**. 5. Open the Change Request you created for this role change. -6. Click **ReSpider Now**. Once the Spider is complete, you can review your change. -7. Click **Complete** in the Change Request status once you verify your changes. +6. Click **ReSpider Now**. After the Spider is complete, you can review your change. +7. Click **Complete** in the Change Request status after you verify your changes. ## Add New Customizations to a Change Request Customizations can be added to any open Change Request. On the Change Request, click **Lookup Customization** to launch a window where you can search for customizations, or enter existing customizations in the **Customizations** field. The **Proposed Customizations** are for new -customizations that do not exist in any account. Refer to +customizations that don't exist in any account. Refer to [Creating a Change Request](/docs/platgovnetsuite/changemanagement/creating_change_request.md) for details. ## Search for Customizations @@ -65,7 +65,7 @@ To access a customization quick search, open **Strongpoint** > **Customizations* Quick Search** You can search using several factors and submit. When looking up by **Name**, using **Contains** -helps if you do not have the exact name. +helps if you don't have the exact name. ![custquicksearch](/images/platgovnetsuite/customizations/custquicksearch.webp) @@ -79,7 +79,7 @@ To fix this situation: 1. Open the Change Request. 2. If the ScriptID is correct, you can edit the Object and use **Change ID** to fix the object. -3. If the ScriptID is not correct: +3. If the ScriptID isn't correct: 1. Return the Change Request to **In Progress**. 2. Fix the identifier. @@ -98,17 +98,17 @@ Administrators can perform Approval Overrides on a Change Request. The Status bar is set to **Approved (Override)** and the administrator's name is displayed in the **Approval Override By** field. -## Change By Field Showing AutoSpider or Could Not Be Determined +## Change By Field Showing AutoSpider or Couldn't Be Determined -If the AutoSpider is not run, your Change Logs will be missing the **Changed by** and **Actual +If the AutoSpider isn't run, your Change Logs will be missing the **Changed by** and **Actual Change Date** fields. When the Change Log is newly created, the fields contain **Pending -AutoSpider**. If too many days go by, the fields change to **Could not be determined**. +AutoSpider**. If too many days go by, the fields change to **Couldn't be determined**. Refer to [Setting Up the AutoSpider and Alerts](/docs/platgovnetsuite/installation/running_the_spider.md) for details. ## New Script Deployments on Non-Compliant Changes Report -This situation occurs when you create a script through a Change Request, but do not include the +This situation occurs when you create a script through a Change Request, but don't include the Deployment Record on the Change Request. To properly add and deploy a script: 1. Create the Change Request to add a new script. @@ -118,8 +118,8 @@ Deployment Record on the Change Request. To properly add and deploy a script: 5. Deploy the script. If your site uses [Opportunistic Clearance](/docs/platgovnetsuite/changemanagement/opportunisticclearance/opportunistic_clearance.md), the -deployment record is handled automatically. You should make sure you understand all of the -ramifications of Opportunistic Clearance prior to enabling it for your account. +deployment record is handled automatically. You should ensure you understand all of the +ramifications of Opportunistic Clearance before enabling it for your account. ## Change Logs Attached to the Wrong Change Request @@ -128,7 +128,7 @@ The Change Log is attached to the oldest open Change Request. Best practice is to change the status of completed Change Requests to **Complete**. -## Managed Bundle changes showing up as non-compliant changes? +## Managed Bundle changes showing as non-compliant changes This situation is generally caused due to a time gap between Spider runs. Managed Bundles are evaluated after other changes. The Spider adds them to the non-compliant report the first time a @@ -137,7 +137,7 @@ removes it from the non-compliant report. No action is required to fix this situation. -## You do not have a Valid License Message +## You don't have a Valid License Message If a user sees a License message, you need to grant them a license. Refer to the [License Manager](/docs/platgovnetsuite/installation/license_manager.md) topic. diff --git a/docs/platgovnetsuite/installation/installation_overview.md b/docs/platgovnetsuite/installation/installation_overview.md index 887af128e5..ee0e87b976 100644 --- a/docs/platgovnetsuite/installation/installation_overview.md +++ b/docs/platgovnetsuite/installation/installation_overview.md @@ -24,7 +24,7 @@ Once your installation is complete, you can review the [Installation Settings](/docs/platgovnetsuite/installation/installation_settings_report.md) report. :::note -Optional menu items are hidden by default to keep the menus clean and easy to use. If users do not +Optional menu items are hidden by default to keep the menus clean and easy to use. If users don't see a menu item, they can turn it on through [Menu Management](/docs/platgovnetsuite/installation/managing_menus.md), assuming the feature is included in your [License Type](/docs/platgovnetsuite/installation/features_by_license_type.md). ::: diff --git a/docs/platgovnetsuite/installation/installation_settings_report.md b/docs/platgovnetsuite/installation/installation_settings_report.md index 78453ef401..89dd53c432 100644 --- a/docs/platgovnetsuite/installation/installation_settings_report.md +++ b/docs/platgovnetsuite/installation/installation_settings_report.md @@ -12,7 +12,7 @@ account and provides you with a measurable view of your status. To access the report, open **Strongpoint** > **Strongpoint Support** > **Installation Settings** -- Click **View** to view or print the desired report. +- Click **View** to view or print the report. - Click **Edit** to change global settings or add user notes ## Configuration and Stats @@ -29,7 +29,7 @@ The report has the following tabs: Count** column represents the number of objects the spider detected. The **Documented Record Count** represents the number of objects that were documented. In most cases, they should match when the spider is complete. If you access the report before the scheduled scripts are complete, - you may see incomplete or duplicate records. These will be cleaned up once the scripts complete + you may see incomplete or duplicate records. These will be cleaned up after the scripts complete their work. ### Documentation @@ -59,7 +59,7 @@ Script Archive File Folder ID can be edited. initiation of the script. - **Scripts with FLOStart Tags**: number of scripts with FLOEnd tag inserted to calculate execution time. -- **Scripts with No Audit Tags**: number of scripts that are not being monitored (no inserted +- **Scripts with No Audit Tags**: number of scripts that aren't being monitored (no inserted FLOStart or FLOEnd tags). - **Script Archive File Folder ID**: file identifier of the script archive folder. The **Enable Auto Archive** and default **Auto Archive Folder** are specified on the Installation tab. If enabled, a @@ -87,9 +87,9 @@ Accesses change management features: [ITGC Change Request](/docs/platgovnetsuite/changemanagement/creating_change_request.md). The default is unchecked. When enabled, an automatic ReSpider occurs when a Change Request status is changed to - **Completed**. This starts the ReSpider and ensures that all change logs are complete prior to + **Completed**. This starts the ReSpider and ensures that all change logs are complete before changing the status. If automatic ReSpidering is turned off, there is a risk of changes being - marked as non-compliant if the change logs are not complete when the user changes the status to + marked as non-compliant if the change logs aren't complete when the user changes the status to **Completed**. - **Enhanced User Provisioning**: enables access management for onboarding/offboarding and access change using the **[User Access Change Request](/docs/platgovnetsuite/changemanagement/user_provisioning.md)**. @@ -97,7 +97,7 @@ Accesses change management features: **User Provisioning Change Request** when **Enhanced User Provisioning** is enabled. - **Enable Auto-Role Removal**: automatically implement the offboarding changes approved though the **User Provisioning Change Request** when **Enhanced User Provisioning** is enabled. -- **Notification Sender**: select an email address from the drop down to use when sending +- **Notification Sender**: select an email address from the dropdown to use when sending notification emails. This sender is used when sending alerts for the following: - **User Access** (Onboarding, Offboarding, Temporary Access) - **ITGC** @@ -106,7 +106,7 @@ Accesses change management features: - **SoD Approval** - **SoD Rule Change** - **CR Email Template**: if you customize your **SoD Exemption Approval** or **SoD Rule Change - Approval** CR Templates, add them here so they are not overwritten when the next bundle is + Approval** CR Templates, add them here so they aren't overwritten when the next bundle is installed. Refer to [Advanced PDF / HTML Templates](/docs/platgovnetsuite/customization/pdf_html_templates.md). ![CR Email Template section on the Installation Settings Change Management tab](/images/platgovnetsuite/installing_strongpoint/change_management_cr_email_template.webp) @@ -141,20 +141,19 @@ Accesses the global parameters. Select **Edit** to change them. ### Notes Displays **User Notes** and **System Notes**. Use **New Note** or the **Create New** > **Note** from -the page drop down icon to create a new User Note. +the page dropdown icon to create a new User Note. ### Jira Integration Specifies the Jira credentials to use when Jira and Platform Governance for NetSuite are integrated. -Refer to [Jira Integration](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) for more information. +See [Jira Integration](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) for setup instructions. ### ServiceNow Integration Specifies the ServiceNow credentials to use when ServiceNow and Platform Governance for NetSuite are -integrated. Refer to [ServiceNow Integration](/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_integration.md) for more -information. +integrated. See [ServiceNow Integration](/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_integration.md) for setup instructions. ### Menu Management -Enables hiding menu items you do not use, to improve navigation. Refer to -[Managing Menus](/docs/platgovnetsuite/installation/managing_menus.md) for more information. +Enables hiding menu items you don't use, to improve navigation. See +[Managing Menus](/docs/platgovnetsuite/installation/managing_menus.md) for menu configuration steps. diff --git a/docs/platgovnetsuite/installation/installing_strongpoint.md b/docs/platgovnetsuite/installation/installing_strongpoint.md index 3d80e4ae23..5682a1df88 100644 --- a/docs/platgovnetsuite/installation/installing_strongpoint.md +++ b/docs/platgovnetsuite/installation/installing_strongpoint.md @@ -6,7 +6,7 @@ sidebar_position: 10 # Installing Platform Governance for NetSuite -To get Platform Governance for NetSuite up and running, you need to do the following: +To install Platform Governance for NetSuite, complete the following steps: 1. [Install the bundle](#install-the-bundle) using the correct bundle name and the bundle ID. 2. [Set the number of rows in list segments](#set-the-number-of-row-in-list-segments) to 1,000. This @@ -15,7 +15,7 @@ To get Platform Governance for NetSuite up and running, you need to do the follo 4. [Run the spider](running_the_spider). The spider scans your account in a standardized manner. A series of scheduled scripts is run to document the connections between the customizations. -Starting with Version 6.2.5, queues and priority allocation are deprecated. The bundle is now +Starting with Version 6.2.5, queues, and priority allocation are deprecated. The bundle is now installed using processor architecture for scheduled scripts. All deployments are set to low priority. @@ -44,7 +44,7 @@ The Bundle ID has been updated due to NetSuite changes. It is important that you set your NUMBER OF ROWS IN LIST SEGMENTS to 1,000. This is a NetSuite best practice and critical for the proper spidering of your workflows. If you are unable to edit this field, refer to -[Cannot Change the Number of Rows in List Segments](/docs/platgovnetsuite/reportabug/list_segments_not_editable.md) +[Can't Change the Number of Rows in List Segments](/docs/platgovnetsuite/reportabug/list_segments_not_editable.md) To set the Number of Rows in List Segments: diff --git a/docs/platgovnetsuite/installation/license_manager.md b/docs/platgovnetsuite/installation/license_manager.md index d64dd80743..76066b2123 100644 --- a/docs/platgovnetsuite/installation/license_manager.md +++ b/docs/platgovnetsuite/installation/license_manager.md @@ -22,7 +22,7 @@ If the **Take Web Site Offline for Maintenance** option is changed, you must use ![Add a New License.](/images/platgovnetsuite/installing_strongpoint/license_new.webp) -3. Click **Get Lic. Number** if the **License Number** is blank. If the License Number is not blank, +3. Click **Get Lic. Number** if the **License Number** is blank. If the License Number isn't blank, continue with the next step. 4. Click **New Licensed User**. @@ -55,7 +55,7 @@ Some buttons and fields are only visible when you **Edit** the License. Optimization**, **Intelligent Change Management** and **Enterprise**. - **Edition**: displays your NetSuite Edition. - **Subsidiaries**: displays the number of operating subsidiaries you have in your OneWorld account. - Platform Governance for NetSuite does not count subsidiaries that are only used for financial + Platform Governance for NetSuite doesn't count subsidiaries that are only used for financial transactions or as an elimination subsidiary. - **View**: select **Strongpoint Licensed Users** to filter the view and see the user information. - **Licensed User**: select a user number and click the Open icon that appears if you hover next to @@ -63,7 +63,7 @@ Some buttons and fields are only visible when you **Edit** the License. - **New Licensed User**: opens the **Licensed User** form. - **Edit**: opens the **Licensed User** form for the selected **User**. -Click on a column heading to toggle the sort order based on the column contents. By default, the +Click a column heading to toggle the sort order based on the column contents. By default, the records are sorted alphabetically by **User** name. -NetSuite displays 25 records per page. Use the drop down to select other pages of records. +NetSuite displays 25 records per page. Use the dropdown to select other pages of records. diff --git a/docs/platgovnetsuite/installation/managing_menus.md b/docs/platgovnetsuite/installation/managing_menus.md index 5365cc14da..8652fb79aa 100644 --- a/docs/platgovnetsuite/installation/managing_menus.md +++ b/docs/platgovnetsuite/installation/managing_menus.md @@ -6,7 +6,7 @@ sidebar_position: 90 # Managing Menus -Menus can be personalized by hiding menu items you do not use. Hiding items only affects the current +Menus can be personalized by hiding menu items you don't use. Hiding items only affects the current account. Menus and menu items not included in your License are automatically hidden. For example, if you have diff --git a/docs/platgovnetsuite/installation/redeploy_scripts_sandbox.md b/docs/platgovnetsuite/installation/redeploy_scripts_sandbox.md index 91f73aaae9..99294d7392 100644 --- a/docs/platgovnetsuite/installation/redeploy_scripts_sandbox.md +++ b/docs/platgovnetsuite/installation/redeploy_scripts_sandbox.md @@ -8,7 +8,7 @@ sidebar_position: 120 NetSuite has removed the scheduled status on scripts after a sandbox is refreshed. This stops the scripts required for environment compares, change requests built to push to production, and other -activities. This suitelet enables you to automatically reset all of your Platform Governance for +activities. Use this suitelet to automatically reset all of your Platform Governance for NetSuite scripts. If you have scheduled custom scripts in your sandbox, you must manually set the status after a sandbox refresh. @@ -24,6 +24,6 @@ status after a sandbox refresh. ![Open the Deployment tab](/images/platgovnetsuite/release_notes/script_deploy_tab.webp) 6. Click the Suitelet name: **Strongpoint Reset Schedule Deployments**. -7. Click on the Script **URL**. +7. Click the Script **URL**. ![Click the Script URL](/images/platgovnetsuite/release_notes/script_deploy_url.webp) diff --git a/docs/platgovnetsuite/installation/running_the_spider.md b/docs/platgovnetsuite/installation/running_the_spider.md index de583157b3..61a347254c 100644 --- a/docs/platgovnetsuite/installation/running_the_spider.md +++ b/docs/platgovnetsuite/installation/running_the_spider.md @@ -16,13 +16,13 @@ information. ::: :::note -You must keep this window open for the spider to complete. Do not change roles or accounts during +You must keep this window open for the spider to complete. Don't change roles or accounts during this process. ::: To run the spider: -1. Log in as an Administrator. NetSuite security standards require an active Administrator login to +1. Log in as an Administrator. NetSuite security standards require an active Administrator log in to execute some of the spider’s tasks. 2. Open **Strongpoint** > **Tools** > **Strongpoint Spider**. 3. Select **ReSpider All Records - SLOW** from **Update or ReSpider** if available. @@ -37,7 +37,7 @@ When finished, the gears stop spinning and **Spider Finished** is displayed belo Spider** button. You can close the tab when finished. The spider continues to work in the background to document your account. -If you are not sure the spider completed successfully: +If you aren't sure the spider completed successfully: 1. Open **Strongpoint** > **Strongpoint Support** > **Installation Settings** 2. Click **Print**. @@ -51,7 +51,7 @@ customizations. This phase takes 3 to 5 days to complete. The scripts automatica after 10 minutes and reschedule themselves based on queue priority to enable other scripts to run. If you track the progress of the scripts, you may see that they fail occasionally. The script will -reschedule itself, skip and flag the record that caused the fail. This is normal functionality and +reschedule itself, skip, and flag the record that caused the fail. This is normal functionality and any issues that arise are captured during the data validation phase. ### Confirm the Spider is Complete @@ -62,7 +62,7 @@ Status** tab to confirm the **Last Completed Spider** shows a date. ![Review the Spider Status tab of the Installation Settings](/images/platgovnetsuite/installing_strongpoint/install_settings_spider_status.webp) - **Strongpoint Record Server Side Spider Scheduled Script** is no longer running. -- **Strongpoint Search Customization to Make Join (By Join Proc)** should not have any results. If +- **Strongpoint Search Customization to Make Join (By Join Proc)** shouldn't have any results. If there are items in the results, it indicates the **Strongpoint Make Joins Script** is still running. @@ -75,14 +75,14 @@ validate the data. 1. Open **Strongpoint** > **Support** > **Installation Settings** 2. Click **View** 3. Review the **Recommendation** column for any Customization Types labeled **ReSpider This Record** - or **Run DeDuplicate**. You can click on the column head to change the sort order, or use the + or **Run DeDuplicate**. You can click the column head to change the sort order, or use the record counter on the right side of the table to view additional pages. Note the **Customization Types** so you can ReSpider them. 4. Review the **Documented Record Count** looking for any **0** (zero) values. Note the **Customization Types** so you can ReSpider them. No action is required if the value is blank. 5. Open **Strongpoint** > **Tools** > **Strongpoint Spider** 6. Select **ReSpider All Records - SLOW** from **Update or ReSpider** -7. **Select the Record Types** you noted. Use Ctrl-Click to select multiple record types. You do not +7. **Select the Record Types** you noted. Use Ctrl-Click to select multiple record types. You don't want to start over by ReSpidering the entire account. You can also enter an optional **Name Filter**: entering all of part of the customization name to focus the spider. You can use the **%** wildcard to search with the given name. @@ -90,7 +90,7 @@ validate the data. spider completes. :::note -If some of the Data Validation searches return a result, it does not mean there is a problem. In +If some of the Data Validation searches return a result, it doesn't mean there is a problem. In most cases if there are many results for any given search, you can fix this by ReSpidering the record type with the issue. ::: diff --git a/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md b/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md index bd08251c5e..7225561a87 100644 --- a/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md +++ b/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md @@ -35,7 +35,7 @@ There are two options where to set permissions: ## Creating a Copy of Classic Center This procedure makes a copy of the Strongpoint Classic Center tab that is preserved through bundle -updates. After you create the copy, you must add all of the appropriate category links prior to +updates. After you create the copy, you must add all of the appropriate category links before **Setting Permissions**. 1. Open **Customization** > **Centers and Tabs** > **Center Tabs** @@ -59,7 +59,7 @@ updates. After you create the copy, you must add all of the appropriate category window. Click **Edit** by the Label of the same category and the **Classic Center** version. 3. Add each **Link** and **Label** in your new **Center**, using the **Classic Center** version - as a guide. A drop down completion list is shown as you type. Click **Add** after each + as a guide. A dropdown completion list is shown as you type. Click **Add** after each addition. ![Two category windows open to copy links to your new Center.](/images/platgovnetsuite/installing_strongpoint/copy_categories2.webp) @@ -76,7 +76,7 @@ updates. After you create the copy, you must add all of the appropriate category 1. Open **Customization** > **Centers and Tabs** > **Center Tabs** 2. Click **Edit** by Strongpoint and the correct **Center Type** (**Engineering** in this example). 3. Open the **Audience** tab. -4. Assign the audience. This can be role(s) or specific employees. +4. Assign the audience. This can be roles or specific employees. 5. Click **Save** ![Assigning permissions.](/images/platgovnetsuite/installing_strongpoint/engineeringexample2.webp) diff --git a/docs/platgovnetsuite/installation/setting_up_auto_spider_alerts.md b/docs/platgovnetsuite/installation/setting_up_auto_spider_alerts.md index 6e06a2af73..af336579e8 100644 --- a/docs/platgovnetsuite/installation/setting_up_auto_spider_alerts.md +++ b/docs/platgovnetsuite/installation/setting_up_auto_spider_alerts.md @@ -10,10 +10,10 @@ After you have run your initial spider, the AutoSpider monitors your account on see if customization changes have occurred. This is a light scan of the data to determine if there were any changes. If changes are detected, you are reminded to ReSpider your account. -Best practice is to run the AutoSpider regularly. If the AutoSpider is not run, your Change Logs +Best practice is to run the AutoSpider regularly. If the AutoSpider isn't run, your Change Logs will be missing the **Changed by** and **Actual Change Date** fields. When the Change Log is newly created, the fields contain **Pending AutoSpider**. If too many days go by, the fields change to -**Could not be determined**. +**Couldn't be determined**. ## Set Up the AutoSpider @@ -26,7 +26,7 @@ portlet to load and see the **Spider Triggered** message before continuing. The **AutoSpider Portlet** is required to update certain object types in NetSuite. Once triggered through the dashboard portlet, it picks up all changes on custom objects and triggers the scheduled scripts to reflect them in the Customization records, going back two days. The AutoSpider portlet is -required in order to update these object types: +required to update these object types: - Bundle - Custom Report diff --git a/docs/platgovnetsuite/integrations/integration_mapping.md b/docs/platgovnetsuite/integrations/integration_mapping.md index a4a27d2fd0..e10ba2242c 100644 --- a/docs/platgovnetsuite/integrations/integration_mapping.md +++ b/docs/platgovnetsuite/integrations/integration_mapping.md @@ -20,7 +20,7 @@ Here is the basic process. ## Create the External System Customization Record -You can create the External System before using the mapping tool. If you do not create the External +You can create the External System before using the mapping tool. If you don't create the External System, it can be automatically created by the tool. 1. Open **Strongpoint** > **Customizations** > **Customization** > **New** @@ -35,7 +35,7 @@ System, it can be automatically created by the tool. The **.csv** file is where you specify the customization mapping between the External System and NetSuite. The file is uploaded when you run the tool. You can create a file with the specified headings, or download the template with the link on the first page of the Integration Mapping tool. -Do not change the specified headings. Here is the template: +Don't change the specified headings. Here is the template: ![int_map_csv_template](/images/platgovnetsuite/integrations/int_map_csv_template.webp) @@ -50,7 +50,7 @@ Do not change the specified headings. Here is the template: ## Open Integration Mapping tool -The Mapping Tool menu item is hidden by default. If you do not see the option in your menu, refer to +The Mapping Tool menu item is hidden by default. If you don't see the option in your menu, refer to the [Managing Menus](/docs/platgovnetsuite/installation/managing_menus.md) topic for information on making it available. @@ -89,7 +89,7 @@ Open **Strongpoint** > **Integrations** > **Mapping Tool** ![int_map_search](/images/platgovnetsuite/integrations/int_map_search.webp) -3. Search by all or part of a **Name**, **Type** or all or part of a **ScriptID**. For example, +3. Search by all or part of a **Name**, **Type**, or all or part of a **ScriptID**. For example, enter _cust_ for **Name** and click **Search** to find all customizations containing the search term: diff --git a/docs/platgovnetsuite/integrations/integrations.md b/docs/platgovnetsuite/integrations/integrations.md index 5280698918..73bf471bd3 100644 --- a/docs/platgovnetsuite/integrations/integrations.md +++ b/docs/platgovnetsuite/integrations/integrations.md @@ -17,7 +17,7 @@ Integrations with NetSuite include: - [Jira](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) ticketing System Integration - [ServiceNow](/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_integration.md) ticketing System Integration - [Zendesk](/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md) ticketing System integration -- Our [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) enables your developers to support your ticketing +- The [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) enables your developers to support your ticketing systems, making the integration functionality available to everyone. Integrating your systems with your Platform Governance for NetSuite account helps you make the most of your change management and ticketing strategies. diff --git a/docs/platgovnetsuite/navigating_strongpoint.md b/docs/platgovnetsuite/navigating_strongpoint.md index 2bc55c811c..cdbe71d195 100644 --- a/docs/platgovnetsuite/navigating_strongpoint.md +++ b/docs/platgovnetsuite/navigating_strongpoint.md @@ -13,7 +13,7 @@ can be hidden for each account through [Menu Management](/docs/platgovnetsuite/i These examples show all the options for an **Enterprise Compliance** license. :::note -If you do not see the **Strongpoint** tab, contact your Administrator regarding +If you don't see the **Strongpoint** tab, contact your Administrator regarding [Setting Tab Access](/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md). ::: @@ -27,24 +27,24 @@ Strongpoint Menu tab includes: - **Strongpoint Support**: How to, installation settings and reference information. - **Tools**: Access to the Spider, field impact analysis and SQL Library. -- **Customizations**: Search, manage and analyze your customizations. +- **Customizations**: Search, manage, and analyze your customizations. - **Clean up**: A set of tools to enable organized account clean up. - **Automated Search Clean up**: A set of tools to enable automated account clean up. - **Script Management**: Script analysis and management tools to improve performance. - **Change Management Reports**: Access all of the change reports. -- **Change Management Tools**: Create change requests, manage and track changes. +- **Change Management Tools**: Create change requests, manage, and track changes. - **Financial Controls**: Controls, agent approval and control incident handling. - **Audit**: Tools to audit your accounts. - **Material Risk**: Manage and track material risks. - **Manage Processes**: Process record analysis and search capabilities. - **Map Customizations**: View/edit customizations with no processes. -- **Process Issues**: Search, analyze and track your process issues. +- **Process Issues**: Search, analyze, and track your process issues. - **User Management**: Employee related searches to enhance control of your account. - **Integrations**: Access available integrations. - **Archives**: View archived information. - **Implementation**: View implementation assignments, planned customizations and improvement projects. -- **Testing**: Develop, organize, track and analyze testing of your processes and customizations. +- **Testing**: Develop, organize, track, and analyze testing of your processes and customizations. ## Strongpoint Overview diff --git a/docs/platgovnetsuite/reportabug/list_segments_not_editable.md b/docs/platgovnetsuite/reportabug/list_segments_not_editable.md index 88734d3125..02d97006b5 100644 --- a/docs/platgovnetsuite/reportabug/list_segments_not_editable.md +++ b/docs/platgovnetsuite/reportabug/list_segments_not_editable.md @@ -1,12 +1,12 @@ --- -title: "List Segments Field Cannot be Edited" -description: "List Segments Field Cannot be Edited" +title: "List Segments Field Can't be Edited" +description: "List Segments Field Can't be Edited" sidebar_position: 30 --- -# List Segments Field Cannot be Edited +# List Segments Field Can't be Edited -When setting the Number of Rows in List segments, sometimes the field cannot be edited. +When setting the Number of Rows in List segments, sometimes the field can't be edited. To resolve this: diff --git a/docs/platgovnetsuite/reportabug/mobile_devices.md b/docs/platgovnetsuite/reportabug/mobile_devices.md index 9705ede8f9..b7e5e8c425 100644 --- a/docs/platgovnetsuite/reportabug/mobile_devices.md +++ b/docs/platgovnetsuite/reportabug/mobile_devices.md @@ -6,4 +6,4 @@ sidebar_position: 80 # Platform Governance for NetSuite Not Supported on Mobile Devices -Platform Governance for NetSuite is not supported on mobile devices. Key features are not available. +Platform Governance for NetSuite isn't supported on mobile devices. Key features aren't available. diff --git a/docs/platgovnetsuite/reportabug/report_a_bug.md b/docs/platgovnetsuite/reportabug/report_a_bug.md index fc0d88e808..b1b8b030bb 100644 --- a/docs/platgovnetsuite/reportabug/report_a_bug.md +++ b/docs/platgovnetsuite/reportabug/report_a_bug.md @@ -6,9 +6,8 @@ sidebar_position: 100 # Contact Support -If you encounter any problems using Platform Governance for NetSuite or you have suggested -improvements, we would love to hear from you! Your feedback is incredibly valuable to us and the -continued success of our products. There are multiple options to provide feedback: +If you encounter any problems using Platform Governance for NetSuite or have suggested +improvements, submit feedback through one of the following options: - Contact Support - Comment on a User Guide Topic diff --git a/docs/platgovnetsuite/reportabug/saved_search_times_out.md b/docs/platgovnetsuite/reportabug/saved_search_times_out.md index 5c1524e6f8..e4129b84f9 100644 --- a/docs/platgovnetsuite/reportabug/saved_search_times_out.md +++ b/docs/platgovnetsuite/reportabug/saved_search_times_out.md @@ -34,7 +34,7 @@ To send the results to a recipient: ![saved_search_timeout2](/images/platgovnetsuite/troubleshooting/saved_search_timeout2.webp) -4. Click on **Customize Message** tab. +4. Click **Customize Message** tab. 5. Select **Send as CSV**. ![saved_search_timeout3](/images/platgovnetsuite/troubleshooting/saved_search_timeout3.webp) diff --git a/docs/platgovnetsuite/reportabug/spider_page_not_found.md b/docs/platgovnetsuite/reportabug/spider_page_not_found.md index d09d5ac656..e26c4c6215 100644 --- a/docs/platgovnetsuite/reportabug/spider_page_not_found.md +++ b/docs/platgovnetsuite/reportabug/spider_page_not_found.md @@ -9,5 +9,5 @@ sidebar_position: 50 If you see the **Spider Page Not Found** error: 1. Open **Setup** > **Company** > **General Preferences** -2. Make sure **Web Site Hosting Files Always Available** is checked. +2. Ensure **Web Site Hosting Files Always Available** is checked. 3. Click **Save** diff --git a/docs/platgovnetsuite/reportabug/spider_spins.md b/docs/platgovnetsuite/reportabug/spider_spins.md index 0523a138fe..1b9f694fd4 100644 --- a/docs/platgovnetsuite/reportabug/spider_spins.md +++ b/docs/platgovnetsuite/reportabug/spider_spins.md @@ -1,10 +1,10 @@ --- -title: "Spider Spins and Does Not Finish" -description: "Spider Spins and Does Not Finish" +title: "Spider Spins and Doesn't Finish" +description: "Spider Spins and Doesn't Finish" sidebar_position: 60 --- -# Spider Spins and Does Not Finish +# Spider Spins and Doesn't Finish If you kick off a spider and the gears on the page spin for more than an hour, this is likely an issue with the **IP Restriction**. Contact Netwrix support at diff --git a/docs/platgovnetsuite/reportabug/system_maintenance_period_error.md b/docs/platgovnetsuite/reportabug/system_maintenance_period_error.md index 78a0e36901..96ff641a34 100644 --- a/docs/platgovnetsuite/reportabug/system_maintenance_period_error.md +++ b/docs/platgovnetsuite/reportabug/system_maintenance_period_error.md @@ -17,7 +17,7 @@ If the **Take Web Site Offline for Maintenance** option is changed, you must use Or re-push the bundle to update the Spider link. ::: -In most cases, if you are not using NetSuite web sites there is no impact on your system so you can +In most cases, if you aren't using NetSuite web sites there is no impact on your system so you can do the following: 1. Open **Setup** > Select **Site Builder** > **Set Up Website** diff --git a/docs/platgovnetsuite/scriptmgmt/analyzing_script_performance.md b/docs/platgovnetsuite/scriptmgmt/analyzing_script_performance.md index 01a035bcaa..69ba089fe6 100644 --- a/docs/platgovnetsuite/scriptmgmt/analyzing_script_performance.md +++ b/docs/platgovnetsuite/scriptmgmt/analyzing_script_performance.md @@ -6,22 +6,21 @@ sidebar_position: 10 # Analyzing Script Performance -In order for Script Monitoring to function effectively: +For Script Monitoring to function effectively: -- Scripts must be deployed with a log status that supports Audit tag logging (for example, DEBUG or - AUDIT) +- Scripts must be deployed with a log status that supports Audit tag logging — DEBUG or AUDIT, for example - Script must be unlocked. -- Log level AUDIT is preferred since it is more efficient. DEBUG is not required for released code. +- Log level AUDIT is preferred since it is more efficient. DEBUG isn't required for released code. It can be left in place on locked but not hidden code to permit some monitoring to occur. -Scripts that are not in AUDIT mode can be found using the search **Strongpoint** > **Script +Scripts that aren't in AUDIT mode can be found using the search **Strongpoint** > **Script Management** > **Active Script Deployments Not in Audit Log Status**. You can change the criteria to exclude scripts set to DEBUG. ## Add Audit Start Tags :::note -Do not use this Mass Update if you share files between your User Event Scripts and Client Scripts. +Don't use this Mass Update if you share files between your User Event Scripts and Client Scripts. ::: The **Add Audit Tags Mass Update** inserts audit **Start Tags** into the scripts to enable the @@ -31,22 +30,22 @@ update backs up your scripts so you can access the older version through the Cus Platform Governance for NetSuite has an Archive folder to store the original versions, and this folder must be set on the mass update when adding audit tags. -Audit tags cannot be automatically added for Client Scripts due to the NetSuite Client Script +Audit tags can't be automatically added for Client Scripts due to the NetSuite Client Script execution flow. They can be manually added, as described in this topic. These procedures only apply to unlocked scripts. 1. Open **Documents** > **Files** > **File Cabinet** 2. Expand **SuiteBundles** > **Bundle 294336** 3. Look for **Archive** under **FLODocs Enterprise** or **FLODocs Enterprise (2)** -4. Click on folder containing **Archive**, and copy the **Internal ID** of the Archive folder. If - the **Internal ID** column is not displayed: +4. Click folder containing **Archive**, and copy the **Internal ID** of the Archive folder. If + the **Internal ID** column isn't displayed: 1. Open **NetSuite Home** > **Set Preferences** - 2. Under **Defaults**, make sure **Show Internal IDs** is checked on the **General** tab. + 2. Under **Defaults**, ensure **Show Internal IDs** is checked on the **General** tab. 3. Click **Save** 5. Open **Lists** > **Mass Update** > **Mass Updates** -6. Click on **Custom Updates** > **Customization** > **Strongpoint Add Audit Tag** +6. Click **Custom Updates** > **Customization** > **Strongpoint Add Audit Tag** 7. Enter **Strongpoint Add Audit Tag** for Name. 8. Paste the **Internal ID** of the **Archive** folder. @@ -54,15 +53,15 @@ to unlocked scripts. 9. Click **Preview** to review the actions. Click **Perform Update** to add the Start tags. 10. End tags are used to measure script average run time. In many cases, there is no systematic way - of identifying where the end of the script is. Our recommended approach is to use the script + of identifying where the end of the script is. The recommended approach is to use the script metrics, such as **# of daily executions** to prioritize which scripts you want to measure the average run time. Then add the end tag manually to the end of the script. ## Adding Audit Tags Manually -Include the **NetSuite N/log Module**. Refer to the -[NetSuite N/log help](https://tstdrv1643032.app.netsuite.com/app/help/helpcenter.nl?fid=section_4574548135.html) -for more information. +Include the **NetSuite N/log Module**. See the +[NetSuite N/log Module reference](https://tstdrv1643032.app.netsuite.com/app/help/helpcenter.nl?fid=section_4574548135.html) +for syntax and usage details. **FLOStart** and **FLOEnd** Tags are NetSuite Audit tags inserted using standard syntax: @@ -89,13 +88,13 @@ for more information. - Inside last line of relevant function - Only required for execution speed logging -Refer to the -[NetSuite log.audit help](https://tstdrv1643032.app.netsuite.com/app/help/helpcenter.nl?fid=section_4430384449.html) -for more information on SuiteScript 2.0. +See the +[NetSuite log.audit reference](https://tstdrv1643032.app.netsuite.com/app/help/helpcenter.nl?fid=section_4430384449.html) +for SuiteScript 2.0 syntax details. ## Validate the Tags -The audit tag information is updated in the documentation once the Script Parser runs (daily). You +The audit tag information is updated in the documentation after the Script Parser runs (daily). You can validate the audit tags are in place by: - Running **Strongpoint** > **Script Management** > **Scripts with No Audit Tags** diff --git a/docs/platgovnetsuite/scriptmgmt/reviewing_script_performance_errors.md b/docs/platgovnetsuite/scriptmgmt/reviewing_script_performance_errors.md index 5191718c97..e74baf6fab 100644 --- a/docs/platgovnetsuite/scriptmgmt/reviewing_script_performance_errors.md +++ b/docs/platgovnetsuite/scriptmgmt/reviewing_script_performance_errors.md @@ -34,9 +34,9 @@ field and export. Script error reporting requires the scripts to be in at least Audit mode. **Error Report**: Summary of all the available errors logged in the system for various scripts. -Errors are summarized into types by excluding specific data such as line numbers, ids and, where +Errors are summarized into types by excluding specific data such as line numbers, ids, and where detectable, execution data. The result is a manageable number of errors. Error data expires over -time. This should not be viewed as a continuing or reliable view of all errors over time. +time. This shouldn't be viewed as a continuing or reliable view of all errors over time. **Yesterday’s Script Errors**: Summary of all the available errors logged in the system for various scripts for the previous day. diff --git a/docs/platgovnetsuite/scriptmgmt/script_mgmt_overview.md b/docs/platgovnetsuite/scriptmgmt/script_mgmt_overview.md index 7a0cec1beb..32b1be88e6 100644 --- a/docs/platgovnetsuite/scriptmgmt/script_mgmt_overview.md +++ b/docs/platgovnetsuite/scriptmgmt/script_mgmt_overview.md @@ -15,7 +15,7 @@ can: - Understand script execution times :::note -Platform Governance for NetSuite does not document or analyze locked scripts. +Platform Governance for NetSuite doesn't document or analyze locked scripts. ::: ## Automatically Archiving Scripts @@ -38,22 +38,22 @@ Managing script errors is the first level of analysis required for optimization. can greatly increase performance and fix broken scripts. Script error reports provides a summary of all the available errors logged in the system for various -scripts. Errors are summarized into types by excluding specific data such as line numbers, ids and, +scripts. Errors are summarized into types by excluding specific data such as line numbers, ids, and where detectable, execution data. The result is a manageable number of errors. 1. Ensure that the scripts are log levels are at least Error (anything other than Emergency). See the NetSuite User Guide article “Setting Script Execution Log Levels” for log level definitions. 2. Review the Error Report. All script errors are reported regardless of if the script is locked, unlocked, part of a bundle or any other factor. -3. Identify errors that are not material to your business and mark them as resolved +3. Identify errors that aren't material to your business and mark them as resolved 4. Platform Governance for NetSuite no longer reports those errors, so any future errors that occur are unexpected and should be managed. ## Analyze Script Performance Data -Platform Governance for NetSuite enables you to systematically analyze: +With Platform Governance for NetSuite, you can systematically analyze: -- How often scripts are executing to enable you to focus on high volume scripts or identity scripts +- How often scripts are executing so you can focus on high-volume scripts or identity scripts that are executing many times more than the transactions in the account would warrant. - Who is triggering the script to identify scripts that are being triggered inappropriately, which is an efficient use of system capacity. @@ -61,7 +61,7 @@ Platform Governance for NetSuite enables you to systematically analyze: There are two requirements to analyze and report script performance data: -1. Start Tags must be inserted at the beginning of the script in order to track frequency of +1. Start Tags must be inserted at the beginning of the script to track frequency of execution and who is triggering the script. End tags are required for Script Average Run Time. 2. Log level of the scripts be set to at least Audit or Debug. @@ -70,11 +70,11 @@ There are pre-built saved mass updates to quickly do this, but some factors need Since tags need to be added to the script file, there are some limitations on the data Platform Governance for NetSuite can analyze for locked scripts. -1. **Locked Script Records**: A locked script record does not impact script analysis since Platform +1. **Locked Script Records**: A locked script record doesn't impact script analysis since Platform Governance for NetSuite analyzes the Script File. If all elements of the script are unlocked or if only the script record is locked, Platform Governance for NetSuite can report on script performance metrics. -2. **Locked but readable (not hidden) Script File**: Script tags cannot be added to locked files, +2. **Locked but readable (not hidden) Script File**: Script tags can't be added to locked files, but Platform Governance for NetSuite can read them if they have audit tags already in them. - With audit tags: @@ -83,35 +83,34 @@ Governance for NetSuite can analyze for locked scripts. - Document who is executing the script - Provides a sense of how often it is executing. It tracks the number of executions per tag and averages them. The number can vary based on the placement of the tags and how the script is - executed any given time. While it does not provide an exact number, it will be within the + executed any given time. While it doesn't provide an exact number, it will be within the right range and can help identify if a script is executing significantly more than the transaction volume would indicate. - Without audit tags: Same and locked and hidden scripts below. 3. **Locked and hidden script files**: For scripts where the script file is hidden and locked, - Platform Governance for NetSuite cannot track performance metrics, in most cases. However, if the + Platform Governance for NetSuite can't track performance metrics, in most cases. However, if the script Log Level is changed to Debug mode, Platform Governance for NetSuite can document who is executing the script while the script is at that log level. ## Define the Scope of your Analysis -The focus of script analysis can vary based on your business needs. We recommend the following based +The focus of script analysis can vary based on your business needs. The following guidance is based on the questions you are trying to answer: -**Which scripts are executing too often or being triggered by the wrong people across the whole -account?** +**Which scripts are executing too often or being triggered by the wrong people across the whole account** This question would require a broader approach and applying audit tags and changing log levels across the account. However, if you have a large number of locked and hidden scripts, you may be forced to go with a more focused approach due to the limitations mentioned above. -**How are my scripts performing in a particular process?** +**How scripts perform in a particular process** To get a process focused view, you can use the Map Customization Tools to associate bundles and -scripts to processes. This enables you to apply audit tags and change log levels for scripts +scripts to processes, letting you apply audit tags and change log levels for scripts associated with specific processes using the mass update filters. -**How are particular scripts or bundles performing?** +**How particular scripts or bundles perform** In this case you can either add the audit tags and change the log levels manually or filter the mass updates. @@ -123,17 +122,17 @@ consider the following factors. 1. Changing the log level from Error or Emergency to Audit, which is required for Script Analysis may increase the level of log entries that appear on the Execution Log tab based on what tags are in the scripts. -2. Log levels **cannot** be automatically changed for bundled deployments. Bundled deployment log +2. Log levels **can't** be automatically changed for bundled deployments. Bundled deployment log levels need to be changed manually. 3. Since audit tags can only be added to unlocked files, changing the log levels of locked files serves no purpose from a Script Analysis perspective. -Platform Governance for NetSuite has the following capabilities to set up script analysis. We will -provide specific ways to use this tools based on your objectives and account set up. +Platform Governance for NetSuite has the following capabilities to set up script analysis. Specific +ways to use these tools depend on your objectives and account setup. ## Identify which Scripts and how many Scripts have Locked and Hidden Files -As mentioned above audit tags cannot be added to these files and changing the log levels is moot. A +As mentioned above, audit tags can't be added to these files and changing the log levels is moot. A future bundle will have this search built in, but you can quickly identify and count the number of locked scripts by creating this saved search: @@ -154,9 +153,9 @@ options to download or edit the file, the script file is unlocked. ## Run Mass Updates A core part of the script performance analysis involves the use of audit tags. These audit tags only -provide data when the scripts are in Audit or Debug mode. It is important to switch the scripts over -to one of those two levels if appropriate.The Add Audit Tags mass update backs up and then adds -start tags to all of your unlocked scripts. This enables tracking frequency of execution. You can +provide data when the scripts are in Audit or Debug mode. Switch the scripts to +one of those two levels if appropriate.The Add Audit Tags mass update backs up and then adds +start tags to all of your unlocked scripts. This tracks execution frequency. You can manually add end tags for script execution time tracking. [Analyzing Script Performance](/docs/platgovnetsuite/scriptmgmt/analyzing_script_performance.md). @@ -171,7 +170,7 @@ who used it and how long it took to execute. Schedule the Script Utilization Dat You can monitor the progress of the script data collection with **Strongpoint** > **Script Management** > **Tagged scripts with No Data** The scripts on this list will fall off this search as data is collected. Scripts that remain on this -list are not being executed. +list aren't being executed. ## Review Script Performance and Error Reports diff --git a/docs/platgovnetsuite/sod/approving_exceptions_sod_rules.md b/docs/platgovnetsuite/sod/approving_exceptions_sod_rules.md index 13cfdd5acc..f94f285978 100644 --- a/docs/platgovnetsuite/sod/approving_exceptions_sod_rules.md +++ b/docs/platgovnetsuite/sod/approving_exceptions_sod_rules.md @@ -21,8 +21,8 @@ To create a change request: level. - **Reason for Role or Permission Change** Enter the information supporting the approval request. - - Select one or more of the **Affected Employee(s)**, **Customization (User Role)**, **Proposed - User Role(s)**, **Proposed Global Permission(s)**, and **Affected Rule(s)**. + - Select one or more of the **Affected Employees**, **Customization (User Role)**, **Proposed + User Roles**, **Proposed Global Permissions**, and **Affected Rules**. 3. Click **In Progress** in the status bar to indicate you are working on the request. 4. Click **Preview SoD Violations** to see what violations may occur. diff --git a/docs/platgovnetsuite/sod/assigning_role_with_preapproved_change_request.md b/docs/platgovnetsuite/sod/assigning_role_with_preapproved_change_request.md index bb4e5b239f..65b7fa42a8 100644 --- a/docs/platgovnetsuite/sod/assigning_role_with_preapproved_change_request.md +++ b/docs/platgovnetsuite/sod/assigning_role_with_preapproved_change_request.md @@ -19,8 +19,8 @@ sidebar_position: 70 level. - **Reason for Role or Permission Change** Enter the information supporting the approval request. - - Select one or more of the **Affected Employee(s)**, **Customization (User Role)**, **Proposed - User Role(s)**, **Proposed Global Permission(s)**, and **Affected Rule(s)**. + - Select one or more of the **Affected Employees**, **Customization (User Role)**, **Proposed + User Roles**, **Proposed Global Permissions**, and **Affected Rules**. 3. Click **In Progress** in the status bar to indicate you are working on the request. 4. Click **Preview SoD Violations** to see what violations may occur. diff --git a/docs/platgovnetsuite/sod/creating_an_approved_change_request_clear_violation.md b/docs/platgovnetsuite/sod/creating_an_approved_change_request_clear_violation.md index ec249ac63f..5d34507fa3 100644 --- a/docs/platgovnetsuite/sod/creating_an_approved_change_request_clear_violation.md +++ b/docs/platgovnetsuite/sod/creating_an_approved_change_request_clear_violation.md @@ -9,7 +9,7 @@ sidebar_position: 80 ## Assign a Non-Compliant Role to an Employee :::note -Make sure the SoD Rule that it will violate is **Non-Blocking**. This way the employee record can be +Ensure the SoD Rule that it will violate is **Non-Blocking**. This way the employee record can be saved even if it is a non-compliant role. ::: @@ -34,8 +34,8 @@ To create an approved change request: level. - **Reason for Role or Permission Change**: Enter the information supporting the approval request. - - Select one or more of the **Affected Employee(s)**, **Affected Rule(s)** and **Affected User - Role(s)**. + - Select one or more of the **Affected Employees**, **Affected Rules** and **Affected User + Roles**. 3. Click **In Progress** in the status bar to indicate you are working on the request. 4. **Save** the Change Request. diff --git a/docs/platgovnetsuite/sod/creating_sod_approval_request.md b/docs/platgovnetsuite/sod/creating_sod_approval_request.md index 4289a1d613..515380f3a9 100644 --- a/docs/platgovnetsuite/sod/creating_sod_approval_request.md +++ b/docs/platgovnetsuite/sod/creating_sod_approval_request.md @@ -29,11 +29,11 @@ To create an SoD Approval request: 4. Enter information for **Scope**: - - For **Cross Role Exemption**, select one or more of the **Affected Employee(s)**, **Affected - Rule(s)** or **Affected Role(s)**. + - For **Cross Role Exemption**, select one or more of the **Affected Employees**, **Affected + Rules** or **Affected Roles**. - For **Role Exemption** - - Select one or more of the **Affected Employee(s)** and **Affected Rule(s)**. + - Select one or more of the **Affected Employees** and **Affected Rules**. - Select one or more options for applying the exemption. If you choose **Select Current Employees**, the **Affected Employee** entry is enabled. @@ -52,7 +52,7 @@ SoD Exemption** button is available after the request is Approved. ![Add Employees to Approved SoD Exemption](/images/platgovnetsuite/sod/sod_add_employee.webp) 1. Click **Add Employees to SoD Exemption**. -2. Select one or more **Affected Employee(s)** to add. +2. Select one or more **Affected Employees** to add. ![Select Affected Employees](/images/platgovnetsuite/sod/sod_add_employee_select.webp) diff --git a/docs/platgovnetsuite/sod/creating_sod_rules.md b/docs/platgovnetsuite/sod/creating_sod_rules.md index 81b17aa285..337f9dc634 100644 --- a/docs/platgovnetsuite/sod/creating_sod_rules.md +++ b/docs/platgovnetsuite/sod/creating_sod_rules.md @@ -29,11 +29,11 @@ implementing your custom form. The following are general definitions of access levels for permissions in NetSuite. -- **View**: The user has access to view existing files. The user cannot create, edit, or delete +- **View**: The user has access to view existing files. The user can't create, edit, or delete existing files. -- **Create**: The user can create new and view existing files. The user cannot edit or delete +- **Create**: The user can create new and view existing files. The user can't edit or delete existing files. -- **Edit**: The user has access to create, view, and edit files. The user cannot delete existing +- **Edit**: The user has access to create, view, and edit files. The user can't delete existing files. - **Full**: The user can create, view, edit, and delete files. @@ -45,14 +45,14 @@ The following are general definitions of access levels for permissions in NetSui 2. **External ID** is assigned by Platform Governance for NetSuite. Custom rules are numbered 1000 or above. External IDs for custom rules can be edited. SoD Library rule External IDs are 1 - through 999 and cannot be edited. + through 999 and can't be edited. 3. Add a Rule **Name** and **Description** and optional **Memo**. 4. **Status** indicates the current state of the Rule: **Test on Roles**, **Disabled**, **Test on Employees**, **Approved**, **Pending for Approval**, **Disabled - Feature Not In Use**, or **Disabled - Compensating Control**. Only **Approved**and **Active** rules are applied. 5. Select or add a new **Risk** (optional). 6. Select the **Process** from the list. The rule pertains to the group of activities and - transactions defined for the selected **Process**. The **Process** for an SoD Library rule cannot + transactions defined for the selected **Process**. The **Process** for an SoD Library rule can't be edited. 7. Check to make the rule **Inactive** if needed (optional). 8. Check to **Block Conflict** to block the save attempt on the employee record if the employee @@ -62,20 +62,20 @@ The following are general definitions of access levels for permissions in NetSui ![SoD Access Controls](/images/platgovnetsuite/sod/sod_access_controls.webp) - **Role-based** - Select one or more **Roles** from the displayed list. The Permissions and - Advanced Permission Controls are not available for this option. + Advanced Permission Controls aren't available for this option. - **Permission-based** 1. Select **One-Sided Rule** (only Base Permissions/Levels) or **Two-Sided Rule** (both Base and Conflicting Permissions/Levels). 2. Select one or more **Base Permissions** and one or more **Base Permission Levels**. For **Base Permission**, you can enter part of the name to see a matching list, or use the - drop down to view all of the permissions. + dropdown to view all of the permissions. 3. Optionally add a **Base Permission Text Match** to filter for conflicts matching the base permission string. For example: **ADMI\_** matches all **ADMI** permissions. Can use **startswith** search operator. 4. For Two-Sided Rules, select one or more **Conflicting Permissions** and one or more **Conflicting Permission Levels**. For **Conflict Permission**, you can enter part of the - name to see a matching list, or use the drop down to view all of the permissions. + name to see a matching list, or use the dropdown to view all of the permissions. 5. Optionally add a **Conflict Permission Text Match** to filter for conflicts matching the conflicting permission string. For example: **ADMI\_** matches all **ADMI** permissions. Can use **startswith** search operator. @@ -134,9 +134,9 @@ SoD Rule Import available to enable bulk add or update SoD rules to your product - Roles - Memo - Base Permission - - Base Permission Level(s) + - Base Permission Levels - Conflicting Permission - - Conflicting Permission Level(s) + - Conflicting Permission Levels - Base Permission Text Match - Conflict Permission Text Match - Subsidiaries diff --git a/docs/platgovnetsuite/sod/sod_clean_up.md b/docs/platgovnetsuite/sod/sod_clean_up.md index df5b9f840e..4f2ac89b44 100644 --- a/docs/platgovnetsuite/sod/sod_clean_up.md +++ b/docs/platgovnetsuite/sod/sod_clean_up.md @@ -15,7 +15,7 @@ Platform Governance for NetSuite automatically removes employees from SoD Approv of these conditions occur: - NetSuite access is removed -- Applicable role(s) are removed +- Applicable roles are removed - Employee is In-activated :::note diff --git a/docs/platgovnetsuite/sod/sod_notifications.md b/docs/platgovnetsuite/sod/sod_notifications.md index fc15a8d8b0..3e74d62e81 100644 --- a/docs/platgovnetsuite/sod/sod_notifications.md +++ b/docs/platgovnetsuite/sod/sod_notifications.md @@ -22,6 +22,6 @@ information to approvers for SoD violations. 4. A confirmation is displayed when the change request is created. You can click the link to view the request. 5. Once a change request is generated,Platform Governance for NetSuite sends email to the approvers. - The email shows the requested change, the SoD violation(s) and links to the change request. + The email shows the requested change, the SoD violations, and links to the change request. ![sod_email_msg](/images/platgovnetsuite/sod/sod_email_msg.webp) diff --git a/docs/platgovnetsuite/sod/sod_overview.md b/docs/platgovnetsuite/sod/sod_overview.md index e00887dbe2..fb43706287 100644 --- a/docs/platgovnetsuite/sod/sod_overview.md +++ b/docs/platgovnetsuite/sod/sod_overview.md @@ -6,10 +6,9 @@ sidebar_position: 170 # SoD Overview -Advanced Segregation of Duties (SoD) gives you complete separation of duties and access controls. It -allows you to log violations and block access to critical permissions / access to your system. +Advanced Segregation of Duties (SoD) gives you complete separation of duties and access controls. Use Advanced SoD to log violations and block access to critical permissions in your system. -## What is Advanced SoD? +## What Advanced SoD provides Advanced SoD provides: @@ -22,10 +21,10 @@ Advanced SoD provides: - **Warning messages and email alerts** to let you know when you are in an undesired zone. - **Custom reports** for documentation, retroactive approvals and continuous access reviews, ultimately preserving audit trails. -- The power of **Agent** to fill in gaps, monitor and document activities of “super users” and those +- The power of **Agent** to fill in gaps, monitor, and document activities of “super users” and those with positional authority. -## Why use Advanced SoD? +## Benefits of Advanced SoD By implementing Advanced SoD you can create flexible and easy to maintain rules. @@ -41,7 +40,7 @@ You can create rules that: - Have a blocking option to prevent assignment of critical roles or permissions without authorization -## How does Advanced SoD work? +## How Advanced SoD works Advanced SoD works through the following System Process Flow: @@ -55,18 +54,18 @@ Advanced SoD's also works through the following Functional Process Flow: | **Use Case Causing SoD Conflict** | Are SoD Conflicts Addressed by an existing Approved Exemption? | SoD Incident /Change Log Created | Platform Governance for NetSuite Systematic Updates | | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| New Employee Onboarded and one Role assigned | Role Exemption | Compliant SoD Incident(s) | 1. New Employee added to Affected Employees on the Role Exemption (if **All Current and Future** checkbox is checked, if not it is treated as SoD Conflicts that have no Exemption)
2. Role Exemption associated to the SoD Incident(s) | -| | Cross Role Exemption | Compliant SoD Incident(s) | 1. Cross Role Exemption associated to the SoD Incident(s) | | -| | SoD Conflicts that have no Exemption | Unresolved SoD Incident(s) | 1. No immediate action taken
2. If an Exemption is created to resolve the SoD Conflict(s) in arrears, it is associated to the SoD Incident(s) at that time | | -| New Employee Onboarded and multiple Roles assigned | Role Exemption | Compliant SoD Incident(s) only for single Role SoD Incident(s) | 1. New Employee added to Affected Employees on the Role Exemption (if **All Current and Future** checkbox is checked, if not it is treated as SoD Conflicts that have no Exemption)
2. Role Exemption associated to the SoD Incident(s) | -| | Cross Role Exemption | Compliant SoD Incident(s) for those caused by multiple Roles | 1. Cross Role Exemption associated to the SoD Incident(s) | | -| | SoD Conflicts that have no Exemption | Unresolved SoD Incident(s) | 1. No immediate action taken
2. If an Exemption is created to resolve the SoD Conflict(s) in arrears, it is associated to the SoD Incident(s) at that time | | +| New Employee Onboarded and one Role assigned | Role Exemption | Compliant SoD Incidents | 1. New Employee added to Affected Employees on the Role Exemption (if **All Current and Future** checkbox is checked, if not it is treated as SoD Conflicts that have no Exemption)
2. Role Exemption associated to the SoD Incidents | +| | Cross Role Exemption | Compliant SoD Incidents | 1. Cross Role Exemption associated to the SoD Incidents | | +| | SoD Conflicts that have no Exemption | Unresolved SoD Incidents | 1. No immediate action taken
2. If an Exemption is created to resolve the SoD Conflicts in arrears, it is associated to the SoD Incidents at that time | | +| New Employee Onboarded and multiple Roles assigned | Role Exemption | Compliant SoD Incidents only for single Role SoD Incidents | 1. New Employee added to Affected Employees on the Role Exemption (if **All Current and Future** checkbox is checked, if not it is treated as SoD Conflicts that have no Exemption)
2. Role Exemption associated to the SoD Incidents | +| | Cross Role Exemption | Compliant SoD Incidents for those caused by multiple Roles | 1. Cross Role Exemption associated to the SoD Incidents | | +| | SoD Conflicts that have no Exemption | Unresolved SoD Incidents | 1. No immediate action taken
2. If an Exemption is created to resolve the SoD Conflicts in arrears, it is associated to the SoD Incidents at that time | | | Existing Employee Offboarded by unchecking **Give Access** checkbox or removing all Roles | Role Exemption | | 1. Employee removed from Affected Employees on the SoD Role Exemption | | | Cross Role Exemption | | 1. Employee removed from Affected Employees on the SoD Cross Role Exemption | | | | SoD Conflicts that have no Exemption | | 1. N/A. Employee has been Offboarded, no new SoD Conflict exists | | -| Existing Employee gets a new Role(s) causing new SoD Incident(s) | Role Exemption | Compliant SoD Incident(s) only for single Role SoD Incident(s) | 1. Role Exemption associated to the SoD Incident(s) (if **All Current and Future** checkbox is checked, if not it is treated as SoD Conflicts that have no Exemption) | -| | Cross Role Exemption | Compliant SoD Incident(s) for those caused by multiple Roles | 1. Cross Role Exemption associated to the SoD Incident(s) | | -| | SoD Conflicts that have no Exemption | Unresolved SoD Incident(s) | 1. No immediate action taken
2. If an Exemption is created to resolve the SoD Conflict(s) in arrears, it is associated to the SoD Incident(s) at that time | | -| Existing Employee with a Cross Role Conflict has one or more Roles removed. SoD must be re-evaluated. | Role Exemption | Compliant SoD Incident(s) only for single Role SoD Incident(s) | 1. Role Exemption associated to the SoD Incident(s) (if **All Current and Future** checkbox is checked, if not it is treated as SoD Conflicts that have no Exemption)
2. Employee added to Affected Employees on the Role Exemption
3. If the Role removal resolved an existing SOD Conflict, Employee removed from Affected Employees on the SOD Role Exemption | -| | Cross Role Exemption | Compliant SoD Incident(s) for those caused by multiple Roles | 1. Cross Role Exemption associated to the SOD Incident(s).
2. If the Role removal resolved an existing SOD Conflict, Employee removed from Affected Employees on the SOD Cross Role Exemption | | -| | SoD Conflicts that have no Exemption | Unresolved SoD Incident(s) | 1. No immediate action taken
2. If an Exemption is created to resolve the SoD Conflict(s) in arrears, it is associated to the SoD Incident(s) at that time | | +| Existing Employee gets a new Roles causing new SoD Incidents | Role Exemption | Compliant SoD Incidents only for single Role SoD Incidents | 1. Role Exemption associated to the SoD Incidents (if **All Current and Future** checkbox is checked, if not it is treated as SoD Conflicts that have no Exemption) | +| | Cross Role Exemption | Compliant SoD Incidents for those caused by multiple Roles | 1. Cross Role Exemption associated to the SoD Incidents | | +| | SoD Conflicts that have no Exemption | Unresolved SoD Incidents | 1. No immediate action taken
2. If an Exemption is created to resolve the SoD Conflicts in arrears, it is associated to the SoD Incidents at that time | | +| Existing Employee with a Cross Role Conflict has one or more Roles removed. SoD must be re-evaluated. | Role Exemption | Compliant SoD Incidents only for single Role SoD Incidents | 1. Role Exemption associated to the SoD Incidents (if **All Current and Future** checkbox is checked, if not it is treated as SoD Conflicts that have no Exemption)
2. Employee added to Affected Employees on the Role Exemption
3. If the Role removal resolved an existing SOD Conflict, Employee removed from Affected Employees on the SOD Role Exemption | +| | Cross Role Exemption | Compliant SoD Incidents for those caused by multiple Roles | 1. Cross Role Exemption associated to the SOD Incidents.
2. If the Role removal resolved an existing SOD Conflict, Employee removed from Affected Employees on the SOD Cross Role Exemption | | +| | SoD Conflicts that have no Exemption | Unresolved SoD Incidents | 1. No immediate action taken
2. If an Exemption is created to resolve the SoD Conflicts in arrears, it is associated to the SoD Incidents at that time | | diff --git a/docs/platgovnetsuite/sod/sod_reports.md b/docs/platgovnetsuite/sod/sod_reports.md index f375ca07da..7feb3dd131 100644 --- a/docs/platgovnetsuite/sod/sod_reports.md +++ b/docs/platgovnetsuite/sod/sod_reports.md @@ -45,7 +45,7 @@ SoD Testing
| SoD Change Management | Description | | --- | --- | | SoD Change Requests (List) | All SoD Change Requests for affected employees, approval status, affected rule and roles and rule status. | -| New SoD Approval (Form) | Change Request form for employee, role or permission changes. | +| New SoD Approval (Form) | Change Request form for employee, role, or permission changes. | | New SoD Rule Change (Form) | Change Request form for a Rule change. | ## SoD Risk Management @@ -76,7 +76,7 @@ SoD Testing
| SoD Employee Access | Description | | --- | --- | -| Employee Access Review Report | Summary of employees with access. Click on employee to view roles, permissions and levels. | +| Employee Access Review Report | Summary of employees with access. Click employee to view roles, permissions, and levels. | | Employees with Administrator Role | List of all employees with Administrator role. | | Employees Roles Assigned/Changed | Log of all role changes. | | Employees Permissions Assigned/Changed | Log of all permission changes. | @@ -100,5 +100,5 @@ SoD Testing
| --- | --- | | User Role Test Violations Summary | List of all test violations for roles. Includes SoD Violation, Non-Compliant Roles, Base Permissions and Conflicting Permissions. | | Employee Test Violations Summary | List of all test violations for employees. Includes SoD Violation, Non-Compliant Roles, Base Permissions and Conflicting Permissions. | -| User Role Test Violation Detailed | List with User Role Name link, SoD Violation, Base Permissions, Conflicting Permissions, User Role link and SoD Rule data. Report can be sorted, filtered and exported to Excel. Click **Create SoD Approval** to create an exemption from the report. The exemption is created as type **Role Exemption**. | -| Employee Test Violation Detailed | List with Employee Name link, SoD Violation, Non-compliant Roles, Non-compliant Global Permissions, Base Permissions, Conflicting Permissions and SoD Rule data. Report can be sorted, filtered and exported to Excel. Click **Create SoD Approval** to create an exemption from the report. The exemption is created as type **Cross Role Exemption**. | +| User Role Test Violation Detailed | List with User Role Name link, SoD Violation, Base Permissions, Conflicting Permissions, User Role link and SoD Rule data. Report can be sorted, filtered, and exported to Excel. Click **Create SoD Approval** to create an exemption from the report. The exemption is created as type **Role Exemption**. | +| Employee Test Violation Detailed | List with Employee Name link, SoD Violation, Non-compliant Roles, Non-compliant Global Permissions, Base Permissions, Conflicting Permissions and SoD Rule data. Report can be sorted, filtered, and exported to Excel. Click **Create SoD Approval** to create an exemption from the report. The exemption is created as type **Cross Role Exemption**. | diff --git a/docs/platgovnetsuite/sod/sod_test_case_scenarios.md b/docs/platgovnetsuite/sod/sod_test_case_scenarios.md index 720ed3d610..d799db314f 100644 --- a/docs/platgovnetsuite/sod/sod_test_case_scenarios.md +++ b/docs/platgovnetsuite/sod/sod_test_case_scenarios.md @@ -19,7 +19,7 @@ Here are test case scenarios for SoD rules: **SoD Rules** -Admin Role should not be assigned without second level approval and monitoring. +Admin Role shouldn't be assigned without second level approval and monitoring. **Process** @@ -36,7 +36,7 @@ To assign an administrator role to a user: **Result** If the SoD rule is violated, the change made will not be allowed and will be blocked right away. A -user should not be assigned an Administrator role unless there is a pre-approved change request. A +user shouldn't be assigned an Administrator role unless there is a pre-approved change request. A prompt violation message will be seen by the user trying to make the change. The user will not be able to proceed with the save action. @@ -44,7 +44,7 @@ able to proceed with the save action. SoD Rules -Users who have permission to create Sales Orders should not have the permission to Approve Sales +Users who have permission to create Sales Orders shouldn't have the permission to Approve Sales orders. Process @@ -71,8 +71,8 @@ If the SoD rule is violated, an SoD incident is logged and the user is prompted **SoD Rules** -Anyone who can create a journal should not be able to approve it. Users who have permission to -create sales orders should not have the permission to approve sales orders. +Anyone who can create a journal shouldn't be able to approve it. Users who have permission to +create sales orders shouldn't have the permission to approve sales orders. **Process** @@ -94,7 +94,7 @@ If the SoD rule is violated, an SoD incident is logged and the user is prompted **SoD Rules** -Anyone who can create a bill should not be able to approve it and should not reconcile. +Anyone who can create a bill shouldn't be able to approve it and shouldn't reconcile. **Process** @@ -143,7 +143,7 @@ To assign an administrator role: **Result** -1. The change made is NOT blocked. There would be NO SoD Violation pop-up. +1. The change made isn't blocked. There would be NO SoD Violation pop-up. 2. Employee now has the Administrator role. 3. The SoD Rule field in the Employee form is set to Cleared. 4. A Change Log is created, and is listed under the Resolved SoD Incidents list on the **Access** @@ -151,7 +151,7 @@ To assign an administrator role: Incidents**. 5. The Change Log has the following details: - - Change Log is compliant (**Noncompliance** checkbox is NOT checked) + - Change Log is compliant (**Noncompliance** checkbox isn't checked) - **SoD Rule** is Administrator assignment requires approval - The employee given the new Administrator role is set in the **Affected Employee** field - The pre approved Change Request is set in the **Related Change Request** field @@ -160,9 +160,9 @@ To assign an administrator role: **SoD Rules** -Anyone who can create a journal should not be able to approve it. +Anyone who can create a journal shouldn't be able to approve it. -Anyone entering customer orders cannot approve or process it. +Anyone entering customer orders can't approve or process it. **Process** diff --git a/docs/platgovnetsuite/sod/sod_testing.md b/docs/platgovnetsuite/sod/sod_testing.md index 7ca43e8487..6520974cd3 100644 --- a/docs/platgovnetsuite/sod/sod_testing.md +++ b/docs/platgovnetsuite/sod/sod_testing.md @@ -29,13 +29,13 @@ Any of these events require a role to be re-evaluated: **Trigger Role Job** -- Anytime Role(s) are added/updated +- Anytime Roles are added/updated - Anytime the Rules are added/updated - Manual trigger on the Role **Trigger Role Assignment** -- Anytime Role(s) are added/updated +- Anytime Roles are added/updated - Anytime the Rules are added/updated - Anytime Role Assignments on an Employee are added/updated - Anytime Global Permissions are added/updated diff --git a/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md b/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md index c3fa2122d3..13fed657c2 100644 --- a/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md +++ b/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md @@ -6,11 +6,11 @@ sidebar_position: 40 # Integration API -The Integration API enables external access to Customization and Change Request objects. Third party -application are able to integrate via these APIs. +The Integration API provides external access to Customization and Change Request objects. Third party +applications can integrate via these APIs. - **Customizations** -- **Change Requests** can be created, updated, retrieved and deleted. +- **Change Requests** can be created, updated, retrieved, and deleted. - **ERD** and **Impact Analysis** tools are available. - [Customizations API](/docs/platgovnetsuite/ticketingintegrations/apioverview/customizationsapi/customizations_api.md) can be retrieved from your NetSuite account and can be @@ -18,7 +18,7 @@ application are able to integrate via these APIs. - [Get Customizations](/docs/platgovnetsuite/ticketingintegrations/apioverview/customizationsapi/get_customizations.md): Returns customizations based on your filters. -- [Change Request API](/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/change_request_api.md) can be created, updated, retrieved and deleted. The +- [Change Request API](/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/change_request_api.md) can be created, updated, retrieved, and deleted. The ERD and Impact Analysis tools are available. Here are the Change Request API commands: - [Get Change Request](/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_change_request.md): Returns the change request associated with an diff --git a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/add_update_change_request.md b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/add_update_change_request.md index 0b0adb8c61..d334b28d10 100644 --- a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/add_update_change_request.md +++ b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/add_update_change_request.md @@ -132,9 +132,9 @@ request(for duplicate additions/updates). **Message** -**"Unable to load Change Request. External ID: xxxx"**: There is an error with the change request. +**"Uncan load Change Request. External ID: xxxx"**: There is an error with the change request. -**"Change Request update prohibited. Change Request status is xxxx"**: The change request can not be +**"Change Request update prohibited. Change Request status is xxxx"**: The change request can't be modified because of the current status. Error messages are returned if any exceptions are encountered. diff --git a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/delete_customizations_change_request.md b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/delete_customizations_change_request.md index 9392fc1217..406d7153c7 100644 --- a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/delete_customizations_change_request.md +++ b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/delete_customizations_change_request.md @@ -132,9 +132,9 @@ request(for duplicate deletions). **Message** -**"Unable to load Change Request. External ID: xxxx"**: There is an error with the change request. +**"Uncan load Change Request. External ID: xxxx"**: There is an error with the change request. -**"Change Request update prohibited. Change Request status is xxxx"**: The change request can not be +**"Change Request update prohibited. Change Request status is xxxx"**: The change request can't be modified because of the current status. Error messages are returned if any exceptions are encountered. diff --git a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_change_request.md b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_change_request.md index 97650c30d5..84cbacf006 100644 --- a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_change_request.md +++ b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_change_request.md @@ -194,7 +194,7 @@ associated ERD links. **Message** -**"Unable to load Change Request. External ID: xxxx"**: There is an error with the change request. +**"Uncan load Change Request. External ID: xxxx"**: There is an error with the change request. Error messages are returned if any exceptions are encountered. diff --git a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_erd.md b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_erd.md index d853c7e805..34e851d1d7 100644 --- a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_erd.md +++ b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_erd.md @@ -101,7 +101,7 @@ links. **Message** -**"Unable to load Change Request. External ID: xxxx"**: There is an error with the change request. +**"Uncan load Change Request. External ID: xxxx"**: There is an error with the change request. Error messages are returned if any exceptions are encountered. diff --git a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_impact_analysis.md b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_impact_analysis.md index e70bc073e5..3003dc0151 100644 --- a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_impact_analysis.md +++ b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_impact_analysis.md @@ -150,13 +150,13 @@ Returns a JSON format string. customizations attached to the change request. **"No Impact Analysis detected."**: No impact analysis detected, either no customizations attached or -the attached customizations do not have impact analysis data available. +the attached customizations don't have impact analysis data available. ### Error Messages **Message** -**"Unable to load Impact Analysis. External ID: xxxx"**: There is an error with the change request. +**"Uncan load Impact Analysis. External ID: xxxx"**: There is an error with the change request. Error messages are returned if any exceptions are encountered. diff --git a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/push_change_request.md b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/push_change_request.md index 32332f680d..aa8f73d8d9 100644 --- a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/push_change_request.md +++ b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/push_change_request.md @@ -227,7 +227,7 @@ Returns a JSON format string. **Message** -**"Unable to load Change Request. External ID: xxxx"**: There is an error with the change request. +**"Uncan load Change Request. External ID: xxxx"**: There is an error with the change request. Error messages are returned if any exceptions are encountered. diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md index 16504ebd99..ab0ee7772d 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md @@ -6,21 +6,21 @@ sidebar_position: 4 # Jira Forge FAQs and Basic Troubleshooting -This section will discuss frequently asked questions and basic troubleshooting for Platform Governance's Jira Forge app. +This section covers frequently asked questions and basic troubleshooting for Platform Governance's Jira Forge app. -1. I already have Strongpoint Connect app installed in my instance. Is it okay to install the Forge app as well? - - **Yes**, it is perfectly okay to install the Forge app even though you currently have the Connect app. They should not cause any conflicts during installation and during using either one of them or both of them at the same time. +1. The Strongpoint Connect app is already installed. Can the Forge app be installed alongside it? + - **Yes**, it is fine to install the Forge app even though the Connect app is installed. They shouldn't cause any conflicts during installation or while using either app or both at the same time. -2. What will happen to the data in Netwrix Settings page in Connect app once I have installed the Forge app? - - Data in the Netwrix Settings page in Connect app does not get migrated to the Netwrix NetSuite Settings page in the Forge app. Since these are 2 different implementation/apps, you will have to manually migrate the Connect app data to Forge app. +2. What happens to the data in the Netwrix Settings page in Connect app after the Forge app is installed? + - Data in the Netwrix Settings page in Connect app doesn't get migrated to the Netwrix NetSuite Settings page in the Forge app. Since these are 2 different implementations/apps, the Connect app data must be manually migrated to Forge app. -3. Is it normal that I see two (2), Netwrix NetSuite tabs in my issues panel if my instance has both Connect and Forge apps? +3. Is it normal to see two (2) Netwrix NetSuite tabs in the issues panel when both Connect and Forge apps are installed? - **Yes**, it is normal. Two (2) separate apps have separate file descriptors that show separate tabs in the issue panel. -4. Why did all my data in Netwrix NetSuite Settings page in Forge app disappear when I updated to a new version? - - This is Atlassian's way of securing your data, every install or update is a fresh start. However, there are 2 ways to retrieve your data: (1) You will have to raise a ticket to Atlassian support to restore the data in your instance when the Jira Forge app was installed or updated. (2) You can manually input them back yourself. +4. Why did all the data in the Netwrix NetSuite Settings page in the Forge app disappear after updating to a new version? + - This is Atlassian's way of securing data. Every install or update is a fresh start. However, there are 2 ways to retrieve the data: (1) Raise a ticket to Atlassian support to restore the data in the instance for when the Jira Forge app was installed or updated. (2) Manually re-enter the data. -5. Is there impact to existing connect tickets if forge is being used? - - **No**. Since the change request information is being pulled from the NetSuite account that Jira Forge is currently connected to, there should be no impact when switching to the Forge app. +5. Is there impact to existing Connect tickets if Forge is being used? + - **No**. Since the change request information is being pulled from the NetSuite account that Jira Forge is connected to, there should be no impact when switching to the Forge app. **Back to:** [Jira Forge Walkthrough Example](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough) diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_integration.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_integration.md index 275b7ec159..50216cfc63 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_integration.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_integration.md @@ -6,7 +6,7 @@ sidebar_position: 1 # Jira Forge -Platform Governance for NetSuite's Change Management capabilities are integrated with Jira, one of the most popular issue ticketing and development project management systems. Customers are able to look for and include NetSuite Customizations, assess impacts for requested changes, and push Jira change tickets into a Change Request. This enables easy management of changes, seamless tracking of compliant changes and automating the reconciliation of change logs during an audit. +Platform Governance for NetSuite's Change Management capabilities are integrated with Jira, one of the most popular issue ticketing and development project management systems. Customers can look for and include NetSuite Customizations, assess impacts for requested changes, and push Jira change tickets into a Change Request. This enables easy management of changes, seamless tracking of compliant changes, and automating the reconciliation of change logs during an audit. ## Integration Overview @@ -16,9 +16,9 @@ Platform Governance for NetSuite's Change Management capabilities are integrated ### Features and Benefits -With Platform Governance for NetSuite's integration of NetSuite and Jira (Cloud), you can use the Jira tool while we automatically add and track the associated changes in your NetSuite account. The integration eliminates the need for double entry in the two systems. +With Platform Governance for NetSuite's integration of NetSuite and Jira (Cloud), you can use the Jira tool while Platform Governance for NetSuite automatically adds and tracks the associated changes in your NetSuite account. The integration eliminates the need for double entry in the two systems. -Jira Integration uses the latest Atlassian Forge implementation which provides enhanced security, ensuring data does not leave the ecosystem and adheres to strict security standards (SOC2, ISO/IEC 27001). +Jira Integration uses the latest Atlassian Forge implementation which provides enhanced security, ensuring data doesn't leave the ecosystem and adheres to strict security standards (SOC2, ISO/IEC 27001). The Jira Forge integration automatically syncs Jira tickets with a NetSuite change request: @@ -37,9 +37,9 @@ Change Managers and System Administrators quickly realize the integration benefi ### Technical Considerations -Review these considerations prior to deploying the Jira integration: +Review these considerations before deploying the Jira integration: -1. Platform Governance for NetSuite integration is implemented as a Forge app. It can be enabled or disabled based on configuration and runs independently of other scripts, ensuring it does not interfere with existing processes. +1. Platform Governance for NetSuite integration is implemented as a Forge app. It can be enabled or disabled based on configuration and runs independently of other scripts, ensuring it doesn't interfere with existing processes. 2. All functions are self-executing, complying with Atlassian Jira Forge's best practices. 3. No DOM manipulation or global scripts are deployed. 4. No external libraries are needed. It is plain JavaScript. diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md index 79815682fc..17352987d2 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md @@ -25,15 +25,17 @@ Netwrix Platform Governance(Strongpoint) bundle is a key prerequisite for Jira F For installation details you may refer to the installation guide found in [Installing Platform Governance for NetSuite](/docs/platgovnetsuite/installation/installing_strongpoint). -#### NOTE: +:::note If the latest version of the bundle is already installed, you may skip this part. +::: ### Install the latest Netwrix Platform Governance Jira bundle -This step will require a user to have NetSuite account access and an Administrator role for that account. This bundle must be version **2.0** or higher to work properly. The Netwrix Platform Governance Jira bundle is a non-managed bundle, please check the [Community](https://community.netwrix.com/c/products/platform-governance-netsuite/181) regularly for the latest updates and announcements. +This step will require a user to have NetSuite account access and an Administrator role for that account. This bundle must be version **2.0** or higher to work properly. The Netwrix Platform Governance Jira bundle is a non-managed bundle, check the [Community](https://community.netwrix.com/c/products/platform-governance-netsuite/181) regularly for the latest updates and announcements. -#### NOTE: +:::note If the latest version of the bundle is already installed, you may skip this part. +::: 1. Log in to the NetSuite account and navigate to Search & Install Bundles page. - In the Dashboard main menu: **Customization > SuiteBundler > Search & Install Bundles** @@ -42,7 +44,7 @@ If the latest version of the bundle is already installed, you may skip this part ![Jira Forge Bundle Search](/images/platgovnetsuite/integrations/jira_forge_jira_bundle_search.webp) -3. Click on Netwrix Platform Governance Jira bundle in the search results. +3. Click Netwrix Platform Governance Jira bundle in the search results. 4. Click Install when the Bundle Details opens. 5. Click Install Bundle on the Preview Bundle Install page. @@ -80,12 +82,13 @@ This step will require a user to have NetSuite account access and an Administrat Token Based Authentication is set up through NetSuite. Here is the basic process: -1. NetSuite Administrator creates an Integration Record for the Platform Governance for NetSuite application. This only needs to be performed once per account. Open **Setup > Integration > Integration Management > Manage Integrations > New**. For more information, refer to the NetSuite help article Create Integration Records for Applications to Use TBA. To view a list of integration records in this account, open **Setup > Integration > Integration Management > Manage Integrations**. +1. NetSuite Administrator creates an Integration Record for the Platform Governance for NetSuite application. This only needs to be performed once per account. Open **Setup > Integration > Integration Management > Manage Integrations > New**. See the NetSuite help article "Create Integration Records for Applications to Use TBA" for details. To view a list of integration records in this account, open **Setup > Integration > Integration Management > Manage Integrations**. - #### NOTE: - Please take note and keep these values to yourself. + :::note + Take note of these values and keep them secure. + ::: -2. Each user creates their token in NetSuite. Refer to the NetSuite help Manage TBA Tokens in the NetSuite UI for details. Once you have created your tokens, add them to Jira. +2. Each user creates their token in NetSuite. Refer to the NetSuite help Manage TBA Tokens in the NetSuite UI for details. After you have created your tokens, add them to Jira. 3. Create an Access Token by navigating to main menu, **Setup > Users/Roles > Access Tokens > New**. 4. Fill the fields with the following values: - Application Name: The Integration Record that was created in Step 1. @@ -95,31 +98,32 @@ Token Based Authentication is set up through NetSuite. Here is the basic process - Skip checking Inactive checkbox 5. Click 'Save'. - #### NOTE: + :::note You can also create a Token Based Authentication for your NetSuite Administrator role. Follow the steps below: - 1. Login as an **Administrator** role in NetSuite. - 2. In your NetSuite account dashboard, navigate to the bottom left part of the page. Under **Settings**, you should see **Manage Access Tokens** and be able to click the link. + 1. Log in as an **Administrator** role in NetSuite. + 2. In your NetSuite account dashboard, navigate to the bottom left part of the page. Under **Settings**, you should see **Manage Access Tokens**. Click the link. ![Jira Forge NetSuite Admin TBA](/images/platgovnetsuite/integrations/jira_forge_netsuite_tba_admin.webp) - 3. You should be redirected to **My Access Tokens** page. Click the **New My Access Token** button, this allows you to create a TBA record for your Administrator role. - 4. Select an Application Name(Integration record) for this token. + 3. On the **My Access Tokens** page, click the **New My Access Token** button to create a TBA record for your Administrator role. + 4. Select an Application Name (Integration record) for this token. 5. Click **Save**. - **IMPORTANT:** Please take note and keep these values to yourself. + **IMPORTANT:** Take note of these values and keep them secure. + ::: ### Set up Jira Credentials This step will require a user to have Jira instance access and a user to have NetSuite account access. 1. Create a Jira token via this URL: https://id.atlassian.com/manage-profile/security/api-tokens - - Take note of the token value as this will be associated with your email address that is used to login to the Atlassian/Jira ecosystem. Refer to the Atlassian documentation to obtain a Token. + - Take note of the token value as this will be associated with your email address that is used to log in to the Atlassian/Jira ecosystem. Refer to the Atlassian documentation to obtain a Token. 2. In this step, you should have the following credentials on hand - Jira user email address - Jira token generated above. 3. In NetSuite, go to Netwrix Configuration and Stats by navigating in the main menu, **Netwrix > Netwrix Support > Installation Settings**. There should only be **ONE(1)** record displayed. Click 'Edit' and it should open the Configuration and Stats page. -4. Click 'Jira Integration' tab. You should be able to see a number of fields. Turn your attention to Jira User and Jira Token fields. +4. Click 'Jira Integration' tab. You should be can see a number of fields. Turn your attention to Jira User and Jira Token fields. 5. Populate these fields with the following values: - Jira User - Jira user email address in step 2. - Jira token - Jira token generated in step 1. @@ -127,7 +131,7 @@ Click 'Save'. ### Set up Jira Status Mapping -To take advantage of the automatic synchronization feature, we recommend reviewing your Jira statuses to be mapped to the Change Management statuses. When a ticket status is updated to a mapped status, Platform Governance for NetSuite handles the synchronization between Jira and NetSuite. +To take advantage of the automatic synchronization feature, review your Jira statuses to be mapped to the Change Management statuses. When a ticket status is updated to a mapped status, Platform Governance for NetSuite handles the synchronization between Jira and NetSuite. The mapping allows multiple Jira statuses to map to each Change Request status. The mapping is part of the Configure NetSuite and Jira procedure. @@ -136,7 +140,7 @@ Refer to the Atlassian documentation for instructions on 1. In NetSuite, go to Netwrix Configuration and Stats by navigating in the main menu, **Netwrix > Netwrix Support > Installation Settings**. There should only be **ONE(1)** record displayed. Click 'Edit' and it should open the Configuration and Stats page. -Enter the mappings between your Jira statuses and the Change Request statuses. For best practice, define your Jira statuses prior to this step. You can enter multiple Jira statuses for each Change Request status, separated by commas. For example, Ready for Deployment,Done. Assign your relevant mapping for each of the Change Request statuses: +Enter the mappings between your Jira statuses and the Change Request statuses. For best practice, define your Jira statuses before this step. You can enter multiple Jira statuses for each Change Request status, separated by commas. For example, Ready for Deployment,Done. Assign your relevant mapping for each of the Change Request statuses: **Jira Statuses for In Progress Status** @@ -150,9 +154,9 @@ Enter the mappings between your Jira statuses and the Change Request statuses. F **Jira Statuses for Canceled Status** -2. Check Automatic Synchronization to enable Platform Governance for NetSuite to handle the synchronization between Jira and NetSuite when a Ticket status is updated to a mapped status, without having to click Push. If you are using an account where you do not want to create a Change Request, leave this unchecked so you can do your research or testing without generating Change Requests. +2. Check Automatic Synchronization to enable Platform Governance for NetSuite to handle the synchronization between Jira and NetSuite when a Ticket status is updated to a mapped status, without having to click Push. If you are using an account where you don't want to create a Change Request, leave this unchecked so you can do your research or testing without generating Change Requests. -3. Check Allow NS to Jira Push to enable pushing NetSuite change requests into Jira. Otherwise, you can leave it as unchecked if you do not need to enable this feature. +3. Check Allow NS to Jira Push to enable pushing NetSuite change requests into Jira. Otherwise, you can leave it as unchecked if you don't need to enable this feature. Click 'Save' @@ -207,7 +211,7 @@ This step will require a user to have Jira instance access where Netwrix Platfor 5. Click 'Create' and the newly added/created TBA record should be listed in the page. -Additionally, 'Update' and 'Delete' buttons are found on the right part of your record. These buttons allow you to update or delete the record, respectively. +Additionally, 'Update' and 'Delete' buttons are found on the right part of your record. Use these buttons to update or delete the record, respectively. ![Jira Forge Netwrix NetSuite Settings TBA List](/images/platgovnetsuite/integrations/jira_forge_tba_list.webp) diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md index a521ab1e06..f9307d345c 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md @@ -6,9 +6,9 @@ sidebar_position: 3 # Jira Forge Walkthrough -If you have reached this part it means that you have completed ALL prerequisites found in the Jira Forge Setup page. If NOT, please go through the setup steps for a smooth walkthrough of the integration's features. +If you have reached this part it means that you have completed ALL prerequisites found in the Jira Forge Setup page. If NOT, go through the setup steps for a smooth walkthrough of the integration's features. -This walkthrough is one example based on our test account. You must install and configure the Jira integration, including setting up the Jira Statuses prior to using this walkthrough. +This walkthrough is one example based on a test account. You must install and configure the Jira integration, including setting up the Jira Statuses before using this walkthrough. ### The walkthrough demonstrates these steps: @@ -23,18 +23,18 @@ This walkthrough is one example based on our test account. You must install and - Other notable features ### Create a Jira Ticket -1. Login to your Jira account. +1. Log in to your Jira account. 2. Open a Project. 3. Click Create (+). 4. Fill the necessary fields and Click 'Create' ### Logging In and Connecting to a NetSuite Account -Before proceeding to this step, make sure you already have created a TBA record. If not please see [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. +Before proceeding to this step, ensure you already have created a TBA record. If not see [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. 1. In your issue ticket, you should see the 'Netwrix NetSuite Forge' tab in the issues tab. Click the tab. Two possible displays: - 1. If you have NOT executed [Set up Jira Project Keys](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-project-keys) in the Setup Page, you will see this message displayed "Only projects defined in the Netwrix Settings page can use this integration". Please check if you have done that part. + 1. If you have NOT executed [Set up Jira Project Keys](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-project-keys) in the Setup Page, you will see this message displayed "Only projects defined in the Netwrix Settings page can use this integration". check if you have done that part. ![Jira Forge Issue No Project Key](/images/platgovnetsuite/integrations/jira_forge_issue_no_project_key.webp) @@ -44,14 +44,14 @@ Before proceeding to this step, make sure you already have created a TBA record. ![Jira Forge Issue Connect Form](/images/platgovnetsuite/integrations/jira_forge_issue_connect_form.webp) -2. If you are seeing the connect fields, you are in the right track. Please select a NetSuite account to connect to. -3. Upon selecting an account, the app loads. It is establishing the initial connection process. Once it is successful, the "Connect" button below should be enabled. Otherwise, please double check the TBA credentials that you have entered in [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. +2. If you are seeing the connect fields, you are on the right track. Select a NetSuite account to connect to. +3. Upon selecting an account, the app loads. It is establishing the initial connection process. After it succeeds, the "Connect" button below should be enabled. Otherwise, double check the TBA credentials that you have entered in [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. ![Jira Forge Issue Connect Form Successful](/images/platgovnetsuite/integrations/jira_forge_issue_connect_form_successful.webp) 4. Click "Connect" button. -5. You should see the ITGC Form for our Jira app. Change Request data is loaded, it also shows which account where you are currently connected. +5. You should see the ITGC Form for the Jira app. Change Request data is loaded, it also shows which account where the app is connected. ![Jira Forge Issue Connect Form Successful ITGC](/images/platgovnetsuite/integrations/jira_forge_connect_itgc_form.webp) @@ -77,7 +77,7 @@ Available filters: ![Jira Forge Lookup Customization Modal](/images/platgovnetsuite/integrations/jira_forge_lookup_customization_modal.webp) -2. Choose a filter to narrow down the selection of customizations. In this case, we will use the Name filter. Click the "Lookup" button. +2. Choose a filter to narrow down the selection of customizations. Use the Name filter. Click the "Lookup" button. ![Jira Forge Lookup Customization Modal Name Filter](/images/platgovnetsuite/integrations/jira_forge_lookup_name_filter.webp) @@ -100,7 +100,7 @@ Available filters: ![Jira Forge Proposed Customization Modal](/images/platgovnetsuite/integrations/jira_forge_proposed_customization_modal.webp) -5. Select the Type for your proposed customization. In this case, we will select "Body Field" type. Notice that the Script ID/Name field is prepopulated with the prefix of the script ID, this allows the user ease of use and not mistakenly input the wrong script ID prefix for the type. Type the script ID of your choice. +5. Select the Type for your proposed customization. Select the "Body Field" type. Notice that the Script ID/Name field is prepopulated with the prefix of the script ID, this prevents accidentally entering the wrong script ID prefix for the type. Enter the script ID of your choice. ![Jira Forge Proposed Customization Input](/images/platgovnetsuite/integrations/jira_forge_add_proposed_wth_input.webp) @@ -135,7 +135,7 @@ Below shows the existing and proposed customizations that were added in steps 1 ![Jira Forge Remove Customizations Flag Success](/images/platgovnetsuite/integrations/jira_forge_remove_customization_successful.webp) -If you have reached this section, you were able to execute the following: +If you have reached this section, you were can execute the following: - Use the Lookup customization filter - Add existing and proposed customizations - Delete/remove a customization @@ -166,9 +166,9 @@ To use import feature follow the steps below: 3. Click the "Import Customizations" button. You will see a flag message at the lower left side of your screen indicating that the importing process is In Progress. -4. Once the importing is successful, all valid objects will populate the Customization and Proposed Customization tables accordingly. You will also see a flag message indicating the importing process is successful. +4. After the importing is successful, all valid objects will populate the Customization and Proposed Customization tables accordingly. You will also see a flag message indicating the importing process is successful. -If you have reached this section, you were able to execute the following: +If you have reached this section, you were can execute the following: - Use the Import Customization feature and add customizations in bulk. ### Perform Risk Assessment @@ -186,12 +186,12 @@ To use Impact Analysis follow the steps below: ![Jira Forge Impact Analysis Calculating](/images/platgovnetsuite/integrations/jira_forge_calculating_impact_analysis.webp) -3. The modal populates with objects that are impacted. They are categorized as **Can Be Safely Deleted or Modified**, **Cannot Be Safely Deleted or Modified** and **Inactive Customizations (Already Deleted)**. Objects under the **Cannot Be Safely Deleted or Modified** will also show the Impacted Customizations. +3. The modal populates with objects that are impacted. They are categorized as **Can Be Safely Deleted or Modified**, **Can't Be Safely Deleted or Modified** and **Inactive Customizations (Already Deleted)**. Objects under the **Can't Be Safely Deleted or Modified** will also show the Impacted Customizations. ![Jira Forge Impact Analysis Data](/images/platgovnetsuite/integrations/jira_forge_impact_analysis.webp) -If you have reached this section, you were able to execute the following: +If you have reached this section, you were can execute the following: - Perform an impact analysis on the customization that are add/attached to the Jira ticket change request. ### View Entity Relation Diagram @@ -220,16 +220,16 @@ To use ERD follow the steps below: ![Jira Forge ERD Data NetSuite](/images/platgovnetsuite/integrations/jira_forge_sample_erd.webp) -If you have reached this section, you were able to execute the following: +If you have reached this section, you were can execute the following: - View the entity relation diagram of the customization that is add/attached to the Jira ticket change request. ### Ready for Development -Once you have resolved any risk or conflicts, your changes are ready for development: +After you have resolved any risk or conflicts, your changes are ready for development: 1. Change the Jira status of your ticket to match the status set up for Jira Statuses for Pending Approval Status. For example, Selected for Development. -2. Click Push if you are not using Automatic Synchronization to push status changes. A confirmation your Change Request was Created/Updated is displayed. +2. Click Push if you aren't using Automatic Synchronization to push status changes. A confirmation your Change Request was Created/Updated is displayed. - Below shows the "Push" button. @@ -251,7 +251,7 @@ Once you have resolved any risk or conflicts, your changes are ready for develop ![Jira Forge Change Request Pending Approval](/images/platgovnetsuite/integrations/jira_forge_change_request_pending_approval_status.webp) -If you have reached this section, you were able to execute the following: +If you have reached this section, you were can execute the following: - Push a change request from a Jira ticket. - See the change request status from Jira. @@ -264,9 +264,9 @@ When development is done, and the Change Request is approved according to your p ![Jira Forge Change Request Approved](/images/platgovnetsuite/integrations/jira_forge_approved_cr_status.webp) -2. Change the Jira status of your ticket to match the status set up for Jira Statuses for Approved Status. In our example set up, we have two possible statuses: Ready for Deployment and Done. Setting up two statuses enables you to split up the deployment and the ticket closure if you want to monitor the deployment task separately. Both statuses are valid for Deployment, but only Done closes the Jira ticket and updates the Change Request to Completed. +2. Change the Jira status of your ticket to match the status set up for Jira Statuses for Approved Status. In this example, there are two possible statuses: Ready for Deployment and Done. Two statuses let you split the deployment and the ticket closure if you want to monitor the deployment task separately. Both statuses are valid for Deployment, but only Done closes the Jira ticket and updates the Change Request to Completed. -3. Click Push if you are not using Automatic Synchronization to push status changes. A confirmation your Change Request was Created/Updated is displayed. +3. Click Push if you aren't using Automatic Synchronization to push status changes. A confirmation your Change Request was Created/Updated is displayed. - Below shows a flag with a message that the action is in progress. @@ -279,7 +279,7 @@ When development is done, and the Change Request is approved according to your p 4. If you used Ready for Deployment, update your Jira status to Done once your deployment and verification activities are complete. -If you have reached this section, you were able to execute the following: +If you have reached this section, you were can execute the following: - Push a change request from a Jira ticket. - See the Approved change request status from Jira. @@ -300,9 +300,9 @@ If you have reached this section, you were able to execute the following: ### Other notable features -These are the other features whose actions are not that commonly used but are of equal importance in the integration app. +These are the other features whose actions aren't that commonly used but are of equal importance in the integration app. -1. **Add Bundle ID** - The **+** button beside the Affected Bundle ID field. User will be able to add NetSuite bundle IDs to the change request. You can add one bundle ID at a time for this action. It is only an add functionality, removing a bundle ID in the change request would require the user to contact a NetSuite Administrator or user for this action. +1. **Add Bundle ID** - The **+** button beside the Affected Bundle ID field. User will be can add NetSuite bundle IDs to the change request. You can add one bundle ID at a time for this action. It is only an add functionality, removing a bundle ID in the change request would require the user to contact a NetSuite Administrator or user for this action. ![Jira Forge Add Bundle Button](/images/platgovnetsuite/integrations/jira_forge_add_bundle_button.webp) @@ -320,7 +320,7 @@ These are the other features whose actions are not that commonly used but are of ![Jira Forge Push External Modal](/images/platgovnetsuite/integrations/jira_forge_push_external_modal.webp) -3. **Settings** - The Settings is a drop-down button, allows the user to switch NetSuite accounts to connect to. When "Settings" button is clicked, a "Change Account" option is shown. When the user clicks "Change Account", the session is disconnected and the connection to a NetSuite account stopped. The connection form is then shown to allow the user to connect to another NetSuite account. +3. **Settings** - The Settings is a dropdown button, allows the user to switch NetSuite accounts to connect to. When "Settings" button is clicked, a "Change Account" option is shown. When the user clicks "Change Account", the session is disconnected and the connection to a NetSuite account stopped. The connection form is then shown to allow the user to connect to another NetSuite account. ![Jira Forge Settings Button](/images/platgovnetsuite/integrations/jira_forge_settings_change_account.webp) diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md index eff630446b..4bca3f9435 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md @@ -7,7 +7,7 @@ sidebar_position: 10 # Jira Platform Governance for NetSuite's Change Management capabilities are integrated with Jira, one of -the most popular issue ticketing and development project management systems. Customers are able to +the most popular issue ticketing and development project management systems. Customers can look for and include NetSuite Customizations, assess impacts for requested changes, and push Jira change tickets into a Change Request. This enables easy management of changes, seamless tracking of compliant changes and automating the reconciliation of change logs during an audit. @@ -21,7 +21,7 @@ compliant changes and automating the reconciliation of change logs during an aud ### Features and Benefits With Platform Governance for NetSuite's integration of NetSuite and Jira (Cloud), you can use the -Jira tool while we automatically add and track the associated changes in your NetSuite account. The +Jira tool while Platform Governance for NetSuite automatically adds and tracks the associated changes in your NetSuite account. The integration eliminates the need for double entry in the two systems. The Jira integration automatically syncs Jira tickets with NetSuite change request: @@ -41,7 +41,7 @@ Change Managers and System Administrators quickly realize the integration benefi ### Technical Considerations -Review these considerations prior to deploying the Jira integration: +Review these considerations before deploying the Jira integration: 1. Platform Governance for NetSuite's integration is a client script that can be enabled or disabled by form, user, or role. It has high order value to ensure it is the last thing to run and does @@ -67,7 +67,7 @@ To set up the Strongpoint Jira integration: ### Review Your Jira Statuses -To take advantage of the automatic synchronization feature, we recommend reviewing your Jira +To take advantage of the automatic synchronization feature, review your Jira statuses to be mapped to the Change Management statuses. When a ticket status is updated to a mapped status, Platform Governance for NetSuite handles the synchronization between Jira and NetSuite. @@ -81,7 +81,7 @@ Refer to the Atlassian documentation for instructions on 1. Open **Customization** > **SuiteBundler** > **Search & Install Bundles** 2. Search for bundle **311231** -3. Click on **StrongPoint Jira integration Client Side** in the search results. +3. Click **StrongPoint Jira integration Client Side** in the search results. 4. Click **Install** when the Bundle Details opens. 5. Click **Install Bundle** on the **Preview Bundle** Install page. @@ -94,7 +94,7 @@ Refer to the Atlassian documentation for instructions on [Atlassian documentation](https://confluence.atlassian.com/cloud/api-tokens-938839638.html) to obtain a Token 5. Enter the mappings between your Jira statuses and the Change Request statuses. For best practice, - define your Jira statuses prior to this step. You can enter multiple Jira statuses for each + define your Jira statuses before this step. You can enter multiple Jira statuses for each Change Request status, separated by commas. For example, **Ready for Deployment,Done**. Assign your mapping for each of the Change Request statuses: @@ -107,7 +107,7 @@ Refer to the Atlassian documentation for instructions on 6. Check **Automatic Synchronization** to enable Platform Governance for NetSuite to handle the synchronization between Jira and NetSuite when a Ticket status is updated to a mapped status. - without having to click **Push**. If you are using an account where you do not want to create a + without having to click **Push**. If you are using an account where you don't want to create a Change Request, leave this unchecked so you can do your research or testing without generating Change Requests. @@ -135,7 +135,7 @@ Refer to the Atlassian documentation for instructions on ![Jira Search.](/images/platgovnetsuite/integrations/jira_search.webp) -3. Click on the **Strongpoint for NetSuite** tile to open the details and follow the installation +3. Click the **Strongpoint for NetSuite** tile to open the details and follow the installation prompts. ### Create an Integration User Account (optional) @@ -159,7 +159,7 @@ Token Based Authentication is set up through NetSuite. Here is the basic process **Integration Management** > **Manage Integrations**. 2. Each user creates their token in NetSuite. Refer to the [NetSuite help Manage TBA Tokens in the NetSuite UI](https://netsuite.custhelp.com/app/answers/detail/a_id/41902) - for details. Once you have created your tokens, add them to Jira. + for details. After you have created your tokens, add them to Jira. 3. Open **Jira**. 4. Open your **Projects** page: @@ -187,8 +187,8 @@ This process is performed by the Jira Administrator. 2. Select **Strongpoint NetSuite** activity tab. Select a NetSuite account to connect to. 3. Add customization/s(existing or proposed) to the Jira ticket: - - Two ways to add: (a.) Click on **Lookup Customization** or **Proposed Customization** to - narrow down customizations to attach. (b.) Click on **Import Customization** , add + - Two ways to add: (a.) Click **Lookup Customization** or **Proposed Customization** to + narrow down customizations to attach. (b.) Click **Import Customization** , add customizations in bulk from a file. File format accepted are XML and ZIP files. File contents for XML should have the same format as the MANIFEST.xml file in the SDF Project. SDF zip format uses the SDF structure as extracted from an existing SDF project. diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_upload_addon_not_showing.md b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_upload_addon_not_showing.md index 97e369effb..cf7338116c 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_upload_addon_not_showing.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_upload_addon_not_showing.md @@ -6,7 +6,7 @@ sidebar_position: 30 # Jira Upload Add On Not Showing -If the Upload add on is not shown on your screen, you are either not a Jira administrator or you +If the Upload add on isn't shown on your screen, you are either not a Jira administrator or you have not checked **Enable development mode**. To enable development mode: diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_walkthrough_example.md b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_walkthrough_example.md index 162981a559..269875e20c 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_walkthrough_example.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_walkthrough_example.md @@ -6,9 +6,9 @@ sidebar_position: 10 # Jira Walkthrough Example -This walkthrough is one example based on our test account. You must +This walkthrough is one example based on a test account. You must [install and configure](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) the Jira integration, including setting up the -**[Jira Statuses](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md)** prior to using this walkthrough. +**[Jira Statuses](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md)** before using this walkthrough. The walkthrough demonstrates these steps: @@ -21,7 +21,7 @@ The walkthrough demonstrates these steps: ## Create a Jira Ticket -1. Login to your Jira account. +1. Log in to your Jira account. 2. Open a Project. 3. Click **Create** (**+**). @@ -37,7 +37,7 @@ The walkthrough demonstrates these steps: 5. Click **Create**. :::note -Alerts and notifications may occur during this walkthrough, and are not included in these steps. For +Alerts and notifications may occur during this walkthrough, and aren't included in these steps. For example, override alert, notifications for approvers, and notification for the change request. ::: @@ -59,17 +59,17 @@ example, override alert, notifications for approvers, and notification for the c section). The **Synchronized with**status displays the account you are logged into for NetSuite. :::note -You cannot login if you do not have the **appropriate role permissions to create a Change Request**. +You can't log in if you don't have the **appropriate role permissions to create a Change Request**. ::: -If you do not enter the correct email or password, an error is displayed. After six unsuccessful +If you don't enter the correct email or password, an error is displayed. After six unsuccessful consecutive attempts to login, your account is suspended for 30 minutes. ![jira_example_credentials_error](/images/platgovnetsuite/integrations/jira_example_credentials_error.webp) ## Add Customizations -Once you have logged in, the form is displayed. +After you have logged in, the form is displayed. ![Jira Strongpoint form](/images/platgovnetsuite/release_notes/jira_strongpoint_form.webp) - **Synchronized with** displays the connected account. Click **Change Account** to switch to a @@ -93,7 +93,7 @@ Once you have logged in, the form is displayed. Customizations** list. You can delete added Customizations with the ![delete](/images/platgovnetsuite/integrations/delete.webp)icon. - **Push** creates the Change Request in NetSuite. **Push** is also used to manually update your - Change Request if you are not using the [Automatic Synchronization](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) feature. + Change Request if you aren't using the [Automatic Synchronization](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) feature. - **Push External** same as **Push** except you can specify a different Jira account. - **Impact Analysis** and **View ERD** are tools to Perform Risk Assessment. @@ -122,11 +122,11 @@ Once you have logged in, the form is displayed. ### Add Proposed Customizations -In this procedure, we are adding a new Customization. +In this procedure, this procedure adds a new Customization. 1. Enter a new, valid Script ID in the **Add Customizations** field. For this example, enter **customlist_customer_priorities**. -2. Click (**+**) to add it. If the Script ID is valid, and does not match an existing Script ID, the +2. Click (**+**) to add it. If the Script ID is valid, and doesn't match an existing Script ID, the new Customization is added to the **Proposed Customizations** list. ![Customization added to Proposed Customization list](/images/platgovnetsuite/integrations/jira_example_proposed_customization.webp) @@ -149,7 +149,7 @@ Strongpoint**. ### Import Customizations from Jira -In this procedure, we are adding customizations exported into an xml file. This is not required, but +In this procedure, this procedure adds customizations exported into an xml file. This isn't required, but is an alternative if you have a lot of customizations. 1. Click **Import Customization**. @@ -170,7 +170,7 @@ Analysis** to run the tool. Here is an example report: ![Impact analysis report](/images/platgovnetsuite/integrations/jira_example_impact_analysis.webp) -Before proceeding with your changes, review each warning to ensure your change does not break +Before proceeding with your changes, review each warning to ensure your change doesn't break something. Dependencies can easily be reviewed with the ERD tool. ### View ERD @@ -188,11 +188,11 @@ dependencies. ## Ready for Development -Once you have resolved any risk or conflicts, your changes are ready for development: +After you have resolved any risk or conflicts, your changes are ready for development: 1. Change the Jira status of your ticket to match the status set up for **Jira Statuses for Pending Approval Status**. For example, **Selected for Development**. -2. Click **Push** if you are not using [Automatic Synchronization](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) to push +2. Click **Push** if you aren't using [Automatic Synchronization](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) to push status changes. A confirmation your Change Request was Created/Updated is displayed. 3. Expand the **Change Request** field on the right. The status is now **Pending Approval**. There is a link to open the Change Request in NetSuite. @@ -211,11 +211,11 @@ ticket is ready to be updated. 1. Expand the **Change Request** field on the right. The status is **Approved**. ![Change Request is now Approved](/images/platgovnetsuite/integrations/jira_example_approved.webp) 2. Change the Jira status of your ticket to match the status set up for **Jira Statuses for Approved - Status**. In our example set up, we have two possible statuses: **Ready for Deployment** and - **Done**. Setting up two statuses enables you to split up the deployment and the ticket closure + Status**. In this example set up, there are two possible statuses: **Ready for Deployment** and + **Done**. Two statuses let you split up the deployment and the ticket closure if you want to monitor the deployment task separately. Both statuses are valid for Deployment, but only **Done** closes the Jira ticket and updates the Change Request to **Completed**. -3. Click **Push** if you are not using [Automatic Synchronization](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) to push +3. Click **Push** if you aren't using [Automatic Synchronization](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md) to push status changes. A confirmation your Change Request was Created/Updated is displayed. 4. If you used **Ready for Deployment**, update your Jira status to **Done** once your deployment and verification activities are complete. diff --git a/docs/platgovnetsuite/ticketingintegrations/process_issues.md b/docs/platgovnetsuite/ticketingintegrations/process_issues.md index 61ca15da0a..8be6c46c0d 100644 --- a/docs/platgovnetsuite/ticketingintegrations/process_issues.md +++ b/docs/platgovnetsuite/ticketingintegrations/process_issues.md @@ -31,16 +31,16 @@ continue to use that and reference the external ticket in the Change Request. A Unique **ID** is generated after the Process Issue is created. 4. Enter a meaningful **Name** for the Process Issue. 5. Select a **Parent Issue** if applicable. This field is used to group issues. You can either type - part of the name and press Tab, or use the drop down icon and select from a list. + part of the name and press Tab, or use the dropdown icon and select from a list. 6. Change the **Owner** if needed. 7. Select a **Type** for the issue. **Type** is used for sorting and organizing issues. You can set up types to trigger alerts to object owners and managers. You can use the predefined types or use **New** to create your own. Here are basic definitions: - - **Question**: question about a feature, function or process. + - **Question**: question about a feature, function, or process. - **Suggestion**: idea for improving functionality or process. - **Broken Process**: problem with a process, but not blocking productivity or performance. - - **Waste**: steps or work that is not necessary. + - **Waste**: steps or work that isn't necessary. - **Control Log**: An automatically created process if you have the **Strongpoint Controls** package. - **Script Error**: error within a script causing it not to function as expected. @@ -67,15 +67,15 @@ continue to use that and reference the external ticket in the Change Request. the **Status** is set to **Closed**. 13. Click **Add Proposed Customization** to create a customization for this Process Issue. Select the **Type** and complete the **Script ID** or **Name**, depending on the **Type**. Click **+Add - more proposed customizations** to add another, or **Add Proposed Customization(s)** to continue. -14. Assign a **Status** to help track the issue. Do not assign as **Completed As Process Issue** or - **Closed** until all work has been done, and all change requests are completed, deployed and + more proposed customizations** to add another, or **Add Proposed Customizations** to continue. +14. Assign a **Status** to help track the issue. Don't assign as **Completed As Process Issue** or + **Closed** until all work has been done, and all change requests are completed, deployed, and verified. - **Not Started** is the default. - **In Progress**: work or investigation has started. - **Completed As Process Issue**: work has been completed, all changes and change requests are - complete, deployed and verified. + complete, deployed, and verified. - **Converted to Change Request**: a change request has been created for the issue. - **Next Review**: indicates the issue will be looked at again the next time process issues are reviewed. @@ -106,13 +106,13 @@ You can manage your Process Issues through reports: Open **Strongpoint** > **Process Issues** > **Process Issue Overview** -You can enter filters to sort the issues and click on the column heads to change the sort order. -Reports can be exported to CSV, Excel, PDF, printed or emailed using the icons. +You can enter filters to sort the issues and click the column heads to change the sort order. +Reports can be exported to CSV, Excel, PDF, printed, or emailed using the icons. You can also edit some fields inline: -1. Click on **EDIT** in the report tool bar. When enabled, it is green with a check mark. -2. Click on the red pencil icon in the column head. Columns without the pencil icon cannot be +1. Click **EDIT** in the report tool bar. When enabled, it is green with a check mark. +2. Click the red pencil icon in the column head. Columns without the pencil icon can't be edited. 3. Click in the column to open a text box. diff --git a/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_create_ticket.md b/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_create_ticket.md index 12274ceced..c10d7d5539 100644 --- a/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_create_ticket.md +++ b/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_create_ticket.md @@ -7,7 +7,7 @@ sidebar_position: 20 # Creating a Ticket and Change Request for ServiceNow The [ServiceNow integration](/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_install_configure_netsuite.md) must be installed and -configured prior to use. +configured before use. 1. Open **ServiceNow**. 2. Select **Manage** > **Instance**. @@ -48,7 +48,7 @@ configured prior to use. ![servicenow_impact_analysis](/images/platgovnetsuite/integrations/servicenow_impact_analysis.webp) - Click on the links to open the record in NetSuite for further research. + Click the links to open the record in NetSuite for further research. ![servicenow_impact_analysis_ns](/images/platgovnetsuite/integrations/servicenow_impact_analysis_ns.webp) @@ -58,5 +58,5 @@ configured prior to use. ![servicenow_erd](/images/platgovnetsuite/integrations/servicenow_erd.webp) 14. Click **Submit**. The list of change requests is displayed. -15. Once the change request is moved to the Authorize state, click **Push Deployment Record** in the +15. After the change request is moved to the Authorize state, click **Push Deployment Record** in the menu bar to complete the change request. diff --git a/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_install_configure_netsuite.md b/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_install_configure_netsuite.md index 94c87df52e..c63b912a92 100644 --- a/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_install_configure_netsuite.md +++ b/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_install_configure_netsuite.md @@ -10,7 +10,7 @@ sidebar_position: 10 1. Open **Customization** > **SuiteBundler** > **Search & Install Bundles** 2. Search for bundle id **311232** -3. Click on bundle name **ServiceNow Integration** +3. Click bundle name **ServiceNow Integration** 4. When the **Bundle Details** opens, click **Install**. ![servicenowinstall2](/images/platgovnetsuite/integrations/servicenowinstall2.webp) @@ -18,7 +18,7 @@ sidebar_position: 10 5. When **Preview Bundle** opens, review the bundle and click **Install** to finish. 6. Open **Strongpoint** > **Strongpoint Support** > **Installation Settings** > **View** 7. Open the **ServiceNow Integration** tab. -8. If the **Service Now URL** is not present: +8. If the **Service Now URL** isn't present: 1. Click **Edit**. 2. Add the url. The format is: _https://dev67367.service-now.com/_ @@ -52,7 +52,7 @@ sidebar_position: 10 **URL**: _[https://github.com/StrongpointGit/strongpoint-ns-ssn.git](https://github.com/StrongpointGit/strongpoint-ns-ssn.git)_ **Credential**: - Select your credential from the drop down list + Select your credential from the dropdown list **User Name**: sp-integrations **Branch**: master @@ -82,7 +82,7 @@ You can configure ServiceNow for your users: You can set conditions on NetSuite integration buttons to control when they are displayed on specific change records. If you use ServiceNow, you can set Configuration Items to manage change -requests for different platforms, projects or products. +requests for different platforms, projects, or products. You need to know the IDs of the configuration items to set conditions. Ask your ServiceNow administrator for help. @@ -97,7 +97,7 @@ administrator for help. 2. Set the **Condition** field to restrict display based on specific configuration items. If your company uses a different solution to identify changes for the NetSuite platform, contact your - ServiceNow administrator to help determine the conditions to be set. In this example, we set the + ServiceNow administrator to help determine the conditions to be set. In this example, the condition to be: **current.cmdb_ci == 'configuration_item_sys_id'** @@ -113,7 +113,7 @@ This is an example procedure to display the **Push Deployment Record** button on has passed the **Authorize** state. Your organization may have a different approval process. You can set any other stage (standard or custom) depending on your approval processes. - If you need help to determine the correct conditions per your customizations, please contact your + If you need help to determine the correct conditions per your customizations,contact your Service Now Administrator. 1. In ServiceNow, open **System Applications** > **Studio** @@ -146,9 +146,9 @@ modify this to only allow configured users to see the tab. ![Open the ServiceNow Configuration items](/images/platgovnetsuite/integrations/servicenow_tab1.webp) 3. Select the system for the user to grant access to the tab. - 4. Select **Copy sys_id** from the drop down menu. + 4. Select **Copy sys_id** from the dropdown menu. - ![Select Copy sys_id from the drop down menu](/images/platgovnetsuite/integrations/servicenow_tab2.webp) + ![Select Copy sys_id from the dropdown menu](/images/platgovnetsuite/integrations/servicenow_tab2.webp) 5. Paste the identifier in a file where you can access it to add to the script when you are finished locating the system identifiers. An example identifier is diff --git a/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_integration.md b/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_integration.md index fd5a5a65d7..f4a162cb3a 100644 --- a/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_integration.md +++ b/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_integration.md @@ -9,7 +9,7 @@ sidebar_position: 20 ## Features and Benefits With Platform Governance for NetSuite's integration of **NetSuite** and **ServiceNow**, you can use -the **ServiceNow** tool while we automatically add and track the associated changes in your NetSuite +the **ServiceNow** tool while Platform Governance for NetSuite automatically adds and tracks the associated changes in your NetSuite account. The integration eliminates the need for double entry in the two systems. The ServiceNow integration automatically syncs ServiceNow with NetSuite: @@ -28,10 +28,10 @@ Change Managers and System Administrators quickly realize the integration benefi ## Technical Considerations -The following should be considered prior to deploying the ServiceNow integration: +The following should be considered before deploying the ServiceNow integration: 1. The integration is a client script that can be enabled or disabled by form, user, or role. It has - high order value to ensure it is the last thing to run and does not interrupt any other process. + high order value to ensure it is the last thing to run and doesn't interrupt any other process. 2. All functions are self-executing, complying with ServiceNow's best practices. 3. No DOM manipulation or global scripts are deployed. 4. No external libraries are needed. It is plain JavaScript. diff --git a/docs/platgovnetsuite/ticketingintegrations/ticketing_integrations.md b/docs/platgovnetsuite/ticketingintegrations/ticketing_integrations.md index 283c50f04f..39a2839b05 100644 --- a/docs/platgovnetsuite/ticketingintegrations/ticketing_integrations.md +++ b/docs/platgovnetsuite/ticketingintegrations/ticketing_integrations.md @@ -18,6 +18,6 @@ Ticketing Integrations with NetSuite include: - [ServiceNow](/docs/platgovnetsuite/ticketingintegrations/servicenowintegration/servicenow_integration.md) - [Zendesk](/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md) - [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) enables your developers to support your ticketing - systems, making the integration functionality available to everyone. Integrating your systems with + systems, making the integration functionality availcan everyone. Integrating your systems with your Platform Governance for NetSuite account helps you make the most of your change management and ticketing strategies. diff --git a/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md b/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md index b19f8543f5..e1e475c9cd 100644 --- a/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md +++ b/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md @@ -7,7 +7,7 @@ sidebar_position: 30 # Zendesk Platform Governance For NetSuite's Change Management capabilities are integrated with Zendesk, one -of the most popular customer service and issue ticketing systems. Customers are able to look for and +of the most popular customer service and issue ticketing systems. Customers can look for and include NetSuite Customizations, assess impacts for requested changes, and push Zendesk change tickets into a Change Request. This enables easy management of changes, seamless tracking of compliant changes and automating the reconciliation of change logs during an audit. @@ -32,7 +32,7 @@ To set up the Zendesk integration: 1. Open **Customization** > **SuiteBundler** > **Search & Install Bundles** 2. Search for bundle **402177** -3. Click on **Netwrix Platform Governance Zendesk** in the search results. +3. Click **Netwrix Platform Governance Zendesk** in the search results. 4. Click **Install** when the Bundle Details opens. 5. Click **Install Bundle** on the **Preview Bundle** Install page. @@ -111,9 +111,9 @@ After you install the Zendesk app, set up the approvals. 2. Enter the group and approval information: - **Allow these Zendesk groups to request approval** one or more groups who can request approval - for a change request. Select a group from the drop down list. Click **+**. Repeat as needed. + for a change request. Select a group from the dropdown list. Click **+**. Repeat as needed. - **Allow these Zendesk groups to approve** one or more groups who can approve a change request. - Select a group from the drop down list. Click **+**. Repeat as needed. + Select a group from the dropdown list. Click **+**. Repeat as needed. - **Approval process** select the approval process to use. **Platform Governance Approval in Zendesk**, **Platform Governance Approval in NetSuite**, **No Approval Needed**, or **Not set**. diff --git a/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_walkthrough_example.md b/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_walkthrough_example.md index 19b15ceca9..0832e6b920 100644 --- a/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_walkthrough_example.md +++ b/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_walkthrough_example.md @@ -6,12 +6,12 @@ sidebar_position: 10 # Zendesk Walkthrough Example -This walkthrough is one example based on our test account. You must -[install and configure](/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md) the Zendesk integration, prior to using this +This walkthrough is one example based on a test account. You must +[install and configure](/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md) the Zendesk integration, before using this walkthrough. :::note -Alerts and notifications may occur during this walkthrough, and are not included in these steps. For +Alerts and notifications may occur during this walkthrough, and aren't included in these steps. For example, override alert, notifications for approvers, and notification for the change request. ::: @@ -22,7 +22,7 @@ The walkthrough demonstrates these steps: ## Create a Zendesk Ticket -1. Login in to your Zendesk dashboard. +1. Log in to your Zendesk dashboard. 2. Open your **Views**. ![Open the Zendesk Views](/images/platgovnetsuite/integrations/zendesk_views.webp) @@ -38,7 +38,7 @@ The walkthrough demonstrates these steps: - **Select Assignee**: assignees are added as users or groups. - Click **take it** to assign it to yourself. - Start typing a user name and pick from one of the matches. User names are listed by group. - - Expand the drop down and open a group. Select a user or assign it to the group. + - Expand the dropdown and open a group. Select a user or assign it to the group. - **Followers**: add users to follow this ticket. - Click **follow** to add yourself. - Start typing a user name and pick from one of the matches. @@ -49,7 +49,7 @@ The walkthrough demonstrates these steps: can also **Apply macro** if applicable. :::note -The app information is not available until the ticket is created. +The app information isn't available until the ticket is created. ::: 6. Click **Submit as New**. @@ -61,7 +61,7 @@ The app information is not available until the ticket is created. Open your new Zendesk ticket. **Test Ticket** in this example. :::note -If you do not see the app, make sure the Apps are toggled on using the Apps icon +If you don't see the app, ensure the Apps are toggled on using the Apps icon ![Zendesk Apps visibility icon](/images/platgovnetsuite/integrations/zendesk_apps_icon.webp) and verify you are a member of a group or role [authorized to access the app](/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md). @@ -73,14 +73,14 @@ and verify you are a member of a group or role Specify a Bundle to use a bundle for the scope of change. This is optional. -1. Expand the drop down. +1. Expand the dropdown. 2. Enter the Bundle ID. -3. Click + to add the bundle. 232111 in this example. You can remove a bundle using the drop down +3. Click + to add the bundle. 232111 in this example. You can remove a bundle using the dropdown toggle. ![Specify an optional Bundle ID](/images/platgovnetsuite/integrations/zendesk_bundleid.webp) -Once you have made a change, the **Request Approval** button is available if you are a member of a +After you have made a change, the **Request Approval** button is available if you are a member of a group with the [Set up Approvals](zendesk_integration.md#set-up-approvals) permission. ![Request Approval button appears when a change has been made.](/images/platgovnetsuite/integrations/zendesk_request_approval.webp) @@ -122,7 +122,7 @@ There is an options menu available for each added customization. Options include There is an options menu available for each added proposed customization. Click options to **Remove** the customization. -### Need Help? +### Getting help If you encounter any issues or need assistance, contact support at this [link](https://www.netwrix.com/support.html). diff --git a/docs/platgovnetsuite/uar/access_app.md b/docs/platgovnetsuite/uar/access_app.md index ebeca87b3c..ed018d7b98 100644 --- a/docs/platgovnetsuite/uar/access_app.md +++ b/docs/platgovnetsuite/uar/access_app.md @@ -10,7 +10,7 @@ The User Access Review bundle must be [installed](/docs/platgovnetsuite/uar/inst accounts and a UAR license to access User Access Review. **User Access Review** is available on the NetSuite menu bar if you have a -[license](/docs/platgovnetsuite/uar/install_app.md). If it is not on your menu, contact your Netwrix or NetSuite +[license](/docs/platgovnetsuite/uar/install_app.md). If it isn't on your menu, contact your Netwrix or NetSuite administrator. ![User Access Review menu](/images/platgovnetsuite/uar/uar_menu.webp) @@ -30,8 +30,8 @@ Dashboards are role specific. There are common elements for all the dashboards. - **Menu bar**: Home icon, current role, and **Logout** are present for all roles. Lists and History options depend on the role. -- **Shortcuts**: Drill down into the specifics when you click on a shortcut. Available for all +- **Shortcuts**: Expand the details when you click a shortcut. Available for all roles. - **Charts**: Visual representation of the current reviews. Admin and Owner only. -- **Notifications**: system notifications about your reviews. Admin, Owner and Additional Reviewer +- **Notifications**: system notifications about your reviews. Admin, Owner, and Additional Reviewer only. diff --git a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_membership_reviews.md b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_membership_reviews.md index e052018261..c049e73a10 100644 --- a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_membership_reviews.md +++ b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_membership_reviews.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Additional Reviewer Membership Reviews -This type of review is used to keep your roles up to date. When you click on a membership review, +This type of review is used to keep your roles up to date. When you click a membership review, the list of users with the role is displayed. The links open the appropriate record in NetSuite, for example the **User** link opens the **User** record. @@ -53,7 +53,7 @@ This display provides a global view of the user's access. ![Reviewing user roles](/images/platgovnetsuite/uar/uar_additional_reviewer/additional_user_reviewer_review.webp) 2. Review their Global Permissions, Other Roles, and SoD Violations. The links all open the specific records for further review. If the user should retain the role, click **Mark Completed**. The - status is updated. You cannot undo this action. + status is updated. You can't undo this action. ![Mark your review complete](/images/platgovnetsuite/uar/uar_additional_reviewer/additional_user_reviewer_complete.webp) 3. Click **Submit** or make additional changes. diff --git a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_overview.md b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_overview.md index 473df2e617..b15198d786 100644 --- a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_overview.md +++ b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_overview.md @@ -8,7 +8,7 @@ sidebar_position: 50 Additional Reviewers are assigned by the UAR owners to perform reviews. Additional Reviewers are notified with an email message when a new review has been assigned. You can click one of the links -in the email, or login to NetSuite and open [User Access Review](/docs/platgovnetsuite/uar/access_app.md) to access the +in the email, or log in to NetSuite and open [User Access Review](/docs/platgovnetsuite/uar/access_app.md) to access the dashboard. 1. Open **User Access Review** from NetSuite. diff --git a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_uar_list.md b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_uar_list.md index c37ca8c6f5..c4c4cdfe0e 100644 --- a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_uar_list.md +++ b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_uar_list.md @@ -27,7 +27,7 @@ Use **Clear** to reset the Filters. - Second Date field only: All reviews created before the specified date are listed. - Both Date fields: All reviews created in the date range are listed. -- **Status** Select from the drop down list. **All** is the default. +- **Status** Select from the dropdown list. **All** is the default. Possible statuses are **Not Started**, **Pending Assignment**, **In Progress**, **Complete**, **Cancelled** and **Waiting for CR**. - **Sort By** Displays a list of either **Global Reviews** or **Single Reviews**. **Global Reviews** @@ -44,15 +44,15 @@ Use **Clear** to reset the Filters. Single is **Membership** or **Permission**. The review type is set when the review is created. - **Status** Current status of the review: - - **Pending Assignment** Review does not have an assigned owner. + - **Pending Assignment** Review doesn't have an assigned owner. - **Not Started** Email notification has been sent, review has not been started. - **In Progress** Review has been started. - **Additional Reviewer** Review has been assigned to an additional reviewer. - **Change Request** Change request has been created. The **Change Request ID** is added to the row. The link opens the Change Request. **CR Rejected**, **CR Cancelled**, and **CR Complete** are the other Change Request status values. - - **Waiting for CR** Change request cannot be started, because there is an existing change - request in progress for the role or permission as part of a different global review. Once the + - **Waiting for CR** Change request can't be started, because there is an existing change + request in progress for the role or permission as part of a different global review. After the existing change request is complete, the current review can continue. - **Cancelled** Review has been canceled. Canceled global reviews are shown in the UAR History list. Canceled single reviews are shown in the global review. @@ -82,15 +82,15 @@ showing all of the single reviews associated with the global review. when the review is created. - **Status** Current status of the review: - - **Pending Assignment** Review does not have an assigned owner. + - **Pending Assignment** Review doesn't have an assigned owner. - **Not Started** Email notification has been sent, review has not been started. - **In Progress** Review has been started. - **Additional Reviewer** Review has been assigned to an additional reviewer. - **Change Request** Change request has been created. The **Change Request ID** is added to the row. The link opens the Change Request. **CR Rejected**, **CR Cancelled**, and **CR Complete** are the other Change Request status values. - - **Waiting for CR** Change request cannot be started, because there is an existing change - request in progress for the role or permission as part of a different global review. Once the + - **Waiting for CR** Change request can't be started, because there is an existing change + request in progress for the role or permission as part of a different global review. After the existing change request is complete, the current review can continue. - **Cancelled** Review has been canceled. Canceled global reviews are shown in the UAR History list. Canceled single reviews are shown in the global review. diff --git a/docs/platgovnetsuite/uar/adminoverview/admin_overview.md b/docs/platgovnetsuite/uar/adminoverview/admin_overview.md index 7acd2ed6e2..e6bac55dff 100644 --- a/docs/platgovnetsuite/uar/adminoverview/admin_overview.md +++ b/docs/platgovnetsuite/uar/adminoverview/admin_overview.md @@ -6,7 +6,7 @@ sidebar_position: 30 # UAR Admin -**UAR Admin** manages the UAR process. Administrators login to NetSuite and open +**UAR Admin** manages the UAR process. Administrators log in to NetSuite and open [User Access Review](/docs/platgovnetsuite/uar/access_app.md) to access the dashboard. UAR administrators can: - Assign owners to a role diff --git a/docs/platgovnetsuite/uar/adminoverview/admin_owner_list.md b/docs/platgovnetsuite/uar/adminoverview/admin_owner_list.md index 431d8a027b..cd2064d7c8 100644 --- a/docs/platgovnetsuite/uar/adminoverview/admin_owner_list.md +++ b/docs/platgovnetsuite/uar/adminoverview/admin_owner_list.md @@ -9,7 +9,7 @@ sidebar_position: 10 Access your **Owner List** from your menu bar. This is where Administrators can add or remove owners from reviews. All changes are captured in the [UAR History](/docs/platgovnetsuite/uar/adminoverview/uar_history.md). -Auditors can view the Owner list and Owner notes, but cannot add or remove owners. +Auditors can view the Owner list and Owner notes, but can't add or remove owners. Here is an example of the **Owner List**: @@ -21,11 +21,11 @@ Filters help you organize your Owner list. Use **Clear** to reset the Filters. -- **Center Type** Select from the drop down list. **All** is the default. +- **Center Type** Select from the dropdown list. **All** is the default. - **Role Type of Review** Displays **Both**, **Custom** only, or **Standard** only roles in the list. -- **Owner** Select from the drop down list. **All** is the default. -- **Role** Select from the drop down list. **All** is the default. +- **Owner** Select from the dropdown list. **All** is the default. +- **Role** Select from the dropdown list. **All** is the default. - Select either **All Roles** (default) or **Roles with missing Owners**. ## Owner List @@ -39,7 +39,7 @@ Use **Clear** to reset the Filters. - **Role** is the role to be reviewed. - **From Bundle** the bundle number if applicable. - **Custom/Standard** the role type. -- **Center Type** the center for the role. +- **Center Type**: enter the center for the role. - **Role Membership Owner** the user assigned to the role membership. - **Role Permission Owner** the user assigned to the role permissions. - **Access Owner** the user assigned to the role access. @@ -53,9 +53,9 @@ Use **Clear** to reset the Filters. ![Add Owner](/images/platgovnetsuite/uar/uar_admin/add_owner.webp) -3. **Select Role** from the drop down. From Bundle, Custom/Standard and Center Type are +3. **Select Role** from the dropdown. From Bundle, Custom/Standard and Center Type are automatically added. -4. Select users from the drop downs for the ownership roles. +4. Select users from the dropdowns for the ownership roles. 5. Click **Save** when your changes are complete. ### Change Owner @@ -63,8 +63,8 @@ Use **Clear** to reset the Filters. You can change any of the owners from the Owner List. 1. Open **Owner List** from your menu bar. -2. Select an existing role. The drop down lists for the ownership roles are displayed. -3. Select users from the drop downs for the ownership roles. +2. Select an existing role. The dropdown lists for the ownership roles are displayed. +3. Select users from the dropdowns for the ownership roles. 4. Click **Save** when your changes are complete. ### Remove Owner diff --git a/docs/platgovnetsuite/uar/adminoverview/admin_pending_assignments.md b/docs/platgovnetsuite/uar/adminoverview/admin_pending_assignments.md index e9ec0af4d9..3c1a4c6e06 100644 --- a/docs/platgovnetsuite/uar/adminoverview/admin_pending_assignments.md +++ b/docs/platgovnetsuite/uar/adminoverview/admin_pending_assignments.md @@ -20,8 +20,8 @@ Filters help you organize your Pending Role Assignments list. Use **Clear** to reset the Filters. -- **Role** Select from the drop down list. **All** is the default. -- **Center Type** Select from the drop down list. **All** is the default. +- **Role** Select from the dropdown list. **All** is the default. +- **Center Type** Select from the dropdown list. **All** is the default. - **Role Type** Displays **Both**, **Custom** only, or **Standard** only roles in the list. ## Pending Assignments List @@ -33,7 +33,7 @@ Use **Clear** to reset the Filters. - **Role** is the role to be reviewed. - **From Bundle** the bundle number if applicable. - **Custom/Standard** the role type. -- **Center Type** the center for the role. +- **Center Type**: enter the center for the role. - **Role Membership Owner** the user assigned to the role membership. - **Role Permission Owner** the user assigned to the role permissions. - **Role Access Owner** the user assigned to the role access. @@ -45,8 +45,8 @@ Use **Clear** to reset the Filters. You can assign owners on the **Pending Role Assignments List**. 1. Open **Pending Role Assignments** from your menu bar. -2. Select an existing role. The drop down lists for the ownership roles are displayed. -3. Select users from the drop downs for the ownership roles. +2. Select an existing role. The dropdown lists for the ownership roles are displayed. +3. Select users from the dropdowns for the ownership roles. 4. Click **Save** when your changes are complete. ### Set a Due Date diff --git a/docs/platgovnetsuite/uar/adminoverview/admin_uar_list.md b/docs/platgovnetsuite/uar/adminoverview/admin_uar_list.md index 4452312140..14894b50de 100644 --- a/docs/platgovnetsuite/uar/adminoverview/admin_uar_list.md +++ b/docs/platgovnetsuite/uar/adminoverview/admin_uar_list.md @@ -28,7 +28,7 @@ Use **Clear** to reset the Filters. - Second Date field only: All reviews created before the specified date are listed. - Both Date fields: All reviews created in the date range are listed. -- **Status** Select from the drop down list. **All** is the default. +- **Status** Select from the dropdown list. **All** is the default. Possible statuses are **Not Started**, **Pending Assignment**, **In Progress**, **Complete**, **Cancelled** and **Waiting for CR**. - **Sort By** Displays a list of either **Global Reviews** or **Single Reviews**. **Global Reviews** @@ -53,15 +53,15 @@ Use **Clear** to reset the Filters. - **Owner** (single) is the owner of the role review type. - **Status** Current status of the review: - - **Pending Assignment** Review does not have an assigned owner. + - **Pending Assignment** Review doesn't have an assigned owner. - **Not Started** Email notification has been sent, review has not been started. - **In Progress** Review has been started. - **Additional Reviewer** Review has been assigned to an additional reviewer. - **Change Request** Change request has been created. The **Change Request ID** is added to the row. The link opens the Change Request. **CR Rejected**, **CR Cancelled**, and **CR Complete** are the other Change Request status values. - - **Waiting for CR** Change request cannot be started, because there is an existing change - request in progress for the role or permission as part of a different global review. Once the + - **Waiting for CR** Change request can't be started, because there is an existing change + request in progress for the role or permission as part of a different global review. After the existing change request is complete, the current review can continue. - **Cancelled** Review has been canceled. Canceled global reviews are shown in the UAR History list. Canceled single reviews are shown in the global review. @@ -86,12 +86,12 @@ Use **Clear** to reset the Filters. ![Create a review](/images/platgovnetsuite/uar/uar_admin/create_review2.webp) -4. Use the drop down to **Select Global Review** this option is only if you chose **Single**. It is +4. Use the dropdown to **Select Global Review** this option is only if you chose **Single**. It is not available if you are creating a new **Global** review. The existing information for the Global review is populated. 5. Add or remove one or more roles. The left pane shows all the available roles, the right pane shows the roles you have added. The **Add all active roles** shows active roles in the left pane. - It toggles to **Show all active and assigned roles** in the left pane. You cannot change + It toggles to **Show all active and assigned roles** in the left pane. You can't change permissions on Standard roles or the Administrator role.. 6. Select **Type of Review**. This is only available if you are creating a new **Global** review. You can select one or both options. @@ -142,13 +142,13 @@ Use **Clear** to reset the Filters. - Second Date field only: All reviews created before the specified date are listed. - Both Date fields: All reviews created in the date range are listed. -- **Status** Select from the drop down list. **All** is the default. +- **Status** Select from the dropdown list. **All** is the default. Possible statuses are **Not Started**, **Pending Assignment**, **In Progress**, **Complete**, **Cancelled** and **Waiting for CR**. -- **Role** Select the role from the drop down list. **All** is the default. +- **Role** Select the role from the dropdown list. **All** is the default. - **Type of Review** Displays **Both**, **Membership** only, or **Permission** only reviews in the Review list. -- **Owner** Select from the drop down list. +- **Owner** Select from the dropdown list. ### Review List Actions @@ -172,7 +172,7 @@ There are various actions you can perform from this list: - **Owner** Current review owner. - **Status** Current status of the review: - - **Pending Assignment** Review does not have an assigned owner. + - **Pending Assignment** Review doesn't have an assigned owner. - **Not Started** Email notification has been sent, review has not been started. - **In Progress** Review has been started. - **Additional Reviewer** Review has been assigned to an @@ -180,8 +180,8 @@ There are various actions you can perform from this list: - **Change Request** Change request has been created. The **Change Request ID** is added to the row. The link opens the Change Request. **CR Rejected**, **CR Cancelled**, and **CR Complete** are the other Change Request status values. - - **Waiting for CR** Change request cannot be started, because there is an existing change - request in progress for the role or permission as part of a different global review. Once the + - **Waiting for CR** Change request can't be started, because there is an existing change + request in progress for the role or permission as part of a different global review. After the existing change request is complete, the current review can continue. - **Cancelled** Review has been canceled. Canceled global reviews are shown in the UAR History list. Canceled single reviews are shown in the global review. diff --git a/docs/platgovnetsuite/uar/adminoverview/owner_membership_reviews.md b/docs/platgovnetsuite/uar/adminoverview/owner_membership_reviews.md index ec06af8c34..54b63fb13c 100644 --- a/docs/platgovnetsuite/uar/adminoverview/owner_membership_reviews.md +++ b/docs/platgovnetsuite/uar/adminoverview/owner_membership_reviews.md @@ -6,7 +6,7 @@ sidebar_position: 40 # Membership Reviews -This type of review is used to keep your roles up to date. When you click on a membership review, +This type of review is used to keep your roles up to date. When you click a membership review, the list of users with the role is displayed. The links open the appropriate record in NetSuite, for example the **User** link opens the **User** record. Access membership reviews from **UAR List** in your menu bar, or one of the review shortcuts. @@ -61,7 +61,7 @@ This display provides a global view of the user's access. 1. Select the user. 2. Review their Global Permissions, Other Roles, and SoD Violations. The links all open the specific records for further review. If the user should retain the role, click **Mark Completed**. The - status is updated. You cannot undo this action. + status is updated. You can't undo this action. ![Mark user as reviewed](/images/platgovnetsuite/uar/uar_owner/mark_complete.webp) ### Remove Users from the Role @@ -88,14 +88,14 @@ To remove one or more users from the role: If the Change Request is rejected (**CR Rejected status**) or canceled (**CR Cancelled**), the user row is returned to a pending state and can then be reviewed again. Use the Change Request - ID link to open the Change Request and review the **Approver Comments** for more information. + ID link to open the Change Request and review the **Approver Comments** for rejection details. ### Assign an Additional Reviewer You can add additional reviewers to the review: 1. Select the user. -2. Select an additional reviewer from the drop down list. +2. Select an additional reviewer from the dropdown list. ![Assign an additional reviewer](/images/platgovnetsuite/uar/uar_owner/additional_user_assign.webp) The user line is highlighted. You can click **Undo** to cancel the addition before you click **Submit**. diff --git a/docs/platgovnetsuite/uar/adminoverview/owner_permission_reviews.md b/docs/platgovnetsuite/uar/adminoverview/owner_permission_reviews.md index 3044646dd2..3a0b22c922 100644 --- a/docs/platgovnetsuite/uar/adminoverview/owner_permission_reviews.md +++ b/docs/platgovnetsuite/uar/adminoverview/owner_permission_reviews.md @@ -6,7 +6,7 @@ sidebar_position: 50 # Permission Reviews -This type of review is used to keep your role permissions up to date. When you click on a permission +This type of review is used to keep your role permissions up to date. When you click a permission review, the permissions list is displayed. Access permission reviews from **UAR List** in your menu bar, or one of the review shortcuts. @@ -21,7 +21,7 @@ review. Filters help you organize your Permissions review list: -- **Level**: Permission Level can be **All** (default), **View**, **Create**, **Edit** or **Full**. +- **Level**: Permission Level can be **All** (default), **View**, **Create**, **Edit**, or **Full**. - **Category**: Permission Category can be **All** (default), **Transactions**, **Reports**, **Lists**, **Setup**, or **Custom Records**. - **Role Permission**: Full list of all of your defined permissions. **All** is the default. @@ -57,7 +57,7 @@ Other available actions: 1. Select one or more **Role Permissions**. 2. Review the **Permission** and the **Level** are appropriate for the role. If correct, click - **Mark Completed**. The status is updated. You cannot undo this action. + **Mark Completed**. The status is updated. You can't undo this action. ![Mark the Permission review complete](/images/platgovnetsuite/uar/uar_owner/permission_review_complete.webp) ### Change Permission Level @@ -85,7 +85,7 @@ To change a permission level: is rejected (**CR Rejected status**) or canceled (**CR Cancelled**), the permission row is returned to a pending state. -5. You can click on the **Change Request ID** link and review the **Approver Notes**. +5. You can click the **Change Request ID** link and review the **Approver Notes**. ### Add a Permission diff --git a/docs/platgovnetsuite/uar/adminoverview/uar_history.md b/docs/platgovnetsuite/uar/adminoverview/uar_history.md index 719d79bcbc..6edda16f96 100644 --- a/docs/platgovnetsuite/uar/adminoverview/uar_history.md +++ b/docs/platgovnetsuite/uar/adminoverview/uar_history.md @@ -7,7 +7,7 @@ sidebar_position: 60 # UAR History When reviews are complete, they are added to the **UAR History**. Click **UAR History** in your menu -bar to access the list. Completed reviews cannot be modified. You can use **Filters** to narrow down +bar to access the list. Completed reviews can't be modified. You can use **Filters** to narrow down your list. Additional reporting for extracting permission and membership data is available from the [administrator](/docs/platgovnetsuite/uar/adminoverview/admin_uar_list.md) and [owner](/docs/platgovnetsuite/uar/owneroverview/owner_uar_list.md) Review lists. @@ -19,7 +19,7 @@ Additional Reviewers see completed reviews where they were assigned. ![Open UAR History](/images/platgovnetsuite/uar/uar_history.webp) -Click on a **Review Name** to access details about the review, **Q1 2022_Membership_Buyer** in this +Click a **Review Name** to access details about the review, **Q1 2022_Membership_Buyer** in this example. The Review is opened, displaying the **Review** tab. ![UAR History Review tab](/images/platgovnetsuite/uar/uar_history_review.webp) @@ -27,7 +27,7 @@ example. The Review is opened, displaying the **Review** tab. ## Review Tab The **Review** tab displays all of the roles or permissions reviewed as part of the completed Global -Review. Record links are provided in each row to drill down into the data records. +Review. Record links are provided in each row to view the data records in detail. ## Review Notes Tab diff --git a/docs/platgovnetsuite/uar/auditoroverview/auditor_overview.md b/docs/platgovnetsuite/uar/auditoroverview/auditor_overview.md index a3e3543c4e..ad597729e1 100644 --- a/docs/platgovnetsuite/uar/auditoroverview/auditor_overview.md +++ b/docs/platgovnetsuite/uar/auditoroverview/auditor_overview.md @@ -6,7 +6,7 @@ sidebar_position: 60 # UAR Auditor -Auditors have view only access to specific UAR data. Auditors login to NetSuite and open +Auditors have view only access to specific UAR data. Auditors log in to NetSuite and open [User Access Review](/docs/platgovnetsuite/uar/access_app.md) to access the dashboard. 1. Open **User Access Review** from NetSuite. diff --git a/docs/platgovnetsuite/uar/install_app.md b/docs/platgovnetsuite/uar/install_app.md index 60213731de..70048e83c5 100644 --- a/docs/platgovnetsuite/uar/install_app.md +++ b/docs/platgovnetsuite/uar/install_app.md @@ -37,7 +37,7 @@ for the UAR App or Licensing Existing Users for UAR. ## Licensing New Users for the UAR App -This procedure is used to add a UAR license to an existing NetSuite user who is not licensed for +This procedure is used to add a UAR license to an existing NetSuite user who isn't licensed for Platform Governance for NetSuite. 1. Open **Strongpoint** > **Strongpoint Support** > **License Manager**. diff --git a/docs/platgovnetsuite/uar/owneroverview/owner_overview.md b/docs/platgovnetsuite/uar/owneroverview/owner_overview.md index 7ec6c7f540..896c6317d9 100644 --- a/docs/platgovnetsuite/uar/owneroverview/owner_overview.md +++ b/docs/platgovnetsuite/uar/owneroverview/owner_overview.md @@ -16,7 +16,7 @@ The [Owner User Access Reviews List](/docs/platgovnetsuite/uar/owneroverview/own reviews. Owners are notified with an email message when a new review has been assigned. You can click one of -the links in the email, or login to NetSuite and open [User Access Review](/docs/platgovnetsuite/uar/access_app.md) to +the links in the email, or log in to NetSuite and open [User Access Review](/docs/platgovnetsuite/uar/access_app.md) to access the dashboard. 1. Open **User Access Review** from NetSuite. diff --git a/docs/platgovnetsuite/uar/owneroverview/owner_uar_list.md b/docs/platgovnetsuite/uar/owneroverview/owner_uar_list.md index f268775692..cda613fb5b 100644 --- a/docs/platgovnetsuite/uar/owneroverview/owner_uar_list.md +++ b/docs/platgovnetsuite/uar/owneroverview/owner_uar_list.md @@ -29,12 +29,12 @@ Use **Clear** to reset the Filters. - Second Date field only: All reviews created before the specified date are listed. - Both Date fields: All reviews created in the date range are listed. -- **Status** Select from the drop down list. **All** is the default. +- **Status** Select from the dropdown list. **All** is the default. Possible statuses are **Not Started**, **Pending Assignment**, **In Progress**, **Complete**, **Cancelled** and **Waiting for CR**. - **Sort By** Displays a list of either **Global Reviews** or **Single Reviews**. **Global Reviews** are displayed by default. -- **Role** Select the role from the drop down list. **All** is the default. +- **Role** Select the role from the dropdown list. **All** is the default. - **Type of Review** (single) Displays **Both**, **Membership** only, or **Permission** only reviews in the Review list. @@ -52,7 +52,7 @@ Use **Clear** to reset the Filters. - **Owner** (single) is the owner of the role review type. - **Status** Current status of the review: - - **Pending Assignment** Review does not have an assigned owner. + - **Pending Assignment** Review doesn't have an assigned owner. - **Not Started** Email notification has been sent, review has not been started. - **In Progress** Review has been started. - **Additional Reviewer** Review has been assigned to an @@ -60,8 +60,8 @@ Use **Clear** to reset the Filters. - **Change Request** Change request has been created. The **Change Request ID** is added to the row. The link opens the Change Request. **CR Rejected**, **CR Cancelled**, and **CR Complete** are the other Change Request status values. - - **Waiting for CR** Change request cannot be started, because there is an existing change - request in progress for the role or permission as part of a different global review. Once the + - **Waiting for CR** Change request can't be started, because there is an existing change + request in progress for the role or permission as part of a different global review. After the existing change request is complete, the current review can continue. - **Cancelled** Review has been canceled. Canceled global reviews are shown in the UAR History list. Canceled single reviews are shown in the global review. @@ -95,7 +95,7 @@ showing all of the single reviews associated with the global review. when the review is created. - **Status** Current status of the review: - - **Pending Assignment** Review does not have an assigned owner. + - **Pending Assignment** Review doesn't have an assigned owner. - **Not Started** Email notification has been sent, review has not been started. - **In Progress** Review has been started. - **Additional Reviewer** Review has been assigned to an @@ -103,8 +103,8 @@ showing all of the single reviews associated with the global review. - **Change Request** Change request has been created. The **Change Request ID** is added to the row. The link opens the Change Request. **CR Rejected**, **CR Cancelled**, and **CR Complete** are the other Change Request status values. - - **Waiting for CR** Change request cannot be started, because there is an existing change - request in progress for the role or permission as part of a different global review. Once the + - **Waiting for CR** Change request can't be started, because there is an existing change + request in progress for the role or permission as part of a different global review. After the existing change request is complete, the current review can continue. - **Cancelled** Review has been canceled. Canceled global reviews are shown in the UAR History list. Canceled single reviews are shown in the global review. diff --git a/docs/platgovnetsuite/uar/uar_overview.md b/docs/platgovnetsuite/uar/uar_overview.md index 11e72b1b8e..66187a3f6a 100644 --- a/docs/platgovnetsuite/uar/uar_overview.md +++ b/docs/platgovnetsuite/uar/uar_overview.md @@ -6,7 +6,7 @@ sidebar_position: 110 # User Access Review -Roles and Permissions are not a set once and forget about them activity. Both should be reviewed +Roles and Permissions aren't a set once and forget about them activity. Both should be reviewed regularly to ensure your data is secured and users in your organization have the right access. **User Access Review** streamlines this review process, making it easy to manage and review all access to your NetSuite data. UAR users must have a [license](/docs/platgovnetsuite/uar/install_app.md). @@ -39,7 +39,7 @@ Access and permissions to UAR is controlled by roles: - Request Changes to Permission or Permission Levels to owned Roles. - Request Changes to Role Assignments for owned Roles. - Designate an Additional Approver for a Membership Review for owned Roles. For example, a user - that does not report to you has a Role you own. You may want the user’s supervisor to also + that doesn't report to you has a Role you own. You may want the user’s supervisor to also approve the Role Assignment. - **UAR Auditor** read-only access to the UAR to perform auditing functions. diff --git a/docs/platgovnetsuite/what_does_strongpoint_document.md b/docs/platgovnetsuite/what_does_strongpoint_document.md index 9c7b2b8084..d977c3d357 100644 --- a/docs/platgovnetsuite/what_does_strongpoint_document.md +++ b/docs/platgovnetsuite/what_does_strongpoint_document.md @@ -1,10 +1,10 @@ --- -title: "What is Documented?" +title: "What is documented" description: "What is Documented?" sidebar_position: 14 --- -# What is Documented? +# What is documented There are four outcomes for customizations Platform Governance for NetSuite finds in the system: @@ -22,15 +22,15 @@ The following critical metadata related to your account customizations is captur - Custom Fields (for example, Body, Item, Entity, Column, Item Number and Other Field) - Mass Updates (except for mass update schedule information) - Saved Searches (fields, criteria, joins with scripts/workflows and formulas) -- Unlocked and Unencrypted Script Records (for example, Client, User Event, Scheduled, Suitelets and +- Unlocked and Unencrypted Script Records (for example, Client, User Event, Scheduled, Suitelets, and Workflow Action) -- Locked Script Records (however related dependencies can not be established) +- Locked Script Records (however related dependencies can't be established) - NetSuite Preferences (Accounting Preferences, Company Preferences etc.) - Integrations - Forms (Entry and Transaction) - Script Deployments - Script Library -- SuiteCommerce Advanced folder files and all custom SS, SSP and JS files +- SuiteCommerce Advanced folder files and all custom SS, SSP, and JS files - User Permission Overrides - User Roles - User Role Assignments @@ -38,44 +38,44 @@ The following critical metadata related to your account customizations is captur ## Partially Documented in the Customization Record -The following NetSuite objects are partially documented. They are not fully documented for one or +The following NetSuite objects are partially documented. They aren't fully documented for one or more of the following reasons: -- Record types do not have a NetSuite API that exposes the full customization data -- Records are standard objects which cannot be changed +- Record types don't have a NetSuite API that exposes the full customization data +- Records are standard objects which can't be changed | Object | Category | Description | Change Impact | Change Tracking | | --------------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Custom Report | Other | Custom Reports are documented including the report name, type and the date the report was last modified. | Changing these can impact what data is shown on the report. | Example: Change to Report Layout - detects the Date Last Modified in the Analytics Audit Log was changed and creates a change log. - Change Log indicates when the Report was updated. - You need to look at the Custom Report itself:
1. Open **Customize the Custom Report**
2. Click **More Options**
3. Open **Audit Trail** tab. | -| PDF Template | Other | PDF Templates are document including the template name, type and the date the template was last modified. | Changing these can impact email templates and other areas where PDF templates are used. | TBD | +| Custom Report | Other | Custom Reports are documented including the report name, type, and the date the report was last modified. | Changing these can impact what data is shown on the report. | Example: Change to Report Layout - detects the Date Last Modified in the Analytics Audit Log was changed and creates a change log. - Change Log indicates when the Report was updated. - You need to look at the Custom Report itself:
1. Open **Customize the Custom Report**
2. Click **More Options**
3. Open **Audit Trail** tab. | +| PDF Template | Other | PDF Templates are document including the template name, type, and the date the template was last modified. | Changing these can impact email templates and other areas where PDF templates are used. | TBD | | Standard Column Field | Standard Objects | Customization records are created only for Standard objects that are in use by scripted objects such as Workflows or Scripts. These are tracked to identify the automation dependencies. | No risk since there is no way to change standard objects in NetSuite. | If a standard object is added to or removed from a customization, a change log will be created for that customization. | | Standard Report | Standard Objects | Customization records are created only for Standard objects that are in use by scripted objects such as Workflows or Scripts. These are tracked to identify the automation dependencies. | No risk since there is no way to change standard objects in NetSuite. | If a standard object is added to or removed from a customization, a change log will be created for that customization. | | Standard Sub List | Standard Objects | Customization records are created only for Standard objects that are in use by scripted objects such as Workflows or Scripts. These are tracked to identify the automation dependencies. | No risk since there is no way to change standard objects in NetSuite. | If a standard object is added to or removed from a customization, a change log will be created for that customization. | ## Not Documented in the Customization Record -These record types do not have a NetSuite API to enable Platform Governance for NetSuite to capture +These record types don't have a NetSuite API to enable Platform Governance for NetSuite to capture customization data. | Object | Category | Description | Change Impact | | ---------------------- | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | | Custom Sub List | Other | This is the sublist that is displayed on the form. | Changing this can change what appears on a form. | -| HTML File | Web Related | Files that are part of the web site if the customer is using the NetSuite eCommerce modules, SiteBuilder or SuiteCommerce Advanced. | Changing these can change the pages of the website. | -| Integration | External System/Integration | Information relating to integrations to external systems are not documented. | Changes to objects in NetSuite could impact functionality in other systems. | +| HTML File | Web Related | Files that are part of the web site if the customer is using the NetSuite eCommerce modules, SiteBuilder, or SuiteCommerce Advanced. | Changing these can change the pages of the website. | +| Integration | External System/Integration | Information relating to integrations to external systems aren't documented. | Changes to objects in NetSuite could impact functionality in other systems. | | Item/Category Template | Web Related | Applies to companies that use SiteBuilder. | Changing these can change the functionality of the website. | -| JavaScript File | Web Related | These are JavaScript files in the file cabinet that are often used for automation on websites. Applies to customers using NetSuite eCommerce modules, SiteBuilder or SuiteCommerce Advanced. | Changing these can change the functionality of the website. | +| JavaScript File | Web Related | These are JavaScript files in the file cabinet that are often used for automation on websites. Applies to customers using NetSuite eCommerce modules, SiteBuilder, or SuiteCommerce Advanced. | Changing these can change the functionality of the website. | | Layout | Web Related | Applies to companies that use SiteBuilder | Changing these can change the functionality of the website. | | Scorecard Report | Other | Applies to dashboard objects. | Changing this will change what is displayed on the dashboard. | | Scriptlet | Deprecated | These object types have been deprecated by NetSuite and are no longer in use. | If still in use, changes to these objects can impact system functionality. | | Web Tag | Web Related | Applies to companies that use SiteBuilder | Changing these can change the functionality of the website. | -| Web Site | Web Related | The metadata that defines the web site for customers using the NetSuite eCommerce modules, SiteBuilder or SuiteCommerce Advanced. | Changing this can impact website functionality. | +| Web Site | Web Related | The metadata that defines the web site for customers using the NetSuite eCommerce modules, SiteBuilder, or SuiteCommerce Advanced. | Changing this can impact website functionality. | ## Agent Tracking Agent is part of the Enterprise Compliance package. Agent provides controls for financial changes -that do not represent configuration changes, such as changes to item account settings and violations -of standard policies. You can monitor, manage, remedy and block critical changes to financially -relevant fields, records and settings. +that don't represent configuration changes, such as changes to item account settings and violations +of standard policies. You can monitor, manage, remedy, and block critical changes to financially +relevant fields, records, and settings. Creation or modification of: diff --git a/docs/platgovnetsuite/what_is_a_spider.md b/docs/platgovnetsuite/what_is_a_spider.md index 110b93dead..1badcef642 100644 --- a/docs/platgovnetsuite/what_is_a_spider.md +++ b/docs/platgovnetsuite/what_is_a_spider.md @@ -1,10 +1,10 @@ --- -title: "What is a Spider?" +title: "What is a spider" description: "What is a Spider?" sidebar_position: 16 --- -# What is a Spider? +# What is a spider The Spider searches your account and creates the documentation for your customizations. The spider includes dependencies for saved searches in standard and custom fields. Here are items documented by @@ -40,9 +40,9 @@ by Spidering all the customization records as well doing a full update on the re account (every customization). The initial manual Spider is run during as part of the installation process: [Running the Spider](/docs/platgovnetsuite/installation/running_the_spider.md). -When running the spider, you must keep the window open for the spider to continue working. Do not +When running the spider, you must keep the window open for the spider to continue working. Don't change roles or accounts during spidering. NetSuite security standards require an active -Administrator login to execute some of the spider’s tasks. +Administrator log in to execute some of the spider’s tasks. You can specify specific record types to focus the spider: @@ -52,10 +52,10 @@ The AutoSpider monitors your account on an ongoing basis to see if customization occurred. This is a light scan of the data to determine if there were any changes. If changes are detected, you are reminded to ReSpider your account. -Best practice is to run the AutoSpider regularly. If the AutoSpider is not run, your Change Logs +Best practice is to run the AutoSpider regularly. If the AutoSpider isn't run, your Change Logs will be missing the **Changed by** and **Actual Change Date** fields. When the Change Log is newly created, the fields contain **Pending AutoSpider**. If too many days go by, the fields change to -**Could not be determined**. +**Couldn't be determined**. ### AutoSpider Portlet @@ -66,7 +66,7 @@ The **AutoSpider Portlet** is required to update certain object types in NetSuit through the dashboard portlet, it picks up all changes on custom objects and triggers the scheduled scripts to reflect them in the Customization records, going back two days. -The AutoSpider portlet is required in order to update these object types: +The AutoSpider portlet is required to update these object types: - Bundle - SuiteApp @@ -86,14 +86,14 @@ The AutoSpider portlet is required in order to update these object types: ## ReSpider Now The **ReSpider Now** feature is used to document or update documentation for a specific -customization or a specific set of customizations on demand. Once you are finished adding your -new/updated objects to your customization record or change request, simply click **ReSpider Now** on +customization or a specific set of customizations on demand. After you finish adding your +new/updated objects to your customization record or change request, click **ReSpider Now** on your form, and your documentation is updated in real time. Here is an example of a customization record with the **ReSpider Now** option: ![ReSpiderNow](/images/platgovnetsuite/respider_now.webp) -Proposed customizations do not work for custom forms and custom reports, since they do not have -Script IDs. NetSuite is currently working on this, but it is still in development. For searches, -**ReSpider Now** uses the permissions of the current logged in user. If the user does not have the +Proposed customizations don't work for custom forms and custom reports, since they don't have +Script IDs. NetSuite is working on this. For searches, +**ReSpider Now** uses the permissions of the current logged-in user. If the user doesn't have the correct permission set, the search shows as private. From 04e03e98ca32c447ae6198e88c91b1f0d8c8ba3c Mon Sep 17 00:00:00 2001 From: jth-nw Date: Mon, 4 May 2026 17:52:41 -0500 Subject: [PATCH 15/27] fix(platgovnetsuite): resolve Dale linting issues across all docs Fixes passive voice, future tense, hedging language, positional references ("Here is/are"), temporal "once", wordiness, idioms, and informal tone across 96 files in the platgovnetsuite documentation. Generated with AI Co-Authored-By: Claude Code --- .../agent/agent_clear_incident.md | 8 +-- ...ent_creating_preapproved_change_request.md | 12 ++-- .../agent/agent_example_set_control.md | 4 +- ...ent_example_unresolved_control_incident.md | 5 +- .../agent/agent_getting_started.md | 4 +- docs/platgovnetsuite/agent/agent_lookback.md | 8 +-- docs/platgovnetsuite/agent/agent_overview.md | 16 ++--- ..._strongpoint_netsuite_7-0_release_notes.md | 23 +++---- ..._strongpoint_netsuite_7-1_release_notes.md | 50 ++++++-------- ..._strongpoint_netsuite_7-2_release_notes.md | 18 ++--- ..._strongpoint_netsuite_7-3_release_notes.md | 17 ++--- .../automated_search_cleanup.md | 28 +++----- .../bundleremoval/bundle_removal_overview.md | 10 +-- .../categorizing_customizations.md | 8 +-- .../creating_custom_list_and_fields.md | 2 +- .../creating_four_mass_updates.md | 3 +- .../creating_two_mass_updates.md | 6 +- .../exporting_information_to_excel.md | 7 +- .../bundleremoval/final_tasks.md | 14 +--- .../investigating_through_saved_searches.md | 6 +- .../change_management_reports.md | 20 ++---- .../approving_change_request.md | 8 +-- .../change_and_approval_policy.md | 5 +- .../change_management_overview.md | 12 +--- .../changing_deactivating_policies.md | 4 +- .../comparing_environments.md | 17 ++--- .../creating_change_request.md | 14 ++-- .../creating_change_request_from_case.md | 4 +- .../creating_change_request_old_form.md | 7 +- .../changemanagement/example_sample_change.md | 4 +- .../multi_environment_change_management.md | 11 ++- ..._record_changes_related_approved_change.md | 2 +- .../resolving_non_compliant_changes.md | 10 +-- .../setting_up_multi_stream_approval.md | 7 +- .../changemanagement/setting_up_policies.md | 18 ++--- .../setting_up_subsidiary_policies.md | 6 +- .../changemanagement/use_custom_cr_forms.md | 4 +- .../changemanagement/user_provisioning.md | 11 +-- .../changemanagement/using_change_logs.md | 9 +-- .../platgovnetsuite/cleanup/archive_fields.md | 8 +-- .../cleanup/cleanup_default_ids.md | 3 +- .../cleanup/cleanup_overview.md | 14 ++-- .../cleanup/cleanup_unused_customizations.md | 22 ++---- .../platgovnetsuite/cleanup/date_last_used.md | 6 +- .../platgovnetsuite/cleanup/restore_fields.md | 3 +- .../update_field_description_and_help.md | 4 +- .../identify_impacted_objects.md | 7 +- .../customization/integration_record.md | 7 +- .../understanding_customization_record.md | 7 +- .../customization/using_erd.md | 3 +- docs/platgovnetsuite/faq.md | 19 ++---- docs/platgovnetsuite/index.md | 23 +++---- .../installation/go_live_faq.md | 10 ++- .../installation/installation_overview.md | 7 +- .../installation_settings_report.md | 6 +- .../installation/installing_strongpoint.md | 6 +- .../installation/running_the_spider.md | 6 +- .../installation/setting_permissions.md | 2 +- .../setting_strongpoint_tab_access.md | 2 +- .../setting_up_auto_spider_alerts.md | 12 ++-- .../integrations/integration_mapping.md | 8 +-- .../reportabug/spider_spins.md | 3 +- .../scriptmgmt/script_mgmt_overview.md | 16 ++--- .../platgovnetsuite/sod/creating_sod_rules.md | 4 +- docs/platgovnetsuite/sod/sod_clean_up.md | 4 +- docs/platgovnetsuite/sod/sod_notifications.md | 6 +- docs/platgovnetsuite/sod/sod_overview.md | 4 +- docs/platgovnetsuite/sod/sod_reports.md | 2 +- .../sod/sod_test_case_scenarios.md | 7 +- .../apioverview/api_overview.md | 4 +- .../changerequestapi/change_request_api.md | 2 +- .../jiraforgeintegration/jira_forge_faq.md | 2 +- .../jiraforgeintegration/jira_forge_set_up.md | 48 ++++++------- .../jira_forge_walkthrough.md | 68 +++++++++---------- .../jiraintegration/jira_integration.md | 4 +- .../jira_walkthrough_example.md | 6 +- .../ticketingintegrations/process_issues.md | 6 +- .../zendeskintegration/zendesk_integration.md | 3 +- .../zendesk_walkthrough_example.md | 2 +- docs/platgovnetsuite/tools/tools_overview.md | 2 +- docs/platgovnetsuite/uar/access_app.md | 2 +- .../add_reviewer_overview.md | 2 +- .../add_reviewer_uar_list.md | 2 +- .../uar/adminoverview/admin_overview.md | 2 +- .../uar/adminoverview/admin_owner_list.md | 2 +- .../admin_pending_assignments.md | 2 +- .../uar/adminoverview/admin_uar_list.md | 4 +- .../adminoverview/owner_membership_reviews.md | 6 +- .../adminoverview/owner_permission_reviews.md | 8 +-- .../uar/auditoroverview/auditor_overview.md | 2 +- .../uar/owneroverview/owner_overview.md | 2 +- .../uar/owneroverview/owner_uar_list.md | 2 +- docs/platgovnetsuite/uar/uar_overview.md | 6 +- .../user_managment_overview.md | 2 +- .../what_does_strongpoint_document.md | 6 +- docs/platgovnetsuite/what_is_a_spider.md | 28 ++------ 96 files changed, 329 insertions(+), 549 deletions(-) diff --git a/docs/platgovnetsuite/agent/agent_clear_incident.md b/docs/platgovnetsuite/agent/agent_clear_incident.md index c3c4516eee..5fc424453b 100644 --- a/docs/platgovnetsuite/agent/agent_clear_incident.md +++ b/docs/platgovnetsuite/agent/agent_clear_incident.md @@ -6,10 +6,9 @@ sidebar_position: 50 # Clearing a Control Incident -Unresolved Control Incidents are filtered and displayed under the Unresolved Control Incidents -Report. +Unresolved Control Incidents appear in the Unresolved Control Incidents Report. -Here is the process to clear/resolve a control incident: +To clear or resolve a control incident: 1. Open **Strongpoint** > **Financial Controls** > **Unresolved Control Incidents** 2. Click the **Customization** to display the incidents. @@ -23,8 +22,7 @@ Here is the process to clear/resolve a control incident: The incident moves from **Unresolved Control Incident Log** to **Resolved Control Incident Log**. -Alternatively, you can complete this process by inline editing of the Unresolved Control Incidents -Report:: +You can also clear an incident by inline editing the Unresolved Control Incidents Report: 1. Click **EDIT** in the report tool bar. When enabled, it is green with a check mark. 2. Click the red pencil icon in the column head. Columns without the pencil icon can't be diff --git a/docs/platgovnetsuite/agent/agent_creating_preapproved_change_request.md b/docs/platgovnetsuite/agent/agent_creating_preapproved_change_request.md index a1bea0e7f9..0c4629c497 100644 --- a/docs/platgovnetsuite/agent/agent_creating_preapproved_change_request.md +++ b/docs/platgovnetsuite/agent/agent_creating_preapproved_change_request.md @@ -10,7 +10,7 @@ You can create a custom change request form for an Agent Preapproved Change Requ [Using Custom Change Request Forms](/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md) for information on implementing your custom form. -Here are the steps to create a pre-approved change request for a control: +To create a pre-approved change request for a control: 1. Open **Strongpoint** > **Financial Controls** > **New Agent Control Approval** @@ -46,12 +46,8 @@ Here are the steps to create a pre-approved change request for a control: - External Link - Parent Change Request -7. Click **Pending Approval** in the status bar when you are finished with the Change Request. A - confirmation prompt is displayed. When confirmed, Approval Notifications are sent to the - approvers. -8. Once approved, click **Completed** in the status bar to finish the Change Request. If rejected, - you can return the Change Request to **In Progress**, fix any issues, and resubmit it to - **Pending Approval**. +7. Click **Pending Approval** in the status bar when you finish the Change Request. A confirmation prompt appears. After you confirm, Approval Notifications are sent to the approvers. +8. After approval, click **Completed** in the status bar to finish the Change Request. If rejected, return the Change Request to **In Progress**, fix any issues, and resubmit it for **Pending Approval**. ### Status Bar States @@ -75,7 +71,7 @@ Approvers are notified. Status can be demoted. -Status promoted based on Approvers actions. +Status advances based on approver actions. ![change_request_bar_approved](/images/platgovnetsuite/change_management/change_request_bar_approved.webp) diff --git a/docs/platgovnetsuite/agent/agent_example_set_control.md b/docs/platgovnetsuite/agent/agent_example_set_control.md index fdc8f34c33..4fcb3eaecf 100644 --- a/docs/platgovnetsuite/agent/agent_example_set_control.md +++ b/docs/platgovnetsuite/agent/agent_example_set_control.md @@ -6,7 +6,7 @@ sidebar_position: 60 # Example: Set an Agent Control -Here is the process to create a control to monitor changes: +To create a control to monitor changes: 1. Create a Saved Search 2. Create the Customization Record @@ -81,7 +81,7 @@ From the customization record: it here. - **Risk/Requirement**: Assign or create a new Control Process and Risk Requirement. For example, **1259 Purchase Order Controls**. -- **Control Error/Warning**: warnings or errors are displayed in this box. +- **Control Error/Warning**: displays warnings or errors. - **Cross Match Control**, **Cross Match Field** and **Cross Match Operator** can be set to effectively perform a double join to filter your data and eliminate false positives. For example, a script to create an invoice from the user interface is saved to be run as administrator. A user diff --git a/docs/platgovnetsuite/agent/agent_example_unresolved_control_incident.md b/docs/platgovnetsuite/agent/agent_example_unresolved_control_incident.md index 8ae1af2491..cf0dbf9d24 100644 --- a/docs/platgovnetsuite/agent/agent_example_unresolved_control_incident.md +++ b/docs/platgovnetsuite/agent/agent_example_unresolved_control_incident.md @@ -6,10 +6,7 @@ sidebar_position: 70 # Example: Unresolved Control Incident -A modification has been made to the **Purchase Limit** and **Purchase Approval Limit** for Luigi -Derossi from 0.00 to 5,000.00. The change has been saved and the control has been run from the -Customization record. Since the change was made without prior approval, the change is logged and can -be found under **Unresolved Control Incidents**. +The **Purchase Limit** and **Purchase Approval Limit** for Luigi Derossi were modified from 0.00 to 5,000.00. The change was saved and the control was run from the Customization record. Because the change was made without prior approval, it is logged under **Unresolved Control Incidents**. To view unresolved control incidents: diff --git a/docs/platgovnetsuite/agent/agent_getting_started.md b/docs/platgovnetsuite/agent/agent_getting_started.md index 507c860eba..e106fd6a5f 100644 --- a/docs/platgovnetsuite/agent/agent_getting_started.md +++ b/docs/platgovnetsuite/agent/agent_getting_started.md @@ -13,7 +13,7 @@ controls / searches you need. | Role | Description | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Control Owner | Defaults to the person that creates the control, but can be changed.
Receives alerts when a violation occurs.
May be a Change Request Approver to Pre-approve / Authorize related changes. | +| Control Owner | Defaults to the person who creates the control, but can be changed.
Receives alerts when a violation occurs.
Can be a Change Request Approver to pre-approve or authorize related changes. | | Control Assignee | Manages the process risk.
Receives alerts when a violation occurs.
Approves Change Requests to Pre-approve / Authorize related changes. | | Process Owner | Owns the Process and associated material risk.
Receives alerts when a violation occurs.
Receives periodic control reports.
Approves Change Requests to Pre-approve / Authorize related changes. | @@ -23,4 +23,4 @@ controls / searches you need. | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Record Control | Tracks all changes to the record (Customer, Vendor, Employee, Item)
Any changes trigger a violation record / alert. | | Record Field Control | Tracks changes to specified fields in a record.
Changes on the specified fields trigger a violation record / alert. | -| Transactional Data Control | Tracks changes to transaction records and events
Search types may be Journal entries, Checks, Bills, and so on.
This data type can be monitored as a whole (i.e. any changes
additions, modifications, deletions), or specified (e.g. only Journal entries that have been modified after being approved, or journal entries entered and approved by the same user, or list of ad-hoc checks only, and so on). | +| Transactional Data Control | Tracks changes to transaction records and events.
Search types include Journal entries, Checks, Bills, and so on.
This data type can be monitored as a whole (any changes, additions, modifications, deletions), or narrowed to specific events (for example, Journal entries modified after approval, journal entries entered and approved by the same user, or ad-hoc checks only). | diff --git a/docs/platgovnetsuite/agent/agent_lookback.md b/docs/platgovnetsuite/agent/agent_lookback.md index fae3d0eeba..89d36469dc 100644 --- a/docs/platgovnetsuite/agent/agent_lookback.md +++ b/docs/platgovnetsuite/agent/agent_lookback.md @@ -10,7 +10,7 @@ _Agent Lookback_ gives **Enterprise** license customers the capability to run an a specified past date through the current date. The control is run in single day batches, simulating a daily run. -The Agent Lookback is accessed from the Customization record for the control. +Access Agent Lookback from the Customization record for the control. 1. Open **Strongpoint** > **Financial Controls** > **Controls**. 2. **Edit** the control to run. @@ -25,10 +25,8 @@ The Agent Lookback is accessed from the Customization record for the control. 7. Add the details and click **Set**. 8. Click **Add** . 9. Click **Save**. -10. The **Lookback Start Date** and **Lookback Next Date** are now populated on your Customization - record. -11. **Save** the customization record. The Lookback agent runs single day batches for the specified - dates. +10. The **Lookback Start Date** and **Lookback Next Date** are populated on your Customization record. +11. **Save** the customization record. The Lookback agent runs single-day batches for the specified dates. ### Lookback Run diff --git a/docs/platgovnetsuite/agent/agent_overview.md b/docs/platgovnetsuite/agent/agent_overview.md index 7e9598a89f..48773aab06 100644 --- a/docs/platgovnetsuite/agent/agent_overview.md +++ b/docs/platgovnetsuite/agent/agent_overview.md @@ -9,10 +9,9 @@ sidebar_position: 130 Use Agent to monitor and manage the creation, deletion, or change of key records and fields associated with transactional and master data as well as system critical settings by: -- Filling in the gaps left by Segregation of Duties (SoD) by providing monitoring and documentation - of situations such as: +- Filling gaps left by Segregation of Duties (SoD) by monitoring and documenting situations such as: - Positional authority conflicts: having the power to override controls. - - Admin / Full access user: having permissions to do just about anything in the system. + - Admin / Full access user: having permissions to perform any action in the system. - Turning basic saved searches into powerful monitoring controls by automatically checking on them on an hourly, daily, weekly, monthly, or quarterly basis. - Capturing the results of saved searches into an immutable Change Log. @@ -24,13 +23,10 @@ associated with transactional and master data as well as system critical setting record level. - Creating tasks and issues automatically and assigning to specific employees when a control violation takes place. -- Extending NetSuite capabilities with cross-match functionality to easily perform a double JOIN in - your search. +- Extending NetSuite capabilities with cross-match functionality to perform a double JOIN in your search. -Check out Netwrix University for helpful tutorials. -[Sign in to your Netwrix account](https://www.netwrix.com/my_training.html) to access the NS3-2 -Agent Financial Controls series. Contact your Customer Success Manager if you don't have access to -Netwrix University. +Netwrix University offers tutorials for Agent Financial Controls. +[Sign in to your Netwrix account](https://www.netwrix.com/my_training.html) to access the NS3-2 Agent Financial Controls series. Contact your Customer Success Manager if you don't have access to Netwrix University. ## Agent Control Categories @@ -60,7 +56,7 @@ match for the control incident result. Yes, the Change Request’s Customization field can accommodate multiple Control records. All of the controls listed under the Customization field are associated with the Change Request. -##### How Agent handles Pre-approvals when the control results are grouped (i.e. Group Results In Alert checkbox is marked in the Control setting) +##### How Agent handles Pre-approvals when the control results are grouped (the Group Results In Alert checkbox is marked in the Control setting) When the results are grouped, all results must match the Change Request Control filters for the Change Log to be a pre-approved incident. diff --git a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-0_release_notes.md b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-0_release_notes.md index b15a3a1024..6364b618eb 100644 --- a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-0_release_notes.md +++ b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-0_release_notes.md @@ -33,9 +33,7 @@ June 16, 2023 - **Autospider**, **Manual Spider** and **ReSpider Now** now support French (both France and Canada) for Strongpoint customers using French in NetSuite. -- **Changed By No HTML** and **Diff No HTML** result options are available for customizing your - Searches. Specifying use these options to export the Change Management Reports with the - fields in plain text, removing the HTML tags to improve readability. +- **Changed By No HTML** and **Diff No HTML** result options are available for customizing your Searches. Use these options to export the Change Management Reports with fields in plain text, removing HTML tags to improve readability. - Open **Strongpoint** > **Change Management Reports** > _report_name_ > **Customize**. - Click **Edit this Search**. @@ -56,8 +54,7 @@ May 16, 2023 changes are now handled as platform changes, and don't generate non-compliant change logs for user roles. - You must manually resolve any of the non-compliant changes system generated before this - release. This update isn't retroactive. + Manually resolve any non-compliant changes the system generated before this release. This update isn't retroactive. - Added a **Print** button to all Change Request screens. @@ -96,17 +93,17 @@ content, not the status. Copied change requests are set to the **Not Started** s ## Jira 1.2.13 -Here are the enhancements for the release: +The following are the enhancements for the release: - Change customization name to allow Single quotes ('). - Added **Location** to the **Type** dropdown on the **Add Proposed Customization** form. ## Jira 1.2.11 -Here are the enhancements for the release: +The following are the enhancements for the release: - Import Customizations from Jira -- Enable Allow NS to Jira Push (must be done before creating a ticket from NetSuite to Jira) +- Enable Allow NS to Jira Push (must be done before creating a ticket from NetSuite to Jira) - Create Ticket from NetSuite to Jira - Change customization name to allow Single quotes ('). - Added **Group** to the **Type** dropdown on the **Add Proposed Customization** form. @@ -117,7 +114,7 @@ An **Import Customization** button has been added to the Jira Strongpoint form. xml file exported from a Jira ticket. ![Jira Strongpoint form](/images/platgovnetsuite/release_notes/jira_strongpoint_form.webp) -### Enable Allow NS to Jira Push +### Enable Allow NS to Jira Push This feature must be enabled before you can create tickets from NetSuite to Jira. @@ -137,7 +134,7 @@ Jira. 3. Click **Push to Jira**. 4. Select your Jira project. ![Select a Jira Project](/images/platgovnetsuite/release_notes/jira_ns_jira_push2.webp) -5. Click **Push**. A Change Request Pushed message is displayed. Click **Close**. +5. Click **Push**. A Change Request Pushed message appears. Click **Close**. 6. Open the **Related Change Records** tab. The ticket number is added as an **External Change Request Number**. **CM-15** in this example. ![The ticket number is on the Related Change Records tab](/images/platgovnetsuite/release_notes/jira_create_cr_related_change.webp) @@ -149,16 +146,14 @@ Jira. ## Jira 1.2.10 -Here are the enhancements for the release: +The following are the enhancements for the release: - Credentials are now persistent, and don't need to be entered every time. - Strongpoint Settings page added to Jira ### Strongpoint Settings for Jira -The Strongpoint Settings app is accessed through Jira. This is where you create your Token Based -Authentication (TBA) credentials for your account. Once created, they are available to you for easy -selection when performing your tasks. +The Strongpoint Settings app is accessed through Jira. Use it to create your Token Based Authentication (TBA) credentials for your account. After creation, they are available for easy selection when performing your tasks. Token-Based Authentication is set up through NetSuite. Refer to [Setting up Token-Based Authentication](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md). diff --git a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-1_release_notes.md b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-1_release_notes.md index c0da088f07..9a67b75306 100644 --- a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-1_release_notes.md +++ b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-1_release_notes.md @@ -10,10 +10,8 @@ sidebar_position: 30 November 30, 2023 -- Support links are changing December 1st, the new link is - [https://www.netwrix.com/support.html](https://www.netwrix.com/support.html) -- NetSuite changes, such a moving an account to a different datacenter, are now treated as a - Platform change. They don't create a non-compliant Change Log record. +- Support links changed December 1st. The new link is [https://www.netwrix.com/support.html](https://www.netwrix.com/support.html). +- NetSuite changes, such as moving an account to a different datacenter, are now treated as a Platform change. They don't create a non-compliant Change Log record. - Improved handling of custom employee center roles across the Strongpoint spiders. - Bundle updates were enabling **Automatic Synchronization** between Strongpoint and Jira, changing settings where **Automatic Synchronization** was disabled. **Automatic Synchronization** defaults @@ -67,29 +65,26 @@ September 20, 2023 ![Refresh Changed By](/images/platgovnetsuite/change_management/change_log_refresh.webp) -- Removed extraneous Customization record link in Search Clean Up notification emails. - Non-Strongpoint users receive the notification and can't use the link. +- Removed an extraneous Customization record link in Search Clean Up notification emails. Non-Strongpoint users who receive the notification cannot use the link. ## Core 7.1 August 23, 2023 -Every release may contain enhancements internally and customer-specific bug fixes to keep -Strongpoint running smoothly. +Every release contains internal enhancements and customer-specific bug fixes to keep Strongpoint running smoothly. **NetSuite Release 2023.2 Support** The Strongpoint Searches have been updated to support NetSuite's change of **Formula (Text) Fields** to the new **Formula (HTML) Fields**. This is a NetSuite security enhancement. -Strongpoint 7.1 must be installed before the NetSuite 2023.2 release to ensure a smooth upgrade: +Install Strongpoint 7.1 before the NetSuite 2023.2 release to ensure a smooth upgrade: -1. Install Strongpoint 7.1 in your Sandbox August 15th. -2. Test Strongpoint 7.1 before August 22nd. Contact your Customer Success Manager if you have - questions. -3. Strongpoint 7.1 will be pushed to your production environment starting August 23rd. +1. Install Strongpoint 7.1 in your Sandbox by August 15th. +2. Test Strongpoint 7.1 before August 22nd. Contact your Customer Success Manager if you have questions. +3. Strongpoint 7.1 was pushed to your production environment starting August 23rd. -NetSuite will begin pushing release 2023.2 the end of August. +NetSuite began pushing release 2023.2 at the end of August. If you have custom searches, you must update them to support the NetSuite change. To view the list of saved searches in your account that contain code in **Formula(Text)** fields, open: @@ -127,22 +122,19 @@ NetSuite Release 2023.2 Support The Strongpoint Searches have been updated to support NetSuite's change of **Formula (Text) Fields** to the new **Formula (HTML) Fields**. This is a NetSuite security enhancement. -Strongpoint 7.1 and SoD 1.6 must be installed before the NetSuite 2023.2 release to ensure a -smooth upgrade: +Install Strongpoint 7.1 and SoD 1.6 before the NetSuite 2023.2 release to ensure a smooth upgrade: -1. Install Strongpoint 7.1 and SoD 1.6 in your Sandbox August 15th. -2. Test Strongpoint 7.1 and SoD 1.6 before August 22nd. Contact your Customer Success Manager if you - have questions. -3. Strongpoint 7.1 and SoD 1.6 will be pushed to your production environment starting August 23rd. +1. Install Strongpoint 7.1 and SoD 1.6 in your Sandbox by August 15th. +2. Test Strongpoint 7.1 and SoD 1.6 before August 22nd. Contact your Customer Success Manager if you have questions. +3. Strongpoint 7.1 and SoD 1.6 were pushed to your production environment starting August 23rd. -NetSuite will begin pushing release 2023.2 the end of August. +NetSuite began pushing release 2023.2 at the end of August. ## Jira 1.3 November 30, 2023 -- Support links are changing December 1st, the new link is - [https://www.netwrix.com/support.html](https://www.netwrix.com/support.html) +- Support links changed December 1st. The new link is [https://www.netwrix.com/support.html](https://www.netwrix.com/support.html). ## Jira 1.2.16 @@ -169,14 +161,14 @@ September 27, 2023 ## Jira 1.2.13 -Here are the enhancements for the release: +The following are the enhancements for the release: - Change customization name to allow Single quotes ('). - Added **Location** to the **Type** dropdown on the **Add Proposed Customization** form. ## Jira 1.2.11 -Here are the enhancements for the release: +The following are the enhancements for the release: - Import Customizations from Jira - Enable Allow NS to Jira Push (must be done before creating a ticket from NetSuite to Jira) @@ -210,7 +202,7 @@ Jira. 3. Click **Push to Jira**. 4. Select your Jira project. ![Select a Jira Project](/images/platgovnetsuite/release_notes/jira_ns_jira_push2.webp) -5. Click **Push**. A Change Request Pushed message is displayed. Click **Close**. +5. Click **Push**. A Change Request Pushed message appears. Click **Close**. 6. Open the **Related Change Records** tab. The ticket number is added as an **External Change Request Number**. **CM-15** in this example. ![The ticket number is on the Related Change Records tab](/images/platgovnetsuite/release_notes/jira_create_cr_related_change.webp) @@ -222,16 +214,14 @@ Jira. ## Jira 1.2.10 -Here are the enhancements for the release: +The following are the enhancements for the release: - Credentials are now persistent, and don't need to be entered every time. - Strongpoint Settings page added to Jira Strongpoint Settings for Jira -The Strongpoint Settings app is accessed through Jira. This is where you create your Token Based -Authentication (TBA) credentials for your account. Once created, they are available to you for easy -selection when performing your tasks. +The Strongpoint Settings app is accessed through Jira. Use it to create your Token Based Authentication (TBA) credentials for your account. After creation, they are available for easy selection when performing your tasks. Token-Based Authentication is set up through NetSuite. Refer to [Setting up Token-Based Authentication](/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md). diff --git a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-2_release_notes.md b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-2_release_notes.md index c20398a2fa..e719fd4d31 100644 --- a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-2_release_notes.md +++ b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-2_release_notes.md @@ -14,21 +14,21 @@ December 22, 2023 **New:** **Strongpoint Integration API** -Strongpoint is excited to release an [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) to enable your +Strongpoint is excited to release an [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) to enable your developers to support your ticketing systems! Customers enthusiastically embraced the Strongpoint -pre-built integrations for Jira, ServiceNow, and Zendesk. The API makes this integration +pre-built integrations for Jira, ServiceNow, and Zendesk. The API makes this integration functionality available to everyone. Integrating your systems with your Strongpoint account helps you make the most of your change management and ticketing strategies. -Here are the API highlights: +API highlights: - **Customizations** can be retrieved from your NetSuite account and can be added and removed from your Change Requests. - **Change Requests** can be created, updated, retrieved, and deleted. -- **ERD** and **Impact Analysis** tools are available. -- API commands are documented in the [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) section of this +- **ERD** and **Impact Analysis** tools are available. +- API commands are documented in the [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) section of this guide. -- API commands are available in [Postman](http://postman.com/), where you can try them out and test +- API commands are available in [Postman](http://postman.com/), where you can try them out and test them. There are Postman links in this guide. **New: Strongpoint Reset Schedule Deployments Suitelet for Sandbox Refresh** @@ -41,7 +41,7 @@ after a sandbox refresh. 1. Open your Sandbox. 2. Open **Customization** > **Scripting** > **Scripts**. -3. Set the Filter **Type** to **Suitelet** and the **Bundle ID** to **294336**. +3. Set the Filter **Type** to **Suitelet** and the **Bundle ID** to **294336**. ![Find the Suitelet](/images/platgovnetsuite/release_notes/scripts.webp) @@ -60,7 +60,7 @@ after a sandbox refresh. December 19, 2023 - Changed the format of the **Reason for Exemption** column on the **Strongpoint SoD Change Requests - (List)** report to **Formula Text**. Due to NetSuite 2023.2 changes, HTML tags were displaying in + (List)** report to **Formula Text**. Due to NetSuite 2023.2 changes, HTML tags were displaying in the report. Refer to NetSuite Release 2023.2 Support for more details on the NetSuite change. - Improved handling of inline edits on Employee names. Making an inline name change doesn't affect open SoD Exemptions for the employee. @@ -72,6 +72,6 @@ to the new **Formula (HTML) Fields**. This is a NetSuite security enhancement. If you have custom searches, you must update them to support the NetSuite change. To view the list of saved searches in your account that contain code in **Formula(Text)** fields, open: -**Lists** > **Search** > **Saved Searches with HTML in Formula(Text)** +**Lists** > **Search** > **Saved Searches with HTML in Formula(Text)** ![Run the Saved Search to view changes](/images/platgovnetsuite/release_notes/formulahtml.webp) diff --git a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-3_release_notes.md b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-3_release_notes.md index 04bf64de0f..fd93ca0753 100644 --- a/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-3_release_notes.md +++ b/docs/platgovnetsuite/archive/netwrix_strongpoint_netsuite_7-3_release_notes.md @@ -59,24 +59,15 @@ New: **Formula Update in Searches** The **Strongpoint Open Noncompliant Changes**, **Strongpoint What Changed**, and **Open Noncompliant Changes - Audit** searches criteria has been updated. -As part of an ongoing effort to minimize non-material change logs and save time on reporting, Netwrix -has reviewed and updated some of the filters in the non-compliant and what changed compliance -reports. +As part of an ongoing effort to minimize non-material change logs and save time on reporting, Netwrix reviewed and updated some of the filters in the non-compliant and what-changed compliance reports. -A filter was discovered in the search criteria that could cause change logs to be excluded. This -filter was used during the implementation of change detection through the autospider portlet, to -filter out duplicate logs caused by late reconciliation of changes done by the scheduling processes. With the -improved process scheduling, the filter is no longer needed. +A filter in the search criteria could cause change logs to be excluded. This filter was used during the implementation of change detection through the autospider portlet to filter out duplicate logs caused by late reconciliation of changes made by the scheduling processes. With the improved process scheduling, the filter is no longer needed. -For some accounts, this may result in additional change logs from previous periods in these reports. -These logs were always available on the customization records and the original change log -information will not have changed. +For some accounts, this may result in additional change logs from previous periods in these reports. These logs were always available on the customization records and the original change log information has not changed. New: Jira On-Prem -Atlassian is discontinuing support for the Jira On-Prem solution. Jira Cloud will be the only -supported option. You can use the Strongpoint [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) to create -your own integration with your ticketing system. +Atlassian discontinued support for the Jira On-Prem solution. Jira Cloud is the only supported option. Use the Strongpoint [Integration API](/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md) to create your own integration with your ticketing system. **Resolved Issues** diff --git a/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup.md b/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup.md index 3f58b12eff..da93e62a6f 100644 --- a/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup.md +++ b/docs/platgovnetsuite/automatedsearchcleanup/automated_search_cleanup.md @@ -16,9 +16,7 @@ before using this feature. Saved Searches are powerful customizations used throughout NetSuite and interconnected to other customizations. As user-created Saved Searches proliferate, NetSuite accounts become inefficient and -overall performance degrades. This rules-based tool provides administrators the ability to identify -and archive Saved Searches and keep NetSuite accounts organized, easy to understand, and improve -efficiency and performance. Archived searches can be restored with limitations. +overall performance degrades. This rules-based tool enables administrators to identify and archive Saved Searches and keep NetSuite accounts organized, efficient, and easy to understand. Archived searches can be restored with limitations. The **Automated Search Clean Up** tool has two operating modes: @@ -136,8 +134,7 @@ Lists any searches excluded after the **Preview** function is used. The **Preview** function provides a quick method to mark Saved Searches to be retained or to included for clean up. The Run Now feature begins an immediate run for the rule. -1. Administrators can click **Preview** on an Search Clean Up Rule. **Preview** displays the rule, - filters and conditions. +1. Click **Preview** on a Search Clean Up Rule. **Preview** displays the rule, filters, and conditions. 2. Review the Search List. Check **Include** to trigger a final notification email to be sent to the owner/user. Check **Retain Search** to keep the search. @@ -150,7 +147,7 @@ included for clean up. The Run Now feature begins an immediate run for the rule. ### Run Now -This option immediately begins an Search Clean Up using the current rule. +This option immediately begins a Search Clean Up using the current rule. If a Saved Search matches the Clean Up Rule: @@ -223,9 +220,7 @@ Click **Notification Tracker** on the **Notifications** tab to launch the tracke ### Notification Tracker -Accesses all of the communications and history for search clean ups. You can list all notifications -sent by rule or by the job. Provides traceability between the clean up rules, clean up jobs, and -email notifications. +Accesses all communications and history for search clean ups. List all notifications sent by rule or by job. Provides traceability between the clean up rules, clean up jobs, and email notifications. ![cleanup_notification_tracker](/images/platgovnetsuite/clean_up/cleanup_notification_tracker.webp) @@ -252,29 +247,24 @@ The Retain process: - Updates the **Date Last Used, Retained/Restored** to the current date. - Adds the search to the **Automated Search Clean Up** > **Retained Searches** report. The **Search Retain Reason** is shown on this report. -- Notifies the owners/users the search will be retained. +- Notifies the owners/users that the search is retained. ## Auto Archiving a Search -If search owners or users don't click **Retain this search** in the email notifications, the -search is archived. The Archive process: +If search owners or users don't click **Retain this search** in the email notifications, the search is archived. The Archive process: - Archives the search. - Adds the search to the **Automated Search Clean Up** > **Archived Searches** report. - Marks Customization record for the search **Inactive**. -- A **Restore** button is added to the **Clean Up** tab on the customization record for the search. +- A **Restore** button appears on the **Clean Up** tab on the customization record for the search. - Auto Archive notifications are sent to the rule owner and administrators. A **Restore** link is included in the email. ## Restoring an Auto Archived Search -A NetSuite Administrator can restore an auto archived search with some limitations. Open the **Clean -Up** tab of the Customization record for the search or the report **Automated Search Clean Up** > -**Archived Searches**. Click **Restore**. Or use the **Restore** link in the email sent to the rule -owner and administrators. +A NetSuite Administrator can restore an auto archived search with some limitations. Open the **Clean Up** tab of the Customization record for the search, or the **Automated Search Clean Up** > **Archived Searches** report. Click **Restore**, or use the **Restore** link in the email sent to the rule owner and administrators. -- Search is restored with limitations. Restored searches have a different internal ID from their - original version, resetting the audit trail. +- Search is restored with limitations. Restored searches have a different internal ID from the original version, resetting the audit trail. - Updates the **Date Last Used, Retained/Restored** to the current date. - Adds the search to the **Automated Search Clean Up** > **Retained Searches** list. diff --git a/docs/platgovnetsuite/bundleremoval/bundle_removal_overview.md b/docs/platgovnetsuite/bundleremoval/bundle_removal_overview.md index 663ef9f433..b24f876a81 100644 --- a/docs/platgovnetsuite/bundleremoval/bundle_removal_overview.md +++ b/docs/platgovnetsuite/bundleremoval/bundle_removal_overview.md @@ -12,7 +12,7 @@ updates and saved searches. By following the bundle removal process, the current Customizations that are built on top of a bundle can cause issues or break when the bundle is removed. Platform Governance for NetSuite helps you determine what could cause issues or break if you remove the bundle by: -- Safely and easily recognizing which customizations are built on top of the bundle. +- Recognizing which customizations are built on top of the bundle. - Seeing how customizations relate to different components. - Detecting all the components that don't connect to any object in your NetSuite account. - Identifying and separating objects that have the possibility of breaking. @@ -35,10 +35,7 @@ To remove a bundle: possible, find a TAM resource that is familiar with Platform Governance for NetSuite as well as is familiar with the bundle type that you are trying to remove. - **Developer and/or Administrator**: Depending on how your business processes are built around - your scripts, when you remove the bundle the associated scripts will be removed as well. A - developer and/or administrator should be assigned to investigate the scripts, see what scripts - need to be recreated and rebuild them. + **Developer and/or Administrator**: When you remove the bundle, the associated scripts are removed as well. Assign a developer or administrator to investigate the scripts, identify which scripts need to be recreated, and rebuild them. 2. Document your account. If Platform Governance for NetSuite is already installed and running in your account, you can run a manual spider to update your account. If you have a new account, @@ -48,5 +45,4 @@ To remove a bundle: 5. Create Saved Searches and export/import CSV files (where applicable). 6. Export the information to Excel. -The process should be completed in your sandbox environment to see how it affects your other -environments (production). +Complete the process in your sandbox environment to see how it affects your other environments (production). diff --git a/docs/platgovnetsuite/bundleremoval/categorizing_customizations.md b/docs/platgovnetsuite/bundleremoval/categorizing_customizations.md index 59fa9927a4..6f96153bcb 100644 --- a/docs/platgovnetsuite/bundleremoval/categorizing_customizations.md +++ b/docs/platgovnetsuite/bundleremoval/categorizing_customizations.md @@ -6,13 +6,9 @@ sidebar_position: 30 # Categorizing Customizations -Part of the bundle removal process is to categorize all the customizations in your account, this is -completed with saved searches and csv imports and exports (due to some limitations with mass -updates). +Categorizing all customizations in your account is part of the bundle removal process. This is done with saved searches and CSV imports and exports, because mass updates don't have summary criteria for this type of search. -Bundle components that don't have relationships outside the bundle or customizations that aren't -related to the bundle need to be flagged with CSV imports/exports since mass updates don't have -summary criteria for this type of search. +Bundle components that don't have relationships outside the bundle, or customizations that aren't related to the bundle, must be flagged with CSV imports and exports. ## Create First Saved Search diff --git a/docs/platgovnetsuite/bundleremoval/creating_custom_list_and_fields.md b/docs/platgovnetsuite/bundleremoval/creating_custom_list_and_fields.md index 94ccb85cb7..813271b5e9 100644 --- a/docs/platgovnetsuite/bundleremoval/creating_custom_list_and_fields.md +++ b/docs/platgovnetsuite/bundleremoval/creating_custom_list_and_fields.md @@ -6,7 +6,7 @@ sidebar_position: 20 # Creating a Custom List and Fields -Seven custom fields and one custom list needs to be created for the bundle’s customization records. +Create seven custom fields and one custom list for the bundle’s customization records. The custom list holds six different values to view the different scenarios that are covered. The customization records have one custom field to show the name of the scenario that the customization belongs to and six different check boxes, one for each scenario. diff --git a/docs/platgovnetsuite/bundleremoval/creating_four_mass_updates.md b/docs/platgovnetsuite/bundleremoval/creating_four_mass_updates.md index 07f17506e4..6debc2154d 100644 --- a/docs/platgovnetsuite/bundleremoval/creating_four_mass_updates.md +++ b/docs/platgovnetsuite/bundleremoval/creating_four_mass_updates.md @@ -6,8 +6,7 @@ sidebar_position: 40 # Creating Four Mass Updates -After you have created the first two mass updates and the two saved searches, you need to follow a -similar process to ensure the rest of the objects have been included for the bundle removal. +After you create the first two mass updates and the two saved searches, follow a similar process to include the remaining objects for the bundle removal. ## Mass Update Scenario 3 diff --git a/docs/platgovnetsuite/bundleremoval/creating_two_mass_updates.md b/docs/platgovnetsuite/bundleremoval/creating_two_mass_updates.md index f9820d86dd..5f8d6cf124 100644 --- a/docs/platgovnetsuite/bundleremoval/creating_two_mass_updates.md +++ b/docs/platgovnetsuite/bundleremoval/creating_two_mass_updates.md @@ -8,8 +8,7 @@ sidebar_position: 10 ## First Mass Update -The first mass update flags all the bundle components to be cleaned up and set the status on the -Customization to **To Be Cleaned Up**. It identifies everything needing removal. +The first mass update flags all the bundle components for cleanup and sets the status on the Customization to **To Be Cleaned Up**. It identifies everything needing removal. To create the first mass update: @@ -43,8 +42,7 @@ You can remove more than one bundle at a time. ## Second Mass Update -The second mass update flags all the objects related to the bundle and sets a status on the -Customization to **To Be Investigated**. It identifies everything needing investigation. +The second mass update flags all the objects related to the bundle and sets the Customization status to **To Be Investigated**. It identifies everything needing investigation. 1. Open **Lists** > **Mass Update** > **Mass Updates** 2. Open **General Updates** > **Custom Records** > **Customization** diff --git a/docs/platgovnetsuite/bundleremoval/exporting_information_to_excel.md b/docs/platgovnetsuite/bundleremoval/exporting_information_to_excel.md index 3e70e3730f..87c6ae6ffd 100644 --- a/docs/platgovnetsuite/bundleremoval/exporting_information_to_excel.md +++ b/docs/platgovnetsuite/bundleremoval/exporting_information_to_excel.md @@ -6,9 +6,7 @@ sidebar_position: 60 # Exporting Information to Excel -You can export the information from the removal scenarios to Excel and then search for the -customizations affected by the bundle removal. Here is an example of using the removal scenarios 5 -and 6 to find affected customizations. +Export the information from the removal scenarios to Excel to search for customizations affected by the bundle removal. The following example uses removal scenarios 5 and 6 to find affected customizations. - Scenario 5: **Outside bundle referencing inside**. All customizations built in the account that make use of the bundle components. @@ -30,7 +28,6 @@ To find the relationships that only exist within the bundle: 1. Copy the name of a record. 2. Go to the opposite scenario and do a search with the pasted name. -3. This shows you the bundle components that are being used so you are aware of what will be removed - when the bundle is gone. These are the records that need to be replicated. +3. This shows the bundle components in use so you know what is removed when the bundle is gone. These are the records that need to be replicated. **Next Step:** [Final Tasks](/docs/platgovnetsuite/bundleremoval/final_tasks.md) diff --git a/docs/platgovnetsuite/bundleremoval/final_tasks.md b/docs/platgovnetsuite/bundleremoval/final_tasks.md index 34a140fb8f..5fee4ccb47 100644 --- a/docs/platgovnetsuite/bundleremoval/final_tasks.md +++ b/docs/platgovnetsuite/bundleremoval/final_tasks.md @@ -8,23 +8,13 @@ sidebar_position: 70 ## Reviewing Critical and Non Critical Sheets -**Critical sheets** include all customizations that make use of the bundle components. You should -ensure you are aware of what these bundle components are doing and analyze the risks of removing -them. Specifically, you should review the customizations from scenarios 3 and 6: Scenario 3: are -non-bundle components that are used by bundle components, so there may be fields that are set by -scripts, workflows, or searches that belong to the bundle. Scenario 6: are non-bundle components that -use at least one bundle component for something, so their functionality and/or display may be -broken. +**Critical sheets** include all customizations that use bundle components. Review what these bundle components do and analyze the risks of removing them. Specifically, review the customizations from scenarios 3 and 6: Scenario 3 covers non-bundle components used by bundle components, so there may be fields set by scripts, workflows, or searches that belong to the bundle. Scenario 6 covers non-bundle components that use at least one bundle component, so their functionality or display may break. **Non critical sheets** include all the customizations from scenarios 1, 2, 4, and 5. ## Testing -Testing should occur in the sandbox environment first. Retest functionality after the bundle removal -to ensure everything is working as expected. As part of the testing, run the -[Comparing Environments](/docs/platgovnetsuite/changemanagement/comparing_environments.md) tool to see all the -differences after the bundle removal (sandbox vs. production). It helps you determine what needs to -be moved to the production environment. +Test in the sandbox environment first. Retest functionality after the bundle removal to confirm everything works as expected. Run the [Comparing Environments](/docs/platgovnetsuite/changemanagement/comparing_environments.md) tool to see all the differences after the bundle removal (sandbox vs. production). This helps you determine what needs to be moved to the production environment. After you remove the bundle from your production environment, run a post deployment check to make sure everything is the same between the sandbox and production environments. diff --git a/docs/platgovnetsuite/bundleremoval/investigating_through_saved_searches.md b/docs/platgovnetsuite/bundleremoval/investigating_through_saved_searches.md index 5de06136c9..3c3d6077e1 100644 --- a/docs/platgovnetsuite/bundleremoval/investigating_through_saved_searches.md +++ b/docs/platgovnetsuite/bundleremoval/investigating_through_saved_searches.md @@ -6,11 +6,9 @@ sidebar_position: 50 # Investigating Through Saved Searches -After running all the mass updates and CSV imports (where needed), you can build six saved searches, -one for each scenario. Within each scenario you can easily identify all the customizations for -further investigation. +After running all the mass updates and CSV imports (where needed), build six saved searches, one for each scenario. Within each scenario you can identify all the customizations for further investigation. -Included in the results columns of these saved searches, you will find the following fields: +The results columns of these saved searches include the following fields: - **Name**: to identify the customization. - **ScriptID**: to locate the customization. diff --git a/docs/platgovnetsuite/change_management_reports.md b/docs/platgovnetsuite/change_management_reports.md index da9cc35fd7..85501d2ced 100644 --- a/docs/platgovnetsuite/change_management_reports.md +++ b/docs/platgovnetsuite/change_management_reports.md @@ -23,7 +23,7 @@ Open **Strongpoint** > **Change Management Reports** and one of the available re ## Policy Changes -This report displays policy changes. This is used by change managers to monitor policies. +This report displays policy changes. Change managers use it to monitor policies. The criteria for this report includes: @@ -31,8 +31,7 @@ The criteria for this report includes: ## Open Non-Compliant Changes -This report displays non-compliant changes that have not been resolved. This is used by change -managers to track changes that require action. +This report displays non-compliant changes that have not been resolved. Change managers use it to track changes that require action. The criteria for this report includes: @@ -47,8 +46,7 @@ The criteria for this report excludes: ## Resolved Non-Compliant Changes -This report displays non-compliant changes that have been resolved. This is used by change managers -and auditors to review non-complaint changes that have been resolved. +This report displays non-compliant changes that have been resolved. Change managers and auditors use it to review non-compliant changes that have been resolved. The criteria for this report includes: @@ -63,9 +61,7 @@ The criteria for this report excludes: ## Compliant Changes -This report displays changes that the system has automatically cleared as compliant. Compliant -changes are automatically marked as closed. This is used by Change Managers and auditors to review -changes that have been automatically cleared as compliant. +This report displays changes that the system automatically cleared as compliant. Compliant changes are automatically marked as closed. Change Managers and auditors use it to review changes that have been automatically cleared as compliant. The criteria for this report includes: @@ -79,8 +75,7 @@ The criteria for this report excludes: ## Approval Override -This report displays changes with an Approval Override. This is used by Change Managers and auditors -to review changes that have been approved outside of the specified approval process. +This report displays changes with an Approval Override. Change Managers and auditors use it to review changes approved outside the specified approval process. The criteria for this report includes: @@ -143,7 +138,7 @@ The criteria for this report excludes: - Non-material Platform changes -Here is the criteria for non-material changes: +The criteria for non-material changes: - System generated changes. - XML changes that don't directly affect the object definition. For example, Script Deployment @@ -183,8 +178,7 @@ The criteria for this report excludes: ## What Changed -This report is used by Change Managers to view a complete listing of all changes in the system -excluding non-material changes. +This report gives Change Managers a complete listing of all changes in the system, excluding non-material changes. The criteria for this report includes: diff --git a/docs/platgovnetsuite/changemanagement/approving_change_request.md b/docs/platgovnetsuite/changemanagement/approving_change_request.md index 993ba4530d..cb5a46568e 100644 --- a/docs/platgovnetsuite/changemanagement/approving_change_request.md +++ b/docs/platgovnetsuite/changemanagement/approving_change_request.md @@ -19,12 +19,8 @@ NetSuite users and have the correct 2. When the Change Request opens, **Approve** and **Reject** buttons are available at the top of the form: - - If all approvers approve the Change Request, the status is changed to **Approved** or - **Approved (Override)** if an administrator approved it. Implement the changes specified by - the Change Request. - - If an approver rejects the Change Request, the status is changed to **Rejected**. You can - return the Change Request to **In Progress**, edit it, and reset it to **Pending Approval** if - there are errors or omissions. + - If all approvers approve the Change Request, the status changes to **Approved** or **Approved (Override)** if an administrator approved it. Implement the changes specified by the Change Request. + - If an approver rejects the Change Request, the status changes to **Rejected**. Return the Change Request to **In Progress**, edit it, and reset it to **Pending Approval** if there are errors or omissions. 3. Change Request owner [Completes and Validates the Change Request](/docs/platgovnetsuite/changemanagement/completing_validating_change_request.md). diff --git a/docs/platgovnetsuite/changemanagement/change_and_approval_policy.md b/docs/platgovnetsuite/changemanagement/change_and_approval_policy.md index 0692993939..cee81cf420 100644 --- a/docs/platgovnetsuite/changemanagement/change_and_approval_policy.md +++ b/docs/platgovnetsuite/changemanagement/change_and_approval_policy.md @@ -38,8 +38,7 @@ For example, a company may have multiple policies. For example: - **Controls Policy** applies to key reports and controls listed on the policy that need specific approval to modify and ensures there are no changes without a proper audit review. -Once in place, the policies remind users of the level of change management required as well as -monitors the changes that do occur and raises alerts to IT if there are any change violations. +When policies are in place, they remind users of the level of change management required and monitor changes that occur, raising alerts to IT for any change violations. You can create a custom change request form for a Policy Approval. Refer to [Using Custom Change Request Forms](/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md) for information on implementing your @@ -51,7 +50,7 @@ Non-material changes are changes detected in objects that aren't performed by a have functional impact. You can review these changes on the [Non-Material Changes report](/docs/platgovnetsuite/change_management_reports.md). -Here is the criteria for non-material changes: +The criteria for non-material changes: - System generated changes. - XML changes that don't directly affect the object definition. For example, Script Deployment diff --git a/docs/platgovnetsuite/changemanagement/change_management_overview.md b/docs/platgovnetsuite/changemanagement/change_management_overview.md index 9a02aa72c7..488051e5ea 100644 --- a/docs/platgovnetsuite/changemanagement/change_management_overview.md +++ b/docs/platgovnetsuite/changemanagement/change_management_overview.md @@ -20,9 +20,7 @@ Platform Governance for NetSuite extends your current change management system s - Manage deployments and sandbox refreshes using best practices. :::note -Once a change request is complete, best practice is to change the status to **Completed**. If there -are multiple open change requests referencing the same object, any changes to the object result in -the change log being associated with the oldest of the approved change requests. +When a change request is complete, change the status to **Completed**. If there are multiple open change requests referencing the same object, any changes to the object are associated with the oldest of the approved change requests. ::: ## Plan, Approve, and Deploy Changes @@ -73,15 +71,11 @@ processes, customizations, and clean up activities. ### Confirm with a Deployment Record -When tracking Full Software Development Lifecycle changes, use the Deployment Record to -track deployment approvals. Once a Change Request is approved, this documents a change is ready for -development. At this point, a new change request with the Stage Deployment Record can be created and -tracked. +When tracking full software development lifecycle changes, use the Deployment Record to track deployment approvals. After a Change Request is approved, this documents that a change is ready for development. At this point, create and track a new change request with the Stage Deployment Record. This enables: - Tracking of deployment activities. -- Documentation of approvals for deployment to document that any changes that occurred during - development have been approved and that the appropriate pre-deployment checks have been completed. +- Documentation of approvals for deployment, confirming that changes that occurred during development have been approved and that the appropriate pre-deployment checks have been completed. This record is linked to the original change request to enable end to end reporting of the change. diff --git a/docs/platgovnetsuite/changemanagement/changing_deactivating_policies.md b/docs/platgovnetsuite/changemanagement/changing_deactivating_policies.md index ac67baef56..359b2d264f 100644 --- a/docs/platgovnetsuite/changemanagement/changing_deactivating_policies.md +++ b/docs/platgovnetsuite/changemanagement/changing_deactivating_policies.md @@ -6,9 +6,7 @@ sidebar_position: 40 # Changing or Deactivating Policies -Policy records determine the non compliance level of changes. Given that changes to these records -has a direct impact on the compliance levels, document, and approve any -modifications. You can deactivate or modify policies with an open and approved change request. +Policy records determine the noncompliance level of changes. Because changes to these records directly affect compliance levels, document and approve all modifications. You can deactivate or modify policies with an open and approved change request. This diagram shows the overall process of what happens when you update a policy: diff --git a/docs/platgovnetsuite/changemanagement/comparing_environments.md b/docs/platgovnetsuite/changemanagement/comparing_environments.md index 5e1529c9f8..64f8f0f805 100644 --- a/docs/platgovnetsuite/changemanagement/comparing_environments.md +++ b/docs/platgovnetsuite/changemanagement/comparing_environments.md @@ -6,10 +6,7 @@ sidebar_position: 170 # Comparing Environments -Compare Environments is a powerful tool to locate customization differences between accounts. It is -a best practice to compare accounts by type (this is a mandatory field). You can compare up to 1000 -records. If there are more than 1000 records, it compares the first 1000 and sends you a -notification that there were more than 1000 records to compare and to restrict the comparison. +Compare Environments locates customization differences between accounts. Compare accounts by type (this is a mandatory field). You can compare up to 1000 records. If there are more than 1000 records, the tool compares the first 1000 and notifies you to restrict the comparison. - Set up TBA Credentials - Run Compare Environments @@ -39,7 +36,7 @@ Environments and to use the **Change Account** feature on a Change Requests. - **Token ID** enter your token ID. - **Token Secret** enter your token secret. -4. Click **Save**. Your credentials are now saved for the environment. +4. Click **Save**. The credentials are saved for the environment. Repeat this process for all environments you use for environment compare or looking up customizations with the **Change Account** feature on a Change Request. Refer to @@ -61,7 +58,7 @@ TBA Credentials** section the first time you use this feature. 2. Enter the information for the target account and source accounts. Tokens are persistent between your sessions. -Here are the field and filter options. +The following are the field and filter options. :::note Only administrators can view the Consumer Key, Consumer Secret, Token ID and Token Secret @@ -135,7 +132,7 @@ When using filters, use only one filter at a time. An exception is using ### Pre-Deployment :::note -If you are migrating new objects, they won't exist in your target account. +New objects being migrated don't exist in the target account yet. ::: To determine what to compare pre-deployment: @@ -162,11 +159,9 @@ To determine what to compare post-deployment: ### Communicating Results -An **Environment Compare Log** is created, and automatically linked to the Change Request for -reference. The log can be shared if there are issues. +An **Environment Compare Log** is created and automatically linked to the Change Request for reference. Share the log if there are issues. -If there are issues, the Deployment Engineer can make changes and re-run the Environment Comparison -to ensure the environments are synchronized. +If there are issues, the Deployment Engineer can make changes and re-run the Environment Comparison to ensure the environments are synchronized. ## Viewing Differences Between Environments diff --git a/docs/platgovnetsuite/changemanagement/creating_change_request.md b/docs/platgovnetsuite/changemanagement/creating_change_request.md index 4ef803fc88..d08a4d241f 100644 --- a/docs/platgovnetsuite/changemanagement/creating_change_request.md +++ b/docs/platgovnetsuite/changemanagement/creating_change_request.md @@ -6,9 +6,7 @@ sidebar_position: 70 # Creating a Change Request -Before making any changes, understand the scope of the planned change, potential -impacts and the level of change required. Documentation is also available if you are using the old -[Change Request](/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md) form. Refer to +Before making any changes, understand the scope of the planned change, potential impacts, and the level of change required. Documentation is also available if you are using the old [Change Request](/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md) form. Refer to [Setting Preferred Forms](/docs/platgovnetsuite/customization/setting_preferred_forms.md) for information on designating your preferred Change Request form. @@ -58,7 +56,7 @@ request in your sandbox account. - Enter a **Script File** name and click **Lookup** to find a customization by all or part of the script file name. For example, **26** shows everything beginning with **26**. - Use multiple filters to further refine your search. For example, **Name** starting with - **a** and **Type** of **List** show all **List** customizations starting with **A**. Once + **a** and **Type** of **List** show all **List** customizations starting with **A**. After the customizations are displayed: - Hover over **Details** to see specifics of the customization. - Click the box(es) to select one or more customizations. Check in the **Name** header to @@ -156,9 +154,7 @@ request in your sandbox account. - External Link - Parent Change Request -5. Click **Pending Approval** in the status bar when you are finished with the Change Request. A - confirmation prompt is displayed. When confirmed, Approval Notifications are sent to the - approvers. +5. Click **Pending Approval** in the status bar when you finish the Change Request. A confirmation prompt appears. After you confirm, Approval Notifications are sent to the approvers. ![change_request_new_pendapprove](/images/platgovnetsuite/change_management/change_request_new_pendapprove.webp) @@ -178,7 +174,7 @@ You can Cancel a Change Request: 3. Confirm cancellation when prompted. 4. Click **Save**. -Status is changed to **Cancelled CR**. +Status changes to **Cancelled CR**. ## Status Bar States @@ -206,7 +202,7 @@ Approval section added to the Change Request. Status can be demoted. -Status promoted based on Approvers actions. +Status advances based on approver actions. ![change_request_bar_approved](/images/platgovnetsuite/change_management/change_request_bar_approved.webp) diff --git a/docs/platgovnetsuite/changemanagement/creating_change_request_from_case.md b/docs/platgovnetsuite/changemanagement/creating_change_request_from_case.md index a728ba0f36..1e6c0b400f 100644 --- a/docs/platgovnetsuite/changemanagement/creating_change_request_from_case.md +++ b/docs/platgovnetsuite/changemanagement/creating_change_request_from_case.md @@ -14,9 +14,7 @@ is enabled, you can automatically create a Change Request directly from your Cas 2. **View** a Case. 3. Click **Create Change Request**. -The Change Request is created, populating the fields specified in the -[Case to Change Request Field Mapping](/docs/platgovnetsuite/installation/installation_settings_report.md) -set up. The Change Request status is set to **Not Started**. +The Change Request is created with the fields specified in the [Case to Change Request Field Mapping](/docs/platgovnetsuite/installation/installation_settings_report.md) setup. The Change Request status is set to **Not Started**. If the **Create Change Request** button isn't visible on the Case, the [Enable Case to Change Request Workflow](/docs/platgovnetsuite/installation/installation_settings_report.md) diff --git a/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md b/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md index 60d19acd32..f29d8e968b 100644 --- a/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md +++ b/docs/platgovnetsuite/changemanagement/creating_change_request_old_form.md @@ -55,11 +55,8 @@ To do this, in your **production** account: are safe to change. - **Change Request:** you are planning on changing objects that require approval to change. -6. Click **Impact Analysis**. This will show you how objects are connected to other things. -7. Scroll down to the bottom of the page and click the **Impact Analysis** tab.This shows you - which customization records can or can't be safely modified as well as customizations that are - inactive. You see a list of the customization records that have been included, and warnings for - impacted customization records that need to be investigated before you make a change. +6. Click **Impact Analysis**. This shows how objects are connected to other things. +7. Scroll down to the bottom of the page and click the **Impact Analysis** tab. This shows which customization records can or can't be safely modified, as well as customizations that are inactive. You see a list of the customization records that have been included, and warnings for impacted customization records that need to be investigated before you make a change. ![impactanalysissubtab](/images/platgovnetsuite/change_management/impactanalysissubtab.webp) diff --git a/docs/platgovnetsuite/changemanagement/example_sample_change.md b/docs/platgovnetsuite/changemanagement/example_sample_change.md index efe1335957..1d1787aab8 100644 --- a/docs/platgovnetsuite/changemanagement/example_sample_change.md +++ b/docs/platgovnetsuite/changemanagement/example_sample_change.md @@ -13,7 +13,7 @@ sidebar_position: 160 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. 5. Click **In Progress** in the status bar. -6. Click **Save**. The Change Level Required, Current Stage and Change Policy are displayed. +6. Click **Save**. The Change Level Required, Current Stage, and Change Policy appear. 7. For this example: If you aren't an **Approver**: @@ -52,7 +52,7 @@ sidebar_position: 160 ## Create a Non-Compliant Change -This change will be flagged as non-compliant and appear on the report as **Non-Compliant**. +This change is flagged as non-compliant and appears on the report as **Non-Compliant**. 1. Change the **Entity Field** (for example, apply it to **Project**) and click **Save**. 2. Open the Customization Record. diff --git a/docs/platgovnetsuite/changemanagement/multi_environment_change_management.md b/docs/platgovnetsuite/changemanagement/multi_environment_change_management.md index 6259bce5cb..554abb9fe6 100644 --- a/docs/platgovnetsuite/changemanagement/multi_environment_change_management.md +++ b/docs/platgovnetsuite/changemanagement/multi_environment_change_management.md @@ -24,8 +24,7 @@ least the Strongpoint Developer Role to perform a Change Request Push. ## Create a Master Change Request in Production -A best practice is to create change requests in your production account so that they aren't lost, -they have an audit trail and approvals can be shown. +Create change requests in your production account so they aren't lost, maintain an audit trail, and show approvals. 1. Open **Strongpoint** > **Change Management Tools** > **ITGC Change Request**. 2. Enter all required fields and additional approvers. @@ -33,7 +32,7 @@ they have an audit trail and approvals can be shown. 4. Open **Strongpoint** > **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). +7. Set the **Target** environment (where the Change Request is pushed). 8. Set the Target log in credentials: **Target Email and Target Password**. 9. Set the **Account ID Target** (this is automatically loaded upon selecting Target account). 10. Set the **Account Target Role**. @@ -67,8 +66,7 @@ they have an audit trail and approvals can be shown. ## Create the Deployment Record -After you have compared your environments, get the deployment record approved. When your deployment -record is approved, deploy the customizations listed on the change request. +After you compare your environments, get the deployment record approved. When approved, deploy the customizations listed on the change request. In your Production environment: @@ -93,8 +91,7 @@ In your Production environment: ## Completing the Process -If testing fails, continue to update the Change Request on Testing/Development and comparing the -environments until test passes. Once testing passes: +If testing fails, continue to update the Change Request on Testing/Development and compare the environments until tests pass. After testing passes: 1. Edit the Change Request in Testing/Development. diff --git a/docs/platgovnetsuite/changemanagement/opportunisticclearance/example_record_changes_related_approved_change.md b/docs/platgovnetsuite/changemanagement/opportunisticclearance/example_record_changes_related_approved_change.md index 877986ad36..73980affb7 100644 --- a/docs/platgovnetsuite/changemanagement/opportunisticclearance/example_record_changes_related_approved_change.md +++ b/docs/platgovnetsuite/changemanagement/opportunisticclearance/example_record_changes_related_approved_change.md @@ -16,7 +16,7 @@ Administrator needs to enable custom record field's Show in List option. ![opp_clearance_case3-1](/images/platgovnetsuite/change_management/opp_clearance_case3-1.webp) 2. IT Approvers approve the change. -3. updates the custom field. No script is using the parent record of the field. +3. Administrator updates the custom field. No script uses the parent record of the field. **Expected Result** diff --git a/docs/platgovnetsuite/changemanagement/resolving_non_compliant_changes.md b/docs/platgovnetsuite/changemanagement/resolving_non_compliant_changes.md index ddf4dacaea..d8cd641747 100644 --- a/docs/platgovnetsuite/changemanagement/resolving_non_compliant_changes.md +++ b/docs/platgovnetsuite/changemanagement/resolving_non_compliant_changes.md @@ -15,10 +15,7 @@ To access the Open Non-Compliant Changes Report: ![Non-Compliant Change Report](/images/platgovnetsuite/change_management/noncompliantreport.webp) ![NonCompliant Flags](/images/platgovnetsuite/change_management/noncompliant_flags.webp) -2. A noncompliant change means something got changed without the required approvals. **View** each - change log record to investigate the change, or use the Mass Update procedure. You can - retroactively attach a change request to a noncompliant change and get the necessary approvals - for the change to be compliant. +2. A noncompliant change means a change occurred without the required approvals. **View** each change log record to investigate the change, or use the Mass Update procedure. Retroactively attach a change request to a noncompliant change and get the necessary approvals for the change to be compliant. 1. Create a New [Change Request](/docs/platgovnetsuite/changemanagement/creating_change_request.md) or open an existing one. 2. Set it to **Pending Approval**. @@ -27,13 +24,12 @@ To access the Open Non-Compliant Changes Report: 5. Enter the **Related Change Request**. 6. Enter the **Related Process Issue** if applicable. 7. Enter the **Resolution Description**. - 8. Once all changes are made, select **Closed** for the **Status**. + 8. After all changes are made, select **Closed** for the **Status**. 9. **Save** the Change Log. ## Resolving Open Non-Compliant Changes Using Mass Update -There are occasions where you want to resolve Open Non-Compliant Change Logs without going through -each one manually. For example, if your Change and Approval Policy was incorrectly set-up or if it +There are occasions where you need to resolve Open Non-Compliant Change Logs without going through each one manually. For example, if your Change and Approval Policy was incorrectly set-up or if it was in place before your Go-Live. For these scenarios Netwrix recommends you create a **Mass Update** to resolve all applicable incidents. diff --git a/docs/platgovnetsuite/changemanagement/setting_up_multi_stream_approval.md b/docs/platgovnetsuite/changemanagement/setting_up_multi_stream_approval.md index 6cce676c08..3e38e600de 100644 --- a/docs/platgovnetsuite/changemanagement/setting_up_multi_stream_approval.md +++ b/docs/platgovnetsuite/changemanagement/setting_up_multi_stream_approval.md @@ -6,10 +6,7 @@ sidebar_position: 60 # Setting Up Multi-Stream Approval -This process enables an administrator to select approvers other than the IT Approvers outlined on -the Policy. The administrator selects the approvers in the order they will approve the request. The -process owner is the final approver. This differs from selecting Additional Approvers from the -Change Request, where the mandated approvers are included. +This process enables an administrator to select approvers other than the IT Approvers outlined on the Policy. The administrator selects the approvers in the order they approve the request. The process owner is the final approver. This differs from selecting Additional Approvers from the Change Request, where the mandated approvers are included. ## Configure Multi-Stream Approval @@ -23,7 +20,7 @@ Change Request, where the mandated approvers are included. 1. Open **Strongpoint** > **Manage Processes** > **Process** > **New** 2. Enter the **Name** and **Owner** for the process. For this example, the name is **Provision Multi-Stream Approval**. -3. **Custom Form** and **Step Type** should be set to **Process**. +3. Set **Custom Form** and **Step Type** to **Process**. 4. Ctrl-Click to select one or more **Additional Approvers**. NOTE: Select the additional approvers in the order you want them to approve. diff --git a/docs/platgovnetsuite/changemanagement/setting_up_policies.md b/docs/platgovnetsuite/changemanagement/setting_up_policies.md index a42a99e1e4..bb29ff2711 100644 --- a/docs/platgovnetsuite/changemanagement/setting_up_policies.md +++ b/docs/platgovnetsuite/changemanagement/setting_up_policies.md @@ -63,9 +63,7 @@ required for changes to the objects to be compliant with this policy. ### Change Levels -**No Logs Created**: changes to these objects update the customization documentation is updated but -doesn't create change logs. A warning text is displayed when the Administrator sets the change -level to **No Logs Created**. +**No Logs Created**: changes to these objects update the customization documentation but don't create change logs. A warning appears when the Administrator sets the change level to **No Logs Created**. **Log Changes Only**: changes to these objects are automatically marked compliant. @@ -158,9 +156,7 @@ This section is only applies to the default policy. **ITGC Approvers** -Groups are an efficient method to specify approvers. For example, if you need one approver from each -of several company functions, you can create a group for each functional area, and select a minimum -of 1 approval. Once each group has approved, the policy moves on to the **Final Approver**. +Groups are an efficient method to specify approvers. For example, if you need one approver from each of several company functions, create a group for each functional area and select a minimum of 1 approval. After each group approves, the policy moves on to the **Final Approver**. - **Group Name**: enter a descriptive name to identify the approvers. - **Approvers**: click in the entry box and select approvers from the available user list. @@ -231,10 +227,7 @@ Segregation of Duties Policies specify the approvers for this policy. ## Set Up Additional Policies -In some cases, you may want stricter controls on certain objects. For example, many public -companies create a specific policy for SOX related searches, since they want it tighter than Log -Only for those objects. To set up object specific policies, the initial spider must be complete, so -you can attach the Customization Record to the policy. +In some cases, you need stricter controls on certain objects. For example, many public companies create a specific policy for SOX-related searches when they need tighter controls than Log Only. To set up object-specific policies, the initial spider must be complete so you can attach the Customization Record to the policy. To set up additional policies: @@ -262,10 +255,9 @@ To set up additional policies: - Select the customization. - Click **Attach**. -9. Click **Save** when you are finished adding customizations to the Policy. +9. Click **Save** when you finish adding customizations to the Policy. -Another method to add customization is through NetSuite's **Mass Update**. Here is the basic -process. See the NetSuite help for details on Mass Update. +Another method to add customizations is through NetSuite's **Mass Update**. The basic process follows. See the NetSuite help for details on Mass Update. 1. Open **Lists** > **Mass Updates** 2. Expand **General Updates** > **Custom Records** > **Customization** diff --git a/docs/platgovnetsuite/changemanagement/setting_up_subsidiary_policies.md b/docs/platgovnetsuite/changemanagement/setting_up_subsidiary_policies.md index 7c4a25198c..aaf0d5853b 100644 --- a/docs/platgovnetsuite/changemanagement/setting_up_subsidiary_policies.md +++ b/docs/platgovnetsuite/changemanagement/setting_up_subsidiary_policies.md @@ -6,11 +6,7 @@ sidebar_position: 30 # Setting Up Subsidiary Policies -Use Subsidiary Approval to set subsidiary-specific policies based on the employees using a -customization. Once an administrator sets up a change policy for a subsidiary, the subsidiary -approvers are set for the process, and the process is attached to the policy. Subsidiary Processes -are automatically created by the spider. Employees using customizations are evaluated and Employee -subsidiaries and corresponding Subsidiary Processes are set to the customization. +Use Subsidiary Approval to set subsidiary-specific policies based on the employees using a customization. After an administrator sets up a change policy for a subsidiary, the subsidiary approvers are set for the process and the process is attached to the policy. The spider automatically creates Subsidiary Processes. Employees using customizations are evaluated, and Employee subsidiaries and corresponding Subsidiary Processes are set on the customization. To set up Subsidiary Approvals: diff --git a/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md b/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md index 7c5867a60a..77eac55507 100644 --- a/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md +++ b/docs/platgovnetsuite/changemanagement/use_custom_cr_forms.md @@ -6,9 +6,7 @@ sidebar_position: 80 # Using Custom Change Request Forms -You can create custom change request forms for ITGC, Agent Pre-Approval, SoD Rule Change, SoD -Approval, Policy Approval and User Provisioning. After you have created your custom forms, modify the -Script Deployment Parameters to use your forms. +You can create custom change request forms for ITGC, Agent Pre-Approval, SoD Rule Change, SoD Approval, Policy Approval, and User Provisioning. After you create your custom forms, modify the Script Deployment Parameters to use your forms. 1. Open **Customization** > **Scripting** > **Scripts** 2. Search for **customdeploy_flo_display_cr** diff --git a/docs/platgovnetsuite/changemanagement/user_provisioning.md b/docs/platgovnetsuite/changemanagement/user_provisioning.md index 6d151920e6..a5f0daa24b 100644 --- a/docs/platgovnetsuite/changemanagement/user_provisioning.md +++ b/docs/platgovnetsuite/changemanagement/user_provisioning.md @@ -58,9 +58,7 @@ custom form. 6. **Save** the change request. 7. Click **Pending Approval** in the status bar. -After the request is approved, the roles are automatically added if you enabled -**Auto-Provisioning**. The change request status is shown as **Complete**. Otherwise, after the -request is approved, you need to manually add the roles and update the status. +After the request is approved, the roles are automatically added if **Auto-Provisioning** is enabled. The change request status shows as **Complete**. Otherwise, after the request is approved, manually add the roles and update the status. A compliant Change Log is generated: @@ -73,8 +71,7 @@ The **Values** tab shows the details of the role changes. 1. Open **Strongpoint** > **Change Management Tools** > **User Provisioning Change Request**. 2. Enter a descriptive **Name** and **Change Overview**. 3. Select **Role Reductions** for **Access type**. The Offboarding detail fields are now visible. -4. Check **Inactivate After Removal** if the affected employees should be inactivated. This should - only be checked if you are removing all of the employee's roles. +4. Check **Inactivate After Removal** if the affected employees should be inactivated. Only check this if you are removing all of the employee's roles. 5. Enter one or more **Affected Employees**. The **Get Roles for Affected Employees** button is now visible. @@ -91,9 +88,7 @@ The **Values** tab shows the details of the role changes. 10. **Save** the change request. 11. Click **Pending Approval** in the status bar. -After the request is approved, the roles are automatically removed at the specified time if you -enabled **Auto-Role Removal**. The change request status is shown as **Complete**. Otherwise, once -the request is approved, you need to manually remove the roles and update the status. +After the request is approved, the roles are automatically removed at the specified time if **Auto-Role Removal** is enabled. The change request status shows as **Complete**. Otherwise, after the request is approved, manually remove the roles and update the status. A compliant Change Log is generated. The **Values** tab shows the details of the role changes. diff --git a/docs/platgovnetsuite/changemanagement/using_change_logs.md b/docs/platgovnetsuite/changemanagement/using_change_logs.md index 6a25e73828..fdb6050056 100644 --- a/docs/platgovnetsuite/changemanagement/using_change_logs.md +++ b/docs/platgovnetsuite/changemanagement/using_change_logs.md @@ -11,9 +11,7 @@ the NetSuite record. Change Logs are accessed from the [Change Management Reports](/docs/platgovnetsuite/change_management_reports.md). :::note -Once a change request is complete, best practice is to change the status to **Completed**. If there -are multiple open change requests referencing the same object, any changes to the object result in -the change log being associated with the oldest of the approved change requests. +When a change request is complete, change the status to **Completed**. If there are multiple open change requests referencing the same object, any changes to the object are associated with the oldest of the approved change requests. ::: To open a Change Log: @@ -119,14 +117,13 @@ The **Values** tab displays the changes that occurred in the Change Log. ## Finding Users Who Have Made Changes -When you want to find out who has made changes, you can run any of the Change Reports and view who -made a change in the **Change By** column. +To find out who has made changes, run any of the Change Reports and view who made a change in the **Change By** column. The **Change By** and **Actual Date** of the change logs are retrieved using System Notes Search for supported record types. If a System Note isn't available, **Change By** displays **Could Not Be Determined** in the Report List. -Recorded types that aren't supported can be retrieved from the AutoSpider. +Record types that aren't supported can be retrieved from the AutoSpider. | Supported Records for System Notes Search | Change By retrieved from the AutoSpider | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | diff --git a/docs/platgovnetsuite/cleanup/archive_fields.md b/docs/platgovnetsuite/cleanup/archive_fields.md index 644839f5ad..b5d6ae60e2 100644 --- a/docs/platgovnetsuite/cleanup/archive_fields.md +++ b/docs/platgovnetsuite/cleanup/archive_fields.md @@ -6,9 +6,7 @@ sidebar_position: 70 # Archive Fields -When cleaning up your account with Platform Governance for NetSuite clean up tools, you may find -fields that are no longer in use and you want to delete them. To do this you need to create a Change -Request and add the fields you want to delete. +When cleaning up your account with Platform Governance for NetSuite clean up tools, you may find fields that are no longer in use and need to be deleted. Create a Change Request and add the fields you want to delete. ## Create a Change Request to Archive Fields @@ -33,6 +31,4 @@ Deleted or Modified** and under **Warning it says Not Archived** ![archivefields2](/images/platgovnetsuite/clean_up/archivefields2.webp) -7. Once your customizations are processed and archived, your customizations are listed under **Can be -Safely Deleted or Modified**. Your [archive folder](/docs/platgovnetsuite/cleanup/set_up_archive_folder.md) has the CSV file you -can download. The file name has the field type and the script ID. +7. After your customizations are processed and archived, they appear under **Can be Safely Deleted or Modified**. Your [archive folder](/docs/platgovnetsuite/cleanup/set_up_archive_folder.md) contains the CSV file you can download. The file name includes the field type and the script ID. diff --git a/docs/platgovnetsuite/cleanup/cleanup_default_ids.md b/docs/platgovnetsuite/cleanup/cleanup_default_ids.md index 44823875ca..f0012e9cc8 100644 --- a/docs/platgovnetsuite/cleanup/cleanup_default_ids.md +++ b/docs/platgovnetsuite/cleanup/cleanup_default_ids.md @@ -6,8 +6,7 @@ sidebar_position: 30 # Clean Up Scripts with Default IDs -Default IDs significantly increase the cost and risks associated with any development work, and are -a critical clean up practice. +Default IDs significantly increase the cost and risk associated with development work and represent a critical clean up practice. 1. Open **Strongpoint** > **Clean Up** > **Default ID** 2. Review each item to determine how they should be modified if their identifier is changed. diff --git a/docs/platgovnetsuite/cleanup/cleanup_overview.md b/docs/platgovnetsuite/cleanup/cleanup_overview.md index 3b273a8be1..dac167732a 100644 --- a/docs/platgovnetsuite/cleanup/cleanup_overview.md +++ b/docs/platgovnetsuite/cleanup/cleanup_overview.md @@ -102,8 +102,7 @@ Change Requests can be created and managed through: ### Organize the Results -The results can be sorted and filtered and are required to group and manage the output for -subsequent steps. You may chose to clean up based on process or record type. +The results can be sorted and filtered to group and manage the output for subsequent steps. Choose to clean up based on process or record type. Every Customization record has a Clean-Up Status field to track the status of the clean-up process for that object. @@ -116,7 +115,7 @@ The statuses are: - **Under Investigation**: A holding status while deciding what to do. - **Disabled/Hidden**:Tracks that the customization has been disabled. - **Archive**: Tracks that the data / set-up was archived. -- **Deleted**: Tracks that the customization has been deleted. The doc will be inactivated. +- **Deleted**: Tracks that the customization has been deleted. The doc is inactivated. - **Ignore**: Removes it from the searches. - **Specific tasks**: Fix Script Id and Reassign Owner. @@ -129,10 +128,7 @@ You can report on these statuses to organize your work. Some changes such as deletion, changes to scriptID, and Help impact the customization itself. For these types of changes, create a Change Request. -However, for Clean Up, you can create new change requests and assign them to the customizations. In -the results view, “Create Change Request” creates a new change request. After it is added to that -customization it will appear under “Related Change Requests”. You can have multiple customizations -assigned to multiple change requests as appropriate. +For Clean Up, create new change requests and assign them to the customizations. In the results view, “Create Change Request” creates a new change request. After it is added to that customization, it appears under “Related Change Requests”. You can assign multiple customizations to multiple change requests as appropriate. ![faq-clean-up-create-change-req](/images/platgovnetsuite/clean_up/faq-clean-up-create-change-req.webp) @@ -148,6 +144,4 @@ The Change Request has archiving and deletion tools to help clean up the account ### ReSpider -At the end of the process of updating the customization record, the account should be re-spidered to -update the Customization Records that document the customizations that were changed. It can be -re-spidered just for a particular record type that is all that was changed. +At the end of the process of updating the customization record, re-spider the account to update the Customization Records that document the changed customizations. Re-spider just for a particular record type if that is all that was changed. diff --git a/docs/platgovnetsuite/cleanup/cleanup_unused_customizations.md b/docs/platgovnetsuite/cleanup/cleanup_unused_customizations.md index 5938d0364e..4afe4c1ae9 100644 --- a/docs/platgovnetsuite/cleanup/cleanup_unused_customizations.md +++ b/docs/platgovnetsuite/cleanup/cleanup_unused_customizations.md @@ -6,17 +6,9 @@ sidebar_position: 10 # Clean Up Unused Customizations -Platform Governance for NetSuite has powerful tools to analyze, organize, and delete unused -customizations in a safe and secure manner. - -Cleaning up fields has a direct impact on system performance. Larger records load slower than small -ones. When a record loads in NetSuite, the system formulates the SQL request, retrieves the data -from the database, assembles the interface, retrieves any related list data or build the -corresponding interface element (in edit mode) amongst other steps. While these are all highly -optimized, records with large field sizes load slower. There can also be impact on system -performance from alerts and other searches applied on demand to data when it is being saved -(particularly if there are custom SQL formulas). The impact is dependent on the extent of the change -and what else is causing performance lag. +Platform Governance for NetSuite has tools to analyze, organize, and delete unused customizations safely. + +Cleaning up fields directly affects system performance. Larger records load slower than smaller ones. When a record loads in NetSuite, the system formulates the SQL request, retrieves the data from the database, assembles the interface, and retrieves any related list data or builds the corresponding interface element (in edit mode), among other steps. Although these are all highly optimized, records with large field sizes load slower. Alerts and other searches applied on demand when data is saved can also affect system performance, especially when custom SQL formulas are involved. The impact depends on the extent of the change and other sources of performance lag. You can organize clean up activities by record types to start with larger groups of customizations before progressing to individual customizations. For example you could progress in the following @@ -114,8 +106,7 @@ practices to determine if it is appropriate to delete any of the customizations. ## Archive Field Data -Once a Change Request has been approved the **Archive Customizations** button is available. When -clicked, any fields in the change request are archived and stored in the **File Cabinet**. +After a Change Request is approved, the **Archive Customizations** button is available. When clicked, any fields in the change request are archived and stored in the **File Cabinet**. ![archive](/images/platgovnetsuite/clean_up/archive.webp) @@ -124,8 +115,7 @@ Deleted or Modified** tab. ## Back Up Searches, Scripts, and Workflows -While there is no mass un-delete functionality, critical information about scripts, searches, and -workflows are preserved in the Customization Record. +There is no mass un-delete functionality, but critical information about scripts, searches, and workflows is preserved in the Customization Record. - **Searches**: All fields, filters, criteria, and other search elements are documented in the Searches tab. @@ -145,4 +135,4 @@ There are two choices for deleting customizations: ## Close the Change Request -Once all activities are complete, mark the change request as complete. +After all activities are complete, mark the change request as complete. diff --git a/docs/platgovnetsuite/cleanup/date_last_used.md b/docs/platgovnetsuite/cleanup/date_last_used.md index 831151d73c..60d0143caa 100644 --- a/docs/platgovnetsuite/cleanup/date_last_used.md +++ b/docs/platgovnetsuite/cleanup/date_last_used.md @@ -6,8 +6,7 @@ sidebar_position: 50 # Date Last Used -Use Date Last Used (DLU) to see what customizations haven't been used recently and could be -deleted. +Use Date Last Used (DLU) to identify customizations that haven't been used recently and can be deleted. Date Last Used (DLU) is captured for changes triggered by users or other customizations. Platform Governance for NetSuite uses a System Notes search to retrieve the date last used for Fields, Saved @@ -55,8 +54,7 @@ Used field. **Searches**: - For searches the DLU is the last time search was used that is listed in search metadata. -- Blank DLU indicates a search that have not been used since the time when NetSuite started - capturing in 2009. +- Blank DLU indicates a search that has not been used since NetSuite started capturing in 2009. - Search “Date Last Used” are checked depending upon the Time To Live specified for searches. - Searches run in Dashboard Portlets doesn't update the DLU. DLU can't be determined for searches only used through Portlets. diff --git a/docs/platgovnetsuite/cleanup/restore_fields.md b/docs/platgovnetsuite/cleanup/restore_fields.md index 12fa9d04b6..123184d0a4 100644 --- a/docs/platgovnetsuite/cleanup/restore_fields.md +++ b/docs/platgovnetsuite/cleanup/restore_fields.md @@ -6,8 +6,7 @@ sidebar_position: 80 # Restore Fields -There isn't a direct restore tool for fields, however you can get your archived fields back using -**Import Assistant** and the CSV file created for archiving. +There isn't a direct restore tool for fields, but you can restore your archived fields using **Import Assistant** and the CSV file created for archiving. ## Import Assistant diff --git a/docs/platgovnetsuite/cleanup/update_field_description_and_help.md b/docs/platgovnetsuite/cleanup/update_field_description_and_help.md index 84b98c056a..7567806072 100644 --- a/docs/platgovnetsuite/cleanup/update_field_description_and_help.md +++ b/docs/platgovnetsuite/cleanup/update_field_description_and_help.md @@ -24,6 +24,6 @@ changed_. The Change Log is closed. ![field_column_sort](/images/platgovnetsuite/clean_up/field_column_sort.png) 2. Add or edit **Description** and **Help** text. - The edited text will be **highlighted in blue** to indicate which fields have been modified. + Edited text is **highlighted in blue** to indicate which fields have been modified. ![cust_ui_help_update](/images/platgovnetsuite/clean_up/cust_ui_help_update.webp) -3. Click **Update** to submit the changes. The page will refresh and display the updated Descriptions and Help. +3. Click **Update** to submit the changes. The page refreshes and displays the updated Descriptions and Help. diff --git a/docs/platgovnetsuite/customization/identify_impacted_objects.md b/docs/platgovnetsuite/customization/identify_impacted_objects.md index 029929c49c..16a41d1ff7 100644 --- a/docs/platgovnetsuite/customization/identify_impacted_objects.md +++ b/docs/platgovnetsuite/customization/identify_impacted_objects.md @@ -92,16 +92,13 @@ From the ERD Search Form, you can search by: ![erdsearchform-2](/images/platgovnetsuite/customizations/erdsearchform-2.webp) -After you have finished your search, you can create a Process Issue or a Change Request from the -results. +After you finish your search, you can create a Process Issue or a Change Request from the results. ![erdsearchform-3](/images/platgovnetsuite/customizations/erdsearchform-3.webp) ## Customization Impact Search -The Customization Impact Search displays customizations and the other customizations that are -impacted by those customizations. For example, it will show if a field is used in a script or a -search. +The Customization Impact Search displays customizations and the other customizations impacted by them. For example, it shows if a field is used in a script or a search. To access a customization quick search: diff --git a/docs/platgovnetsuite/customization/integration_record.md b/docs/platgovnetsuite/customization/integration_record.md index 9c9200db4d..4b52253417 100644 --- a/docs/platgovnetsuite/customization/integration_record.md +++ b/docs/platgovnetsuite/customization/integration_record.md @@ -6,10 +6,7 @@ sidebar_position: 70 # Integration Records -Platform Governance for NetSuite documents your NetSuite integrations, creating an **Integration -Record** for each application. They are normally built and maintained by the Spiders. Changes to -integration records are captured in Change Logs. The **Access Tokens/Integration Record** Policy -control assigns the level of change reporting. +Platform Governance for NetSuite documents your NetSuite integrations by creating an **Integration Record** for each application. The Spiders build and maintain them. Changes to integration records are captured in Change Logs. The **Access Tokens/Integration Record** Policy control assigns the level of change reporting. Token-based authentication can be specified on the **Authentication** tab. Use the **Customization Quick Search** to locate an integration record. @@ -21,6 +18,6 @@ The **Authentication** tab is where you specify additional authorization for the ![Integration record example](/images/platgovnetsuite/customizations/integration_record.webp) -When you make changes to this record, a change log is created. Here is an example: +When you make changes to this record, a change log is created. The following is an example: ![Access token change log](/images/platgovnetsuite/customizations/access_token_change_log.webp) diff --git a/docs/platgovnetsuite/customization/understanding_customization_record.md b/docs/platgovnetsuite/customization/understanding_customization_record.md index 1367e2891b..4419bcac53 100644 --- a/docs/platgovnetsuite/customization/understanding_customization_record.md +++ b/docs/platgovnetsuite/customization/understanding_customization_record.md @@ -6,9 +6,7 @@ sidebar_position: 10 # Understanding the Customization Record -Customization records are the documentation about each customization. They are normally built and -maintained by the Spiders. Use them to search the customizations and attach them to -processes. +Customization records are the documentation about each customization. The Spiders build and maintain them. Use them to search customizations and attach them to processes. Customization records tell you: @@ -19,8 +17,7 @@ Customization records tell you: - Detailed automated documentation (search filters and formulas, related fields, scripts, searches and records). -A Customization is a meta record of the NetSuite customization that is created by the spider -process. Links to other customizations and processes are captured and managed in this record. +A Customization is a meta record of the NetSuite customization created by the spider process. Links to other customizations and processes are captured and managed in this record. ## Understanding the Customization Record diff --git a/docs/platgovnetsuite/customization/using_erd.md b/docs/platgovnetsuite/customization/using_erd.md index 3574d072e9..f9b1381788 100644 --- a/docs/platgovnetsuite/customization/using_erd.md +++ b/docs/platgovnetsuite/customization/using_erd.md @@ -6,8 +6,7 @@ sidebar_position: 20 # Using the ERD -The Entity Relationship Diagram, **ERD** is a visual representation of your Customizations where you -can easily review the relationships and dependencies. The ERD is easily accessible: +The Entity Relationship Diagram (ERD) is a visual representation of your Customizations where you can review relationships and dependencies. The ERD is easily accessible: - **Strongpoint** > **Customizations** > **ERD View** - ERD Search, refer to [Enabling the ERD Search on the Dashboard](#enabling-the-erdsearch-on-the-dashboard) diff --git a/docs/platgovnetsuite/faq.md b/docs/platgovnetsuite/faq.md index 24f80205c9..6e9869428d 100644 --- a/docs/platgovnetsuite/faq.md +++ b/docs/platgovnetsuite/faq.md @@ -6,9 +6,7 @@ sidebar_position: 200 # FAQ -Platform Governance for NetSuite is a stress-free change management and compliance software for -NetSuite and Salesforce. It helps companies manage change in their systems, enabling them to drive -growth with confidence and certainty. Here are answers to frequently asked questions: +Platform Governance for NetSuite is change management and compliance software for NetSuite and Salesforce. It helps companies manage change in their systems with confidence. The following are answers to frequently asked questions: - [Can Platform Governance for NetSuite provide a SOC1 Report?](#can-platform-governance-for-netsuite-provide-a-soc1-report) @@ -50,22 +48,13 @@ can be reimported and retained for archiving purposes by an authorized user. #### What is the time or effort required to use Platform Governance for NetSuite -A lot less than you would expect. The first phase is to get a complete customization -documentation library. All this requires is for the Administrator to install the bundle, press -"Start Spider" and let the system run. After a few nights, the system documentation is complete and -you can review the results in the Status Report. +The first phase is to get a complete customization documentation library. The Administrator installs the bundle, presses **Start Spider**, and lets the system run. After a few nights, the system documentation is complete and you can review the results in the Status Report. User guides and online videos are available to walk you through Clean Up, Script Analysis and other capabilities. Because Platform Governance for NetSuite creates complete documentation and updates on an ongoing basis with your NetSuite and Salesforce records, you can use the pre-built searches or -create your own to get instant visibility into your account. While Platform Governance for NetSuite -greatly reduces the amount of time to find information and identify interdependencies, the NetSuite -and Salesforce Administrators still need to do the appropriate due diligence and analysis to -ensure their actions are appropriate and safe. +create your own to get instant visibility into your account. Platform Governance for NetSuite greatly reduces the time to find information and identify interdependencies. NetSuite and Salesforce Administrators still need to perform appropriate due diligence and analysis to ensure their actions are appropriate and safe. #### Who needs a Platform Governance for NetSuite License — what is the difference between an editor and a viewer -Licenses are only required for editors of Platform Governance for NetSuite (i.e. people who create -or edit processes or view customization documentation). No license is required for users who merely -view documentation. A company will normally start with a small team (the base includes three seats) -and then add users as their usage expands. +Licenses are required for editors of Platform Governance for NetSuite (people who create or edit processes or view customization documentation). No license is required for users who only view documentation. Companies typically start with a small team (the base includes three seats) and add users as usage expands. diff --git a/docs/platgovnetsuite/index.md b/docs/platgovnetsuite/index.md index c9f9911ef3..94c348b7c0 100644 --- a/docs/platgovnetsuite/index.md +++ b/docs/platgovnetsuite/index.md @@ -7,9 +7,7 @@ sidebar_position: 10 # Welcome -Platform Governance for NetSuite is a SuiteApp integrated into the NetSuite backend keeping all your -data within your NetSuite account. Your documentation is automatically maintained so it is always up -to date. +Platform Governance for NetSuite is a SuiteApp integrated into the NetSuite backend. All your data stays within your NetSuite account. Documentation is automatically maintained and always up to date. By implementing Platform Governance for NetSuite you can: @@ -20,14 +18,14 @@ By implementing Platform Governance for NetSuite you can: - Automatically track changes to your customizations using the change logs, so you can see what customizations were changed, how they were changed, when they were changed and who changed them. -Check out Netwrix University for helpful tutorials. -[Sign in to your Netwrix account](https://www.netwrix.com/my_training.html) to access the tutorials. +Netwrix University offers tutorials for Platform Governance for NetSuite. +[Sign in to your Netwrix account](https://www.netwrix.com/my_training.html) to access them. ## Installation and Initial Scan After you install Platform Governance for NetSuite, click the **Start Spider** button and your customizations are documented over the course of 4-5 days with minimal impact on system -performance. Once completed, you have a searchable database of all your customizations. +performance. After it completes, you have a searchable database of all your customizations. ## Documentation and Optimization @@ -39,8 +37,7 @@ have your account both fully documented and optimized. Use the end to end documentation of custom objects and the Clean Up Tools to: - Identify unused fields, searches, and other custom objects. -- Quickly identify dependencies to reduce the risk of breaking things in your account (i.e. see if a - search is being used in a script or workflow). +- Quickly identify dependencies to reduce the risk of breaking customizations in your account (for example, see if a search is being used in a script or workflow). - Use Change Requests to keep your changes organized and capture approvals. ### Script Management @@ -58,7 +55,7 @@ can fix to improve your account. With the Critical Script Analysis methodology y Platform Governance for NetSuite is the only application for NetSuite that enables end to end change management and compliance. This process can be achieved effectively in only 5 weeks after install. -By implementing Platform Governance for NetSuite you give your customers the ability to: +Platform Governance for NetSuite enables you to: - Track all changes to custom objects in NetSuite. - Automatically be alerted to non-compliant changes. @@ -70,16 +67,12 @@ By implementing Platform Governance for NetSuite you give your customers the abi ## Enterprise Compliance -Once Intelligent Change Management is complete, it only takes between 3 to 4 weeks to achieve +After Intelligent Change Management is complete, it only takes between 3 to 4 weeks to achieve Enterprise Compliance. ### Environment Comparison -The Environment Management Module enables NetSuite customers and consultants to quickly and -accurately identify differences between any two NetSuite accounts that havePlatform Governance for -NetSuite Intelligent Change Management installed. Since both accounts have Platform Governance for -NetSuite documentation in place, the tool can quickly and easily compare them. It is principally -used in four scenarios: +The Environment Management Module enables NetSuite customers and consultants to identify differences between any two NetSuite accounts that have Platform Governance for NetSuite Intelligent Change Management installed. Because both accounts have Platform Governance for NetSuite documentation in place, the tool can compare them quickly. It is primarily used in four scenarios: 1. Sandbox Refreshes 2. Migrating Customizations Between Developer and Sandbox Accounts diff --git a/docs/platgovnetsuite/installation/go_live_faq.md b/docs/platgovnetsuite/installation/go_live_faq.md index 49bdf30d7f..01f2747c6a 100644 --- a/docs/platgovnetsuite/installation/go_live_faq.md +++ b/docs/platgovnetsuite/installation/go_live_faq.md @@ -6,7 +6,7 @@ sidebar_position: 110 # Go Live Frequently Asked Questions -Here is a list of common questions customers have asked after they Go Live. +The following are common questions after going live. > _How To_: [Create a Change Request for Role Assignment](#create-a-change-request-for-role-assignment) > @@ -95,12 +95,11 @@ Administrators can perform Approval Overrides on a Change Request. ![Change Status to Approved](/images/platgovnetsuite/installing_strongpoint/golive_approval_override.webp) -The Status bar is set to **Approved (Override)** and the administrator's name is displayed in the -**Approval Override By** field. +The Status bar shows **Approved (Override)** and the **Approval Override By** field shows the administrator's name. ## Change By Field Showing AutoSpider or Couldn't Be Determined -If the AutoSpider isn't run, your Change Logs will be missing the **Changed by** and **Actual +If the AutoSpider isn't run, your Change Logs are missing the **Changed by** and **Actual Change Date** fields. When the Change Log is newly created, the fields contain **Pending AutoSpider**. If too many days go by, the fields change to **Couldn't be determined**. @@ -118,8 +117,7 @@ Deployment Record on the Change Request. To properly add and deploy a script: 5. Deploy the script. If your site uses [Opportunistic Clearance](/docs/platgovnetsuite/changemanagement/opportunisticclearance/opportunistic_clearance.md), the -deployment record is handled automatically. You should ensure you understand all of the -ramifications of Opportunistic Clearance before enabling it for your account. +deployment record is handled automatically. Review all implications of Opportunistic Clearance before enabling it for your account. ## Change Logs Attached to the Wrong Change Request diff --git a/docs/platgovnetsuite/installation/installation_overview.md b/docs/platgovnetsuite/installation/installation_overview.md index ee0e87b976..eeb48fad5b 100644 --- a/docs/platgovnetsuite/installation/installation_overview.md +++ b/docs/platgovnetsuite/installation/installation_overview.md @@ -6,9 +6,7 @@ sidebar_position: 20 # Installation Overview -Installing Platform Governance for NetSuite is straight forward. Follow the steps in these topics to -install the bundle, set access for the Strongpoint tab on the NetSuite toolbar, and manage users. -There is a **Next Step** link at the end of each installation topic. +Follow the steps in these topics to install the bundle, set access for the Strongpoint tab on the NetSuite toolbar, and manage users. There is a **Next Step** link at the end of each installation topic. The bundle is installed using processor architecture for scheduled scripts. All deployments are set to low priority. @@ -20,8 +18,7 @@ to low priority. 5. [Setting Access to the Strongpoint Tab](/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md) 6. [Setting Role Permissions](/docs/platgovnetsuite/installation/setting_permissions.md) -Once your installation is complete, you can review the -[Installation Settings](/docs/platgovnetsuite/installation/installation_settings_report.md) report. +After installation is complete, review the [Installation Settings](/docs/platgovnetsuite/installation/installation_settings_report.md) report. :::note Optional menu items are hidden by default to keep the menus clean and easy to use. If users don't diff --git a/docs/platgovnetsuite/installation/installation_settings_report.md b/docs/platgovnetsuite/installation/installation_settings_report.md index 89dd53c432..63466c6295 100644 --- a/docs/platgovnetsuite/installation/installation_settings_report.md +++ b/docs/platgovnetsuite/installation/installation_settings_report.md @@ -29,7 +29,7 @@ The report has the following tabs: Count** column represents the number of objects the spider detected. The **Documented Record Count** represents the number of objects that were documented. In most cases, they should match when the spider is complete. If you access the report before the scheduled scripts are complete, - you may see incomplete or duplicate records. These will be cleaned up after the scripts complete + you may see incomplete or duplicate records. These are cleaned up after the scripts complete their work. ### Documentation @@ -80,13 +80,13 @@ Accesses change management features: handle complex fields. After the **Enable Case to Change Request Workflow** is enabled, a **Create Change Request** button is available on the **Case** record (**Lists** > **Support** > **Cases**). - Here is an example using a **Formula** for the **Case to Change Request Field Mapping**: + The following example uses a **Formula** for the **Case to Change Request Field Mapping**: ![Example of a Formula in the Case to Change Request Field Mapping](/images/platgovnetsuite/installing_strongpoint/casetocrformula.webp) - **Do Not ReSpider Automatically**: sets the default condition for the **Do Not ReSpider Automatically** setting on the [ITGC Change Request](/docs/platgovnetsuite/changemanagement/creating_change_request.md). The default is unchecked. - When enabled, an automatic ReSpider occurs when a Change Request status is changed to + When enabled, an automatic ReSpider occurs when a Change Request status changes to **Completed**. This starts the ReSpider and ensures that all change logs are complete before changing the status. If automatic ReSpidering is turned off, there is a risk of changes being marked as non-compliant if the change logs aren't complete when the user changes the status to diff --git a/docs/platgovnetsuite/installation/installing_strongpoint.md b/docs/platgovnetsuite/installation/installing_strongpoint.md index 5682a1df88..30dd0fa312 100644 --- a/docs/platgovnetsuite/installation/installing_strongpoint.md +++ b/docs/platgovnetsuite/installation/installing_strongpoint.md @@ -41,9 +41,7 @@ The Bundle ID has been updated due to NetSuite changes. ## Set the Number of Row in List Segments -It is important that you set your NUMBER OF ROWS IN LIST SEGMENTS to 1,000. This is a NetSuite best -practice and critical for the proper spidering of your workflows. If you are unable to edit this -field, refer to +Set your NUMBER OF ROWS IN LIST SEGMENTS to 1,000. This is a NetSuite best practice and critical for the proper spidering of your workflows. If you cannot edit this field, refer to [Can't Change the Number of Rows in List Segments](/docs/platgovnetsuite/reportabug/list_segments_not_editable.md) To set the Number of Rows in List Segments: @@ -53,7 +51,7 @@ To set the Number of Rows in List Segments: 3. Set the value to **1,000**. 4. Click **Save**. -If the field is grayed out, it should be set as a **Company Preference:** +If the field is grayed out, set it as a **Company Preference**: 1. Select **Company Preferences** from **Set Up** > **General Preferences** on the NetSuite main menu. diff --git a/docs/platgovnetsuite/installation/running_the_spider.md b/docs/platgovnetsuite/installation/running_the_spider.md index 61a347254c..f423fcbb1f 100644 --- a/docs/platgovnetsuite/installation/running_the_spider.md +++ b/docs/platgovnetsuite/installation/running_the_spider.md @@ -33,7 +33,7 @@ To run the spider: - Remain logged in as an Administrator. The gears spin during this part of the spider run. It can take between 45-60 minutes to complete. -When finished, the gears stop spinning and **Spider Finished** is displayed below the **Start +When finished, the gears stop spinning and **Spider Finished** appears below the **Start Spider** button. You can close the tab when finished. The spider continues to work in the background to document your account. @@ -103,7 +103,7 @@ You can ReSpider your account at any time. 2. Select **Update Only - FAST** from **Update or ReSpider** 3. Select one or more record types that have an issue. You can also enter an optional **Name Filter**: entering all of part of the customization name to focus the spider. You can use the - **%** wildcard to search with the given name. Here are the record types: + **%** wildcard to search with the given name. The following are the record types: > | | | | > | ------------------------ | -------------------------- | --------------------------------- | @@ -141,7 +141,7 @@ for fully scriptable customization types. Customization metadata and changes are a day when the spiders run. If there are multiple record changes within the day, separate change logs are created for each change to capture system notes and audit trails. -Here is the schedule for each customization type. +The following is the schedule for each customization type. | | | | | ------------------------------------------ | -------------------- | ------------------------------------- | diff --git a/docs/platgovnetsuite/installation/setting_permissions.md b/docs/platgovnetsuite/installation/setting_permissions.md index 019057f4ca..1142727cc9 100644 --- a/docs/platgovnetsuite/installation/setting_permissions.md +++ b/docs/platgovnetsuite/installation/setting_permissions.md @@ -36,7 +36,7 @@ permission list for each role. The Strongpoint roles have the correct access lev 5. **Save** the Permissions. -Here are the Custom Permissions needed for each role. +The following are the custom permissions needed for each role. #### Change Request Approvers diff --git a/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md b/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md index 7225561a87..f74b5bf9db 100644 --- a/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md +++ b/docs/platgovnetsuite/installation/setting_strongpoint_tab_access.md @@ -18,7 +18,7 @@ Access to the Strongpoint tab must be granted to other users or roles: 1. Open **Customization** > **Centers and Tabs** > **Center Tabs** 2. Click **Edit** by Strongpoint - The **Label** should be **Strongpoint**. + Confirm the **Label** is **Strongpoint**. 3. Click the **Audience** tab. 4. Grant access to the appropriate users and roles. Refer to NetSuite’s Help for more details on **Role and Tab Access**. diff --git a/docs/platgovnetsuite/installation/setting_up_auto_spider_alerts.md b/docs/platgovnetsuite/installation/setting_up_auto_spider_alerts.md index af336579e8..d48d4a76df 100644 --- a/docs/platgovnetsuite/installation/setting_up_auto_spider_alerts.md +++ b/docs/platgovnetsuite/installation/setting_up_auto_spider_alerts.md @@ -6,24 +6,24 @@ sidebar_position: 30 # Setting Up the AutoSpider and Alerts -After you have run your initial spider, the AutoSpider monitors your account on an ongoing basis to -see if customization changes have occurred. This is a light scan of the data to determine if there -were any changes. If changes are detected, you are reminded to ReSpider your account. +After you run your initial spider, the AutoSpider monitors your account on an ongoing basis to +detect customization changes. It performs a light scan of the data to determine if there +were any changes. If it detects changes, it reminds you to ReSpider your account. Best practice is to run the AutoSpider regularly. If the AutoSpider isn't run, your Change Logs -will be missing the **Changed by** and **Actual Change Date** fields. When the Change Log is newly +are missing the **Changed by** and **Actual Change Date** fields. When the Change Log is newly created, the fields contain **Pending AutoSpider**. If too many days go by, the fields change to **Couldn't be determined**. ## Set Up the AutoSpider :::note -The AutoSpider portlet should be installed on all Administrator homepages. The AutoSpider triggers +Install the AutoSpider portlet on all Administrator homepages. The AutoSpider triggers when the Administrator logs in. Ideally daily or every other day. Best practice is to wait for the portlet to load and see the **Spider Triggered** message before continuing. ::: -The **AutoSpider Portlet** is required to update certain object types in NetSuite. Once triggered +The **AutoSpider Portlet** is required to update certain object types in NetSuite. After it is triggered through the dashboard portlet, it picks up all changes on custom objects and triggers the scheduled scripts to reflect them in the Customization records, going back two days. The AutoSpider portlet is required to update these object types: diff --git a/docs/platgovnetsuite/integrations/integration_mapping.md b/docs/platgovnetsuite/integrations/integration_mapping.md index e10ba2242c..9847159538 100644 --- a/docs/platgovnetsuite/integrations/integration_mapping.md +++ b/docs/platgovnetsuite/integrations/integration_mapping.md @@ -8,7 +8,7 @@ sidebar_position: 10 The Integration Mapping tool maps customizations between External Systems and NetSuite. -Here is the basic process. +The basic process is as follows. 1. Create the External System Customization record. (optional) 2. Create a **.csv** file. @@ -35,7 +35,7 @@ System, it can be automatically created by the tool. The **.csv** file is where you specify the customization mapping between the External System and NetSuite. The file is uploaded when you run the tool. You can create a file with the specified headings, or download the template with the link on the first page of the Integration Mapping tool. -Don't change the specified headings. Here is the template: +Don't change the specified headings. The following is the template: ![int_map_csv_template](/images/platgovnetsuite/integrations/int_map_csv_template.webp) @@ -110,7 +110,7 @@ Open **Strongpoint** > **Integrations** > **Mapping Tool** 2. Click the linked **Internal ID** to display the ERD for each mapped customization. -Here is an example of an expanded ERD showing **Integrations**, **Sources**, and **External -Dependent Fields**. Note the **External Dependent Fields** is highlighted with a green header. +The following example shows an expanded ERD with **Integrations**, **Sources**, and **External +Dependent Fields**. The **External Dependent Fields** are highlighted with a green header. ![int_mapping_ext_erd](/images/platgovnetsuite/integrations/int_mapping_ext_erd.webp) diff --git a/docs/platgovnetsuite/reportabug/spider_spins.md b/docs/platgovnetsuite/reportabug/spider_spins.md index 1b9f694fd4..a71b2e74c2 100644 --- a/docs/platgovnetsuite/reportabug/spider_spins.md +++ b/docs/platgovnetsuite/reportabug/spider_spins.md @@ -6,7 +6,6 @@ sidebar_position: 60 # Spider Spins and Doesn't Finish -If you kick off a spider and the gears on the page spin for more than an hour, this is likely an -issue with the **IP Restriction**. Contact Netwrix support at +If you start a spider and the gears on the page spin for more than an hour, the issue is likely with the **IP Restriction**. Contact Netwrix support at [https://www.netwrix.com/support.html ](https://www.netwrix.com/support.html) for assistance in configuring your account. diff --git a/docs/platgovnetsuite/scriptmgmt/script_mgmt_overview.md b/docs/platgovnetsuite/scriptmgmt/script_mgmt_overview.md index 32b1be88e6..9b5aec17f9 100644 --- a/docs/platgovnetsuite/scriptmgmt/script_mgmt_overview.md +++ b/docs/platgovnetsuite/scriptmgmt/script_mgmt_overview.md @@ -67,7 +67,7 @@ There are two requirements to analyze and report script performance data: There are pre-built saved mass updates to quickly do this, but some factors need to be considered. -Since tags need to be added to the script file, there are some limitations on the data Platform +Because tags need to be added to the script file, there are some limitations on the data Platform Governance for NetSuite can analyze for locked scripts. 1. **Locked Script Records**: A locked script record doesn't impact script analysis since Platform @@ -83,7 +83,7 @@ Governance for NetSuite can analyze for locked scripts. - Document who is executing the script - Provides a sense of how often it is executing. It tracks the number of executions per tag and averages them. The number can vary based on the placement of the tags and how the script is - executed any given time. While it doesn't provide an exact number, it will be within the + executed any given time. Although it doesn't provide an exact number, it is within the right range and can help identify if a script is executing significantly more than the transaction volume would indicate. - Without audit tags: Same and locked and hidden scripts below. @@ -116,15 +116,14 @@ In this case you can either add the audit tags and change the log levels manuall updates. Platform Governance for NetSuite has tools to automatically change the log level of script -deployments and add start tags to files. However, before deploying these tools, you may want to -consider the following factors. +deployments and add start tags to files. Before deploying these tools, consider the following factors. 1. Changing the log level from Error or Emergency to Audit, which is required for Script Analysis may increase the level of log entries that appear on the Execution Log tab based on what tags are in the scripts. 2. Log levels **can't** be automatically changed for bundled deployments. Bundled deployment log levels need to be changed manually. -3. Since audit tags can only be added to unlocked files, changing the log levels of locked files +3. Because audit tags can only be added to unlocked files, changing the log levels of locked files serves no purpose from a Script Analysis perspective. Platform Governance for NetSuite has the following capabilities to set up script analysis. Specific @@ -133,7 +132,7 @@ ways to use these tools depend on your objectives and account setup. ## Identify which Scripts and how many Scripts have Locked and Hidden Files As mentioned above, audit tags can't be added to these files and changing the log levels is moot. A -future bundle will have this search built in, but you can quickly identify and count the number of +future bundle includes this search, but you can identify and count the number of locked scripts by creating this saved search: - Create a new saved search, type Customization @@ -143,8 +142,7 @@ locked scripts by creating this saved search: - You can add Type to the results to see the script type Compare this number to the number of scripts in your account (Customizations>Scripting [ensure all -filters are cleared]). If a large proportion of your scripts are locked and hidden, you may want to -focus your analysis by changing the log level and adding audit tags to a limited number of scripts. +filters are cleared]). If a large proportion of your scripts are locked and hidden, consider focusing your analysis by changing the log level and adding audit tags to a limited number of scripts. **Customization Record**: You can also see if a script file is locked by looking at the Customization record for that script. On the **Scripting** tab, check the script file. If there are @@ -179,6 +177,6 @@ There are several searches that provide data about script performance and errors Another critical script is the **Strongpoint Parse Script Files SS** (note there is also an on demand version OD). This reads each unlocked script file to check for changes, updates the -documentation and stores an archive copy of any previous version of the code. Once complete it +documentation and stores an archive copy of any previous version of the code. After it completes, it triggers the **Strongpoint MakeJoins** script to complete the documentation by attaching related fields and saved searches. diff --git a/docs/platgovnetsuite/sod/creating_sod_rules.md b/docs/platgovnetsuite/sod/creating_sod_rules.md index 337f9dc634..42d75af18b 100644 --- a/docs/platgovnetsuite/sod/creating_sod_rules.md +++ b/docs/platgovnetsuite/sod/creating_sod_rules.md @@ -90,7 +90,7 @@ The following are general definitions of access levels for permissions in NetSui 11. **Save** the rule. -Once a Rule is saved, the **Change ID** and **Run Retroactive** functions are available. +After a Rule is saved, the **Change ID** and **Run Retroactive** functions are available. There are four tabs to access details: @@ -119,7 +119,7 @@ To view the updates to your SoD rules: ![Updates to SoD Rules report](/images/platgovnetsuite/sod/sod_rules_update_report.webp) -With this report, you can easily identify modified pre-defined SoD rules. There is a saved import +With this report, you can identify modified pre-defined SoD rules. There is a saved import SoD Rule Import available to enable bulk add or update SoD rules to your production environment. 1. Create a **.csv** file with the following fields: diff --git a/docs/platgovnetsuite/sod/sod_clean_up.md b/docs/platgovnetsuite/sod/sod_clean_up.md index 4f2ac89b44..29ba8dfb9e 100644 --- a/docs/platgovnetsuite/sod/sod_clean_up.md +++ b/docs/platgovnetsuite/sod/sod_clean_up.md @@ -27,12 +27,12 @@ Saved Searches are: - **Employees with Standard Roles** identifies all employees assigned to standard roles. - **Employees with Unused Logins** identifies any employees who have not logged in. -- **Employee Permission Changes** identifies all employee permission changes that have occurred. +- **Employee Permission Changes** identifies all employee permission changes. - **Unused Roles - Not Assigned** identifies roles not assigned to any user. - **Unused Roles - Assigned But Not In Use** identifies roles assigned to a user, but never used. - **Role Assignments with No Login in Six Months** identifies assigned roles where a user has not logged in within the past six months. -- **Role Permission Change** identifies all role permission changes that have occurred. +- **Role Permission Change** identifies all role permission changes. - **Employees with Multiple Roles Detailed** identifies users with multiple roles and lists the roles. Multiple roles create conflicts. Users who require multiple roles for support or administration can be isolated in a sandbox using Platform Governance for NetSuite to keep the diff --git a/docs/platgovnetsuite/sod/sod_notifications.md b/docs/platgovnetsuite/sod/sod_notifications.md index 3e74d62e81..f1f7778251 100644 --- a/docs/platgovnetsuite/sod/sod_notifications.md +++ b/docs/platgovnetsuite/sod/sod_notifications.md @@ -9,7 +9,7 @@ sidebar_position: 50 SoD notifications offer a streamlined process for creating change requests and presenting information to approvers for SoD violations. -1. When a task causes an SoD violation, a dialog box is displayed with an option to request an +1. When a task causes an SoD violation, a dialog box appears with an option to request an approval. ![sod_nonblocking_msg](/images/platgovnetsuite/sod/sod_nonblocking_msg.webp) @@ -19,9 +19,9 @@ information to approvers for SoD violations. ![sod_approve_req_msg](/images/platgovnetsuite/sod/sod_approve_req_msg.webp) 3. Add the reason for the approval request. Click **OK**. -4. A confirmation is displayed when the change request is created. You can click the link to view +4. A confirmation appears when the change request is created. You can click the link to view the request. -5. Once a change request is generated,Platform Governance for NetSuite sends email to the approvers. +5. After a change request is generated, Platform Governance for NetSuite sends email to the approvers. The email shows the requested change, the SoD violations, and links to the change request. ![sod_email_msg](/images/platgovnetsuite/sod/sod_email_msg.webp) diff --git a/docs/platgovnetsuite/sod/sod_overview.md b/docs/platgovnetsuite/sod/sod_overview.md index fb43706287..71a7f7ab06 100644 --- a/docs/platgovnetsuite/sod/sod_overview.md +++ b/docs/platgovnetsuite/sod/sod_overview.md @@ -21,12 +21,12 @@ Advanced SoD provides: - **Warning messages and email alerts** to let you know when you are in an undesired zone. - **Custom reports** for documentation, retroactive approvals and continuous access reviews, ultimately preserving audit trails. -- The power of **Agent** to fill in gaps, monitor, and document activities of “super users” and those +- The power of **Agent** to fill gaps, monitor, and document activities of “super users” and those with positional authority. ## Benefits of Advanced SoD -By implementing Advanced SoD you can create flexible and easy to maintain rules. +Advanced SoD lets you create flexible, easy-to-maintain rules. You can create rules that: diff --git a/docs/platgovnetsuite/sod/sod_reports.md b/docs/platgovnetsuite/sod/sod_reports.md index 7feb3dd131..0d8667dcba 100644 --- a/docs/platgovnetsuite/sod/sod_reports.md +++ b/docs/platgovnetsuite/sod/sod_reports.md @@ -6,7 +6,7 @@ sidebar_position: 90 # SoD Reports -Here are the reports available for SoD: +The following reports are available for SoD: SoD Role Management
SoD Incident Management
diff --git a/docs/platgovnetsuite/sod/sod_test_case_scenarios.md b/docs/platgovnetsuite/sod/sod_test_case_scenarios.md index d799db314f..e1bf2ed633 100644 --- a/docs/platgovnetsuite/sod/sod_test_case_scenarios.md +++ b/docs/platgovnetsuite/sod/sod_test_case_scenarios.md @@ -6,7 +6,7 @@ sidebar_position: 110 # SoD Test Case Scenarios -Here are test case scenarios for SoD rules: +The following are test case scenarios for SoD rules: - Assign an Admin Role to a User - Set Conflicting Global Permissions for a User @@ -35,10 +35,7 @@ To assign an administrator role to a user: **Result** -If the SoD rule is violated, the change made will not be allowed and will be blocked right away. A -user shouldn't be assigned an Administrator role unless there is a pre-approved change request. A -prompt violation message will be seen by the user trying to make the change. The user will not be -able to proceed with the save action. +If the SoD rule is violated, the change is blocked immediately. A user can't be assigned an Administrator role without a pre-approved change request. The user trying to make the change sees a violation prompt and cannot proceed with saving. ## Set Conflicting Global Permissions for a User diff --git a/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md b/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md index 13fed657c2..df0fdbc298 100644 --- a/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md +++ b/docs/platgovnetsuite/ticketingintegrations/apioverview/api_overview.md @@ -14,12 +14,12 @@ applications can integrate via these APIs. - **ERD** and **Impact Analysis** tools are available. - [Customizations API](/docs/platgovnetsuite/ticketingintegrations/apioverview/customizationsapi/customizations_api.md) can be retrieved from your NetSuite account and can be - added and removed from your Change Requests. Here is the Customization API command: + added and removed from your Change Requests. The following is the Customization API command: - [Get Customizations](/docs/platgovnetsuite/ticketingintegrations/apioverview/customizationsapi/get_customizations.md): Returns customizations based on your filters. - [Change Request API](/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/change_request_api.md) can be created, updated, retrieved, and deleted. The - ERD and Impact Analysis tools are available. Here are the Change Request API commands: + ERD and Impact Analysis tools are available. The following are the Change Request API commands: - [Get Change Request](/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_change_request.md): Returns the change request associated with an External ID. diff --git a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/change_request_api.md b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/change_request_api.md index e80193f16e..55b22797f9 100644 --- a/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/change_request_api.md +++ b/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/change_request_api.md @@ -8,7 +8,7 @@ sidebar_position: 20 The Change Request API provides external access to retrieve customization from a NetSuite account. -Here are the Change Request API commands: +The following are the Change Request API commands: - [Get Change Request](/docs/platgovnetsuite/ticketingintegrations/apioverview/changerequestapi/get_change_request.md): Returns the change request associated with an External ID. diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md index ab0ee7772d..07b33ec285 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md @@ -21,6 +21,6 @@ This section covers frequently asked questions and basic troubleshooting for Pla - This is Atlassian's way of securing data. Every install or update is a fresh start. However, there are 2 ways to retrieve the data: (1) Raise a ticket to Atlassian support to restore the data in the instance for when the Jira Forge app was installed or updated. (2) Manually re-enter the data. 5. Is there impact to existing Connect tickets if Forge is being used? - - **No**. Since the change request information is being pulled from the NetSuite account that Jira Forge is connected to, there should be no impact when switching to the Forge app. + - **No**. Since the change request information is being pulled from the NetSuite account that Jira Forge is connected to, switching to the Forge app has no impact on existing tickets. **Back to:** [Jira Forge Walkthrough Example](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough) diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md index 17352987d2..5fe53fea8d 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md @@ -50,7 +50,7 @@ If the latest version of the bundle is already installed, you may skip this part ### Install the latest version of the Netwrix Platform Governance Jira Forge app -This process requires access to the Atlassian Marketplace and Administrator permissions on the Jira instance where the app will be installed. +This process requires access to the Atlassian Marketplace and Administrator permissions on the Jira instance where the app is installed. 1. Go to the [Atlassian Marketplace](https://marketplace.atlassian.com/). 2. In the search bar, type in either of the keywords: **Netwrix Platform Governance** or **Strongpoint**(this is the product's previous name). @@ -59,19 +59,19 @@ This process requires access to the Atlassian Marketplace and Administrator perm ![Jira Forge Marketplace Search](/images/platgovnetsuite/integrations/jira_forge_marketplace_search_results.webp) -4. After selecting, you should be redirected to the product's overview page. +4. After selecting, you are redirected to the product overview page. ![Jira Forge Marketplace Overview](/images/platgovnetsuite/integrations/jira_forge_marketplace_overview.webp) 5. Click the **Get it now** button found at the upper-right part of the page. -6. You will now be redirected to the installation process. Select the Jira instance where you want to install Netwrix Platform Governance Forge +6. You are redirected to the installation process. Select the Jira instance where you want to install Netwrix Platform Governance Forge ![Jira Forge Marketplace Select Site](/images/platgovnetsuite/integrations/jira_forge_marketplace_select_site.webp) 7. Click **Review** -8. You are now in the last step where you can review the app's Permissions and Data management. All of these have been strictly reviewed by the Atlassian team and adhere to their security policies. When ready, click **Get it now** button. +8. Review the app Permissions and Data management. All of these have been strictly reviewed by the Atlassian team and adhere to their security policies. When ready, click **Get it now** button. ![Jira Forge Marketplace Review](/images/platgovnetsuite/integrations/jira_forge_marketplace_review_install.webp) @@ -80,7 +80,7 @@ This process requires access to the Atlassian Marketplace and Administrator perm This step will require a user to have NetSuite account access and an Administrator role to that account. -Token Based Authentication is set up through NetSuite. Here is the basic process: +Token Based Authentication is set up through NetSuite. The basic process is as follows: 1. NetSuite Administrator creates an Integration Record for the Platform Governance for NetSuite application. This only needs to be performed once per account. Open **Setup > Integration > Integration Management > Manage Integrations > New**. See the NetSuite help article "Create Integration Records for Applications to Use TBA" for details. To view a list of integration records in this account, open **Setup > Integration > Integration Management > Manage Integrations**. @@ -88,7 +88,7 @@ Token Based Authentication is set up through NetSuite. Here is the basic process Take note of these values and keep them secure. ::: -2. Each user creates their token in NetSuite. Refer to the NetSuite help Manage TBA Tokens in the NetSuite UI for details. After you have created your tokens, add them to Jira. +2. Each user creates their token in NetSuite. Refer to the NetSuite help Manage TBA Tokens in the NetSuite UI for details. After you create your tokens, add them to Jira. 3. Create an Access Token by navigating to main menu, **Setup > Users/Roles > Access Tokens > New**. 4. Fill the fields with the following values: - Application Name: The Integration Record that was created in Step 1. @@ -115,15 +115,15 @@ Token Based Authentication is set up through NetSuite. Here is the basic process ### Set up Jira Credentials -This step will require a user to have Jira instance access and a user to have NetSuite account access. +This step requires Jira instance access and NetSuite account access. 1. Create a Jira token via this URL: https://id.atlassian.com/manage-profile/security/api-tokens - - Take note of the token value as this will be associated with your email address that is used to log in to the Atlassian/Jira ecosystem. Refer to the Atlassian documentation to obtain a Token. -2. In this step, you should have the following credentials on hand + - Note the token value, as it is associated with your email address for the Atlassian/Jira ecosystem. Refer to the Atlassian documentation to obtain a Token. +2. Have the following credentials ready - Jira user email address - Jira token generated above. -3. In NetSuite, go to Netwrix Configuration and Stats by navigating in the main menu, **Netwrix > Netwrix Support > Installation Settings**. There should only be **ONE(1)** record displayed. Click 'Edit' and it should open the Configuration and Stats page. -4. Click 'Jira Integration' tab. You should be can see a number of fields. Turn your attention to Jira User and Jira Token fields. +3. In NetSuite, go to Netwrix Configuration and Stats by navigating in the main menu, **Netwrix > Netwrix Support > Installation Settings**. Only one record is displayed. Click **Edit** to open the Configuration and Stats page. +4. Click 'Jira Integration' tab. Several fields are displayed. Turn your attention to Jira User and Jira Token fields. 5. Populate these fields with the following values: - Jira User - Jira user email address in step 2. - Jira token - Jira token generated in step 1. @@ -138,7 +138,7 @@ The mapping allows multiple Jira statuses to map to each Change Request status. Refer to the Atlassian documentation for instructions on [Defining status field values](https://confluence.atlassian.com/adminjiraserver070/defining-status-field-values-749382903.html?_ga=2.262596428.1900070949.1572132057-2138500458.1540834491). -1. In NetSuite, go to Netwrix Configuration and Stats by navigating in the main menu, **Netwrix > Netwrix Support > Installation Settings**. There should only be **ONE(1)** record displayed. Click 'Edit' and it should open the Configuration and Stats page. +1. In NetSuite, go to Netwrix Configuration and Stats by navigating in the main menu, **Netwrix > Netwrix Support > Installation Settings**. Only one record is displayed. Click **Edit** to open the Configuration and Stats page. Enter the mappings between your Jira statuses and the Change Request statuses. For best practice, define your Jira statuses before this step. You can enter multiple Jira statuses for each Change Request status, separated by commas. For example, Ready for Deployment,Done. Assign your relevant mapping for each of the Change Request statuses: @@ -162,43 +162,43 @@ Click 'Save' ### Set up Jira Project Keys -This step will require a user to have Jira instance access where Netwrix Platform Governance for NetSuite Jira Forge app is installed. You are now closer to using the integration app. +This step requires Jira instance access where the Netwrix Platform Governance for NetSuite Jira Forge app is installed. 1. In your browser, open your Jira application. -2. In the left part of the page, there is a sidebar that lists shortcuts and apps that are installed in this Jira instance. Under 'Your Apps', there should be an app that is titled 'Netwrix NetSuite Settings'. Click it and it should display the Netwrix NetSuite Settings page. +2. In the left part of the page, there is a sidebar that lists shortcuts and apps that are installed in this Jira instance. Under **Your Apps**, click **Netwrix NetSuite Settings**. ![Jira Forge Netwrix NetSuite Settings Menu](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_menu.webp) -3. The page has 2 tabs, Netwrix NetSuite TBA Credentials and Netwrix NetSuite Project Keys. Let's focus on 'Netwrix NetSuite Project Keys' tab. Click the tab. +3. The page has 2 tabs, Netwrix NetSuite TBA Credentials and Netwrix NetSuite Project Keys. Click the **Netwrix NetSuite Project Keys** tab. ![Jira Forge Netwrix NetSuite Settings Project Keys](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_project_keys_menu.webp) -4. 'New Project Key' button should be displayed. Click the button and a modal should pop-out for you to add a Project Key in the field. +4. Click **New Project Key**. A modal opens where you can add a Project Key. - By defining a Project Key, the Platform Governance app can only be displayed and used within the project. ![Jira Forge Netwrix NetSuite Settings Project Keys Modal](/images/platgovnetsuite/integrations/jira_forge_project_key_modal.webp) -5. Click 'Create' and the newly added/created project key should be listed in the page. +5. Click **Create**. The new project key appears in the list. ### Set up Jira TBA Credentials -This step will require a user to have Jira instance access where Netwrix Platform Governance for NetSuite Jira Forge app is installed. You are now closer to using the integration app. +This step requires Jira instance access where the Netwrix Platform Governance for NetSuite Jira Forge app is installed. 1. In your browser, open your Jira application. -2. In the left part of the page, there is a sidebar that lists shortcuts and apps that are installed in this Jira instance. Under 'Your Apps', there should be an app that is titled 'Netwrix NetSuite Settings'. Click it and it should display the Netwrix NetSuite Settings page. +2. In the left part of the page, there is a sidebar that lists shortcuts and apps that are installed in this Jira instance. Under **Your Apps**, click **Netwrix NetSuite Settings**. ![Jira Forge Netwrix NetSuite Settings Menu](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_menu.webp) -3. The page has 2 tabs, Netwrix NetSuite TBA Credentials and Netwrix NetSuite Project Keys. Let's focus on 'Netwrix NetSuite TBA Credentials' tab. Click the tab. +3. The page has 2 tabs, Netwrix NetSuite TBA Credentials and Netwrix NetSuite Project Keys. Click the **Netwrix NetSuite TBA Credentials** tab. ![Jira Forge Netwrix NetSuite Settings Menu TBA](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba.webp) -4. 'New Token Based Authentication' button should be displayed. Click the button and a modal should pop-out for you to add a new TBA record to be used to connect to a NetSuite account. +4. Click **New Token Based Authentication**. A modal opens where you can add a TBA record to connect to a NetSuite account. ![Jira Forge Netwrix NetSuite Settings Menu TBA Modal](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba_modal.webp) @@ -209,15 +209,15 @@ This step will require a user to have Jira instance access where Netwrix Platfor ![Jira Forge Netwrix NetSuite Settings TBA Test Connection](/images/platgovnetsuite/integrations/jira_forge_tba_test_connection_successful.webp) -5. Click 'Create' and the newly added/created TBA record should be listed in the page. +5. Click **Create**. The new TBA record appears in the list. Additionally, 'Update' and 'Delete' buttons are found on the right part of your record. Use these buttons to update or delete the record, respectively. ![Jira Forge Netwrix NetSuite Settings TBA List](/images/platgovnetsuite/integrations/jira_forge_tba_list.webp) -If you have followed the step by step guide in this page, you are good to go and are ready to use the integration app. +After completing this setup, you are ready to use the integration app. -The next page, Jira Forge Walkthrough will show you how the app works! +The next page, Jira Forge Walkthrough, demonstrates how the app works. **Next Step:** [Jira Forge Walkthrough Example](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough) diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md index f9307d345c..b6a9c1b0de 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md @@ -6,7 +6,7 @@ sidebar_position: 3 # Jira Forge Walkthrough -If you have reached this part it means that you have completed ALL prerequisites found in the Jira Forge Setup page. If NOT, go through the setup steps for a smooth walkthrough of the integration's features. +Complete all prerequisites in the Jira Forge Setup page before using this walkthrough. This walkthrough is one example based on a test account. You must install and configure the Jira integration, including setting up the Jira Statuses before using this walkthrough. @@ -31,38 +31,38 @@ This walkthrough is one example based on a test account. You must install and co ### Logging In and Connecting to a NetSuite Account Before proceeding to this step, ensure you already have created a TBA record. If not see [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. -1. In your issue ticket, you should see the 'Netwrix NetSuite Forge' tab in the issues tab. Click the tab. +1. In your issue ticket, click the **Netwrix NetSuite Forge** tab. Two possible displays: - 1. If you have NOT executed [Set up Jira Project Keys](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-project-keys) in the Setup Page, you will see this message displayed "Only projects defined in the Netwrix Settings page can use this integration". check if you have done that part. + 1. If you have NOT executed [Set up Jira Project Keys](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-project-keys) in the Setup Page, this message displays: "Only projects defined in the Netwrix Settings page can use this integration." Complete the [Set up Jira Project Keys](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-project-keys) step first. ![Jira Forge Issue No Project Key](/images/platgovnetsuite/integrations/jira_forge_issue_no_project_key.webp) - 2. If you have, you should see the connect page where you can connect or log in to a NetSuite defined in [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. + 2. If you have, the connect page appears, where you can connect or log in to a NetSuite defined in [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. ![Jira Forge Issue Connect Form](/images/platgovnetsuite/integrations/jira_forge_issue_connect_form.webp) -2. If you are seeing the connect fields, you are on the right track. Select a NetSuite account to connect to. -3. Upon selecting an account, the app loads. It is establishing the initial connection process. After it succeeds, the "Connect" button below should be enabled. Otherwise, double check the TBA credentials that you have entered in [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. +2. Select a NetSuite account to connect to. +3. Upon selecting an account, the app loads. It is establishing the initial connection process. After it succeeds, the **Connect** button is enabled. If it is not, verify the TBA credentials in [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. ![Jira Forge Issue Connect Form Successful](/images/platgovnetsuite/integrations/jira_forge_issue_connect_form_successful.webp) 4. Click "Connect" button. -5. You should see the ITGC Form for the Jira app. Change Request data is loaded, it also shows which account where the app is connected. +5. The ITGC Form for the Jira app is displayed. Change Request data is loaded, it also shows which account where the app is connected. ![Jira Forge Issue Connect Form Successful ITGC](/images/platgovnetsuite/integrations/jira_forge_connect_itgc_form.webp) ### Add or Remove Customizations -Now that you are ready to attach customizations to your Jira ticket. This section shows you how to add and/or remove customizations in the Forge app. +This section shows you how to add and remove customizations in the Forge app. To start adding or removing customizations, follow the steps below: -1. In the form, there should be a button named "Lookup Customization". This allows the user to add existing customization to the Jira ticket. Click the button. A modal should appear. This allows the user to filter and select a customization to attach to the change request. +1. Click the **Lookup Customization** button to add existing customizations to the Jira ticket. A modal opens, letting you filter and select a customization to attach to the change request. Available filters: @@ -82,7 +82,7 @@ Available filters: ![Jira Forge Lookup Customization Modal Name Filter](/images/platgovnetsuite/integrations/jira_forge_lookup_name_filter.webp) -3. Select a customization to attach by ticking the checkbox beside the name. Once ticked, click the "Add Customizations" button at the bottom part of the modal. +3. Select a customization to attach by ticking the checkbox beside the name. After ticking it, click the "Add Customizations" button at the bottom part of the modal. - Below shows a flag with a message that the action is in progress. @@ -93,7 +93,7 @@ Available filters: ![Jira Forge Add Customization Flag In Progress](/images/platgovnetsuite/integrations/jira_forge_successful_add_customization.webp) -4. You can also add customization that is yet to be created. This is what the "Proposed Customization" button is for. To add one, click the "Proposed Customization" button. A modal should appear with the following fields: +4. You can also add customization that is yet to be created. This is what the "Proposed Customization" button is for. To add one, click the "Proposed Customization" button. A modal opens with the following fields: - Type - ScriptID/Name @@ -135,7 +135,7 @@ Below shows the existing and proposed customizations that were added in steps 1 ![Jira Forge Remove Customizations Flag Success](/images/platgovnetsuite/integrations/jira_forge_remove_customization_successful.webp) -If you have reached this section, you were can execute the following: +After completing this section, you can: - Use the Lookup customization filter - Add existing and proposed customizations - Delete/remove a customization @@ -148,7 +148,7 @@ You may contact your company's NetSuite Administrator for a sample of this files To use import feature follow the steps below: -1. Click the "Import Customization" button in the form. A modal will appear with the option to upload a file. As discussed above, only a SDF project in ZIP and XML file formats are accepted. +1. Click the **Import Customization** button in the form. A modal appears with the option to upload a file. As discussed above, only a SDF project in ZIP and XML file formats are accepted. ![Jira Forge Import Customization](/images/platgovnetsuite/integrations/jira_forge_import_customization_modal.webp) @@ -164,16 +164,16 @@ To use import feature follow the steps below: ![Jira Forge Import Customization](/images/platgovnetsuite/integrations/jira_forge_import_sdf_zip.webp) -3. Click the "Import Customizations" button. You will see a flag message at the lower left side of your screen indicating that the importing process is In Progress. +3. Click the **Import Customizations** button. A flag message at the lower left of your screen indicates that the import is in progress. -4. After the importing is successful, all valid objects will populate the Customization and Proposed Customization tables accordingly. You will also see a flag message indicating the importing process is successful. +4. After the import succeeds, all valid objects populate the Customization and Proposed Customization tables. A flag message indicates the import succeeded. -If you have reached this section, you were can execute the following: +After completing this section, you can: - Use the Import Customization feature and add customizations in bulk. ### Perform Risk Assessment -This feature will show you Platform Governance's Impact Analysis tool. This tool reviews your customizations for dependencies or risks. +This feature uses Platform Governance's Impact Analysis tool to review your customizations for dependencies or risks. To use Impact Analysis follow the steps below: @@ -181,7 +181,7 @@ To use Impact Analysis follow the steps below: ![Jira Forge Impact Analysis Button](/images/platgovnetsuite/integrations/jira_forge_impact_analysis_button.webp) -2. A modal will appear to start the risk assessment process. +2. A modal appears to start the risk assessment process. ![Jira Forge Impact Analysis Calculating](/images/platgovnetsuite/integrations/jira_forge_calculating_impact_analysis.webp) @@ -191,8 +191,8 @@ To use Impact Analysis follow the steps below: ![Jira Forge Impact Analysis Data](/images/platgovnetsuite/integrations/jira_forge_impact_analysis.webp) -If you have reached this section, you were can execute the following: -- Perform an impact analysis on the customization that are add/attached to the Jira ticket change request. +After completing this section, you can: +- Perform an impact analysis on the customizations attached to the Jira ticket change request. ### View Entity Relation Diagram @@ -205,7 +205,7 @@ To use ERD follow the steps below: ![Jira Forge View ERD Button](/images/platgovnetsuite/integrations/jira_forge_view_erd_button.webp) -2. A modal will appear to start pulling ERD data. +2. A modal appears to start pulling ERD data. ![Jira Forge Pulling ERD Data](/images/platgovnetsuite/integrations/jira_forge_pulling_erd_data.webp) @@ -215,17 +215,17 @@ To use ERD follow the steps below: ![Jira Forge ERD Data](/images/platgovnetsuite/integrations/jira_forge_list_erd_data.webp) -4. Click "View ERD" link to view the customization's ERD. It will open to a new tab within the same browser. +4. Click **View ERD** to view the customization ERD. It opens in a new browser tab. ![Jira Forge ERD Data NetSuite](/images/platgovnetsuite/integrations/jira_forge_sample_erd.webp) -If you have reached this section, you were can execute the following: -- View the entity relation diagram of the customization that is add/attached to the Jira ticket change request. +After completing this section, you can: +- View the entity relationship diagram of the customization attached to the Jira ticket change request. ### Ready for Development -After you have resolved any risk or conflicts, your changes are ready for development: +After you resolve any risks or conflicts, your changes are ready for development: 1. Change the Jira status of your ticket to match the status set up for Jira Statuses for Pending Approval Status. For example, Selected for Development. @@ -246,20 +246,20 @@ After you have resolved any risk or conflicts, your changes are ready for develo ![Jira Forge Push Successful](/images/platgovnetsuite/integrations/jira_forge_push_successful.webp) -3. The Change Request Status field on the form will show the change request status in NetSuite. The status is now Pending Approval. It is also link to open the Change Request in NetSuite. +3. The Change Request Status field on the form shows the change request status in NetSuite. The status is now Pending Approval, with a link to open the Change Request in NetSuite. ![Jira Forge Change Request Pending Approval](/images/platgovnetsuite/integrations/jira_forge_change_request_pending_approval_status.webp) -If you have reached this section, you were can execute the following: +After completing this section, you can: - Push a change request from a Jira ticket. -- See the change request status from Jira. +- View the change request status from Jira. ### Deploy Changes and Complete the Ticket When development is done, and the Change Request is approved according to your policy, the Jira ticket is ready to be updated. -1. The Change Request Status field on the form will show the change request status in NetSuite. The status is now Approved, this means the change request is now approved in NetSuite. +1. The Change Request Status field on the form shows the change request status in NetSuite. The status is now Approved, indicating the change request is approved in NetSuite. ![Jira Forge Change Request Approved](/images/platgovnetsuite/integrations/jira_forge_approved_cr_status.webp) @@ -279,9 +279,9 @@ When development is done, and the Change Request is approved according to your p 4. If you used Ready for Deployment, update your Jira status to Done once your deployment and verification activities are complete. -If you have reached this section, you were can execute the following: +After completing this section, you can: - Push a change request from a Jira ticket. -- See the Approved change request status from Jira. +- View the Approved change request status from Jira. #### If you open the Change Request in NetSuite: @@ -302,7 +302,7 @@ If you have reached this section, you were can execute the following: These are the other features whose actions aren't that commonly used but are of equal importance in the integration app. -1. **Add Bundle ID** - The **+** button beside the Affected Bundle ID field. User will be can add NetSuite bundle IDs to the change request. You can add one bundle ID at a time for this action. It is only an add functionality, removing a bundle ID in the change request would require the user to contact a NetSuite Administrator or user for this action. +1. **Add Bundle ID** - The **+** button beside the Affected Bundle ID field. Use it to add NetSuite bundle IDs to the change request. You can add one bundle ID at a time. To remove a bundle ID from the change request, contact a NetSuite Administrator. ![Jira Forge Add Bundle Button](/images/platgovnetsuite/integrations/jira_forge_add_bundle_button.webp) @@ -311,7 +311,7 @@ These are the other features whose actions aren't that commonly used but are of ![Jira Forge Add Bundle Modal](/images/platgovnetsuite/integrations/jira_forge_add_bundle_modal.webp) -2. **Push External** - This feature allows the user to "push" the Jira ticket change request and its objects to an external NetSuite account. Pushing to an external NetSuite account save the user's time in creating a change request with the same objects in another NetSuite account. Push external can be executed by clicking the "Push External" button, a modal will appear prompting the user to select a NetSuite account that he/she wishes to push the Jira ticket change request. NetSuite accounts in the modal selection are the same accounts defined by the user in Netwrix NetSuite TBA Credentials page. +2. **Push External** - This feature allows the user to "push" the Jira ticket change request and its objects to an external NetSuite account. Pushing to an external NetSuite account saves time when creating a change request with the same objects in another NetSuite account. To use Push External, click the **Push External** button. A modal appears to select the NetSuite account to push to. NetSuite accounts in the modal are the same accounts defined in the Netwrix NetSuite TBA Credentials page. ![Jira Forge Push External Button](/images/platgovnetsuite/integrations/jira_forge_push_external_button.webp) @@ -325,6 +325,6 @@ These are the other features whose actions aren't that commonly used but are of ![Jira Forge Settings Button](/images/platgovnetsuite/integrations/jira_forge_settings_change_account.webp) -You have successfully finished the step by step Jira Forge Walkthrough! +You have completed the Jira Forge Walkthrough. **Next Step:** [Jira Forge FAQs](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq) diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md index 4bca3f9435..b9cd06b460 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_integration.md @@ -147,7 +147,7 @@ must have access granted for the **Strongpoint Developer Role**. ### Set Up Token Based Authentication -Token Based Authentication is set up through NetSuite. Here is the basic process: +Token Based Authentication is set up through NetSuite. The basic process is as follows: 1. NetSuite Administrator creates an Integration Record for the Platform Governance for NetSuite application. This only needs to be performed once per account. Open **Setup** > **Integration** > @@ -159,7 +159,7 @@ Token Based Authentication is set up through NetSuite. Here is the basic process **Integration Management** > **Manage Integrations**. 2. Each user creates their token in NetSuite. Refer to the [NetSuite help Manage TBA Tokens in the NetSuite UI](https://netsuite.custhelp.com/app/answers/detail/a_id/41902) - for details. After you have created your tokens, add them to Jira. + for details. After you create your tokens, add them to Jira. 3. Open **Jira**. 4. Open your **Projects** page: diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_walkthrough_example.md b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_walkthrough_example.md index 269875e20c..104b64b4fb 100644 --- a/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_walkthrough_example.md +++ b/docs/platgovnetsuite/ticketingintegrations/jiraintegration/jira_walkthrough_example.md @@ -69,7 +69,7 @@ consecutive attempts to login, your account is suspended for 30 minutes. ## Add Customizations -After you have logged in, the form is displayed. +After you log in, the form is displayed. ![Jira Strongpoint form](/images/platgovnetsuite/release_notes/jira_strongpoint_form.webp) - **Synchronized with** displays the connected account. Click **Change Account** to switch to a @@ -166,7 +166,7 @@ is an alternative if you have a lot of customizations. ### Impact Analysis The impact analysis tool reviews your customizations for dependencies or risks. Click **Impact -Analysis** to run the tool. Here is an example report: +Analysis** to run the tool. The following is an example report: ![Impact analysis report](/images/platgovnetsuite/integrations/jira_example_impact_analysis.webp) @@ -188,7 +188,7 @@ dependencies. ## Ready for Development -After you have resolved any risk or conflicts, your changes are ready for development: +After you resolve any risks or conflicts, your changes are ready for development: 1. Change the Jira status of your ticket to match the status set up for **Jira Statuses for Pending Approval Status**. For example, **Selected for Development**. diff --git a/docs/platgovnetsuite/ticketingintegrations/process_issues.md b/docs/platgovnetsuite/ticketingintegrations/process_issues.md index 8be6c46c0d..896b292f73 100644 --- a/docs/platgovnetsuite/ticketingintegrations/process_issues.md +++ b/docs/platgovnetsuite/ticketingintegrations/process_issues.md @@ -35,7 +35,7 @@ continue to use that and reference the external ticket in the Change Request. 6. Change the **Owner** if needed. 7. Select a **Type** for the issue. **Type** is used for sorting and organizing issues. You can set up types to trigger alerts to object owners and managers. You can use the predefined types or use - **New** to create your own. Here are basic definitions: + **New** to create your own. The following are basic definitions: - **Question**: question about a feature, function, or process. - **Suggestion**: idea for improving functionality or process. @@ -77,7 +77,7 @@ continue to use that and reference the external ticket in the Change Request. - **Completed As Process Issue**: work has been completed, all changes and change requests are complete, deployed, and verified. - **Converted to Change Request**: a change request has been created for the issue. - - **Next Review**: indicates the issue will be looked at again the next time process issues are + - **Next Review**: indicates the issue is reviewed again the next time process issues are reviewed. - **Closed**: either the process issue is closed with no action, or the same criteria as **Completed As A Process Issue**. The Spider is automatically run when the **Status** is set @@ -93,7 +93,7 @@ continue to use that and reference the external ticket in the Change Request. issue, or add existing Change Request information. 19. **Save** the Process Issue. -Once a Process Issue is saved, you can open it and use the **New Task** and **New Meeting** +After a Process Issue is saved, you can open it and use the **New Task** and **New Meeting** functionality, or edit the issue to update status information. Use the ERD tab to visually view the records and see the relationships. diff --git a/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md b/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md index e1e475c9cd..1194c64f80 100644 --- a/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md +++ b/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_integration.md @@ -38,8 +38,7 @@ To set up the Zendesk integration: ## Install the App -Here are the steps to install the Zendesk app. You must have **Admin** privileges to install the -app. +To install the Zendesk app, you must have **Admin** privileges. 1. Open your Zendesk dashboard. 2. Click the **Admin** icon in the left panel. It should open a new window to Admin Center. diff --git a/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_walkthrough_example.md b/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_walkthrough_example.md index 0832e6b920..af39156f66 100644 --- a/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_walkthrough_example.md +++ b/docs/platgovnetsuite/ticketingintegrations/zendeskintegration/zendesk_walkthrough_example.md @@ -80,7 +80,7 @@ Specify a Bundle to use a bundle for the scope of change. This is optional. ![Specify an optional Bundle ID](/images/platgovnetsuite/integrations/zendesk_bundleid.webp) -After you have made a change, the **Request Approval** button is available if you are a member of a +After you make a change, the **Request Approval** button is available if you are a member of a group with the [Set up Approvals](zendesk_integration.md#set-up-approvals) permission. ![Request Approval button appears when a change has been made.](/images/platgovnetsuite/integrations/zendesk_request_approval.webp) diff --git a/docs/platgovnetsuite/tools/tools_overview.md b/docs/platgovnetsuite/tools/tools_overview.md index a74c5257cf..e743ed5761 100644 --- a/docs/platgovnetsuite/tools/tools_overview.md +++ b/docs/platgovnetsuite/tools/tools_overview.md @@ -11,6 +11,6 @@ The **Strongpoint** > **Tools** menu accesses: - [Strongpoint Spider](/docs/platgovnetsuite/installation/running_the_spider.md): runs the Spider on your account. - **Strongpoint SQL Library**: accesses the Strongpoint SQL Formula library. Use the available - formulas to simply your Customization development. + formulas to simplify your Customization development. - [Standard Field Impact Analysis](/docs/platgovnetsuite/tools/standard_field_impact_analysis.md): runs an Impact Analysis to determine dependencies. diff --git a/docs/platgovnetsuite/uar/access_app.md b/docs/platgovnetsuite/uar/access_app.md index ed018d7b98..04f984bf60 100644 --- a/docs/platgovnetsuite/uar/access_app.md +++ b/docs/platgovnetsuite/uar/access_app.md @@ -20,7 +20,7 @@ administrator. ![Select your role](/images/platgovnetsuite/uar/uar_role.webp) -Here is an example of the UAR Admin dashboard: +The following is an example of the UAR Admin dashboard: ![UAR Admin Dashboard](/images/platgovnetsuite/uar/dashboard_admin.webp) diff --git a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_overview.md b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_overview.md index b15198d786..ccf22b0588 100644 --- a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_overview.md +++ b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_overview.md @@ -14,7 +14,7 @@ dashboard. 1. Open **User Access Review** from NetSuite. 2. Click **UAR Additional Reviewer** to log in. Your User Access Review dashboard is displayed. -Here is an example additional reviewer dashboard showing new assignments. +The following is an example additional reviewer dashboard showing new assignments. ![Additional Reviewer Dashboard](/images/platgovnetsuite/uar/uar_additional_reviewer/dashboard_add_reviewer.webp) diff --git a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_uar_list.md b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_uar_list.md index c4c4cdfe0e..c4e29dd272 100644 --- a/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_uar_list.md +++ b/docs/platgovnetsuite/uar/addrevieweroverview/add_reviewer_uar_list.md @@ -10,7 +10,7 @@ Access your Additional Reviewer list from **UAR List** in your menu bar, or one shortcuts. Your UAR List displays either the list of Global Reviews or Single Reviews. The view is controlled with the **Sort By** selection in the Filters section. -Here is an example of the **Global** review list: +The following is an example of the **Global** review list: ![UAR list additional reviewer](/images/platgovnetsuite/uar/uar_additional_reviewer/additional_user_uar_list.webp) diff --git a/docs/platgovnetsuite/uar/adminoverview/admin_overview.md b/docs/platgovnetsuite/uar/adminoverview/admin_overview.md index e6bac55dff..95ef4129e7 100644 --- a/docs/platgovnetsuite/uar/adminoverview/admin_overview.md +++ b/docs/platgovnetsuite/uar/adminoverview/admin_overview.md @@ -13,7 +13,7 @@ sidebar_position: 30 - Create Reviews to a Role - View Reviews -Here is an example of the Admin dashboard displayed when you log in: +The following is an example of the Admin dashboard displayed when you log in: ![Admin Dashboard](/images/platgovnetsuite/uar/dashboard_admin.webp) diff --git a/docs/platgovnetsuite/uar/adminoverview/admin_owner_list.md b/docs/platgovnetsuite/uar/adminoverview/admin_owner_list.md index cd2064d7c8..f206c61e03 100644 --- a/docs/platgovnetsuite/uar/adminoverview/admin_owner_list.md +++ b/docs/platgovnetsuite/uar/adminoverview/admin_owner_list.md @@ -11,7 +11,7 @@ from reviews. All changes are captured in the [UAR History](/docs/platgovnetsui Auditors can view the Owner list and Owner notes, but can't add or remove owners. -Here is an example of the **Owner List**: +The following is an example of the **Owner List**: ![Administrator Owner list](/images/platgovnetsuite/uar/uar_admin/owner_list.webp) diff --git a/docs/platgovnetsuite/uar/adminoverview/admin_pending_assignments.md b/docs/platgovnetsuite/uar/adminoverview/admin_pending_assignments.md index 3c1a4c6e06..045f88509f 100644 --- a/docs/platgovnetsuite/uar/adminoverview/admin_pending_assignments.md +++ b/docs/platgovnetsuite/uar/adminoverview/admin_pending_assignments.md @@ -10,7 +10,7 @@ This view makes it easy to identify roles without owners, and facilitates adding **Pending Role Assignments** from your menu bar. All changes are captured in the [UAR History](/docs/platgovnetsuite/uar/adminoverview/uar_history.md). -Here is an example of the **Pending Role Assignments**: +The following is an example of the **Pending Role Assignments**: ![Pending role assignments](/images/platgovnetsuite/uar/uar_admin/pending_role_assignments.webp) diff --git a/docs/platgovnetsuite/uar/adminoverview/admin_uar_list.md b/docs/platgovnetsuite/uar/adminoverview/admin_uar_list.md index 14894b50de..6b3972c23e 100644 --- a/docs/platgovnetsuite/uar/adminoverview/admin_uar_list.md +++ b/docs/platgovnetsuite/uar/adminoverview/admin_uar_list.md @@ -11,7 +11,7 @@ shortcuts. Your UAR List displays either the list of Global Reviews or Single R controlled with the **Sort By** selection in the Filters section. All changes are captured in the [UAR History](/docs/platgovnetsuite/uar/adminoverview/uar_history.md). -Here is an example of the **Global** review list: +The following is an example of the **Global** review list: ![Administrator UAR list](/images/platgovnetsuite/uar/uar_admin/admin_uar.webp) @@ -125,7 +125,7 @@ Reminders can be sent from the administrator's UAR List or from the Review list ## Review List -Clicking on a **Name** in the UAR List opens the Review List. Here is an example. +Clicking on a **Name** in the UAR List opens the Review List. The following is an example. ![Review List](/images/platgovnetsuite/uar/uar_admin/admin_review_list.webp) diff --git a/docs/platgovnetsuite/uar/adminoverview/owner_membership_reviews.md b/docs/platgovnetsuite/uar/adminoverview/owner_membership_reviews.md index 54b63fb13c..35f0f61ab3 100644 --- a/docs/platgovnetsuite/uar/adminoverview/owner_membership_reviews.md +++ b/docs/platgovnetsuite/uar/adminoverview/owner_membership_reviews.md @@ -27,7 +27,7 @@ You can perform these actions as part of your review: - Assign an Additional Reviewer - Complete the Membership Review -Once an action is taken, the Membership review changes to **In Progress**. +After an action is taken, the Membership review changes to **In Progress**. Other available actions: @@ -79,7 +79,7 @@ To remove one or more users from the role: ![Reason for change](/images/platgovnetsuite/uar/uar_owner/change_request_reason.webp) - A Change Request is generated for each user removed from the role. Status is changed to either + A Change Request is generated for each user removed from the role. Status changes to either **Change Request** and the **Change Request ID** added, or **Waiting for CR** if there is an existing change request in progress as part of another review. Click the **Change Request ID** to open the Change Request. @@ -107,7 +107,7 @@ You can add additional reviewers to the review: ### Complete the Membership Review Each row must be in the **Complete** or **CR Complete status**, with all change requests finished -before you can click **Complete Review**. Once a review is complete, no further changes can be made. +before you can click **Complete Review**. After a review is complete, no further changes can be made. ## Review Notes diff --git a/docs/platgovnetsuite/uar/adminoverview/owner_permission_reviews.md b/docs/platgovnetsuite/uar/adminoverview/owner_permission_reviews.md index 3a0b22c922..86a67d7651 100644 --- a/docs/platgovnetsuite/uar/adminoverview/owner_permission_reviews.md +++ b/docs/platgovnetsuite/uar/adminoverview/owner_permission_reviews.md @@ -41,7 +41,7 @@ You can perform these actions as part of your review: - Add a Permission - Complete the Permission Review -Once an action is taken, the Permission review changes to **In Progress**. +After an action is taken, the Permission review changes to **In Progress**. Other available actions: @@ -74,7 +74,7 @@ To change a permission level: ![Reason for change](/images/platgovnetsuite/uar/uar_owner/change_request_reason.webp) - A Change Request is generated for each level change. Status is changed to either **Change + A Change Request is generated for each level change. Status changes to either **Change Request** and the **Change Request ID** added, or **Waiting for CR** if there is an existing change request in progress as part of another review. Click the **Change Request ID** to open the Change Request. @@ -98,7 +98,7 @@ To add a permission: 4. Enter a brief description of why the change is requested when prompted for the **Reason for Change**. Click **Accept** when complete. - A Change Request is generated for each new permission. Status is changed to either **Change + A Change Request is generated for each new permission. Status changes to either **Change Request** and the **Change Request ID** added, or **Waiting for CR** if there is an existing change request in progress as part of another review. Click the **Change Request ID** to open the Change Request. @@ -111,7 +111,7 @@ To add a permission: ### Complete the Permission Review Each permission must be in the **Complete** or **CR Complete status**, with all change requests -finished before you can click **Complete Review**. Once a review is complete, no further changes can +finished before you can click **Complete Review**. After a review is complete, no further changes can be made. ![Permission review complete when all rows are complete](/images/platgovnetsuite/uar/uar_owner/permission_review_complete.webp) diff --git a/docs/platgovnetsuite/uar/auditoroverview/auditor_overview.md b/docs/platgovnetsuite/uar/auditoroverview/auditor_overview.md index ad597729e1..303e9f998d 100644 --- a/docs/platgovnetsuite/uar/auditoroverview/auditor_overview.md +++ b/docs/platgovnetsuite/uar/auditoroverview/auditor_overview.md @@ -12,7 +12,7 @@ Auditors have view only access to specific UAR data. Auditors log in to NetSuit 1. Open **User Access Review** from NetSuite. 2. Click **UAR Auditor** to log in. Your auditor dashboard is displayed. -Here is an example auditor dashboard showing new assignments. +The following is an example auditor dashboard showing new assignments. ![Auditor Dashboard](/images/platgovnetsuite/uar/uar_auditor/dashboard_auditor.webp) diff --git a/docs/platgovnetsuite/uar/owneroverview/owner_overview.md b/docs/platgovnetsuite/uar/owneroverview/owner_overview.md index 896c6317d9..eb6905cf0d 100644 --- a/docs/platgovnetsuite/uar/owneroverview/owner_overview.md +++ b/docs/platgovnetsuite/uar/owneroverview/owner_overview.md @@ -22,7 +22,7 @@ access the dashboard. 1. Open **User Access Review** from NetSuite. 2. Click **UAR Owner** to log in. Your owner dashboard is displayed. -Here is an example owner dashboard showing new assignments. +The following is an example owner dashboard showing new assignments. ![UAR Owner dashboard](/images/platgovnetsuite/uar/uar_owner/dashboard_owner.webp) diff --git a/docs/platgovnetsuite/uar/owneroverview/owner_uar_list.md b/docs/platgovnetsuite/uar/owneroverview/owner_uar_list.md index cda613fb5b..73298d1c94 100644 --- a/docs/platgovnetsuite/uar/owneroverview/owner_uar_list.md +++ b/docs/platgovnetsuite/uar/owneroverview/owner_uar_list.md @@ -10,7 +10,7 @@ Access your owner User Access Reviews List from **UAR List** in your menu bar, shortcuts. Your UAR List displays either the list of Global Reviews or Single Reviews. The view is controlled with the **Sort By** selection in the Filters section. -Here are examples of the **Global** and **Single** review lists: +The following are examples of the **Global** and **Single** review lists: ![Owner UAR list](/images/platgovnetsuite/uar/uar_owner/uar_list_owner.webp) diff --git a/docs/platgovnetsuite/uar/uar_overview.md b/docs/platgovnetsuite/uar/uar_overview.md index 66187a3f6a..13b2f1d546 100644 --- a/docs/platgovnetsuite/uar/uar_overview.md +++ b/docs/platgovnetsuite/uar/uar_overview.md @@ -6,14 +6,14 @@ sidebar_position: 110 # User Access Review -Roles and Permissions aren't a set once and forget about them activity. Both should be reviewed -regularly to ensure your data is secured and users in your organization have the right access. +Roles and permissions aren't a configure-once activity. Both require regular review +to ensure your data is secured and users in your organization have the right access. **User Access Review** streamlines this review process, making it easy to manage and review all access to your NetSuite data. UAR users must have a [license](/docs/platgovnetsuite/uar/install_app.md). ## Terminology -Here are the basic terms used throughout the UAR guide: +The following are the basic terms used throughout the UAR guide: - UAR Reviewer Roles - Review Types diff --git a/docs/platgovnetsuite/user_managment_overview.md b/docs/platgovnetsuite/user_managment_overview.md index 806bc4a2ee..e08a5d6d81 100644 --- a/docs/platgovnetsuite/user_managment_overview.md +++ b/docs/platgovnetsuite/user_managment_overview.md @@ -10,7 +10,7 @@ These reports are available on the User Management Menu: - **Employees with Standard Roles** identifies all employees assigned to standard roles. - **Employees with Unused Logins** identifies any employees who have not logged in. -- **Employee Permission Changes** identifies all permission changes that have occurred. +- **Employee Permission Changes** identifies all permission changes. - **Unused Roles - Not Assigned** identifies roles not assigned to any user. - **Unused Roles - Assigned But Not In Use** identifies roles assigned to a user, but never used. - **Role Assignments with No Login in Six Months** identifies assigned roles where a user has not diff --git a/docs/platgovnetsuite/what_does_strongpoint_document.md b/docs/platgovnetsuite/what_does_strongpoint_document.md index d977c3d357..20d41f8b19 100644 --- a/docs/platgovnetsuite/what_does_strongpoint_document.md +++ b/docs/platgovnetsuite/what_does_strongpoint_document.md @@ -48,9 +48,9 @@ more of the following reasons: | --------------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Custom Report | Other | Custom Reports are documented including the report name, type, and the date the report was last modified. | Changing these can impact what data is shown on the report. | Example: Change to Report Layout - detects the Date Last Modified in the Analytics Audit Log was changed and creates a change log. - Change Log indicates when the Report was updated. - You need to look at the Custom Report itself:
1. Open **Customize the Custom Report**
2. Click **More Options**
3. Open **Audit Trail** tab. | | PDF Template | Other | PDF Templates are document including the template name, type, and the date the template was last modified. | Changing these can impact email templates and other areas where PDF templates are used. | TBD | -| Standard Column Field | Standard Objects | Customization records are created only for Standard objects that are in use by scripted objects such as Workflows or Scripts. These are tracked to identify the automation dependencies. | No risk since there is no way to change standard objects in NetSuite. | If a standard object is added to or removed from a customization, a change log will be created for that customization. | -| Standard Report | Standard Objects | Customization records are created only for Standard objects that are in use by scripted objects such as Workflows or Scripts. These are tracked to identify the automation dependencies. | No risk since there is no way to change standard objects in NetSuite. | If a standard object is added to or removed from a customization, a change log will be created for that customization. | -| Standard Sub List | Standard Objects | Customization records are created only for Standard objects that are in use by scripted objects such as Workflows or Scripts. These are tracked to identify the automation dependencies. | No risk since there is no way to change standard objects in NetSuite. | If a standard object is added to or removed from a customization, a change log will be created for that customization. | +| Standard Column Field | Standard Objects | Customization records are created only for Standard objects that are in use by scripted objects such as Workflows or Scripts. These are tracked to identify the automation dependencies. | No risk since there is no way to change standard objects in NetSuite. | If a standard object is added to or removed from a customization, a change log is created for that customization. | +| Standard Report | Standard Objects | Customization records are created only for Standard objects that are in use by scripted objects such as Workflows or Scripts. These are tracked to identify the automation dependencies. | No risk since there is no way to change standard objects in NetSuite. | If a standard object is added to or removed from a customization, a change log is created for that customization. | +| Standard Sub List | Standard Objects | Customization records are created only for Standard objects that are in use by scripted objects such as Workflows or Scripts. These are tracked to identify the automation dependencies. | No risk since there is no way to change standard objects in NetSuite. | If a standard object is added to or removed from a customization, a change log is created for that customization. | ## Not Documented in the Customization Record diff --git a/docs/platgovnetsuite/what_is_a_spider.md b/docs/platgovnetsuite/what_is_a_spider.md index 1badcef642..3890d15842 100644 --- a/docs/platgovnetsuite/what_is_a_spider.md +++ b/docs/platgovnetsuite/what_is_a_spider.md @@ -7,7 +7,7 @@ sidebar_position: 16 # What is a spider The Spider searches your account and creates the documentation for your customizations. The spider -includes dependencies for saved searches in standard and custom fields. Here are items documented by +includes dependencies for saved searches in standard and custom fields. The following items are documented by the spider: | | | | @@ -35,10 +35,7 @@ There are three ways to use the Spider: ## Manual Spider -Creates the initial documentation of your account. It has the ability to fully document your account -by Spidering all the customization records as well doing a full update on the records in your -account (every customization). The initial manual Spider is run during as part of the installation -process: [Running the Spider](/docs/platgovnetsuite/installation/running_the_spider.md). +Creates the initial documentation of your account. It fully documents your account by spidering all the customization records and updating every customization. The initial manual Spider runs as part of the installation process: [Running the Spider](/docs/platgovnetsuite/installation/running_the_spider.md). When running the spider, you must keep the window open for the spider to continue working. Don't change roles or accounts during spidering. NetSuite security standards require an active @@ -48,12 +45,10 @@ You can specify specific record types to focus the spider: ## AutoSpider -The AutoSpider monitors your account on an ongoing basis to see if customization changes have -occurred. This is a light scan of the data to determine if there were any changes. If changes are -detected, you are reminded to ReSpider your account. +The AutoSpider monitors your account on an ongoing basis to detect customization changes. It performs a light scan of the data. If changes are detected, it reminds you to ReSpider your account. Best practice is to run the AutoSpider regularly. If the AutoSpider isn't run, your Change Logs -will be missing the **Changed by** and **Actual Change Date** fields. When the Change Log is newly +are missing the **Changed by** and **Actual Change Date** fields. When the Change Log is newly created, the fields contain **Pending AutoSpider**. If too many days go by, the fields change to **Couldn't be determined**. @@ -62,9 +57,7 @@ created, the fields contain **Pending AutoSpider**. If too many days go by, the The AutoSpider Portlet is set up as part of the installation process: [Setting Up the AutoSpider and Alerts](/docs/platgovnetsuite/installation/setting_up_auto_spider_alerts.md). -The **AutoSpider Portlet** is required to update certain object types in NetSuite. Once triggered -through the dashboard portlet, it picks up all changes on custom objects and triggers the scheduled -scripts to reflect them in the Customization records, going back two days. +The **AutoSpider Portlet** is required to update certain object types in NetSuite. When triggered through the dashboard portlet, it picks up all changes on custom objects and triggers the scheduled scripts to reflect them in the Customization records, going back two days. The AutoSpider portlet is required to update these object types: @@ -85,15 +78,8 @@ The AutoSpider portlet is required to update these object types: ## ReSpider Now -The **ReSpider Now** feature is used to document or update documentation for a specific -customization or a specific set of customizations on demand. After you finish adding your -new/updated objects to your customization record or change request, click **ReSpider Now** on -your form, and your documentation is updated in real time. Here is an example of a customization -record with the **ReSpider Now** option: +The **ReSpider Now** feature documents or updates documentation for a specific customization or set of customizations on demand. After you finish adding your new or updated objects to your customization record or change request, click **ReSpider Now** on your form. Documentation updates in real time. The following is an example of a customization record with the **ReSpider Now** option: ![ReSpiderNow](/images/platgovnetsuite/respider_now.webp) -Proposed customizations don't work for custom forms and custom reports, since they don't have -Script IDs. NetSuite is working on this. For searches, -**ReSpider Now** uses the permissions of the current logged-in user. If the user doesn't have the -correct permission set, the search shows as private. +Proposed customizations don't work for custom forms and custom reports because they don't have Script IDs. For searches, **ReSpider Now** uses the permissions of the current logged-in user. If the user doesn't have the correct permission set, the search shows as private. From a7b373ee738572203995204c8d74daf7d000b194 Mon Sep 17 00:00:00 2001 From: jth-nw Date: Mon, 4 May 2026 20:46:33 -0500 Subject: [PATCH 16/27] fix(platgovnetsuite): restore faq.md heading anchor broken by Dale pass Dale changed a heading's question mark to an em-dash, which broke the internal anchor link. Restored the original heading text. Generated with AI Co-Authored-By: Claude Code --- docs/platgovnetsuite/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platgovnetsuite/faq.md b/docs/platgovnetsuite/faq.md index 6e9869428d..82bddee3d2 100644 --- a/docs/platgovnetsuite/faq.md +++ b/docs/platgovnetsuite/faq.md @@ -55,6 +55,6 @@ capabilities. Because Platform Governance for NetSuite creates complete document an ongoing basis with your NetSuite and Salesforce records, you can use the pre-built searches or create your own to get instant visibility into your account. Platform Governance for NetSuite greatly reduces the time to find information and identify interdependencies. NetSuite and Salesforce Administrators still need to perform appropriate due diligence and analysis to ensure their actions are appropriate and safe. -#### Who needs a Platform Governance for NetSuite License — what is the difference between an editor and a viewer +#### Who needs a Platform Governance for NetSuite License? What is the difference between an editor and a viewer? Licenses are required for editors of Platform Governance for NetSuite (people who create or edit processes or view customization documentation). No license is required for users who only view documentation. Companies typically start with a small team (the base includes three seats) and add users as usage expands. From 043e5a82a42a30cb16e30fde0fce4c975a797601 Mon Sep 17 00:00:00 2001 From: krzysztofstaszalek Date: Tue, 5 May 2026 13:03:38 +0200 Subject: [PATCH 17/27] EPP_minor_updates_05052026 --- .../admin/cap_module/capai.md | 26 ++++++----- .../admin/cap_module/capmodule.md | 4 ++ .../admin/cap_module/deeppacket.md | 4 ++ .../admin/cap_module/newoutlook.md | 44 ++++++++++--------- .../admin/dc_module/globalsettings.md | 19 +++++--- .../admin/denylistsallowlists/allowlists.md | 4 ++ .../admin/denylistsallowlists/denylists.md | 3 ++ 7 files changed, 64 insertions(+), 40 deletions(-) diff --git a/docs/endpointprotector/admin/cap_module/capai.md b/docs/endpointprotector/admin/cap_module/capai.md index 08dbba20e7..de780791c4 100644 --- a/docs/endpointprotector/admin/cap_module/capai.md +++ b/docs/endpointprotector/admin/cap_module/capai.md @@ -23,24 +23,22 @@ By implementing these controls, organizations can ensure that sensitive informat ## AI Interaction Visibility and Control in Netwrix Endpoint Protector: Data Loss Prevention for LLMs -By incorporating this capability into our DLP solutions, we ensure secure and compliant use of cutting-edge AI technologies, including ChatGPT, Microsoft Copilot, Google Gemini, DeepSeek, X Grok, and Claude, reinforcing our commitment to delivering superior data protection. Moreover, we extend coverage for Microsoft Copilot in Windows ecosystem, supporting the embedded Copilot add-in within Windows 11, the New Outlook, and the New Teams. - -As artificial intelligence continues to transform communication and collaboration processes, Endpoint Protector is committed to developing innovative solutions that address the complex challenges of safeguarding data in modern enterprises. This release marks a significant advancement in our mission to provide superior data security in an increasingly AI-driven world. +Endpoint Protector extends Data Loss Prevention to the most widely used AI technologies — including ChatGPT, Microsoft Copilot, Google Gemini, DeepSeek, X Grok, Claude, Meta AI, and Perplexity — ensuring secure and compliant use across your organization. Coverage includes the embedded Microsoft Copilot add-in in Windows 11, New Outlook, New Teams, and Edge. Endpoint Protector also provides visibility and control over ChatGPT and Copilot native clients. ## How to configure Netwrix EPP to be able to monitor AI prompt transactions? To monitor or control AI prompts with EPP, you need to meet the following prerequisites: -- EPP Server version 2509 or newer -- EPP Client version 2511 or newer +- use latest EPP Server version +- use latest EPP Client version - CAP license with the Content Aware Protection (CAP) module enabled - DPI (Deep Packet Inspection) module enabled If all of the above requirements are fulfilled, most of the setup is already complete. This is because any existing web browser monitor/control policy will automatically apply to user interactions with supported AI chat applications, enforcing your policy definitions when violations occur. -## Use Case Example: +## Use Case Example -### I. Simple CAP Policy Triggering on Credit Card Detection** +### I. Simple CAP Policy Triggering on Credit Card Detection To configure a CAP policy for this purpose: @@ -67,10 +65,10 @@ To configure a CAP policy for this purpose: **Description of video**: -At the initial stage, I conducted a simple comparative test across several AI platforms: Copilot, ChatGPT, Google Gemini, DeepSeek, and X Grok.​ +The test covers several AI platforms: Copilot, ChatGPT, Google Gemini, DeepSeek, and X Grok. - **Responsiveness Check** – Verified that each AI model was actively responding, ensuring the interaction was genuine and not a simulated or dummy web transaction triggered by the URL.​ - - **Data Leakage Simulation** – Copied and pasted real credit card (CC) patterns and requested validation from each AI. By the way – samples are generated by one of AI engine:). The CAP (DLP) policy was configured to automatically block any transaction if CC data was detected.​ + - **Data Leakage Simulation** – Credit card (CC) patterns were submitted to each AI platform to request validation. Sample data was generated using an AI engine. The CAP policy was configured to automatically block any transaction containing CC data. - **Cross-Engine Validation** – Repeated the same procedure across all mentioned AI engines to confirm consistent behavior and validate DLP enforcement.​ - **Conclusion** – The demonstration confirms that **Netwrix EPP DLP integrates seamlessly with AI tools such as Copilot, ChatGPT, Google Gemini, DeepSeek, and X Grok** to **prevent data leakage, enforce compliance, and ensure secure information handling at the endpoint level**, while maintaining a positive user experience. @@ -84,7 +82,9 @@ To configure a CAP policy for this purpose: 2. Define CAP application exit points by selecting the web browsers you want to monitor or control. Make sure the relevant browsers are checked so the policy will be applied when users interact with AI chat applications through these browsers. - **Tip:** For Copilot plugins in New Outlook, Teams, or Windows 11 25H2, it is recommended to also verify the in-app definitions for Outlook and Teams when configuring policies. +:::tip +For Copilot plugins in New Outlook, Teams, or Windows 11 25H2, also verify the in-app definitions for Outlook and Teams when configuring policies. +::: ![Define CAP application exit points](capai_usecase01_02.webp) @@ -92,8 +92,10 @@ To configure a CAP policy for this purpose: ![Define CAP Policy Denylists](capai_usecase02_01.webp) -\*\*Tip:\*\* You can use contextual rules to create complex pattern definitions for more accurate and flexible policy enforcement. -![Define CAP Policy conetual parameters](capai_usecase02_02.webp) +:::tip +You can use contextual rules to create complex pattern definitions for more accurate and flexible policy enforcement. +::: +![Define CAP Policy contextual parameters](capai_usecase02_02.webp) 4. Save the policy and assign it to your selected endpoints. 5. This will ensure that the policy is enforced on the devices where you want to monitor or control AI prompt transactions. diff --git a/docs/endpointprotector/admin/cap_module/capmodule.md b/docs/endpointprotector/admin/cap_module/capmodule.md index e866551f5f..bdb41b9cc5 100644 --- a/docs/endpointprotector/admin/cap_module/capmodule.md +++ b/docs/endpointprotector/admin/cap_module/capmodule.md @@ -36,6 +36,10 @@ points: - Print screens - Printers and others +:::note +**Known limitation:** When using Zoho WorkDrive or GDrive (Google Drive) sync applications, reported or blocked file names display internal cache paths instead of the original file name, which prevents location-based and file name denylists from working reliably. Block and Report log entries may be duplicated due to application-level transfer retries, and reported file sizes may be inaccurate. File shadowing works intermittently — shadows may contain corrupted content or be created without a hash, preventing download from the server. +::: + ## Content Aware Protection Activation Content Aware Protection comes as the second level of data protection available in Endpoint diff --git a/docs/endpointprotector/admin/cap_module/deeppacket.md b/docs/endpointprotector/admin/cap_module/deeppacket.md index b17c21b776..4986bd08b2 100644 --- a/docs/endpointprotector/admin/cap_module/deeppacket.md +++ b/docs/endpointprotector/admin/cap_module/deeppacket.md @@ -30,6 +30,10 @@ To ensure consistent DPI behavior after enabling or disabling the feature or upg the Endpoint Protector, a restart of your computer is required. ::: +:::note +**Known limitation:** Location-based denylists and allowlists are not reliable when Deep Packet Inspection (DPI) is active. DPI operates at the network level and identifies files by matching transferred data hashes against files on the local machine. If the same file exists in multiple locations, Endpoint Protector cannot determine which copy was transferred, and location-based rules cannot be applied. +::: + ## Stealthy DPI vs. regular DPI What are the different network visibility strategies available on Windows? diff --git a/docs/endpointprotector/admin/cap_module/newoutlook.md b/docs/endpointprotector/admin/cap_module/newoutlook.md index 69cac86206..69da771ebb 100644 --- a/docs/endpointprotector/admin/cap_module/newoutlook.md +++ b/docs/endpointprotector/admin/cap_module/newoutlook.md @@ -10,7 +10,7 @@ Starting from Endpoint Protector Clients version 5.9.4.3, New Outlook can be ful Microsoft 365 Web Add-ins are associated with user accounts rather than computers or devices. Once an add-in is deployed to a user account, every device that the user employs to access that account will have the add-in available. This means it cannot be restricted to just one device, such as the user's Mac computer only. -For detailed instructions and more information, please refer to the official documentation available through Microsoft and Endpoint Protector resources: +For detailed instructions and more information, refer to the official documentation available through Microsoft and Endpoint Protector resources: - [Microsoft resources](https://learn.microsoft.com/en-us/office/dev/add-ins/overview/office-add-ins) - [Centralized deployment FAQ](https://learn.microsoft.com/en-us/microsoft-365/admin/manage/centralized-deployment-faq?view=o365-worldwide) @@ -19,7 +19,7 @@ Both Netwrix and Microsoft recommend deploying the add-in in phases, starting wi ::: :::warning Important -It is important to configure the policy correctly so that the add-in is deployed selectively, rather than to all users—especially those who do not require it. Also the javascript's variables configuration allows for the add-in to remain inactive or non-obtrusive unless the EPP agent is running on a device. This ensures that the add-in does not block operations unnecessarily if the agent is not active. Please refer to dedicated subchapter [Default Behavior of New Outlook Add-in and EPP Client](#default-behavior-of-new-outlook-add-in-and-epp-client). +It is important to configure the policy correctly so that the add-in is deployed selectively, rather than to all users—especially those who do not require it. The JavaScript variable configuration also allows the add-in to remain inactive or non-obtrusive unless the EPP agent is running on a device. This ensures that the add-in does not block operations unnecessarily if the agent is not active. Refer to the dedicated subchapter [Default Behavior of New Outlook Add-in and EPP Client](#default-behavior-of-new-outlook-add-in-and-epp-client). ::: When you install an add-in in Outlook.com, it will also appear in other versions of Outlook. For example, if you install an add-in in Outlook.com, you will see it when you open the desktop version of Outlook. @@ -47,12 +47,14 @@ The Endpoint Protector add-in requires certain files to be hosted by the custome Hosting the above ensures that the add-in can communicate appropriately with the EPP system to enable its functionalities. + You are responsible for hosting these files. Host them at a publicly reachable URL. The URL of each hosted file must match the value configured in the manifest. Refer to the following chapters for details. + :::warning Important - Having any downtime to the hosted files (mainpage.html, validator.js) will result in an impossibility to send ANY emails for the users that have the add-in assigned to their account. + Any downtime affecting the hosted files (mainpage.html, validator.js) will prevent users with the add-in assigned from sending any emails. ::: :::note - It is recommended that the two files, mainpage.html and validator.js, be hosted together in the same directory (folder) and be accessible from the internet. If you choose to host the files differently, you must update the link to the validator in mainpage.html by modifying the "src" attribute as follows: + Host mainpage.html and validator.js in the same directory. If you host the files separately, update the validator link in mainpage.html by modifying the `src` attribute as follows: ```html ``` @@ -65,7 +67,7 @@ Ensure that a standard Endpoint Protector (EPP) Content Aware Protection (CAP) p Ensure that the setting under Content Aware Protection → Deep Packet Inspection called "Block Unsupported Protocols in New Outlook" is turned off. This setting is no longer needed if the EPP add-in is in use. :::note -On MacOS a EPP certificate is utilized to ensure secure communication between the add-in and the EppClient. Please refer to the existing User Manual chapter for [detailed instructions](https://docs.netwrix.com/docs/endpointprotector/admin/cap_module/deeppacket#deep-packet-inspection-certi%EF%AC%81cate-on-macos). If you have configured DPI certificate on MacOS, you can ignore this note. +On macOS, an EPP certificate is used to ensure secure communication between the add-in and the EppClient. Refer to the existing User Manual chapter for [detailed instructions](./deeppacket#dpi-certi%EF%AC%81cate-on-macos). If you have configured the DPI certificate on macOS, you can ignore this note. ::: ## Pre-configuring add-in (manifest.xml) @@ -79,10 +81,10 @@ At the core of any Office Add-in is the manifest file (.xml). This file acts as In short, the manifest tells Outlook how to integrate and run the add-in. If the manifest is missing or incorrect, the add-in won't function properly. -In order to prepare the Netwrix EPP add-in for Outlook accounts, the provided template needs to be updated in several places listed below. All these places are marked with the comment ``. +To configure the EPP add-in for Outlook accounts, update the provided template in the places listed below. All these places are marked with the comment ``. 1. Define icons location\ -This part is mandatory for Microsoft add-in validator. Edit it by defining proper URL to mentioned files. +This is required by the Microsoft add-in validator. Replace the placeholder URLs with the actual URLs for the icon files. ```xml @@ -92,8 +94,8 @@ This part is mandatory for Microsoft add-in validator. Edit it by defining prope ``` -2. Define domain name for add-in url - Edit it by defining proper domain. +2. Define the add-in domain name + Replace `www.example.com` with your actual domain. ```xml @@ -104,8 +106,8 @@ This part is mandatory for Microsoft add-in validator. Edit it by defining prope - If the same domain is used for all URLs, it only needs to be added once. - Extend the existing list by adding your domain at the end between the `` tags, and before the closing `` tag. -3. Define validator location\ - Edit it by defining proper URL to validator. +3. Define the validator location\ + Replace the placeholder URL with the actual URL to your `validator.js` file. ```xml @@ -116,8 +118,8 @@ This part is mandatory for Microsoft add-in validator. Edit it by defining prope ``` -4. Define mainpage validator\ - Edit it by defining proper URL to mainpage validator. +4. Define the main page URL\ + Replace the placeholder URL with the actual URL to your `mainpage.html` file. ```xml @@ -146,7 +148,7 @@ However, the add-in has a predefined, hardcoded behavior when it cannot communic ```javascript const DEFAULT_ACTION = true; // true = Allow, false = block ``` -3. Change argument value "true" for "false". +3. Change the value from `true` to `false`. :::warning Important Use this option carefully and ensure it is aligned with your rollout plan to avoid interruptions in essential business email communication. @@ -159,7 +161,7 @@ There is also an option to replace the add-in default message in the tooltip pro **To change that:** 1. Edit hosted **validator.js** file. -2. Edit 2nd line "DEFAULT_MESSAGE" value: +2. Edit the `DEFAULT_MESSAGE` value on the second line: ```javascript const DEFAULT_MESSAGE = "This email was blocked due to a policy violation. Please review and modify the message before resending."; ``` @@ -172,9 +174,9 @@ This prompt supports only one language locale. ## Manual Deployment Method -Manual deployment method is not the recommended one as it requires to be repeated on each user account. This method is intended for pilot phases, troubleshooting or feature PoC's. +The manual deployment method is not recommended because it must be repeated for each user account. This method is intended for pilot phases, troubleshooting, or feature PoCs. -This option is only available if your organization defines the possibility to add custom add-ins by user. +This option is only available if your organization allows users to add custom add-ins. Refer to official Microsoft KB article: [Use add-ins in Outlook](https://support.microsoft.com/en-us/office/use-add-ins-in-outlook-1ee261f9-49bf-4ba6-b3e2-2ba7bcab64c8) @@ -182,17 +184,17 @@ Refer to official Microsoft KB article: [Use add-ins in Outlook](https://support 1. Host validators and icon files. 2. Preconfigure manifest.xml as described in previous chapter. -3. In your preferred browser, go to https://aka.ms/olksideload. This opens Outlook on the web, then loads the Add-Ins for Outlook dialog after a few seconds: +3. In your preferred browser, go to https://aka.ms/olksideload. This opens Outlook on the web and loads the **Add-Ins for Outlook** dialog after a few seconds. 4. Select **My add-ins**. 5. In the Custom Add-in's section, select **Add a custom add-in**, then choose **Add from file**. ![Custom addin file selection](mscustomaddin.webp "Custom addin file selection") 6. Select the XML file for the add-in. 7. Select **Open** to install the add-in. -8. After making changes, please allow some time for them to propagate. According to Microsoft, this process can take anywhere from a few minutes to up to 24 hours. +8. After making changes, allow some time for them to propagate. According to Microsoft, this process can take anywhere from a few minutes to up to 24 hours. ## Central Deployment Method -The central deployment method provides administrators with the capability to deploy the EPP New Outlook add-in in phases across global user populations. This approach helps minimize administrative effort and ensures a smooth implementation process. For detailed guidance, please consult the official Microsoft Knowledge Base (KB): [Office add-ins](https://learn.microsoft.com/en-us/microsoft-365/admin/manage/office-addins?view=o365-worldwide) +The central deployment method provides administrators with the capability to deploy the EPP New Outlook add-in in phases across global user populations. This approach helps minimize administrative effort and ensures a smooth implementation process. For detailed guidance, refer to the official Microsoft Knowledge Base (KB): [Office add-ins](https://learn.microsoft.com/en-us/microsoft-365/admin/manage/office-addins?view=o365-worldwide). **To deploy the add-in through the Microsoft Admin Center (https://admin.microsoft.com/):** @@ -208,4 +210,4 @@ The central deployment method provides administrators with the capability to dep 7. When the desired list appears under **To be added**, click **Next** and then click **Accept Permissions**. Review the needed permissions and click **Accept**. 8. Ensure to keep **Deployment Method** as **Fixed (Default)**. 9. Click **Next** and then **Finish deployment**. -10. After making changes, please allow some time for them to propagate. According to Microsoft, this process can take anywhere from a few minutes to up to 24 hours. +10. After making changes, allow some time for them to propagate. According to Microsoft, this process can take anywhere from a few minutes to up to 24 hours. diff --git a/docs/endpointprotector/admin/dc_module/globalsettings.md b/docs/endpointprotector/admin/dc_module/globalsettings.md index 8ead46e743..dae0d5b0ea 100644 --- a/docs/endpointprotector/admin/dc_module/globalsettings.md +++ b/docs/endpointprotector/admin/dc_module/globalsettings.md @@ -139,8 +139,7 @@ the Client’s behavior for each specific entity (Global, Groups, and Computers - User Remediation Pop-up – this setting is available when the - [User Remediation](/docs/endpointprotector/admin/systempar.md#user-remediation) feature is active and enables -[User Remediation](/docs/endpointprotector/admin/systempar.md#user-remediation) feature is active and enables + [User Remediation](/docs/endpointprotector/admin/systempar.md#user-remediation) feature is active and enables User Remediation pop-up notifications for end-users. - Enforce User Remediation Pop-up - this setting is available only if the User Remediation Pop-up setting is enabled. When this setting is enabled, end-users cannot disable User Remediation Pop-up @@ -633,14 +632,14 @@ For example, when a user opens Microsoft Word, an Endpoint Protector DLL is load - Advanced Scanning Exceptions is a list of applications into which Endpoint Protector won't inject its DLL when the "Advanced Printer and MTP Scanning" is enabled. For example, many applications can't be used to print or to copy files to MTP devices, so it does not make sense to inject the Endpoint Protector DLL into them. For best performance or to avoid unexpected interactions with Endpoint Protector, these applications can be added to the “Advanced Scanning Exceptions” list. -- Block Print from Browsers – Enable this setting to prevent users from printing web pages from any - supported browser on Windows. +- Block Print from Browsers – prevents users from printing web pages from any supported browser on Windows. For details, see [Block Print from Browsers](#block-print-from-browsers). :::note The Content-Aware Protection (CAP) feature is available only for Chrome and Edge via a dedicated extension. For other browsers, this setting will block print functionality. ::: +![Block Print from Browsers settings](blockprintone.webp) - Block Print if CAP Cannot Process File – This setting determines the action if CAP cannot access the file content. By default, printing is allowed. This option applies only to Chrome and Edge @@ -649,10 +648,10 @@ For example, many applications can't be used to print or to copy files to MTP de - File Hash - if you enable this setting, a file hash will be generated and included in the file transfer logs. -- Scan Printed Document – select if you want to be notified a threat was restricted on the whole - document or on the specific page. +- Scan Printed Document – specifies whether to scan the entire document or individual pages when a print operation is detected. + - `Per printed page` – scans each page as it is printed. Metadata is not included, as metadata is not printed. + - `Per document` – scans the entire file, including metadata (MIP/NDC). Use this option when metadata inspection is required. -![File Tracing and Shadowing Settings](blockprintone.webp) :::warning Newer Linux Ubuntu versions have 'snap'-based applications installed by default, @@ -697,6 +696,9 @@ Upgrading the Endpoint Protector Client with the browser plug-in enabled will re full computer restart. ::: +:::note +When printing from Excel Online, changes made in the last few seconds may not be inspected immediately. The web application must sync recent changes to OneDrive before Endpoint Protector can inspect them. The sync delay depends on your connection bandwidth and the autosave configuration in your Microsoft 365 apps. +::: ![blockprinttwo](blockprinttwo.webp) @@ -914,6 +916,9 @@ data**. For new deployments, **Obfuscate Sensitive Data** is enabled by default. Read the [Data Obfuscation Rules](#data-obfuscation-rules) section for more information. ::: +:::warning +Use debug mode only for troubleshooting or when replicating an issue for further Netwrix Support Escalations. Debug mode enables detailed logging of all EPP Client operations, which causes local EPP logs to grow rapidly. For regular operation, use a less verbose mode, such as `informational` or `error`. +::: ![Used to debug feature and collect logs](debugloggingtwo.webp) diff --git a/docs/endpointprotector/admin/denylistsallowlists/allowlists.md b/docs/endpointprotector/admin/denylistsallowlists/allowlists.md index 5807810f20..d6b29db197 100644 --- a/docs/endpointprotector/admin/denylistsallowlists/allowlists.md +++ b/docs/endpointprotector/admin/denylistsallowlists/allowlists.md @@ -105,6 +105,10 @@ The same behavior also applies for Groups. The Administrator has the option to c ![New File Location Allowlists ](filelocationnewdenylists.webp) +:::note +**Known limitation:** Location-based denylists and allowlists are not reliable when Deep Packet Inspection (DPI) is active. DPI operates at the network level and identifies files by matching transferred data hashes against files on the local machine. If the same file exists in multiple locations, Endpoint Protector cannot determine which copy was transferred, and location-based rules cannot be applied. +::: + ## Network Share Network Share Allowlists are custom-defined lists of network share addresses where transfers of diff --git a/docs/endpointprotector/admin/denylistsallowlists/denylists.md b/docs/endpointprotector/admin/denylistsallowlists/denylists.md index 2a2e262cc2..19524f299c 100644 --- a/docs/endpointprotector/admin/denylistsallowlists/denylists.md +++ b/docs/endpointprotector/admin/denylistsallowlists/denylists.md @@ -100,6 +100,9 @@ File Location Denylist will not apply to groups of users, only to groups of comp File Location Denylist will only apply for the selected computer groups after 15 minutes. ::: +:::note +**Known limitation:** Location-based denylists and allowlists are not reliable when Deep Packet Inspection (DPI) is active. DPI operates at the network level and identifies files by matching transferred data hashes against files on the local machine. If the same file exists in multiple locations, Endpoint Protector cannot determine which copy was transferred, and location-based rules cannot be applied. +::: ![File Location New Denylist](filelocationnewdenylists.webp) From 96501197488dc718fb76eeed1bc90babe38ce1eb Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Tue, 5 May 2026 11:25:30 +0000 Subject: [PATCH 18/27] fix(vale): auto-fix style issues (Vale + Dale) --- .../admin/cap_module/capai.md | 22 +-- .../admin/cap_module/capmodule.md | 4 +- .../admin/cap_module/deeppacket.md | 35 +++-- .../admin/cap_module/newoutlook.md | 24 ++-- .../admin/dc_module/globalsettings.md | 133 ++++++++---------- .../admin/denylistsallowlists/allowlists.md | 37 +++-- .../admin/denylistsallowlists/denylists.md | 50 +++---- 7 files changed, 145 insertions(+), 160 deletions(-) diff --git a/docs/endpointprotector/admin/cap_module/capai.md b/docs/endpointprotector/admin/cap_module/capai.md index de780791c4..4d56537566 100644 --- a/docs/endpointprotector/admin/cap_module/capai.md +++ b/docs/endpointprotector/admin/cap_module/capai.md @@ -19,13 +19,13 @@ This new functionality enables businesses to maintain precise control over infor **Benefits** -By implementing these controls, organizations can ensure that sensitive information is protected during interactions with AI applications, thereby reducing the risk of data leaks and maintaining compliance with internal and external data security policies. +By implementing these controls, organizations can protect sensitive information during interactions with AI applications, thereby reducing the risk of data leaks and maintaining compliance with internal and external data security policies. ## AI Interaction Visibility and Control in Netwrix Endpoint Protector: Data Loss Prevention for LLMs Endpoint Protector extends Data Loss Prevention to the most widely used AI technologies — including ChatGPT, Microsoft Copilot, Google Gemini, DeepSeek, X Grok, Claude, Meta AI, and Perplexity — ensuring secure and compliant use across your organization. Coverage includes the embedded Microsoft Copilot add-in in Windows 11, New Outlook, New Teams, and Edge. Endpoint Protector also provides visibility and control over ChatGPT and Copilot native clients. -## How to configure Netwrix EPP to be able to monitor AI prompt transactions? +## Configure Netwrix EPP to Monitor AI Prompt Transactions To monitor or control AI prompts with EPP, you need to meet the following prerequisites: @@ -34,7 +34,7 @@ To monitor or control AI prompts with EPP, you need to meet the following prereq - CAP license with the Content Aware Protection (CAP) module enabled - DPI (Deep Packet Inspection) module enabled -If all of the above requirements are fulfilled, most of the setup is already complete. This is because any existing web browser monitor/control policy will automatically apply to user interactions with supported AI chat applications, enforcing your policy definitions when violations occur. +If you meet all of the preceding requirements, most of the setup is already complete. This is because any existing web browser monitor/control policy will automatically apply to user interactions with supported AI chat applications, enforcing your policy definitions when violations occur. ## Use Case Example @@ -46,7 +46,7 @@ To configure a CAP policy for this purpose: ![Define base CAP policy settings](capai_usecase01_01.webp) -2. Define CAP application exit points by selecting the web browsers you want to monitor or control. Make sure the relevant browsers are checked so the policy will be applied when users interact with AI chat applications through these browsers. +2. Define CAP application exit points by selecting the web browsers you want to monitor or control. ensure the relevant browsers are checked so the policy applies when users interact with AI chat applications through these browsers. ![Define CAP application exit points](capai_usecase01_02.webp) @@ -55,13 +55,13 @@ To configure a CAP policy for this purpose: ![Define CAP Policy Denylists](capai_usecase01_03.webp) 4. Save the policy and assign it to your selected endpoints. -5. This will ensure that the policy is enforced on the devices where you want to monitor or control AI prompt transactions. +5. Endpoint Protector enforces the policy on the devices where you want to monitor or control AI prompt transactions. -**You can check above example at the video below:** +**Watch the following video to see this example:** **Description of video**: @@ -80,7 +80,7 @@ To configure a CAP policy for this purpose: ![Define base CAP policy settings](capai_usecase01_01.webp) -2. Define CAP application exit points by selecting the web browsers you want to monitor or control. Make sure the relevant browsers are checked so the policy will be applied when users interact with AI chat applications through these browsers. +2. Define CAP application exit points by selecting the web browsers you want to monitor or control. ensure the relevant browsers are checked so the policy applies when users interact with AI chat applications through these browsers. :::tip For Copilot plugins in New Outlook, Teams, or Windows 11 25H2, also verify the in-app definitions for Outlook and Teams when configuring policies. @@ -98,13 +98,13 @@ You can use contextual rules to create complex pattern definitions for more accu ![Define CAP Policy contextual parameters](capai_usecase02_02.webp) 4. Save the policy and assign it to your selected endpoints. -5. This will ensure that the policy is enforced on the devices where you want to monitor or control AI prompt transactions. +5. Endpoint Protector enforces the policy on the devices where you want to monitor or control AI prompt transactions. -**You can check above example at the video below:** +**Watch the following video to see this example:** **Description of video:** diff --git a/docs/endpointprotector/admin/cap_module/capmodule.md b/docs/endpointprotector/admin/cap_module/capmodule.md index bdb41b9cc5..c66d75aebf 100644 --- a/docs/endpointprotector/admin/cap_module/capmodule.md +++ b/docs/endpointprotector/admin/cap_module/capmodule.md @@ -18,7 +18,7 @@ accidental or intentional file transfers of sensitive company data, such as: databases, etc. :::warning -Endpoint Protector cannot scan encrypted files or applications that use encryption to +Endpoint Protector can't scan encrypted files or applications that use encryption to secure communication. ::: @@ -43,7 +43,7 @@ points: ## Content Aware Protection Activation Content Aware Protection comes as the second level of data protection available in Endpoint -Protector. The module is displayed but requires a simple activation by pressing the Enable button. +Protector. The module is displayed but requires activation by pressing the Enable button. If not previously provided, the contact details of the Main Administrator will be required. diff --git a/docs/endpointprotector/admin/cap_module/deeppacket.md b/docs/endpointprotector/admin/cap_module/deeppacket.md index 4986bd08b2..ff8d677785 100644 --- a/docs/endpointprotector/admin/cap_module/deeppacket.md +++ b/docs/endpointprotector/admin/cap_module/deeppacket.md @@ -10,7 +10,7 @@ The Deep Packet Inspection functionality provides a certain degree of granularit fine-tune the content inspection functionality to the network specifications. :::note -Enabling Deep Packet Inspection could impact upload speed of inspected files. Use our +Enabling Deep Packet Inspection could impact upload speed of inspected files. Use the network extension instead of Packet Filter as a possible workaround (i.e., turn Intercept VPN Traffic on). ::: @@ -31,7 +31,7 @@ the Endpoint Protector, a restart of your computer is required. ::: :::note -**Known limitation:** Location-based denylists and allowlists are not reliable when Deep Packet Inspection (DPI) is active. DPI operates at the network level and identifies files by matching transferred data hashes against files on the local machine. If the same file exists in multiple locations, Endpoint Protector cannot determine which copy was transferred, and location-based rules cannot be applied. +**Known limitation:** Location-based denylists and allowlists aren't reliable when Deep Packet Inspection (DPI) is active. DPI operates at the network level and identifies files by matching transferred data hashes against files on the local machine. If the same file exists in multiple locations, Endpoint Protector can't determine which copy was transferred, and location-based rules can't be applied. ::: ## Stealthy DPI vs. regular DPI @@ -45,7 +45,7 @@ How do Stealthy DPI and Redirect-Based DPI compare in terms of EPP Client functi - Stealthy DPI and Redirect-Based DPI are functionally similar and require no changes to Endpoint Protector policies. Users can select the mode that best suits their infrastructure preferences. Both methods use the same resources and generate identical events. - However, they differ in handling bypasses for failed connections: - - Regular DPI (Redirect-Based): Offers more flexibility by allowing a feature to bypass connections that cannot be intercepted, with the proxy rebuilding the network connection to the destination after a failure. + - Regular DPI (Redirect-Based): Offers more flexibility by allowing a feature to bypass connections that can't be intercepted, with the proxy rebuilding the network connection to the destination after a failure. - Stealthy DPI: Achieves a similar bypass result using the improved "DPI Bypass" feature available in Endpoint Protector version 5.9.3.0. When should you choose Stealthy DPI over Regular DPI (Redirect-Based)? @@ -55,7 +55,7 @@ When should you choose Stealthy DPI over Regular DPI (Redirect-Based)? ## Deep Packet Inspection Diagrams -The diagrams below illustrate the high-level logic for Deep Packet Inspection (DPI) across different operating systems. Additionally, they illustrate the distinctions between Stealthy and Regular DPI modes of operation for macOS. +The following diagrams illustrate the high-level logic for Deep Packet Inspection (DPI) across different operating systems. Additionally, they illustrate the distinctions between Stealthy and Regular DPI modes of operation for macOS. ### For Windows - regular DPI @@ -81,10 +81,10 @@ Certificate Authority to intercept network traffic by Deep Packet Inspection an Protector Server communication. Endpoint Protector offers the option to automatically refresh Certificates with various scheduling -alternatives. After a new Certificate is generated, it will be sent in to the Client and replace the +alternatives. After Endpoint Protector generates a new Certificate, it sends the Certificate to the Client to replace the existing one. -To configure Deep Packet Inspection - Auto-refresh Certificate feature, please reference the following +To configure Deep Packet Inspection - Auto-refresh Certificate feature, reference the following steps: **Step 1 –** Go to **System Configuration** > **System Settings**> **Deep Packet Inspection - @@ -92,15 +92,14 @@ Auto-refresh Certificate** and chose **Automatically** option **Step 2 –** Choose one of available scheduling options and **Save** changes. -**Step 3 –** New Certificate will be distributed automatically to the endpoints after it is -generated. +**Step 3 –** Endpoint Protector automatically distributes the new Certificate to the endpoints after generating it. **Step 4 –** Reboot the endpoint to enforce a new Certificate. ![Configuring the Deep Packet Inspection - Auto-refresh Certificate feature](autorefreshcert.webp) -EPP DPI module generates a certificate only at the first time a user visits a website and caches that certificate for subsequent visits to the same website. The certificate cache deletion interval can be configured in EPP Server versions 5.8.0.0 and above (please refer to this UM section [System Settings - DPI certificate](/docs/endpointprotector/admin/systemconfiguration/systemsettings) . Alternatively, the certificate cache is cleared either upon computer reboot or when the DPI feature is disabled. +EPP DPI module generates a certificate only at the first time a user visits a website and caches that certificate for subsequent visits to the same website. The certificate cache deletion interval can be configured in EPP Server versions 5.8.0.0 and above (refer to this UM section [System Settings - DPI certificate](/docs/endpointprotector/admin/systemconfiguration/systemsettings) . Alternatively, the certificate cache is cleared either upon computer reboot or when the DPI feature is disabled. Endpoint Protector employs the same criteria as the Chromium open-source web browser for verifying website certificates, referencing the corporate CA certificates found in the system certificate stores. You can assess this validation by using diagnostic websites like https://badssl.com/. @@ -155,7 +154,7 @@ select **Always Trust**. **Step 6 –** **Save** the changes. :::warning -Please be aware that regenerating the Server Certificate Stack will require macOS and +be aware that regenerating the Server Certificate Stack will require macOS and Linux users to manually add the new certificate into the keychain. On Windows, the certificate will be updated automatically. ::: @@ -235,7 +234,7 @@ Protection Policy. ![Deep Packet Inspection Ports and Settings](dpiports.webp) :::note -The "Local" flag setting will only function with "Stealthy DPI" on Windows and "Intercept VPN Traffic" on macOS. It is not operational on Linux. +The "Local" flag setting will only function with "Stealthy DPI" on Windows and "Intercept VPN Traffic" on macOS. It isn't operational on Linux. ::: In this section you can also manage the following settings: @@ -271,7 +270,7 @@ In this section you can also manage the following settings: - Block unsupported protocols in New Outlook – Enable this setting to block unsupported protocols and the send email function in New Outlook without affecting legacy Outlook. Recommended for those not using the EPP add-in to limit the app as an egress channel. Keep off if EPP add-in is used. -- Monitor webmail – Enable this setting to scan the subject and body for Gmail, Outlook and Yahoo on +- Monitor webmail – Enable this setting to scan the subject and body for Gmail, Outlook, and Yahoo on the browser. Attachments will be monitored regardless of this setting. :::warning @@ -284,7 +283,7 @@ In this section you can also manage the following settings: You can also use the Monitor webmail feature to detect source code for web browsers emails in subject and body. For email applications, source code can be detected in subject, and for the - body, source code cannot be enabled for detection without breaking other functionality. + body, source code can't be enabled for detection without breaking other functionality. :::note Always use Monitor webmail with Extended Source Code Detection setting enabled. @@ -294,7 +293,7 @@ In this section you can also manage the following settings: - Allowed domains for Google Business accounts - You can use this setting to allow the users to access specific Google domains for professional usage when Deep Packet Inspection is enabled. - To specify the allowed business accounts, type an entry on the Add allowed Business accounts and + To specify the allowed business accounts, enter a value in the Add allowed Business accounts field and then click **+** The new entry will be displayed on the Allowed Business accounts list, from where you can delete @@ -302,19 +301,19 @@ In this section you can also manage the following settings: :::warning Endpoint Protector will block access to all Google domains (business and private) - used for Gmail, Google Drive, Google Docs, etc. that are not listed here. If the list remains + used for Gmail, Google Drive, Google Docs, etc. that aren't listed here. If the list remains empty, no Google domain will be blocked. ::: ![Allowed domains for Google Business accounts](alloweddomainsgoogle.webp) :::warning - "To include consumer Google Accounts, such as those ending in @gmail.com and @googlemail.com, enter "consumer_accounts" in the list instead of "gmail.com". This change is necessary, and the current issue is being closed as "won't fix". We may consider opening a documentation task to link the relevant Google document to our user manual. For more information, refer to: [Google Support](https://support.google.com/a/answer/1668854?hl=en). + To include consumer Google Accounts, such as those ending in @gmail.com and @googlemail.com, enter "consumer_accounts" in the list instead of "gmail.com". See [Google Support documentation on this topic](https://support.google.com/a/answer/1668854?hl=en). ::: ### Monitor Webmail JSON Format Parser Usage -To use this setting, you need to be familiarized with JSON concepts and structures. +To use this setting, you must be familiar with JSON concepts and structures. Go over the following Syntax examples considering the values used are the default values from the Endpoint Protector Server UI: @@ -353,7 +352,7 @@ Endpoint Protector Server UI: :::info It is advised, that due to recent changes applied by cloud providers, to not -apply any changes in the JSON parser, unless Monitor Webmail is not working +apply any changes in the JSON parser, unless Monitor Webmail isn't working ::: diff --git a/docs/endpointprotector/admin/cap_module/newoutlook.md b/docs/endpointprotector/admin/cap_module/newoutlook.md index 69da771ebb..cf96149b7d 100644 --- a/docs/endpointprotector/admin/cap_module/newoutlook.md +++ b/docs/endpointprotector/admin/cap_module/newoutlook.md @@ -8,7 +8,7 @@ sidebar_position: 50 Starting from Endpoint Protector Clients version 5.9.4.3, New Outlook can be fully managed as a Content Aware Protection Exit Point via the Microsoft 365 Web Add-in. Unlike COM add-ins for classic Outlook, which are installed directly on individual endpoints, Microsoft Web Add-ins need to be deployed centrally using the Microsoft 365 Admin Center or manually within the user account in Outlook application. -Microsoft 365 Web Add-ins are associated with user accounts rather than computers or devices. Once an add-in is deployed to a user account, every device that the user employs to access that account will have the add-in available. This means it cannot be restricted to just one device, such as the user's Mac computer only. +Microsoft 365 Web Add-ins are associated with user accounts rather than computers or devices. Once an add-in is deployed to a user account, every device that the user employs to access that account will have the add-in available. This means it can't be restricted to just one device, such as the user's Mac computer only. For detailed instructions and more information, refer to the official documentation available through Microsoft and Endpoint Protector resources: - [Microsoft resources](https://learn.microsoft.com/en-us/office/dev/add-ins/overview/office-add-ins) @@ -19,12 +19,12 @@ Both Netwrix and Microsoft recommend deploying the add-in in phases, starting wi ::: :::warning Important -It is important to configure the policy correctly so that the add-in is deployed selectively, rather than to all users—especially those who do not require it. The JavaScript variable configuration also allows the add-in to remain inactive or non-obtrusive unless the EPP agent is running on a device. This ensures that the add-in does not block operations unnecessarily if the agent is not active. Refer to the dedicated subchapter [Default Behavior of New Outlook Add-in and EPP Client](#default-behavior-of-new-outlook-add-in-and-epp-client). +Configure the policy correctly so that the add-in is deployed selectively, rather than to all users—especially those who don't require it. The JavaScript variable configuration also allows the add-in to remain inactive or non-obtrusive unless the EPP agent is running on a device. This ensures that the add-in doesn't block operations unnecessarily if the agent isn't active. Refer to the dedicated subchapter [Default Behavior of New Outlook Add-in and EPP Client](#default-behavior-of-new-outlook-add-in-and-epp-client). ::: When you install an add-in in Outlook.com, it will also appear in other versions of Outlook. For example, if you install an add-in in Outlook.com, you will see it when you open the desktop version of Outlook. -The EPP Client will also enforce the Content Aware Policies on those accounts when accessed through Outlook on the Web, with no additional configuration needed. Note that the presence of the add-in is not displayed in the Outlook interface. +The EPP Client will also enforce the Content Aware Policies on those accounts when accessed through Outlook on the Web, with no additional configuration needed. The Outlook interface doesn't display the add-in. To obtain the Outlook add-in manifest and validator files, visit the latest announcements on the Netwrix community portal or contact Netwrix Global Services & Support. @@ -43,11 +43,11 @@ The Endpoint Protector add-in requires certain files to be hosted by the custome - **mainpage.html** - Needs to be hosted; this is the entry point of the add-in. - **validator.js** - The script that performs the necessary functions for the add-in. - - **main_64.png, main_128.png** - These icons are also required by Microsoft; otherwise, the add-in cannot be validated by Microsoft admin center. + - **main_64.png, main_128.png** - These icons are also required by Microsoft; otherwise, the add-in can't be validated by Microsoft admin center. Hosting the above ensures that the add-in can communicate appropriately with the EPP system to enable its functionalities. - You are responsible for hosting these files. Host them at a publicly reachable URL. The URL of each hosted file must match the value configured in the manifest. Refer to the following chapters for details. + You are responsible for hosting these files. Host them at a publicly reachable URL. The URL of each hosted file must match the value configured in the manifest. The following chapters describe each requirement. :::warning Important Any downtime affecting the hosted files (mainpage.html, validator.js) will prevent users with the add-in assigned from sending any emails. @@ -102,7 +102,7 @@ This is required by the Microsoft add-in validator. Replace the placeholder URLs www.example.com ``` - Make sure that every domain in the URLs of the hosted files is added to the `` list: + ensure that you add every domain in the URLs of the hosted files to the `` list: - If the same domain is used for all URLs, it only needs to be added once. - Extend the existing list by adding your domain at the end between the `` tags, and before the closing `` tag. @@ -139,7 +139,7 @@ Ensure these URLs are correctly hosted on your server and accessible via the int The default behavior of the New Outlook add-in and EPP Client will align with the EPP Content Aware Protection (CAP) policy defined for email and Outlook actions. This includes capabilities such as reporting, blocking, and other egress channel controls when specific conditions are met. -However, the add-in has a predefined, hardcoded behavior when it cannot communicate with the EPP Client, assuming the EPP Client is not present. In this scenario, it is configured to allow sending messages. For customers who wish to enforce a restrictive policy that blocks the option to send out emails, this option is available. +However, the add-in has a predefined, hardcoded behavior when it can't communicate with the EPP Client, assuming the EPP Client isn't present. In this scenario, it is configured to allow sending messages. For customers who want to enforce a restrictive policy that blocks the option to send out emails, this option is available. **To change that:** @@ -174,9 +174,9 @@ This prompt supports only one language locale. ## Manual Deployment Method -The manual deployment method is not recommended because it must be repeated for each user account. This method is intended for pilot phases, troubleshooting, or feature PoCs. +The manual deployment method isn't recommended because it must be repeated for each user account. This method is intended for pilot phases, troubleshooting, or feature PoCs. -This option is only available if your organization allows users to add custom add-ins. +This option is only available if your organization lets users add custom add-ins. Refer to official Microsoft KB article: [Use add-ins in Outlook](https://support.microsoft.com/en-us/office/use-add-ins-in-outlook-1ee261f9-49bf-4ba6-b3e2-2ba7bcab64c8) @@ -194,7 +194,7 @@ Refer to official Microsoft KB article: [Use add-ins in Outlook](https://support ## Central Deployment Method -The central deployment method provides administrators with the capability to deploy the EPP New Outlook add-in in phases across global user populations. This approach helps minimize administrative effort and ensures a smooth implementation process. For detailed guidance, refer to the official Microsoft Knowledge Base (KB): [Office add-ins](https://learn.microsoft.com/en-us/microsoft-365/admin/manage/office-addins?view=o365-worldwide). +The central deployment method allows administrators to deploy the EPP New Outlook add-in in phases across global user populations. This approach helps minimize administrative effort and ensures a smooth implementation process. For detailed guidance, refer to the official Microsoft Knowledge Base (KB): [Office add-ins](https://learn.microsoft.com/en-us/microsoft-365/admin/manage/office-addins?view=o365-worldwide). **To deploy the add-in through the Microsoft Admin Center (https://admin.microsoft.com/):** @@ -205,9 +205,9 @@ The central deployment method provides administrators with the capability to dep ![Choose Upload custom apps](msaddincustomappselect.webp "Choose Upload custom apps") 5. Under **Upload Apps to Deploy**, choose the **App type** of **Office Add-in**, choose **Upload manifest file (.xml) from device**, and click **Choose File**.\ ![Upload Apps to Deploy](msaddincentraladdinfileselect.webp "Upload Apps to Deploy") -6. After selecting the file and clicking **Next**, under **Add users**, choose **Specific users/groups** and use the search box to populate the search box with the desired groups.\ +6. After selecting the file and clicking **Next**, under **Add users**, choose **Specific users/groups** and use the search box to populate the search box with the groups you want.\ ![Specific users/groups selector](msaddinspecifictargetuser.webp "Specific users/groups selector") -7. When the desired list appears under **To be added**, click **Next** and then click **Accept Permissions**. Review the needed permissions and click **Accept**. +7. When the list appears under **To be added**, click **Next** and then click **Accept Permissions**. Review the needed permissions and click **Accept**. 8. Ensure to keep **Deployment Method** as **Fixed (Default)**. 9. Click **Next** and then **Finish deployment**. 10. After making changes, allow some time for them to propagate. According to Microsoft, this process can take anywhere from a few minutes to up to 24 hours. diff --git a/docs/endpointprotector/admin/dc_module/globalsettings.md b/docs/endpointprotector/admin/dc_module/globalsettings.md index dae0d5b0ea..33de67f055 100644 --- a/docs/endpointprotector/admin/dc_module/globalsettings.md +++ b/docs/endpointprotector/admin/dc_module/globalsettings.md @@ -10,7 +10,7 @@ From this section, you can apply settings globally to all Endpoint Protector ent Any setting that appears in Global Settings offers additional functionality, as these settings can be customized per group, user, or computer. This allows administrators to configure precise, granular policies across the organization using the options available in this tab. Because of this, Global Settings may include options that are also available in other components, such as [Content Aware Protection](/docs/endpointprotector/admin/cap_module/capmodule.md), [Deep Packet Inspection](/docs/endpointprotector/admin/cap_module/deeppacket.md) or [Enforced Encryption](/docs/endpointprotector/admin/ee_module/eemodule.md). -- If there are no settings defined granularly for a computer, and it does not belong to a group, +- If there are no settings defined granularly for a computer, and it doesn't belong to a group, these are the settings it will inherit. - If the computer belongs to a group, then it will inherit that group’s settings. @@ -26,7 +26,7 @@ the Client’s behavior for each specific entity (Global, Groups, and Computers - Client Mode – select a mode to change Endpoint Protector Client behavior. :::note - Learn more from the [Client Mode](#client-mode) section. + See the [Client Mode](#client-mode) section. ::: @@ -55,15 +55,15 @@ the Client’s behavior for each specific entity (Global, Groups, and Computers - Tamper Mode – enable this setting to protect the Endpoint Protector Client from unauthorized termination and modification -> **CAUTION:** A machine or service reboot is mandatory after enabling this setting to work -> correctly. +:::warning +A machine or service reboot is mandatory after enabling this setting to work correctly. +::: - Policy Refresh Interval (sec) – enter the time interval at which the Client checks with the Server and updates with the latest settings, rights, and policies. :::note - The policy refresh cycles may be influenced by Azure Active Directory sync intervals - (or Active Directory syncs) if Endpoint Protector is configured to sync entities. Please consider + Azure Active Directory sync intervals (or Active Directory syncs) may affect the policy refresh cycles if Endpoint Protector is configured to sync entities. Consider the sync intervals of your Azure Active Directory or Active Directory sync processes when determining an appropriate policy refresh interval. ::: @@ -84,10 +84,10 @@ the Client’s behavior for each specific entity (Global, Groups, and Computers files are permanently deleted. - Log Size (MB) – enter the largest size of all logs stored on the Client. If the value is reached, new logs will overwrite the oldest ones. These circumstances occur only when the Client and Server - do not communicate for a large period of time. + don't communicate for a large period of time. - Shadow Size (MB) – enter the largest size of all file shadows on the Client. If the value is reached, new shadows will overwrite the oldest ones. These circumstances occur only when the - Client and Server do not communicate for a large period of time. + Client and Server don't communicate for a large period of time. - Min File Size for Shadowing (KB) – enter the smallest size of a file at which a File Shadow is created. - Max File Size for Shadowing (KB) – enter the largest size of a file at which a File Shadow is @@ -108,7 +108,7 @@ the Client’s behavior for each specific entity (Global, Groups, and Computers :::note Source Code Detection may encounter challenges when dealing with small code snippets. This can occur due to the potential overlap among various programming languages. It's important - to consider these limitations when configuring and utilizing Source Code Detection for optimal + to consider these limitations when configuring and using Source Code Detection for optimal results. ::: @@ -142,14 +142,14 @@ the Client’s behavior for each specific entity (Global, Groups, and Computers [User Remediation](/docs/endpointprotector/admin/systempar.md#user-remediation) feature is active and enables User Remediation pop-up notifications for end-users. - Enforce User Remediation Pop-up - this setting is available only if the User Remediation Pop-up - setting is enabled. When this setting is enabled, end-users cannot disable User Remediation Pop-up + setting is enabled. When this setting is enabled, end-users can't disable User Remediation Pop-up notifications. - Notifications Pop-up – you can select between the traditional notification, system tray, or pop-up notifications. - Enable Minifilter driver – only available for Windows, this setting allows the use of an enhanced driver that provides more reliability and ease of maintenance. You can also enable this setting on the Computers/Users/Groups/Global Rights sections with Manage Settings from the Actions column. -- User Remediation Notification Template - you can select from the drop-down list a custom +- User Remediation Notification Template - you can select from the dropdown list a custom notification. - Show Request OTP section in Endpoint Protector Client – disable this setting to hide the Request OTP action from Endpoint Protector Client @@ -160,22 +160,22 @@ the Client’s behavior for each specific entity (Global, Groups, and Computers ### Client Mode -Select from the drop-down list a client mode to define the Endpoint Protector Client behavior. +Select from the dropdown list a client mode to define the Endpoint Protector Client behavior. -![Select from the drop-down list a client mode to define the Endpoint Protector Client behavior.](clientmode.webp) +![Select from the dropdown list a client mode to define the Endpoint Protector Client behavior.](clientmode.webp) 1. Normal – this is the default and recommended setting to use before being fully aware of what the - other modes imply. Normal mode does not apply to Content Aware Protection; all other client + other modes imply. Normal mode doesn't apply to Content Aware Protection; all other client modes, except Silent mode, are specific to Device Control. :::note - If the Normal Mode does not suit your needs, consider the Hidden or Silent modes as + If the Normal Mode doesn't suit your needs, consider the Hidden or Silent modes as the best alternatives. ::: 2. Transparent – use this mode to block all devices whilst maintaining users unaware of any - restrictions or presence of the Endpoint Protector Client. Transparent mode does not apply to + restrictions or presence of the Endpoint Protector Client. Transparent mode doesn't apply to Content Aware Protection; all other client modes, except Silent mode, are specific to Device Control. @@ -187,14 +187,14 @@ Select from the drop-down list a client mode to define the Endpoint Protector C - Keyboards are blocked either when a third one is connected to the same computer or after 48 hours have passed - - Wi-Fi connections are not blocked + - Wi-Fi connections aren't blocked - Bluetooth devices remain operational - - USB modems are not blocked + - USB modems aren't blocked - Administrator receives alerts for all activities 3. Stealth - Use this mode to discreetly monitor users and computers with a focus on Device Control - and file-tracing. Stealth mode does not apply to Content Aware Protection; all other client modes, + and file-tracing. Stealth mode doesn't apply to Content Aware Protection; all other client modes, except Silent mode, are specific to Device Control. :::note @@ -212,7 +212,7 @@ Select from the drop-down list a client mode to define the Endpoint Protector C - Administrator receives alerts for all activities 4. Panic – This mode should be selected under extreme situations when a user’s malicious intent or - activity is detected by the Endpoint Protector Admin. Panic mode does not apply to Content Aware + activity is detected by the Endpoint Protector Admin. Panic mode doesn't apply to Content Aware Protection; all other client modes, except Silent mode, are specific to Device Control. :::info @@ -229,15 +229,15 @@ Select from the drop-down list a client mode to define the Endpoint Protector C - Keyboards are blocked either when a third one is connected to the same computer or after 48 hours have passed - - Wi-Fi connections are not blocked + - Wi-Fi connections aren't blocked - Bluetooth devices remain operational - - USB modems are not blocked + - USB modems aren't blocked - Enable file shadowing and file tracing to view and monitor all user activity - Administrator receives alerts when computers go in and out of Panic Mode 5. Hidden Icon - this mode is similar to Normal mode, except that the Endpoint Protector Client is - not visible to the user. Hidden Icon mode does not apply to Content Aware Protection; all other + not visible to the user. Hidden Icon mode doesn't apply to Content Aware Protection; all other client modes, except Silent mode, are specific to Device Control. Selecting this mode will: @@ -248,7 +248,7 @@ Select from the drop-down list a client mode to define the Endpoint Protector C When Hidden Icon mode is selected, the **Show notifications in Hidden Icon mode** setting becomes available under the Client Mode section. This setting is disabled by default. Enable it to allow client notifications to be displayed while the Endpoint Protector Client icon remains hidden. -6. Silent - this mode is similar to Normal mode, except that pop-up notifications are not visible to +6. Silent - this mode is similar to Normal mode, except that pop-up notifications aren't visible to the user. Selecting this mode will: @@ -267,7 +267,7 @@ systems, keep the Endpoint Protector Notifier window open. ## DPI Configuration :::note -For more Deep Packet Inspection (DPI) description please refer to dedicated chapter: [Deep Packet Inspection](/docs/endpointprotector/admin/cap_module/deeppacket.md). +For more Deep Packet Inspection (DPI) description refer to dedicated chapter: [Deep Packet Inspection](/docs/endpointprotector/admin/cap_module/deeppacket.md). ::: In this section, you can manage the following settings: @@ -282,7 +282,7 @@ In this section, you can manage the following settings: intercept VPN traffic on macOS using the network extension framework :::note - Learn more from the [Intercept VPN Traffic](#intercept-vpn-traffic) topic. + See the [Intercept VPN Traffic](#intercept-vpn-traffic) topic. ::: - Linux proxy loopback address – aims to facilitate seamless integration with custom VPN and proxy solutions, particularly those like Cisco ANYConnect. When activated, you can specify a custom loopback address, tipically within the 127.0.0.0/8 range. This features is applicable for Linux Clients with version 2509.x.x.x or later @@ -294,11 +294,9 @@ In this section, you can manage the following settings: - Peer Certificate Validation – enable this setting to turn on the Endpoint Protector certificate validation of the websites that are accessed by the user when DPI is active - - Ignore Expiration Date - when checked, expired certificates will be ignored and traffic will be - permitted. - - Ignore Trust - when checked, certificates will not be validated against the Root Certificate. - - Ignore Hostname - when checked, the certificate hostname property will not be validated against - the server hostname. + - Ignore Expiration Date - when checked, Endpoint Protector ignores expired certificates and permits traffic. + - Ignore Trust - when checked, Endpoint Protector does not validate certificates against the Root Certificate. + - Ignore Hostname - when checked, Endpoint Protector does not validate the certificate hostname property against the server hostname. :::warning Disabling setting ‘Peer Certificate Validation’ will not impact Endpoint Protector @@ -341,8 +339,7 @@ In this section, you can manage the following settings: - ‘Certificate Pinning’ also falls under this category. :::note - Learn more about - [Using Wireshark for Network Traffic Analysis](#using-wireshark-for-network-traffic-analysis). + See [Using Wireshark for Network Traffic Analysis](#using-wireshark-for-network-traffic-analysis). ::: @@ -366,7 +363,7 @@ In this section, you can manage the following settings: 4. Bypass Websockets - - Enable this setting, when Websites utilize websockets with arbitrary data protocols. + - Enable this setting, when Websites use websockets with arbitrary data protocols. - Endpoint Protector passthroughs connections upon the HTTP connection's upgrade to a websocket. @@ -395,15 +392,14 @@ In this section, you can manage the following settings: enabled, illustrates such situations (the website will be accessible). :::warning - Please be aware that the current Default DPI list and the new Default DPI bypass - list are exclusively utilized when manually checked within CAP (Content Aware Protection) + be aware that the current Default DPI list and the new Default DPI bypass + list apply only when manually checked within CAP (Content Aware Protection) policies. ::: :::note - Learn more about Timeout Period for Bypassed Websites, and Handling of Bypassed - Domains and Applications. + See the Timeout Period for Bypassed Websites, and Handling of Bypassed Domains and Applications sections. ::: @@ -411,7 +407,7 @@ In this section, you can manage the following settings: Endpoint Protector Server when connections are being bypassed on endpoints. :::note - Learn more about [Bypass Log Reporting Frequency](#bypass-log-reporting-frequency). + See [Bypass Log Reporting Frequency](#bypass-log-reporting-frequency). ::: - DPI Bypass for Unidentified Application – this will enable bypassing DPI while logging traffic details, @@ -535,14 +531,14 @@ Protector server achieves this reset. ### Using Wireshark for Network Traffic Analysis -Prior to a "DPI certificate rejected" event, Wireshark can be instrumental in diagnosing network +Before a "DPI certificate rejected" event, Wireshark can be instrumental in diagnosing network traffic. The presence of a "TLS alert" error in Wireshark signals the impending event. ## File Tracing and Shadowing In this section, you can manage the following settings: -- File Tracing – this feature allows you to monitor data traffic between protected endpoints and +- File Tracing – use this feature to monitor data traffic between protected endpoints and removable devices, internal eSATA HDDs, and Network Shares. It also shows other actions that took place, such as files named, deleted, accessed, modified, etc. @@ -553,7 +549,7 @@ In this section, you can manage the following settings: copies of files accessed by users. The creation of shadow copies can be triggered by the following events: file copy, file write, and file -read. Events such as file deleted, file renamed, etc. do not trigger the function. You can enable File +read. Events such as file deleted, file renamed, etc. don't trigger the function. You can enable File Shadowing on all supported Removable Devices: - eSATA HDDs or Time Machines @@ -563,7 +559,7 @@ Shadowing on all supported Removable Devices: - E-mail Body :::warning -File Shadowing cannot be used without File Tracing. +File Shadowing can't be used without File Tracing. ::: @@ -573,24 +569,21 @@ not occur for newly created files; however, the system diligently tracks file File Shadowing for subsequent file events as expected. :::note -For your deployment, we strongly advise activating File Shadowing for not more than 15% of -your total endpoint capacity (e.g., for a 1000 endpoint deployment, File Shadowing should be set to -a maximum of 150 endpoints for optimal performance). For more users, please contact customer support -for recommended settings. +For your deployment, activate File Shadowing for not more than 15% of your total endpoint capacity (e.g., for a 1000-endpoint deployment, File Shadowing should be set to a maximum of 150 endpoints for optimal performance). For more users, contact customer support for recommended settings. ::: - Exclude Extensions from Tracing – you can disable File Tracing for specific file types. - Exclude Extensions from Scanning – you can disable scanning for specific file types. -- File Tracing Direction – this setting enables you to monitor file transfers based on transfer +- File Tracing Direction – this setting lets you monitor file transfers based on transfer direction: - Outgoing File Tracing Direction is defined by transfers made from the local machine to removable devices. - Incoming File Tracing Direction indicates transfers from the removable devices to the local machine. - - Both (Outgoing & Incoming) allows you to monitor all types of transfers that are made between + - Both (Outgoing & Incoming) lets you monitor all types of transfers that are made between removable devices and the local machine. :::note @@ -601,8 +594,8 @@ for recommended settings. :::note - MTP (Media Transfers Protocols) file transfer is currently supported only on Windows - client machines. It allows you to transfer files in one direction, from your PC to your Android + MTP (Media Transfers Protocols) file transfer is supported only on Windows + client machines. Use it to transfer files in one direction, from your PC to your Android device. ::: @@ -630,7 +623,7 @@ For example, when a user opens Microsoft Word, an Endpoint Protector DLL is load ::: - Advanced Scanning Exceptions is a list of applications into which Endpoint Protector won't inject its DLL when the "Advanced Printer and MTP Scanning" is enabled. -For example, many applications can't be used to print or to copy files to MTP devices, so it does not make sense to inject the Endpoint Protector DLL into them. For best performance or to avoid unexpected interactions with Endpoint Protector, these applications can be added to the “Advanced Scanning Exceptions” list. +For example, many applications can't be used to print or to copy files to MTP devices, so it doesn't make sense to inject the Endpoint Protector DLL into them. For best performance or to avoid unexpected interactions with Endpoint Protector, these applications can be added to the “Advanced Scanning Exceptions” list. - Block Print from Browsers – prevents users from printing web pages from any supported browser on Windows. For details, see [Block Print from Browsers](#block-print-from-browsers). @@ -641,7 +634,7 @@ For example, many applications can't be used to print or to copy files to MTP de ![Block Print from Browsers settings](blockprintone.webp) -- Block Print if CAP Cannot Process File – This setting determines the action if CAP cannot access +- Block Print if CAP Can't Process File – This setting determines the action if CAP can't access the file content. By default, printing is allowed. This option applies only to Chrome and Edge with the browser extension on Windows. @@ -649,7 +642,7 @@ For example, many applications can't be used to print or to copy files to MTP de transfer logs. - Scan Printed Document – specifies whether to scan the entire document or individual pages when a print operation is detected. - - `Per printed page` – scans each page as it is printed. Metadata is not included, as metadata is not printed. + - `Per printed page` – scans each page as it is printed. Metadata isn't included, as metadata isn't printed. - `Per document` – scans the entire file, including metadata (MIP/NDC). Use this option when metadata inspection is required. @@ -675,7 +668,7 @@ This setting is available only for Windows. :::warning After enabling the Block Print from Browsers setting and applying the configuration on -the Client to enforce it, please be aware that open browser tabs will need to be reloaded, or a +the Client to enforce it, be aware that open browser tabs will need to be reloaded, or a browser restart will be required for the changes to take effect. ::: @@ -702,7 +695,7 @@ When printing from Excel Online, changes made in the last few seconds may not be ![blockprinttwo](blockprinttwo.webp) -Users printing from Google Chrome and Microsoft Edge can utilize content-aware detection by +Users printing from Google Chrome and Microsoft Edge can use content-aware detection by enforcing a Content Aware Policy that includes Printers from the Policy Exit Points section. For seamless protection, the Endpoint Protector Browser Connection extension installs automatically the first time upon enabling the Block Print from Browsers setting. This extension enhances content @@ -710,7 +703,7 @@ scanning capabilities during web document printing, integrating seamlessly on bo sides. :::note -The extension does not function in 'in Private/Incognito' mode. If it fails to load, it +The extension doesn't function in 'in Private/Incognito' mode. If it fails to load, it reverts to full Block-mode with Printing, providing comprehensive protection. ::: @@ -748,7 +741,7 @@ users from removing it, follow these steps: **Step 2 –** Download the [Chrome Group Policy](https://chromeenterprise.google/browser/download/#chrome-group-policy). - **Step 3 –** Configure your Group Policy as shown below. + **Step 3 –** Configure your Group Policy as shown in the following screenshot. - Endpoint Protector Browser Connector ID: nnnaeanocbmnnjjlcfhcbpefmlgbcgoi @@ -756,21 +749,21 @@ users from removing it, follow these steps: 1. Microsoft Edge - **Step 1 –** Utilize the + **Step 1 –** use the [Configure Microsoft Edge](https://learn.microsoft.com/en-us/deployedge/configure-microsoft-edge) guide provided by Microsoft. **Step 2 –** Download the [Edge Group Policy Template](https://learn.microsoft.com/en-US/troubleshoot/windows-client/group-policy/create-and-manage-central-store). - **Step 3 –** Configure your Group Policy as shown below. + **Step 3 –** Configure your Group Policy as shown in the following screenshot. - Endpoint Protector Browser Connector ID: nnnaeanocbmnnjjlcfhcbpefmlgbcgoi ![Configuring GPO for Browser Extensions](grouppolicyeditortwo.webp) :::warning -Make sure to thoroughly test the configuration in a controlled environment to ensure the +ensure to thoroughly test the configuration in a controlled environment to ensure the intended behavior. Always keep endpoint security policies updated and aligned with organizational security standards. ::: @@ -803,10 +796,10 @@ the range of 1 KB to 4 GB to accommodate your specific needs. Additionally, in the Windows environment, a default time-out of 10 seconds is applied. For MacOS, a strict 10-second time-out is enforced due to Apple OS architecture, which terminates processes that -do not respond promptly. Linux currently operates without a specific time-out limitation. +don't respond promptly. Linux operates without a specific time-out limitation. :::note -This setting only applies to Content Aware Protection policies and does not affect +This setting only applies to Content Aware Protection policies and doesn't affect eDiscovery Policies and Max File Size for File Shadows. ::: @@ -850,8 +843,7 @@ Limit. ![Set the transfer limit, within a specific time interval (hours)](transferlimit.webp) -The mechanism that checks when the Transfer Limit is reached has been designed in such a way that it -does not impact the performance of the computer. +The mechanism that checks when the Transfer Limit is reached doesn't impact the performance of the computer. Therefore, there might be a slight delay between the exact time the limit is reached and the enforcement of the transfer restrictions. In general, it’s just a few seconds but also depending on @@ -887,8 +879,7 @@ and if Deep Packet Inspection is enabled, it will collect supplementary Deep Pac along with sslsplit logs. :::note -We recommend using the Debug level mode as it contains more than error and warning type -information. +Use the Debug level mode, as it contains more than error and warning type information. ::: @@ -905,7 +896,7 @@ On the Global > Computer > User Settings page, configure the following settings **Step 1 –** Enable **Debug Mode** from the DEBUG logging section. **Step 2 –** Click and select an option on the **set logs level** (None, Error, Warning, -Informational, Debug) drop down. For new deployments, the default level is **Error**. +Informational, Debug) dropdown. For new deployments, the default level is **Error**. **Step 3 –** For Error, Warning, Informational, and Debug log levels select **obfuscate sensitive data**. For new deployments, **Obfuscate Sensitive Data** is enabled by default. @@ -913,7 +904,7 @@ data**. For new deployments, **Obfuscate Sensitive Data** is enabled by default. **Step 4 –** **Save.** :::note -Read the [Data Obfuscation Rules](#data-obfuscation-rules) section for more information. +See [Data Obfuscation Rules](#data-obfuscation-rules). ::: :::warning @@ -989,7 +980,7 @@ Specific use cases: 3. For Brazil ID (CPF), the first 3 and the last 2 characters are obfuscated :::note -Data is not obfuscated for the file-type threat, file-size threat, and date threat. +Data isn't obfuscated for the file-type threat, file-size threat, and date threat. ::: @@ -1018,7 +1009,7 @@ Endpoint Protector installed or in relation to a list of trusted Endpoint Protec To prevent EasyLock from running on computers that don’t have the EPP Client installed, enable **Client Presence Required** at the global level. ::: -- **EE Read-Only Mode** — When enabled, EasyLock blocks write access to encrypted drives on computers not managed by the EPP Client. When disabled (default), EasyLock doesn’t start at all on unmanaged computers. For more information, refer to [Enforced Encryption in Read-Only mode](/docs/endpointprotector/admin/ee_module/eemodule.md#enforced-encryption-in-read-only-mode). +- **EE Read-Only Mode** — When enabled, EasyLock blocks write access to encrypted drives on computers not managed by the EPP Client. When disabled (default), EasyLock doesn’t start at all on unmanaged computers. See [Enforced Encryption in Read-Only mode](/docs/endpointprotector/admin/ee_module/eemodule.md#enforced-encryption-in-read-only-mode). ![Enforced Encryption in Read-Only mode](eeromode.webp) diff --git a/docs/endpointprotector/admin/denylistsallowlists/allowlists.md b/docs/endpointprotector/admin/denylistsallowlists/allowlists.md index d6b29db197..3faf5fda2f 100644 --- a/docs/endpointprotector/admin/denylistsallowlists/allowlists.md +++ b/docs/endpointprotector/admin/denylistsallowlists/allowlists.md @@ -13,11 +13,9 @@ some files (e.g. Word, Excel, PDFs, etc.) can contain confidential information Credit Cards, etc.), other files are highly unlikely to contain such data (e.g. .dll, .exe, .mp3, .avi, etc.). -The purpose of the MIME Type Allowlists is to eliminate the use of resources to inspect redundant -and unnecessary files for content, as well as reducing false positives due to information detected in -the metadata of files where the risk of data loss is extremely low. +MIME Type Allowlists prevent Endpoint Protector from inspecting redundant files for content and reduce false positives from file metadata where the risk of data loss is low. -Example: As songs or video files cannot contain lists of credit card numbers, there is no need to +Example: As songs or video files can't contain lists of credit card numbers, there is no need to inspect them using content filters. MIME Type Allowlists are available for both the Content Aware Protection and eDiscovery modules and @@ -25,10 +23,7 @@ apply to Custom Content, Predefined Content, and Regular Expressions. :::note By default, graphic files, media files, some password-protected archive files and some system -files are automatically defined within the MIME Type Allowlists. While this can be changed, we -recommend only doing so after gaining a deeper understanding of the type of data transferred used, -or stored by the users in your system, and the subsequent logs increase in the Endpoint Protector -Server. +files are automatically defined within the MIME Type Allowlists. While this can be changed, only do so after gaining a deeper understanding of the type of data transferred, used, or stored by the users in your system, and the subsequent logs increase in the Endpoint Protector Server. ::: @@ -47,7 +42,7 @@ To create a new allowlist, under the list of available allowlists, click **Add** and **description** and then select a file from the list or upload a new file you can use in multiple allowlists. -Once the allowlist is created, it will be displayed on the Allowed File list and will be available +After the allowlist is created, it will be displayed on the Allowed File list and will be available when creating or editing a Content Aware Protection or eDiscovery policy. ![New Allowed Files Allowlists ](newallowedfilesallowlists.webp) @@ -83,10 +78,10 @@ a desktop folder on Windows use the pattern "?:\Users\\\*\Desktop\". ![File Location Allowlists](filelocationallowlists.webp) -You can add a new allowlist or edit, delete or export from the Actions column. +You can add a new allowlist or edit, delete, or export from the Actions column. From this section, you can view and add file location denylists and from the Actions column, you can -edit, delete or export an existing denylist. +edit, delete, or export an existing denylist. To create a new denylist, under the list of available denylists, click **Add**, provide a **name** and **description**, add the items separated by a new line, comma, or semicolon and then select the @@ -96,17 +91,17 @@ File Location Allowlists will not apply to groups of users, only to groups of co Location Allowlists will only apply for the selected computer groups after 15 minutes. :::note -By clicking the "Select All Computers" checkbox, ONLY computers existing in the Computers list at that moment can be checked and selected all at once. This DOES NOT imply that all the computers that will ever exist in the EPP Server Computer's list will be added to the "Allowlist - File Location" exception. +By clicking the "Select All Computers" checkbox, ONLY computers existing in the Computers list at that moment can be checked and selected all at once. This doesn't imply that all the computers that will ever exist in the EPP Server Computer's list will be added to the "Allowlist - File Location" exception. This is because adding new entities by default to the File Location's Allowlist exceptions without the Administrator knowledge could prove troublesome. When a new computer is added to the EPP Server, the "Select All Computers" checkbox becomes unchecked again but the computers that were checked before remain selected. By pressing that checkbox again, the newly added/unselected computers are added to the selectoion. -The same behavior also applies for Groups. The Administrator has the option to create custom Groups based on the existing computers/users already existing in the EPP Server's DB. When a new computer is added, it is not allocated to a group by default because the group in which the computer will be placed might not be the one that the Administrator intended for it to be in and it needs to be added manually. +The same behavior also applies for Groups. The Administrator has the option to create custom Groups based on the existing computers/users already existing in the EPP Server's DB. When a new computer is added, it isn't allocated to a group by default because the group in which the computer will be placed might not be the one that the Administrator intended for it to be in and it needs to be added manually. ::: ![New File Location Allowlists ](filelocationnewdenylists.webp) :::note -**Known limitation:** Location-based denylists and allowlists are not reliable when Deep Packet Inspection (DPI) is active. DPI operates at the network level and identifies files by matching transferred data hashes against files on the local machine. If the same file exists in multiple locations, Endpoint Protector cannot determine which copy was transferred, and location-based rules cannot be applied. +**Known limitation:** Location-based denylists and allowlists aren't reliable when Deep Packet Inspection (DPI) is active. DPI operates at the network level and identifies files by matching transferred data hashes against files on the local machine. If the same file exists in multiple locations, Endpoint Protector can't determine which copy was transferred, and location-based rules can't be applied. ::: ## Network Share @@ -131,7 +126,7 @@ inside a Content Aware Protection Policy. ![Network Share Allowlists ](networkshareallowlists.webp) -You can add a new allowlist or edit, delete or export from the Actions column. +You can add a new allowlist or edit, delete, or export from the Actions column. To create a new allowlist, under the list of available allowlists, click **Add**, provide a **name** and **description**, add server name or IP address to define a network share path separated by a new @@ -141,7 +136,7 @@ Network Share Allowlists will not apply to groups of users, only to groups of co Share Allowlists will only apply for the selected computer groups after 15 minutes. :::warning -Do not type the network share path with backslashes (\\) 192.168.0.1\public\users\test; +Don't enter the network share path with backslashes (\\) 192.168.0.1\public\users\test; fileserver\documents\example ::: @@ -160,13 +155,13 @@ E-mail Domain Allowlists are available only for the Content Aware Protection mod ![E-mail Domain Allowlists](emaildomainallowlists.webp) -You can add a new allowlist or edit, delete or export from the Actions column. +You can add a new allowlist or edit, delete, or export from the Actions column. To create a new allowlist, under the list of available allowlists, click **Add**, provide a **name** and **description** and then type or paste items at least three characters separated by a new line, comma, or semicolon. You can import content using the sample file provided on the form. -Once the allowlist is created, it will be displayed on the E-mail Domain list and will be available +After the allowlist is created, it will be displayed on the E-mail Domain list and will be available when creating or editing a Content Aware Protection policy. ![New E-mail Domain Allowlists ](newemaildomainallowlists.webp) @@ -188,7 +183,7 @@ information uploads. ![Deep Packet Inspection Allowlists ](dpiallowlists.webp) -You can add a new allowlist or edit, delete or export from the Actions column. +You can add a new allowlist or edit, delete, or export from the Actions column. You can create or import up to 100 lists of dictionaries, each dictionary comprising up to 50000 web domains. @@ -206,7 +201,7 @@ or semicolon. You can import content using the sample file provided on the form Example: example.endpointprotector, \*example.com, \*example\*, https://website.com, etc. :::warning -“?” cannot be used to replace a character. +“?” can't be used to replace a character. ::: @@ -219,7 +214,7 @@ Due to Gmail usage, take the following into consideration: drop option - You need to allow **doc.google.com** to add images in the email body -Once the allowlist is created, it will be displayed on the Deep Packet Inspection list and will be +After the allowlist is created, it will be displayed on the Deep Packet Inspection list and will be available when creating or editing a Content Aware Protection policy. ![New Deep Packet Inspection Allowlists](newdpiallowlists.webp) diff --git a/docs/endpointprotector/admin/denylistsallowlists/denylists.md b/docs/endpointprotector/admin/denylistsallowlists/denylists.md index 19524f299c..e53023e3e6 100644 --- a/docs/endpointprotector/admin/denylistsallowlists/denylists.md +++ b/docs/endpointprotector/admin/denylistsallowlists/denylists.md @@ -14,7 +14,7 @@ content by Endpoint Protector, available for both Content Aware Protection and e ![Denylists Custom Content configuration](customecontent.webp) From this section, you can view and add e-mail custom content denylists and from the Actions column, -you can edit, delete or export an existing denylist. +you can edit, delete, or export an existing denylist. To create a new denylist, under the list of available denylists, click **Add**, provide a **name** and **description** and then type or paste items at least three characters separated by a new line, @@ -27,7 +27,7 @@ uploaded again. ::: -Once the denylist is created, it will be displayed on the Custom Content list and will be available +After the denylist is created, it will be displayed on the Custom Content list and will be available when creating or editing a Content Aware Protection or eDiscovery policy. ![Creating a new denylist](newdenylist.webp) @@ -38,7 +38,7 @@ File Name Denylists are custom-defined lists of file names detected by Endpoin for both Content Aware Protection and eDiscovery modules. From this section, you can view and add filename denylists and from the Actions column, you can edit, -delete or export an existing denylist. +delete, or export an existing denylist. To create a new denylist, under the list of available denylists, click Add, provide a name and description and then type or paste the file names separated by a new line, comma, or semicolon. You @@ -56,12 +56,12 @@ Examples: Matching and Non-Matching for File Extensions like “.epp”: - Matching – test.epp, mail.epp, 123.epp - Non-Matching – 123.epp.zip, mail.epp.txt -Once the denylist is created, it will be displayed on the File Name list and will be available when +After the denylist is created, it will be displayed on the File Name list and will be available when creating or editing a Content Aware Protection or eDiscovery policy. :::warning For Content Aware Protection, the File Name Denylists work only for Block & Report type -Policies. The Case Sensitive and Whole Words Only features do not apply. +Policies. The Case Sensitive and Whole Words Only features don't apply. ::: @@ -89,7 +89,7 @@ transfer files also needs to be selected from within the Content Aware Protecti From this section, you can view and add file location denylists and from the Actions column, you can -edit, delete or export an existing denylist. +edit, delete, or export an existing denylist. To create a new denylist, under the list of available denylists, click **Add**, provide a **name** and **description**, add the items separated by a new line, comma, or semicolon and then select the @@ -101,7 +101,7 @@ File Location Denylist will only apply for the selected computer groups after 15 ::: :::note -**Known limitation:** Location-based denylists and allowlists are not reliable when Deep Packet Inspection (DPI) is active. DPI operates at the network level and identifies files by matching transferred data hashes against files on the local machine. If the same file exists in multiple locations, Endpoint Protector cannot determine which copy was transferred, and location-based rules cannot be applied. +**Known limitation:** Location-based denylists and allowlists aren't reliable when Deep Packet Inspection (DPI) is active. DPI operates at the network level and identifies files by matching transferred data hashes against files on the local machine. If the same file exists in multiple locations, Endpoint Protector can't determine which copy was transferred, and location-based rules can't be applied. ::: ![File Location New Denylist](filelocationnewdenylists.webp) @@ -164,8 +164,8 @@ and **description** and then add the regex expression. ![You can view and add regex expressions and from the Actions column](regexdenylists.webp) You can test a regular expression for accuracy using the right-side option. Add the content and then -click Test. If the Regular Expression has no errors, then the same content should appear into the -Matched content box, as shown below: +click Test. If the Regular Expression has no errors, then the same content should appear in the +Matched content box: - To match an E-mail – `[-0-9a-zA-Z.+_]+@[-0-9a-zA-Z.+_]+\.[a-zA-Z]{2,4}` - To match an IP – @@ -186,7 +186,7 @@ Endpoint Protector supports both standard Regex syntax and **Perl-Compatible Reg **Case Sensitivity Options in Regular Expressions** -Regular expressions allow you to control how text matching handles letter casing. Depending on your requirements, you can use case-sensitive, case-insensitive, or partially case-insensitive matching. +Regular expressions let you control how text matching handles letter casing. Depending on your requirements, you can use case-sensitive, case-insensitive, or partially case-insensitive matching. **1. Case-Sensitive Matching (Default)** @@ -215,7 +215,7 @@ In the following example, the pattern '(?i)test' will match “test,” “Test, ![](Regexcaseinsensitivity2.png) **3. Partial Case-Insensitive Matching** -Regex also allows you to apply case-insensitive matching only to specific parts of your pattern. +Regex also lets you apply case-insensitive matching only to specific parts of your pattern. You can enable and disable this mode using the following flags: - `(?i)` — enables case-insensitive mode @@ -235,8 +235,8 @@ Does **not match:** `"CONFIDENTIAL DOCUMENT"` | . | Matches any single character except newline (\\n). | a.c matches “abc”, “axc”, etc. | | \* | Matches 0 or more occurrences of the preceding character or group. | bo\* matches “b”, “bo”, “boo”, “booo”, etc. | | [] | Defines a character class, matching any one of the enclosed characters. | [abc] matches “a”, “b”, or “c”. | -| [abc] | Any single character of a, b or c | [abc] matches “a”, “b”, or “c”. | -| [ˆabc] | Any single character expect a, b or c | It will match any single charact expect “a”, “b”, or “c”. | +| [abc] | Any single character of a, b, or c | [abc] matches “a”, “b”, or “c”. | +| [ˆabc] | Any single character expect a, b, or c | It will match any single charact expect “a”, “b”, or “c”. | | [a-z] | A character in range a-z | It will match single character in range of a – z. | | [a-zA-Z] | A character in range a-z & A-Z | It will match single character in range of a – z & A - Z | | \\d | Any digit character | \\d will match any digit 0-9 | @@ -260,7 +260,7 @@ Domain and URL Denylists are available only for the Content Aware Protection mod ![Domain and URL Denylists ](domainurldenylists.webp) From this section, you can view and add domain and URL denylists and from the Actions column, you -can edit, delete or export an existing denylist. +can edit, delete, or export an existing denylist. To create a new denylist, under the list of available denylists, click **Add**, provide a **name** and **description** and then **type or paste** items separated by a new line, comma, or semicolon. @@ -279,7 +279,7 @@ You can define the content by adding the file name, file name and extension, pdf, test1example.pdf. example.endpointprotector.com, \*example.com, \*example\*example, https://website.com -Once the denylist is created, it will be displayed on the Domain and URL list and will be available +After the denylist is created, it will be displayed on the Domain and URL list and will be available when creating or editing a Content Aware Protection policy. ![Creating a New Domain URL denylists](domainurlnewdenylists.webp) @@ -306,7 +306,7 @@ Aware Protection Policy. ![E-mail Domain Denylists](e-maildomaindenylists.webp) From this section, you can view and add e-mail domain denylists and from the Actions column, you can -edit, delete or export an existing e-mail domain denylist. +edit, delete, or export an existing e-mail domain denylist. To create a new denylist, under the list of available denylists, click **Add**, provide a **name** and **description**, add the items separated by a new line, comma, or semicolon and then select the @@ -328,19 +328,19 @@ the example below for Google Chrome: **chrome.exe --incognito** With CLI commands denylists, you can define criteria for command line arguments that match specific -application behaviors. This allows you to create CAP policies tailored to your organization's needs, +application behaviors. This lets you create CAP policies tailored to your organization's needs, ensuring that the launch and behavior of applications align with your security and compliance requirements. :::note Certain native command line utilities such as `ls`, `md`, `cd`, which are embedded in the Operating System Core, may not be captured by CAP visibility. These commands are integral to the -functioning of the operating system and are typically excluded from CAP policies, and are not an +functioning of the operating system and are typically excluded from CAP policies, and aren't an egress channel. ::: -Follow the steps to define CLI command denylist policies. +To define CLI command denylist policies: **Step 1 –** Navigate to **Denylists** > **Application** tab in the Endpoint Protector Console. @@ -352,7 +352,7 @@ control and monitoring of application usage. ![Configuring Applications Denylists](applicationsdenylists.webp) -Follow these steps and leverage CLI commands denylists to enhance your organization's security +Follow these steps and use CLI commands denylists to enhance your organization's security posture and ensure that applications are used in compliance with your policies and regulations. :::note @@ -379,7 +379,7 @@ Protection and eDiscovery policies via the Endpoint Protector Server interface. The Endpoint Protector Server offers three options for defining MIP labels: - MIP Label Name – Specify the human-redable name of the MIP label. -- MIP GUID – Utilize the unique identifier associated with the MIP label. +- MIP GUID – use the unique identifier associated with the MIP label. - Both – Combine both the label name and GUID for maximum accuracy. This flexibility allows administrators to avoid creating custom dictionaries to recognize @@ -389,9 +389,9 @@ MIP labels can be used along other CAP conditions, including content-aware and l scanning. This enable granular control over data protection based on MPIP classifications. :::note -While Endpoint Protector can currently recognize MIP-encrypted files by their GUID (if +While Endpoint Protector can recognize MIP-encrypted files by their GUID (if they follow the latest MIP format used by office web tools labeling), content-aware scanning for -these files is not yet supported. +these files isn't yet supported. ::: @@ -411,7 +411,7 @@ This section covers the use of and integration with Netwrix Data Classification Netwrix Data Classification helps organizations identify, categorize, and tag data based on predefined policies. With NDC, you can understand where sensitive data resides, how it is used, and who has access to it, which supports data security, regulatory compliance, and informed decision-making. -Starting with the 25.12 release, Endpoint Protector allows direct NDC label definition for Content Aware Protection and eDiscovery policies through the Endpoint Protector Server interface, so you do not need to build custom dictionaries to recognize labeled files. +Starting with the 25.12 release, Endpoint Protector allows direct NDC label definition for Content Aware Protection and eDiscovery policies through the Endpoint Protector Server interface, so you don't need to build custom dictionaries to recognize labeled files. ![Configuration for Netwrix Data Classification](NDCClassification.png) @@ -440,4 +440,4 @@ Use the **Look for** field to control how Endpoint Protector matches the classif :::note The NDC labeling feature is supported only on Endpoint Protector Client version 2605.x.x.x and later. -::: \ No newline at end of file +::: From 73f1df13dd43ab74c42713078989199468498d61 Mon Sep 17 00:00:00 2001 From: jth-nw Date: Tue, 5 May 2026 10:28:26 -0500 Subject: [PATCH 19/27] fix(endpointprotector): replace ffi ligature in traffic across globalsettings Replaces Unicode ffi ligature (U+FB03) with ASCII in all 18 instances of "traffic"/"Traffic", fixing two broken heading anchors in the process. Generated with AI Co-Authored-By: Claude Code --- .../admin/dc_module/globalsettings.md | 36 +++++++++---------- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/docs/endpointprotector/admin/dc_module/globalsettings.md b/docs/endpointprotector/admin/dc_module/globalsettings.md index 33de67f055..f04e70d575 100644 --- a/docs/endpointprotector/admin/dc_module/globalsettings.md +++ b/docs/endpointprotector/admin/dc_module/globalsettings.md @@ -272,17 +272,17 @@ For more Deep Packet Inspection (DPI) description refer to dedicated chapter: [D In this section, you can manage the following settings: -- Deep Packet Inspection - if enabled, network and browser traffic can be inspected for content. This +- Deep Packet Inspection - if enabled, network and browser traffic can be inspected for content. This option is required for both the Deep Packet Inspection Allowlists and URL and Domain Denylist - Use Stealthy DPI Driver – enable this driver to improve interoperability with independent software vendors -- Intercept VPN Traffic – if you enable this setting, you allow the Endpoint Protector Client to - intercept VPN traffic on macOS using the network extension framework +- Intercept VPN Traffic – if you enable this setting, you allow the Endpoint Protector Client to + intercept VPN traffic on macOS using the network extension framework :::note - See the [Intercept VPN Traffic](#intercept-vpn-traffic) topic. + See the [Intercept VPN Traffic](#intercept-vpn-traffic) topic. ::: - Linux proxy loopback address – aims to facilitate seamless integration with custom VPN and proxy solutions, particularly those like Cisco ANYConnect. When activated, you can specify a custom loopback address, tipically within the 127.0.0.0/8 range. This features is applicable for Linux Clients with version 2509.x.x.x or later @@ -300,7 +300,7 @@ In this section, you can manage the following settings: :::warning Disabling setting ‘Peer Certificate Validation’ will not impact Endpoint Protector - functionality. It should only be disabled when an alternative network traffic inspection product, + functionality. It should only be disabled when an alternative network traffic inspection product, such as a Secure Web Gateway Solution, is validating website certificates. ::: @@ -318,8 +318,8 @@ In this section, you can manage the following settings: ::: -- DPI Bypass Traffic – this setting automatically bypasses non-inspectable traffic and sends an event - for allowed traffic. +- DPI Bypass Traffic – this setting automatically bypasses non-inspectable traffic and sends an event + for allowed traffic. Possible Bypass reasons: @@ -339,7 +339,7 @@ In this section, you can manage the following settings: - ‘Certificate Pinning’ also falls under this category. :::note - See [Using Wireshark for Network Traffic Analysis](#using-wireshark-for-network-traffic-analysis). + See [Using Wireshark for Network Traffic Analysis](#using-wireshark-for-network-traffic-analysis). ::: @@ -414,19 +414,19 @@ In this section, you can manage the following settings: if available. Applicable only to EPP Clients for Linux with version 2.4.5.x or higher. -![If enabled, network and browser traffic can be inspected for content](dpiconfiguration.png) +![If enabled, network and browser traffic can be inspected for content](dpiconfiguration.png) -### Intercept VPN Traffic +### Intercept VPN Traffic :::note -For more additional DPI Intercept VPN traffic, check: [Deep Packet Inspection Intercept VPN Traffic](/docs/endpointprotector/admin/cap_module/deeppacket.md#deep-packet-inspection-diagrams). +For more additional DPI Intercept VPN traffic, check: [Deep Packet Inspection Intercept VPN Traffic](/docs/endpointprotector/admin/cap_module/deeppacket.md#deep-packet-inspection-diagrams). ::: -If you enable this setting, the Endpoint Protector Client will intercept VPN traffic on macOS using +If you enable this setting, the Endpoint Protector Client will intercept VPN traffic on macOS using the network extension framework. :::note -The Intercept VPN Traffic feature is only available when the Deep Packet Inspection feature +The Intercept VPN Traffic feature is only available when the Deep Packet Inspection feature is enabled. It will only work for macOS from version 11.0 onwards and only if Deep Packet Inspection Certificate is also added. ::: @@ -436,7 +436,7 @@ To use this feature, follow these steps: **Step 1 –** Enable **Deep Packet Inspection**. -**Step 2 –** Enable **Intercept VPN Traffic**. +**Step 2 –** Enable **Intercept VPN Traffic**. **Step 3 –** Select an option for **Endpoint Protector behavior when network extension is disabled** @@ -529,16 +529,16 @@ To reset the bypass state and clear associated records, administrators can initi process. Temporarily disabling and subsequently re-enabling the bypass DPI setting on the Endpoint Protector server achieves this reset. -### Using Wireshark for Network Traffic Analysis +### Using Wireshark for Network Traffic Analysis Before a "DPI certificate rejected" event, Wireshark can be instrumental in diagnosing network -traffic. The presence of a "TLS alert" error in Wireshark signals the impending event. +traffic. The presence of a "TLS alert" error in Wireshark signals the impending event. ## File Tracing and Shadowing In this section, you can manage the following settings: -- File Tracing – use this feature to monitor data traffic between protected endpoints and +- File Tracing – use this feature to monitor data traffic between protected endpoints and removable devices, internal eSATA HDDs, and Network Shares. It also shows other actions that took place, such as files named, deleted, accessed, modified, etc. @@ -563,7 +563,7 @@ File Shadowing can't be used without File Tracing. ::: -File Shadowing can be delayed due to network traffic and Endpoint Protector Settings for different +File Shadowing can be delayed due to network traffic and Endpoint Protector Settings for different computers or file sizes. Shadowed files are usually available after a few minutes. Shadow creation may not occur for newly created files; however, the system diligently tracks file activities and generates File Shadowing for subsequent file events as expected. From 957973de58b32c03d04fec5d6659c4b5192523d6 Mon Sep 17 00:00:00 2001 From: jth-nw Date: Tue, 5 May 2026 10:28:58 -0500 Subject: [PATCH 20/27] fix(endpointprotector): replace all Unicode ligatures in globalsettings MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replaces fi, fl, ff, ffi, ffl ligatures (U+FB00–FB04) with ASCII equivalents across 150 instances — fixes broken search, spell-check, and heading anchors throughout the file. Generated with AI Co-Authored-By: Claude Code --- .../admin/dc_module/globalsettings.md | 300 +++++++++--------- 1 file changed, 150 insertions(+), 150 deletions(-) diff --git a/docs/endpointprotector/admin/dc_module/globalsettings.md b/docs/endpointprotector/admin/dc_module/globalsettings.md index f04e70d575..0df09027bd 100644 --- a/docs/endpointprotector/admin/dc_module/globalsettings.md +++ b/docs/endpointprotector/admin/dc_module/globalsettings.md @@ -10,7 +10,7 @@ From this section, you can apply settings globally to all Endpoint Protector ent Any setting that appears in Global Settings offers additional functionality, as these settings can be customized per group, user, or computer. This allows administrators to configure precise, granular policies across the organization using the options available in this tab. Because of this, Global Settings may include options that are also available in other components, such as [Content Aware Protection](/docs/endpointprotector/admin/cap_module/capmodule.md), [Deep Packet Inspection](/docs/endpointprotector/admin/cap_module/deeppacket.md) or [Enforced Encryption](/docs/endpointprotector/admin/ee_module/eemodule.md). -- If there are no settings defined granularly for a computer, and it doesn't belong to a group, +- If there are no settings defined granularly for a computer, and it doesn't belong to a group, these are the settings it will inherit. - If the computer belongs to a group, then it will inherit that group’s settings. @@ -21,7 +21,7 @@ Any setting that appears in Global Settings offers additional functionality, as ## Client Settings From this section, you can manage settings that relate directly to the Endpoint Protector Client and -the Client’s behavior for each specific entity (Global, Groups, and Computers). +the Client’s behavior for each specific entity (Global, Groups, and Computers). - Client Mode – select a mode to change Endpoint Protector Client behavior. @@ -30,16 +30,16 @@ the Client’s behavior for each specific entity (Global, Groups, and Computers ::: -- Notifier Language – Configure the Endpoint Protector Client to automatically match the OS language - of the user for notifications. When set to "Automatic," the client adjusts its language to the +- Notifier Language – Configure the Endpoint Protector Client to automatically match the OS language + of the user for notifications. When set to "Automatic," the client adjusts its language to the user's OS language preference without any server interactions, enhancing the user experience and reducing confusion. - To configure the Endpoint Protector Notifier language selection: + To configure the Endpoint Protector Notifier language selection: > **Step 1 –** Navigate to Device Control > Global Settings in the Endpoint Protector Console. > -> **Step 2 –** In the "Notifier language" section, select either "Automatic" or "Default" based on +> **Step 2 –** In the "Notifier language" section, select either "Automatic" or "Default" based on > your preferences. > > - “Automatic" means the language will be detected automatically from the OS, without server @@ -50,10 +50,10 @@ the Client’s behavior for each specific entity (Global, Groups, and Computers > **Step 3 –** Save your settings to apply the chosen language selection. > With this enhanced language selection feature, Endpoint Protector provides a more accommodating -> experience for users, making notifications and alerts more accessible and user-centric. +> experience for users, making notifications and alerts more accessible and user-centric. - Tamper Mode – enable this setting to protect the Endpoint Protector Client from unauthorized - termination and modification + termination and modification :::warning A machine or service reboot is mandatory after enabling this setting to work correctly. @@ -63,7 +63,7 @@ A machine or service reboot is mandatory after enabling this setting to work cor and updates with the latest settings, rights, and policies. :::note - Azure Active Directory sync intervals (or Active Directory syncs) may affect the policy refresh cycles if Endpoint Protector is configured to sync entities. Consider + Azure Active Directory sync intervals (or Active Directory syncs) may affect the policy refresh cycles if Endpoint Protector is configured to sync entities. Consider the sync intervals of your Azure Active Directory or Active Directory sync processes when determining an appropriate policy refresh interval. ::: @@ -71,53 +71,53 @@ A machine or service reboot is mandatory after enabling this setting to work cor - Log Interval (min) – enter the time interval at which the Client attempts to re-send the Logs to the Server. - Shadow Interval (min) – enter a time interval between 0-720 minutes at which the Endpoint - Protector Client sends the file Shadows to the Endpoint Protector Server. + Protector Client sends the file Shadows to the Endpoint Protector Server. :::note - Set the interval to 0 to send the file shadows instantly. + Set the interval to 0 to send the file shadows instantly. ::: -- Recovery Folder Retention Period (days) – this setting is specific for Mac and Linux computers. It - acts as a quarantine folder before a transferred file has been fully inspected for content, - avoiding any potential file loss due to blocked transfers. After the specified time interval, the - files are permanently deleted. +- Recovery Folder Retention Period (days) – this setting is specific for Mac and Linux computers. It + acts as a quarantine folder before a transferred file has been fully inspected for content, + avoiding any potential file loss due to blocked transfers. After the specified time interval, the + files are permanently deleted. - Log Size (MB) – enter the largest size of all logs stored on the Client. If the value is reached, new logs will overwrite the oldest ones. These circumstances occur only when the Client and Server don't communicate for a large period of time. -- Shadow Size (MB) – enter the largest size of all file shadows on the Client. If the value is +- Shadow Size (MB) – enter the largest size of all file shadows on the Client. If the value is reached, new shadows will overwrite the oldest ones. These circumstances occur only when the Client and Server don't communicate for a large period of time. -- Min File Size for Shadowing (KB) – enter the smallest size of a file at which a File Shadow is +- Min File Size for Shadowing (KB) – enter the smallest size of a file at which a File Shadow is created. -- Max File Size for Shadowing (KB) – enter the largest size of a file at which a File Shadow is +- Max File Size for Shadowing (KB) – enter the largest size of a file at which a File Shadow is created. -- Devices Recovery Folder Max Size (MB) – this setting is specific for Mac and Linux computers. - Maximum size for the quarantine folder. If the value is reached, new files will overwrite the +- Devices Recovery Folder Max Size (MB) – this setting is specific for Mac and Linux computers. + Maximum size for the quarantine folder. If the value is reached, new files will overwrite the oldest ones. ![Manage settings that relate directly to the Netwrix Endpoint Protector Client](clentsettings.webp) -- Custom Client Notifications - if enabled, the Client Notifications can be customized. -- Mandatory OTP Justification - if enabled, the Justification a User has to provide when requesting or - using an Offline Temporary Password is mandatory. -- Extend Source Code Detection - if enabled, this will extend the detection also inside of file type, +- Custom Client Notifications - if enabled, the Client Notifications can be customized. +- Mandatory OTP Justification - if enabled, the Justification a User has to provide when requesting or + using an Offline Temporary Password is mandatory. +- Extend Source Code Detection - if enabled, this will extend the detection also inside of file type, such as PDF, Docx, etc. With Monitor Webmail setting enabled, you can also detect source code in emails in subject and body using web browsers. :::note Source Code Detection may encounter challenges when dealing with small code snippets. This can occur due to the potential overlap among various programming languages. It's important - to consider these limitations when configuring and using Source Code Detection for optimal + to consider these limitations when configuring and using Source Code Detection for optimal results. ::: - User edited information - if enabled, the User can edit the user and computer information from within the Endpoint Protector Client. -- Optical Character Recognition - if enabled, JPEG, PNG, GIF, BMP, and TIFF file types can be +- Optical Character Recognition - if enabled, JPEG, PNG, GIF, BMP, and TIFF file types can be inspected for content. This option will also change the global MIME Type Allowlists. -- Disable OCR notifications – if enabled, this will disable all notifications generated by the Optical +- Disable OCR notifications – if enabled, this will disable all notifications generated by the Optical Character Recognition setting. - Limit Reporting Content Aware Protection - if enabled, this will allow information discovered after reaching the Threat Threshold or after matching the Content Detection Rule that contains AND @@ -134,23 +134,23 @@ A machine or service reboot is mandatory after enabling this setting to work cor access permission. :::note - For this setting to work successfully, enable the Minifilter Driver setting. + For this setting to work successfully, enable the Minifilter Driver setting. ::: - User Remediation Pop-up – this setting is available when the [User Remediation](/docs/endpointprotector/admin/systempar.md#user-remediation) feature is active and enables - User Remediation pop-up notifications for end-users. + User Remediation pop-up notifications for end-users. - Enforce User Remediation Pop-up - this setting is available only if the User Remediation Pop-up setting is enabled. When this setting is enabled, end-users can't disable User Remediation Pop-up - notifications. -- Notifications Pop-up – you can select between the traditional notification, system tray, or pop-up - notifications. -- Enable Minifilter driver – only available for Windows, this setting allows the use of an enhanced + notifications. +- Notifications Pop-up – you can select between the traditional notification, system tray, or pop-up + notifications. +- Enable Minifilter driver – only available for Windows, this setting allows the use of an enhanced driver that provides more reliability and ease of maintenance. You can also enable this setting on the Computers/Users/Groups/Global Rights sections with Manage Settings from the Actions column. -- User Remediation Notification Template - you can select from the dropdown list a custom - notification. +- User Remediation Notification Template - you can select from the dropdown list a custom + notification. - Show Request OTP section in Endpoint Protector Client – disable this setting to hide the Request OTP action from Endpoint Protector Client - Show Authorize section in Endpoint Protector Client – disable this setting to hide the Authorize @@ -160,13 +160,13 @@ A machine or service reboot is mandatory after enabling this setting to work cor ### Client Mode -Select from the dropdown list a client mode to define the Endpoint Protector Client behavior. +Select from the dropdown list a client mode to define the Endpoint Protector Client behavior. -![Select from the dropdown list a client mode to define the Endpoint Protector Client behavior.](clientmode.webp) +![Select from the dropdown list a client mode to define the Endpoint Protector Client behavior.](clientmode.webp) 1. Normal – this is the default and recommended setting to use before being fully aware of what the other modes imply. Normal mode doesn't apply to Content Aware Protection; all other client - modes, except Silent mode, are specific to Device Control. + modes, except Silent mode, are specific to Device Control. :::note If the Normal Mode doesn't suit your needs, consider the Hidden or Silent modes as @@ -176,13 +176,13 @@ Select from the dropdown list a client mode to define the Endpoint Protector Cl 2. Transparent – use this mode to block all devices whilst maintaining users unaware of any restrictions or presence of the Endpoint Protector Client. Transparent mode doesn't apply to - Content Aware Protection; all other client modes, except Silent mode, are specific to Device + Content Aware Protection; all other client modes, except Silent mode, are specific to Device Control. Selecting this mode will: - Not display the system tray icon - - Not display system tray notifications + - Not display system tray notifications - Block all devices, regardless of authorization, with the following exceptions: - Keyboards are blocked either when a third one is connected to the same computer or after @@ -194,8 +194,8 @@ Select from the dropdown list a client mode to define the Endpoint Protector Cl - Administrator receives alerts for all activities 3. Stealth - Use this mode to discreetly monitor users and computers with a focus on Device Control - and file-tracing. Stealth mode doesn't apply to Content Aware Protection; all other client modes, - except Silent mode, are specific to Device Control. + and file-tracing. Stealth mode doesn't apply to Content Aware Protection; all other client modes, + except Silent mode, are specific to Device Control. :::note As everything is allowed, there will be no disruptions in the daily activities of the @@ -206,14 +206,14 @@ Select from the dropdown list a client mode to define the Endpoint Protector Cl Selecting this mode will: - Not display the system tray icon - - Not display system tray notifications + - Not display system tray notifications - Allow everything, regardless of authorized or not - - Enable file shadowing and file tracing to view and monitor all user activity + - Enable file shadowing and file tracing to view and monitor all user activity - Administrator receives alerts for all activities 4. Panic – This mode should be selected under extreme situations when a user’s malicious intent or activity is detected by the Endpoint Protector Admin. Panic mode doesn't apply to Content Aware - Protection; all other client modes, except Silent mode, are specific to Device Control. + Protection; all other client modes, except Silent mode, are specific to Device Control. :::info It is recommended to use this mode for selected users/groups/computers only, @@ -224,7 +224,7 @@ Select from the dropdown list a client mode to define the Endpoint Protector Cl Selecting this mode will: - Display the system tray icon - - Display system tray notifications + - Display system tray notifications - Block all devices, regardless of authorization, with the following exceptions: - Keyboards are blocked either when a third one is connected to the same computer or after @@ -233,29 +233,29 @@ Select from the dropdown list a client mode to define the Endpoint Protector Cl - Bluetooth devices remain operational - USB modems aren't blocked - - Enable file shadowing and file tracing to view and monitor all user activity + - Enable file shadowing and file tracing to view and monitor all user activity - Administrator receives alerts when computers go in and out of Panic Mode 5. Hidden Icon - this mode is similar to Normal mode, except that the Endpoint Protector Client is not visible to the user. Hidden Icon mode doesn't apply to Content Aware Protection; all other - client modes, except Silent mode, are specific to Device Control. + client modes, except Silent mode, are specific to Device Control. Selecting this mode will: - Not display the system tray icon - - Not display system tray notifications - - Apply all set rights and settings as per their configuration + - Not display system tray notifications + - Apply all set rights and settings as per their configuration When Hidden Icon mode is selected, the **Show notifications in Hidden Icon mode** setting becomes available under the Client Mode section. This setting is disabled by default. Enable it to allow client notifications to be displayed while the Endpoint Protector Client icon remains hidden. -6. Silent - this mode is similar to Normal mode, except that pop-up notifications aren't visible to +6. Silent - this mode is similar to Normal mode, except that pop-up notifications aren't visible to the user. Selecting this mode will: - Display the system tray icon - - Not display system tray notifications - - Apply all set rights and settings as per their configuration + - Not display system tray notifications + - Apply all set rights and settings as per their configuration :::note Certain Linux distributions (like SLED) lack system tray support, resulting in the absence @@ -264,7 +264,7 @@ systems, keep the Endpoint Protector Notifier window open. ::: -## DPI Configuration +## DPI Configuration :::note For more Deep Packet Inspection (DPI) description refer to dedicated chapter: [Deep Packet Inspection](/docs/endpointprotector/admin/cap_module/deeppacket.md). @@ -291,7 +291,7 @@ In this section, you can manage the following settings: - Endpoint Protector Behavior with Network Extension Off – select a behavior type from the available entries -- Peer Certificate Validation – enable this setting to turn on the Endpoint Protector certificate +- Peer Certificate Validation – enable this setting to turn on the Endpoint Protector certificate validation of the websites that are accessed by the user when DPI is active - Ignore Expiration Date - when checked, Endpoint Protector ignores expired certificates and permits traffic. @@ -299,16 +299,16 @@ In this section, you can manage the following settings: - Ignore Hostname - when checked, Endpoint Protector does not validate the certificate hostname property against the server hostname. :::warning - Disabling setting ‘Peer Certificate Validation’ will not impact Endpoint Protector + Disabling setting ‘Peer Certificate Validation’ will not impact Endpoint Protector functionality. It should only be disabled when an alternative network traffic inspection product, - such as a Secure Web Gateway Solution, is validating website certificates. + such as a Secure Web Gateway Solution, is validating website certificates. ::: - Display Dialog Boxes for DPI Dropped Connections - enable this setting to display Dialog windows on endpoint machines, containing more details. -- Disable DPI Dropped Connections Notifications - check this setting to suppress notifications shown - by the Notification Center nearby the System tray. +- Disable DPI Dropped Connections Notifications - check this setting to suppress notifications shown + by the Notification Center nearby the System tray. - Block Unsecured Connection - if enabled, unsecured access through HTTP will be blocked and user access restricted. @@ -323,7 +323,7 @@ In this section, you can manage the following settings: Possible Bypass reasons: - 1. Bypass DPI Certificate Rejection by Third-Party Applications + 1. Bypass DPI Certificate Rejection by Third-Party Applications - Enable this setting, if SSL errors are encountered from the source applications, such as web browsers, like: @@ -332,11 +332,11 @@ In this section, you can manage the following settings: > > SSL_R_SSLV3_ALERT_CERTIFICATE_UNKNOWN - - This signifies that the source application failed to validate the server certificate, + - This signifies that the source application failed to validate the server certificate, which was issued by Endpoint Protector. - - The absence of the DPI certificate in the system keychain may also contribute to this + - The absence of the DPI certificate in the system keychain may also contribute to this scenario. - - ‘Certificate Pinning’ also falls under this category. + - ‘Certificate Pinning’ also falls under this category. :::note See [Using Wireshark for Network Traffic Analysis](#using-wireshark-for-network-traffic-analysis). @@ -348,7 +348,7 @@ In this section, you can manage the following settings: - Enable this setting, when a secure port connection employs custom encryption instead of TLS, the DPI bypass is activated. - - This is exemplified by configuring Telegram.app for DPI monitoring, logging into the + - This is exemplified by configuring Telegram.app for DPI monitoring, logging into the app, and encountering an unknown TLS handshake. 3. Bypass Websites Temporarily Whitelisted (Possible mTLS Connection/SSL Setup @@ -358,7 +358,7 @@ In this section, you can manage the following settings: on the server side of an SSL connection. Endpoint Protector temporarily allow-lists the website. - - While specific examples are infrequent, such instances involve potential mTLS + - While specific examples are infrequent, such instances involve potential mTLS connections. 4. Bypass Websockets @@ -371,24 +371,24 @@ In this section, you can manage the following settings: 5. Bypass on HTTP Errors Indicating mTLS Requirement - - Enable this setting, when a server indicates the requirement of a client certificate + - Enable this setting, when a server indicates the requirement of a client certificate (mTLS). - Endpoint Protector triggers bypass for HTTP error codes like ‘400 Bad Response’ and - ‘496 SSL Certificate Required’. + ‘496 SSL Certificate Required’. - Accessing [https://client.badssl.com/](https://client.badssl.com/) from a web browser - without providing the necessary client certificate illustrates such situations. + without providing the necessary client certificate illustrates such situations. - 6. Bypass Invalid Peer Certificates + 6. Bypass Invalid Peer Certificates - - Enable this setting, to permit connections with invalid peer certificates when ‘Peer - Certificate Validation’ is enabled. + - Enable this setting, to permit connections with invalid peer certificates when ‘Peer + Certificate Validation’ is enabled. - - If both ‘Bypass Invalid Peer Certificates’ and ‘Peer Certificate Validation’ are - enabled, ‘Bypass Invalid Peer Certificates’ will override setting ‘Peer Certificate + - If both ‘Bypass Invalid Peer Certificates’ and ‘Peer Certificate Validation’ are + enabled, ‘Bypass Invalid Peer Certificates’ will override setting ‘Peer Certificate Validation’. - Accessing [https://expired.badssl.com/](https://expired.badssl.com/)from a web browser - with both settings ‘Bypass Invalid Peer Certificates’ and ‘Peer Certificate Validation’ + with both settings ‘Bypass Invalid Peer Certificates’ and ‘Peer Certificate Validation’ enabled, illustrates such situations (the website will be accessible). :::warning @@ -428,7 +428,7 @@ the network extension framework. :::note The Intercept VPN Traffic feature is only available when the Deep Packet Inspection feature is enabled. It will only work for macOS from version 11.0 onwards and only if Deep Packet Inspection -Certificate is also added. +Certificate is also added. ::: @@ -442,9 +442,9 @@ To use this feature, follow these steps: - **Temporary Disable Deep Packet Inspection** – this will disable Deep Packet Inspection temporary - **Block Internet Access** - this will block the Internet connection until the user approves the - Endpoint Protector Proxy configuration. The user also can allow the configuration after rebooting + Endpoint Protector Proxy configuration. The user also can allow the configuration after rebooting the PC. -- **Repeat VPN notification** – this will display the VPN pop-up window multiple times even after the +- **Repeat VPN notification** – this will display the VPN pop-up window multiple times even after the user has previously denied permission. **Step 4 –** Click **Save**. @@ -459,17 +459,17 @@ To use this feature, follow these steps: ![Security and private settings on Mac](generaltabios.webp) -**Step 7 –** On the Endpoint Protector Proxy Configuration pop-up window, click **Allow**. +**Step 7 –** On the Endpoint Protector Proxy Configuration pop-up window, click **Allow**. -![Proxy Configuration pop-up window](proxypop-up.webp) +![Proxy Configuration pop-up window](proxypop-up.webp) :::note When network extension is successfully enabled, a Client Integrity OK log is generated. ::: -**Step 8 –** Go to **System Configuration** > **System Settings** > **Deep Packet Inspection -Certificate**, and then download the CA Certificate. +**Step 8 –** Go to **System Configuration** > **System Settings** > **Deep Packet Inspection +Certificate**, and then download the CA Certificate. ![Downloading a DPI Certificate](dpicertificate.webp) @@ -477,14 +477,14 @@ Certificate**, and then download the CA Certificate. ![Keychain Access application settings on MacOs](keychainaccess.webp) -**Step 10 –** Decompress the ClientCerts file. +**Step 10 –** Decompress the ClientCerts file. -**Step 11 –** Select the **cacert.pem** file and drag and drop it under **System** > **Keychain +**Step 11 –** Select the **cacert.pem** file and drag and drop it under **System** > **Keychain Access**. ![Configuring Client Certificate on MacOs](clientcerts.webp) -**Step 12 –** Double click the **X** from the newly added certificate and select **Always Trust** +**Step 12 –** Double click the **X** from the newly added certificate and select **Always Trust** from the Trust section. ![Keychain Access application settings on MacOs](keychainaccesstwo.webp) @@ -494,7 +494,7 @@ from the Trust section. ### Smart DPI (Log Throttling) Enable this setting to address the number of excessive false positives for URL Denylists. This -improvement provides you with a configuration option to filter out non-relevant information, resulting +improvement provides you with a configuration option to filter out non-relevant information, resulting in a more accurate log that focuses on true false positives and reduces unnecessary noise saving database storage. @@ -502,8 +502,8 @@ database storage. ### Bypass Log Reporting Frequency -Endpoint Protector's agent ensures efficient resource utilization by reporting each domain name and -application pair at most once every two weeks. This approach prevents an overwhelming influx of logs, +Endpoint Protector's agent ensures efficient resource utilization by reporting each domain name and +application pair at most once every two weeks. This approach prevents an overwhelming influx of logs, which could reach excessive numbers if reported more frequently. ### Timeout Period for Bypassed Websites @@ -519,7 +519,7 @@ Endpoint Protector employs a nuanced approach to handle bypassed domains and app #### Memory and Disk Persistence Bypassed website information is stored in both memory and on disk. This dual storage ensures that -the list of skipped websites is readily accessible for efficient future reference. By persisting this +the list of skipped websites is readily accessible for efficient future reference. By persisting this information, the frequency of log generation can be controlled to avoid unnecessary strain on resources. @@ -531,7 +531,7 @@ Protector server achieves this reset. ### Using Wireshark for Network Traffic Analysis -Before a "DPI certificate rejected" event, Wireshark can be instrumental in diagnosing network +Before a "DPI certificate rejected" event, Wireshark can be instrumental in diagnosing network traffic. The presence of a "TLS alert" error in Wireshark signals the impending event. ## File Tracing and Shadowing @@ -540,21 +540,21 @@ In this section, you can manage the following settings: - File Tracing – use this feature to monitor data traffic between protected endpoints and removable devices, internal eSATA HDDs, and Network Shares. It also shows other actions that took - place, such as files named, deleted, accessed, modified, etc. + place, such as files named, deleted, accessed, modified, etc. To enable this feature, you can do so from Device Control, Global Settings, or granularly for Groups or Computers. - File Shadowing – this feature extends the information provided by File Tracing, creating exact - copies of files accessed by users. + copies of files accessed by users. -The creation of shadow copies can be triggered by the following events: file copy, file write, and file -read. Events such as file deleted, file renamed, etc. don't trigger the function. You can enable File +The creation of shadow copies can be triggered by the following events: file copy, file write, and file +read. Events such as file deleted, file renamed, etc. don't trigger the function. You can enable File Shadowing on all supported Removable Devices: - eSATA HDDs or Time Machines - Network Shares -- Content Aware Protection - file transfers through various exit points such as online applications, +- Content Aware Protection - file transfers through various exit points such as online applications, printers, clipboards, etc. - E-mail Body @@ -564,22 +564,22 @@ File Shadowing can't be used without File Tracing. File Shadowing can be delayed due to network traffic and Endpoint Protector Settings for different -computers or file sizes. Shadowed files are usually available after a few minutes. Shadow creation may -not occur for newly created files; however, the system diligently tracks file activities and generates -File Shadowing for subsequent file events as expected. +computers or file sizes. Shadowed files are usually available after a few minutes. Shadow creation may +not occur for newly created files; however, the system diligently tracks file activities and generates +File Shadowing for subsequent file events as expected. :::note For your deployment, activate File Shadowing for not more than 15% of your total endpoint capacity (e.g., for a 1000-endpoint deployment, File Shadowing should be set to a maximum of 150 endpoints for optimal performance). For more users, contact customer support for recommended settings. ::: -- Exclude Extensions from Tracing – you can disable File Tracing for specific file types. +- Exclude Extensions from Tracing – you can disable File Tracing for specific file types. -- Exclude Extensions from Scanning – you can disable scanning for specific file types. -- File Tracing Direction – this setting lets you monitor file transfers based on transfer +- Exclude Extensions from Scanning – you can disable scanning for specific file types. +- File Tracing Direction – this setting lets you monitor file transfers based on transfer direction: - - Outgoing File Tracing Direction is defined by transfers made from the local machine to + - Outgoing File Tracing Direction is defined by transfers made from the local machine to removable devices. - Incoming File Tracing Direction indicates transfers from the removable devices to the local machine. @@ -600,10 +600,10 @@ For your deployment, activate File Shadowing for not more than 15% of your total ::: -- Exclude Extensions from Shadowing – use this setting to disable File Shadowing for specific file +- Exclude Extensions from Shadowing – use this setting to disable File Shadowing for specific file types. -- Scan archive in archive – use this setting to define the archive depth in which content is +- Scan archive in archive – use this setting to define the archive depth in which content is inspected. - Block Time Machine – if you enable this setting, you will block Time Machine backups on macOS. @@ -611,7 +611,7 @@ For your deployment, activate File Shadowing for not more than 15% of your total ![File Tracing and Shadowing Settings](filetracingshadowing.webp) - Metadata Scanning - if you disable this setting, metadata will not be scanned for PDFs, ZIPs, and - Office Files DOCX, XLSX, PPTX, DOC, XLX, PPT). + Office Files DOCX, XLSX, PPTX, DOC, XLX, PPT). - Advanced Printer and MTP Scanning – enables a feature in Endpoint Protector by which a small DLL is loaded into certain Windows applications when they are launched. That small DLL enables Endpoint Protector to monitor printing and files copied to MTP devices, by hooking Windows API functions responsible with printing and copying files to MTP devices. For example, when a user opens Microsoft Word, an Endpoint Protector DLL is loaded into Microsoft Word's address space. If the user wants to print a document, that DLL is called, and Endpoint Protector can scan the printed document content. If the printed content contains sensitive data Endpoint Protector can block the print operation. @@ -638,7 +638,7 @@ For example, many applications can't be used to print or to copy files to MTP de the file content. By default, printing is allowed. This option applies only to Chrome and Edge with the browser extension on Windows. -- File Hash - if you enable this setting, a file hash will be generated and included in the file +- File Hash - if you enable this setting, a file hash will be generated and included in the file transfer logs. - Scan Printed Document – specifies whether to scan the entire document or individual pages when a print operation is detected. @@ -648,17 +648,17 @@ For example, many applications can't be used to print or to copy files to MTP de :::warning Newer Linux Ubuntu versions have 'snap'-based applications installed by default, -affecting Endpoint Protector Client functionality. This may result in missing file-related events in +affecting Endpoint Protector Client functionality. This may result in missing file-related events in File Tracing and File Shadow artifacts. The reliance on 'snap'-based applications also affects -file-related web browser activities, exacerbating this limitation. Consider non-’snap’-based -applications (where possible) as alternative configurations for optimal functionality. +file-related web browser activities, exacerbating this limitation. Consider non-’snap’-based +applications (where possible) as alternative configurations for optimal functionality. ::: ## Block Print from Browsers Enable this setting to restrict the user from printing web pages from various browser types -available, define the specific browsers, and create and enforce a Content Aware Policy that includes +available, define the specific browsers, and create and enforce a Content Aware Policy that includes Printers from the Policy Exit Points section. :::note @@ -667,7 +667,7 @@ This setting is available only for Windows. :::warning -After enabling the Block Print from Browsers setting and applying the configuration on +After enabling the Block Print from Browsers setting and applying the configuration on the Client to enforce it, be aware that open browser tabs will need to be reloaded, or a browser restart will be required for the changes to take effect. ::: @@ -698,7 +698,7 @@ When printing from Excel Online, changes made in the last few seconds may not be Users printing from Google Chrome and Microsoft Edge can use content-aware detection by enforcing a Content Aware Policy that includes Printers from the Policy Exit Points section. For seamless protection, the Endpoint Protector Browser Connection extension installs automatically the -first time upon enabling the Block Print from Browsers setting. This extension enhances content +first time upon enabling the Block Print from Browsers setting. This extension enhances content scanning capabilities during web document printing, integrating seamlessly on both server and client sides. @@ -716,7 +716,7 @@ Microsoft Edge. :::warning -Use the Group Policies to set PDF files to be downloaded instead of opened in the web +Use the Group Policies to set PDF files to be downloaded instead of opened in the web browser for the block print from the browser to function accurately. ::: @@ -727,43 +727,43 @@ disabling or uninstalling the Google Chrome and Microsoft Edge extension. ::: -### Configuring GPO for Browser Extensions +### Configuring GPO for Browser Extensions -To configure Group Policy Objects (GPO) to deploy a browser extension to Windows machines and prevent +To configure Group Policy Objects (GPO) to deploy a browser extension to Windows machines and prevent users from removing it, follow these steps: 1. Google Chrome - **Step 1 –** Refer to the official + **Step 1 –** Refer to the official [Google support guide](https://support.google.com/chrome/a/answer/10407780?hl=en) for detailed instructions. **Step 2 –** Download the [Chrome Group Policy](https://chromeenterprise.google/browser/download/#chrome-group-policy). - **Step 3 –** Configure your Group Policy as shown in the following screenshot. + **Step 3 –** Configure your Group Policy as shown in the following screenshot. - Endpoint Protector Browser Connector ID: nnnaeanocbmnnjjlcfhcbpefmlgbcgoi -![Configuring GPO for Browser Extensions](grouppolicyeditor.webp) +![Configuring GPO for Browser Extensions](grouppolicyeditor.webp) 1. Microsoft Edge **Step 1 –** use the - [Configure Microsoft Edge](https://learn.microsoft.com/en-us/deployedge/configure-microsoft-edge) + [Configure Microsoft Edge](https://learn.microsoft.com/en-us/deployedge/configure-microsoft-edge) guide provided by Microsoft. **Step 2 –** Download the [Edge Group Policy Template](https://learn.microsoft.com/en-US/troubleshoot/windows-client/group-policy/create-and-manage-central-store). - **Step 3 –** Configure your Group Policy as shown in the following screenshot. + **Step 3 –** Configure your Group Policy as shown in the following screenshot. - Endpoint Protector Browser Connector ID: nnnaeanocbmnnjjlcfhcbpefmlgbcgoi -![Configuring GPO for Browser Extensions](grouppolicyeditortwo.webp) +![Configuring GPO for Browser Extensions](grouppolicyeditortwo.webp) :::warning -ensure to thoroughly test the configuration in a controlled environment to ensure the +ensure to thoroughly test the configuration in a controlled environment to ensure the intended behavior. Always keep endpoint security policies updated and aligned with organizational security standards. ::: @@ -776,27 +776,27 @@ Protection and File Tracing visibility over virtual printers like Microsoft to P more. This not only helps conserve valuable log space but also reduces the workload on your analytics and administration teams. With this option, users can focus on tracking PDFs only when they exit your organization's environment and not when they have been created, streamlining -monitoring efforts and improving efficiency. +monitoring efforts and improving efficiency. :::note This feature only applies for Windows. ::: -## Configure Max File Size +## Configure Max File Size -This section allows customers to tailor Content Aware Protection scanner’s file size settings -according to their specific needs. By customizing these settings, users can ensure Endpoint Protector -meets their organization's requirements. The default maximum file size is set at 40 MB, with a +This section allows customers to tailor Content Aware Protection scanner’s file size settings +according to their specific needs. By customizing these settings, users can ensure Endpoint Protector +meets their organization's requirements. The default maximum file size is set at 40 MB, with a maximum limit of 4096 MB. -Furthermore, users have the flexibility to configure additional file type sizes, which are set as -follows by default: PDF (2048 MB) and Archives (256 MB). These file type sizes can be adjusted within -the range of 1 KB to 4 GB to accommodate your specific needs. +Furthermore, users have the flexibility to configure additional file type sizes, which are set as +follows by default: PDF (2048 MB) and Archives (256 MB). These file type sizes can be adjusted within +the range of 1 KB to 4 GB to accommodate your specific needs. Additionally, in the Windows environment, a default time-out of 10 seconds is applied. For MacOS, a strict 10-second time-out is enforced due to Apple OS architecture, which terminates processes that -don't respond promptly. Linux operates without a specific time-out limitation. +don't respond promptly. Linux operates without a specific time-out limitation. :::note This setting only applies to Content Aware Protection policies and doesn't affect @@ -804,7 +804,7 @@ eDiscovery Policies and Max File Size for File Shadows. ::: -![ Tailor Content Aware Protection scanner’s file size settings according to their specific needs. ](maxfileconfg.webp) +![ Tailor Content Aware Protection scanner’s file size settings according to their specific needs. ](maxfileconfg.webp) ## Outside Hours and Outside Network @@ -813,7 +813,7 @@ Control and Content Aware modules. - Outside Hours policies – enable the setting and then set the Working days, Business hours start time, and end time. -- Outside Network policies – enable the setting and then add the DNS Fully Qualified Domain Name and +- Outside Network policies – enable the setting and then add the DNS Fully Qualified Domain Name and DNS IP Addresses. Once these settings are made, the fallback device type rights can be set Globally, per Groups, @@ -835,13 +835,13 @@ and Outside Hours Policy Type also needs to be selected. ## Transfer Limit -From this section, users can set the transfer limit, within a specific time interval (hours). Once -the limit is reached, file transfers to storage devices (Device Control) to control applications +From this section, users can set the transfer limit, within a specific time interval (hours). Once +the limit is reached, file transfers to storage devices (Device Control) to control applications (Content Aware Protection) will no longer be possible, until the time interval expires and the count -is reset. Similarly, file transfers through Network Shares can also be included in the Transfer +is reset. Similarly, file transfers through Network Shares can also be included in the Transfer Limit. -![Set the transfer limit, within a specific time interval (hours)](transferlimit.webp) +![Set the transfer limit, within a specific time interval (hours)](transferlimit.webp) The mechanism that checks when the Transfer Limit is reached doesn't impact the performance of the computer. @@ -852,15 +852,15 @@ the network, it could be up to a few minutes. There are three actions to choose from when the Transfer Limit is reached: - Monitor Only – this setting reports when the limit is reached -- Restrict – this setting blocks the devices and applications that have been defined in the Device +- Restrict – this setting blocks the devices and applications that have been defined in the Device Control policies -- Lockdown – this setting blocks all devices, regardless if they have been defined within the Device +- Lockdown – this setting blocks all devices, regardless if they have been defined within the Device Control policies, including the network interfaces and therefore, any type of transfer :::note To re-establish the Server-Client communication before the Transfer Limit Time Interval -expires, a Transfer Limit Reached Offline Temporary Password is available. For detailed information, -refer to the Offline Temporary Password chapter. +expires, a Transfer Limit Reached Offline Temporary Password is available. For detailed information, +refer to the Offline Temporary Password chapter. ::: @@ -871,10 +871,10 @@ daily, weekly, or monthly basis. ## Debug Logging -You can use this feature to collect logs for a specific issue and send the resulting archive to the +You can use this feature to collect logs for a specific issue and send the resulting archive to the Endpoint Protector Server on the Reports and analysis section, the Logs Report page. -By enabling this feature, the Endpoint Protector Client will create the log file (general log file), +By enabling this feature, the Endpoint Protector Client will create the log file (general log file), and if Deep Packet Inspection is enabled, it will collect supplementary Deep Packet Inspection logs along with sslsplit logs. @@ -883,7 +883,7 @@ Use the Debug level mode, as it contains more than error and warning type inform ::: -![Use this feature to collect logs for a specific issue](debuglogging.webp) +![Use this feature to collect logs for a specific issue](debuglogging.webp) ### Debug Logging Usage @@ -932,7 +932,7 @@ logging option. - This option is available under **Device Control** on the **Computer** page. - Hover over a computer, right-click, and select **Collect diagnostic** - this will collect logs - from a specific computer without input or knowledge from the computer user. + from a specific computer without input or knowledge from the computer user. Logs will be sent to the Endpoint Protector Server on the Logs Report page, Artifact Received events are registered when diagnostic data are received. @@ -970,17 +970,17 @@ the **Actions** column. All data is obfuscated according to the following rules: -- the first 4 characters are displayed if the length of the threat is lower than 12 characters, or -- the first 6 characters are displayed if the length of the threat is longer than 12 characters +- the first 4 characters are displayed if the length of the threat is lower than 12 characters, or +- the first 6 characters are displayed if the length of the threat is longer than 12 characters -Specific use cases: +Specific use cases: 1. For credit cards, the PCI Security Standards were implemented 2. For SSNs, the last 4 characters are displayed -3. For Brazil ID (CPF), the first 3 and the last 2 characters are obfuscated +3. For Brazil ID (CPF), the first 3 and the last 2 characters are obfuscated :::note -Data isn't obfuscated for the file-type threat, file-size threat, and date threat. +Data isn't obfuscated for the file-type threat, file-size threat, and date threat. ::: @@ -1027,7 +1027,7 @@ and the number of reports per page. You can set a maximum number of 10 000 logs to be displayed per report. To export all entries when the log number exceeds the maximum 10 000 limit, use the Create export option or narrow the search -using filters. +using filters. :::note The information you set on this setting will also be applied for eDiscovery. From 60c8a38fe77e57844a94d850aeaa2cdf7a82b94f Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Tue, 5 May 2026 15:44:02 +0000 Subject: [PATCH 21/27] fix(vale): auto-fix style issues (Vale + Dale) --- .../admin/dc_module/globalsettings.md | 25 ++++++++----------- 1 file changed, 10 insertions(+), 15 deletions(-) diff --git a/docs/endpointprotector/admin/dc_module/globalsettings.md b/docs/endpointprotector/admin/dc_module/globalsettings.md index 0df09027bd..34d42c8377 100644 --- a/docs/endpointprotector/admin/dc_module/globalsettings.md +++ b/docs/endpointprotector/admin/dc_module/globalsettings.md @@ -295,8 +295,8 @@ In this section, you can manage the following settings: validation of the websites that are accessed by the user when DPI is active - Ignore Expiration Date - when checked, Endpoint Protector ignores expired certificates and permits traffic. - - Ignore Trust - when checked, Endpoint Protector does not validate certificates against the Root Certificate. - - Ignore Hostname - when checked, Endpoint Protector does not validate the certificate hostname property against the server hostname. + - Ignore Trust - when checked, Endpoint Protector doesn't validate certificates against the Root Certificate. + - Ignore Hostname - when checked, Endpoint Protector doesn't validate the certificate hostname property against the server hostname. :::warning Disabling setting ‘Peer Certificate Validation’ will not impact Endpoint Protector @@ -518,16 +518,13 @@ Endpoint Protector employs a nuanced approach to handle bypassed domains and app #### Memory and Disk Persistence -Bypassed website information is stored in both memory and on disk. This dual storage ensures that -the list of skipped websites is readily accessible for efficient future reference. By persisting this -information, the frequency of log generation can be controlled to avoid unnecessary strain on -resources. +Endpoint Protector stores bypassed website information in both memory and on disk. This dual storage ensures that +the list of skipped websites is readily accessible for efficient future reference. Persisting this +information controls the frequency of log generation and avoids unnecessary strain on resources. #### Clearing Bypass State -To reset the bypass state and clear associated records, administrators can initiate a simple -process. Temporarily disabling and subsequently re-enabling the bypass DPI setting on the Endpoint -Protector server achieves this reset. +To reset the bypass state and clear associated records, administrators can temporarily disable and re-enable the bypass DPI setting on the Endpoint Protector server. ### Using Wireshark for Network Traffic Analysis @@ -548,8 +545,7 @@ In this section, you can manage the following settings: - File Shadowing – this feature extends the information provided by File Tracing, creating exact copies of files accessed by users. -The creation of shadow copies can be triggered by the following events: file copy, file write, and file -read. Events such as file deleted, file renamed, etc. don't trigger the function. You can enable File +The following events trigger shadow copy creation: file copy, file write, and file read. Events such as file deleted, file renamed, etc. don't trigger the function. You can enable File Shadowing on all supported Removable Devices: - eSATA HDDs or Time Machines @@ -610,10 +606,10 @@ For your deployment, activate File Shadowing for not more than 15% of your total ![File Tracing and Shadowing Settings](filetracingshadowing.webp) -- Metadata Scanning - if you disable this setting, metadata will not be scanned for PDFs, ZIPs, and +- Metadata Scanning - if you disable this setting, Endpoint Protector will not scan metadata for PDFs, ZIPs, and Office Files DOCX, XLSX, PPTX, DOC, XLX, PPT). -- Advanced Printer and MTP Scanning – enables a feature in Endpoint Protector by which a small DLL is loaded into certain Windows applications when they are launched. That small DLL enables Endpoint Protector to monitor printing and files copied to MTP devices, by hooking Windows API functions responsible with printing and copying files to MTP devices. +- Advanced Printer and MTP Scanning – enables a feature that loads a small DLL into certain Windows applications when they launch. That small DLL enables Endpoint Protector to monitor printing and files copied to MTP devices, by hooking Windows API functions responsible with printing and copying files to MTP devices. For example, when a user opens Microsoft Word, an Endpoint Protector DLL is loaded into Microsoft Word's address space. If the user wants to print a document, that DLL is called, and Endpoint Protector can scan the printed document content. If the printed content contains sensitive data Endpoint Protector can block the print operation. @@ -668,8 +664,7 @@ This setting is available only for Windows. :::warning After enabling the Block Print from Browsers setting and applying the configuration on -the Client to enforce it, be aware that open browser tabs will need to be reloaded, or a -browser restart will be required for the changes to take effect. +the Client to enforce it, be aware that you will need to reload open browser tabs or restart the browser for the changes to take effect. ::: From 3df4e0d414532e07fce919f1e6569f4c771957d9 Mon Sep 17 00:00:00 2001 From: jth-nw Date: Tue, 5 May 2026 10:59:06 -0500 Subject: [PATCH 22/27] fix(endpointprotector): fix broken anchor in deeppacket after ligature fix Updates the link to globalsettings#dpi-configuration to use ASCII, matching the heading anchor generated after the fi ligature was replaced. Generated with AI Co-Authored-By: Claude Code --- docs/endpointprotector/admin/cap_module/deeppacket.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/endpointprotector/admin/cap_module/deeppacket.md b/docs/endpointprotector/admin/cap_module/deeppacket.md index ff8d677785..de8ca221a1 100644 --- a/docs/endpointprotector/admin/cap_module/deeppacket.md +++ b/docs/endpointprotector/admin/cap_module/deeppacket.md @@ -103,7 +103,7 @@ EPP DPI module generates a certificate only at the first time a user visits a we Endpoint Protector employs the same criteria as the Chromium open-source web browser for verifying website certificates, referencing the corporate CA certificates found in the system certificate stores. You can assess this validation by using diagnostic websites like https://badssl.com/. -If needed, this feature can be configured through the DPI Bypass option described here [Global Settings - DPI configuration](/docs/endpointprotector/admin/dc_module/globalsettings#dpi-configuration). +If needed, this feature can be configured through the DPI Bypass option described here [Global Settings - DPI configuration](/docs/endpointprotector/admin/dc_module/globalsettings#dpi-configuration). ### DPI on Windows From f3f9f90ab28568f3509734aecfa3b5a5c06a0f7e Mon Sep 17 00:00:00 2001 From: jth-nw Date: Tue, 5 May 2026 11:01:42 -0500 Subject: [PATCH 23/27] removed derek plan --- .claude/specs/2026-04-07-derek-design.md | 206 ----------------------- 1 file changed, 206 deletions(-) delete mode 100644 .claude/specs/2026-04-07-derek-design.md diff --git a/.claude/specs/2026-04-07-derek-design.md b/.claude/specs/2026-04-07-derek-design.md deleted file mode 100644 index fdd4ee340e..0000000000 --- a/.claude/specs/2026-04-07-derek-design.md +++ /dev/null @@ -1,206 +0,0 @@ -# Derek Skill — Design Spec - -**Date:** 2026-04-07 -**Status:** Approved - ---- - -## Summary - -Derek is a Claude skill that lints KB articles against the Netwrix KB style guide. It is the KB equivalent of dale — pure input/output, no conversation. Invoked with `/derek `. - -Two deliverables: -1. `kb_style_guide.md` — new file at repo root, authoritative style reference for KB articles -2. `.claude/skills/derek/` — the skill itself - ---- - -## Context - -- KB articles live in `docs/kb//` -- They are written by TSEs (technical support engineers), not the docs team -- They follow a different style guide than regular product docs -- The `feature/frontmatter-autoinjection` script explicitly skips KB files (`docs/kb/*`) because their frontmatter schema is more complex — derek handles it instead -- Dale enforces the docs style guide (`netwrix_style_guide.md`). Derek enforces the KB style guide (`kb_style_guide.md`). **The two guides conflict on contractions and heading case — do not run `/dale` on KB files.** - ---- - -## Deliverable 1: `kb_style_guide.md` - -Created at the repo root alongside `netwrix_style_guide.md`. - -**Source:** Internal wiki KB style guide (`knowledge-style-guide-markdown.md`), with the following additions and overrides. - -### Additions (from docs style guide — apply universally) - -- No "please" in instructions — be direct -- No "simply", "just", "easily", "basically", "obviously" -- No inline "note that" / "please note" — use admonition blocks -- No impersonal constructions: "it is recommended / necessary / possible / required / advised / suggested" -- Active voice — with examples -- Define technical terms and acronyms on first use -- Descriptive link text — never "click here", "read more", "learn more", "see more" - -### Overrides (wiki rule takes precedence over docs style guide) - -| Topic | KB rule | -|---|---| -| Contractions | Write out in full: "do not", "cannot", "you will" | -| Heading case | Title case (Chicago style, capitalizemytitle.com) | - -### Tags field — required, must include `kb` - -The wiki marks `tags` as optional. **This is overridden for the Netwrix repo:** `tags` must be present and must include `kb`. This enables KB article filtering in Algolia search — Algolia indexes the `tags` field automatically, no Algolia config changes required. - -### Frontmatter schema - -All KB articles must have this frontmatter: - -```yaml ---- -description: >- - Short, SEO-friendly summary of the article (1–2 sentences). -keywords: - - keyword one - - keyword two - - (8–12 items total) -products: - - product-id -sidebar_label: 'Article Title' -tags: - - kb -title: "Full Article Title" -knowledge_article_id: kA0Qk000000XXXXKAA ---- -``` - -**Required fields:** - -| Field | Format | -|---|---| -| `title` | Quoted string — full article title | -| `description` | Non-empty string or `>-` multiline block | -| `sidebar_label` | Quoted string — matches or shortens the title | -| `keywords` | YAML list of 8–12 technical/product search terms | -| `products` | YAML list of product IDs (see product names table) | -| `tags` | YAML list; **must include `kb`** | -| `knowledge_article_id` | Salesforce KB article ID matching `kA[0-9A-Za-z]+` | - ---- - -## Deliverable 2: `.claude/skills/derek/` - -### Architecture - -Mirrors dale exactly: `SKILL.md` + `rules/*.yml` + `references/rule-schema.yml`. Option A chosen over Option B (split `rules/` and `checks/`) because the output and invocation are identical, and the added complexity of two processing loops in SKILL.md provides no user-facing benefit. The `reason` field in rule files describes what to look for — equally valid for prose patterns and structural assertions. - -### File layout - -``` -.claude/skills/derek/ - SKILL.md - rules/ - frontmatter-title.yml - frontmatter-description.yml - frontmatter-sidebar-label.yml - frontmatter-keywords-count.yml - frontmatter-products.yml - frontmatter-tags-kb.yml - frontmatter-knowledge-article-id.yml - structure-article-type.yml - no-please.yml - minimizing-difficulty.yml - no-note-that.yml - impersonal-constructions.yml - passive-voice.yml - undefined-jargon.yml - descriptive-links.yml - contractions.yml - title-case-headings.yml - business-jargon.yml - references/ - rule-schema.yml -``` - -18 rules total: 7 frontmatter, 1 structure, 10 prose. - -### SKILL.md behavior - -- Pure linter — no conversation, no explanation beyond the output table -- Creates a Todo for each rule file -- For each rule: reads `reason`, checks the document, notes violations -- Outputs a single table at the end (or "no issues found") -- Includes a warning: **do not run `/dale` on KB files** — the KB style guide and docs style guide conflict on contractions and heading case - -### Output format (same as dale) - -``` -| Line | Rule | Message | Offending Text | -|------|------|---------|----------------| -``` - -- Frontmatter violations where a field is missing: Line is `1` (frontmatter block start) -- Structure violations: Line is the line number of the first mismatched or missing heading -- Structure violations where sections are entirely missing: message includes the expected heading template the writer can copy in - ---- - -## Rules detail - -### Frontmatter rules - -| File | Level | Checks | -|---|---|---| -| `frontmatter-title.yml` | error | `title` present and is a quoted string | -| `frontmatter-description.yml` | error | `description` present and non-empty | -| `frontmatter-sidebar-label.yml` | error | `sidebar_label` present and non-empty | -| `frontmatter-keywords-count.yml` | warning | `keywords` present and contains 8–12 items | -| `frontmatter-products.yml` | error | `products` present with at least one item | -| `frontmatter-tags-kb.yml` | error | `tags` present and includes `kb` | -| `frontmatter-knowledge-article-id.yml` | error | `knowledge_article_id` present and matches `kA[0-9A-Za-z]+` | - -### Structure rule - -| File | Level | Checks | -|---|---|---| -| `structure-article-type.yml` | warning | Infers article type from title, validates required H2 headings are present | - -**Type inference logic:** -- Title starts with `"Error:"` → Error Resolution → expects `## Symptom/Symptoms`, `## Cause/Causes`, `## Resolution/Resolutions` -- Title starts with a gerund or `"How to"` → How-To → expects `## Overview` + `## Instructions`, or `## Question` + `## Answer` -- Everything else → Symptom Resolution → expects `## Symptom/Symptoms`, `## Cause/Causes`, `## Resolution/Resolutions` - -When required headings are missing, the violation message outputs the expected heading template for the inferred type. - -### Prose rules - -| File | Level | Checks | -|---|---|---| -| `passive-voice.yml` | warning | Passive voice constructions in body text | -| `no-please.yml` | warning | "please" in instructions | -| `minimizing-difficulty.yml` | warning | "simply", "just", "easily", "basically", "obviously" | -| `no-note-that.yml` | warning | Inline "note that" or "please note" | -| `impersonal-constructions.yml` | warning | "it is recommended/necessary/possible/required/advised/suggested" | -| `contractions.yml` | warning | Contractions (don't, can't, you'll, etc.) — write out in full in KB articles | -| `title-case-headings.yml` | warning | Headings not in title case (Chicago style) | -| `business-jargon.yml` | warning | "utilize/utilise", "leverage" (non-financial), "synergy" | -| `descriptive-links.yml` | warning | Generic link text: "click here", "read more", "learn more", "see more", "this link" | -| `undefined-jargon.yml` | warning | Technical terms or acronyms used without definition on first use | - -`undefined-jargon.yml` is `warning` (not `error`) because it requires the most judgment and is the most likely source of false positives. - ---- - -## Branch - -New feature branch off `dev`: `feature/derek-skill` - ---- - -## Notes on existing articles - -Article scan (15 articles across 6+ products) found: -- **Tags**: All articles have either `tags: []` or category-based tags — no article has `kb` in tags. `frontmatter-tags-kb` will fire on every existing article. -- **Keyword count**: Range 3–9 across sampled articles, below the 8–12 requirement. `frontmatter-keywords-count` will fire frequently. -- **Missing sidebar_label**: One article found without it. -- These are expected and reflect the remediation work derek is meant to surface. From 7b7e77a69d13378be8d8f53a8a7c043872530e11 Mon Sep 17 00:00:00 2001 From: Dan Piazza <220388267+DanPiazza-Netwrix@users.noreply.github.com> Date: Tue, 5 May 2026 12:04:52 -0400 Subject: [PATCH 24/27] fix(changetracker): convert 2FA config image to text with code formatting Replaced screenshot of appsettings.json with a transcribed JSON code block and applied inline code formatting to file paths and setting references. No information added or removed. Generated with AI Co-Authored-By: Claude Code --- docs/changetracker/8.1/gettingstarted.md | 36 ++++++++++++++++++++---- 1 file changed, 30 insertions(+), 6 deletions(-) diff --git a/docs/changetracker/8.1/gettingstarted.md b/docs/changetracker/8.1/gettingstarted.md index 758ba80329..bc0dd48dd1 100644 --- a/docs/changetracker/8.1/gettingstarted.md +++ b/docs/changetracker/8.1/gettingstarted.md @@ -38,16 +38,40 @@ Passcode (OTP) is not provided during the sign in process, one may be required w certain actions within Change Tracker for the first time during a session. If the root admin user is NOT able to use an authenticator app for 2FA on the first login, then set -the following configuration settings in the C:\inetpub\wwwroot\Change Tracker Generation 7 (NetCore) -Hub\Configs\appsettings.json file as shown: +the following configuration settings in +`C:\inetpub\wwwroot\Change Tracker Generation 7 (NetCore) Hub\Configs\appsettings.json`: +``` security > auth > twoFactor > "registerAdmin": "false" - security > auth > twoFactor > "fallbackEnabled": "true" (default setting) +``` -![2faconfiguration](/images/changetracker/8.1/admin/2faconfiguration.webp) +```json +"security": { + "xsrf": { + "headersenabled": "true" + }, + "auth": { + "lockoutenabled": "false", + "lockoutmaxloginattempts": "3", + "lockoutdurationminutes": "0", + "ipblockingmaxloginattempts": "3", + "ipblockingwindowminutes": "10", + "ipblockingdurationminutes": "10", + "postonly": "false", + "ssoenabled": "false", + "ssoheader": "", + "hidelogin": "false", + "twoFactor": { + "registerAdmin": "false", + "fallbackEnabled": "true" + } + } +} +``` A One-Time Passcode (OTP) may be required when attempting certain actions within Change Tracker for the first time during a session. Without 2FA or an authenticator app, this OTP will be written to -the application log file (C:\inetpub\wwwroot\Change Tracker Generation 7 (NetCore) -Hub\logs\hubservice-log.txt) which is only accessible by local admins. +the application log file +(`C:\inetpub\wwwroot\Change Tracker Generation 7 (NetCore) Hub\logs\hubservice-log.txt`), +which is only accessible by local admins. From 22f5dadcaf20c1ffe0538151b64c5059db45dd8f Mon Sep 17 00:00:00 2001 From: AleksNWX Date: Tue, 5 May 2026 18:05:24 +0200 Subject: [PATCH 25/27] Apply suggestion from @markis Strange I checked it and made changes yesterda. Co-authored-by: Markis Taylor --- docs/accessanalyzer/2601/install/install-commands.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/accessanalyzer/2601/install/install-commands.md b/docs/accessanalyzer/2601/install/install-commands.md index f10d6e6706..ca58fb4b04 100644 --- a/docs/accessanalyzer/2601/install/install-commands.md +++ b/docs/accessanalyzer/2601/install/install-commands.md @@ -49,7 +49,7 @@ Run `dspm-installer [command] --help` to view usage and available options for an ```bash # Set the Keygen license key variable -export LICENSE_KEY='[Y]' +export LICENSE_KEY='[YOUR_LICENSE_KEY]' # Pin to a specific release version export TARGET_REVISION='[VERSION]' From 528a3b17a3db25c9ab3ca42b5a5bfbc353dc3a57 Mon Sep 17 00:00:00 2001 From: Dan Piazza <220388267+DanPiazza-Netwrix@users.noreply.github.com> Date: Tue, 5 May 2026 12:08:18 -0400 Subject: [PATCH 26/27] fix(changetracker): convert 2FA config image to text with code formatting Replaced screenshot of appsettings.json with a transcribed JSON code block, applied inline code formatting to file paths and setting references, and incorporated Vale/Dale auto-fix corrections (contractions, passive voice, idioms, positional references). Generated with AI Co-Authored-By: Claude Code --- docs/changetracker/8.1/gettingstarted.md | 41 +++++++++++++----------- 1 file changed, 23 insertions(+), 18 deletions(-) diff --git a/docs/changetracker/8.1/gettingstarted.md b/docs/changetracker/8.1/gettingstarted.md index bc0dd48dd1..6c52ae0281 100644 --- a/docs/changetracker/8.1/gettingstarted.md +++ b/docs/changetracker/8.1/gettingstarted.md @@ -6,18 +6,17 @@ sidebar_position: 3 # Getting Started -Once you have successfully installed Netwrix Change Tracker, and logged in for the first time (see -2FA section below), you can start putting it to work. Change Tracker can collect data for the -reports with or without agents. By default, an agent is installed on the Change Tracker machine, so -you can quickly check the data collection and reports using that agent. Alternatively, you can -collect data from other devices in your network. Either way, your starting point will be the +After you have successfully installed Netwrix Change Tracker, and logged in for the first time (see [Two Factor Authentication](#two-factor-authentication)), you can start using it. Change Tracker can collect data for the +reports with or without agents. By default, Change Tracker installs an agent on the machine, so +you can check the data collection and reports using that agent. Alternatively, you can +collect data from other devices in your network. In both cases, your starting point will be the [Device Tab](/docs/changetracker/8.1/admin/devices.md). -Once you have established data collection, use the Reports tab to view reports on you device's +After you have established data collection, use the Reports tab to view reports on you device's configuration. Next, use the [Planned Changes Tab](/docs/changetracker/8.1/admin/plannedchanges/plannedchanges.md) manage change events and filter any -changes that are considered as noise. +changes that you consider noise. To add another user, manage licenses, set the planned change intervals, and otherwise configure Change Tracker, review the [Settings Tab](/docs/changetracker/8.1/admin/settingstab/settingstab.md). @@ -27,25 +26,27 @@ Change Tracker, review the [Settings Tab](/docs/changetracker/8.1/admin/settings Sign in as the root "admin" account and follow the instructions to register Change Tracker with an authenticator app on your mobile device. -Once registered with your authenticator app, use it to provide a One-Time Passcode (OTP) to complete +Once you have registered Change Tracker with your authenticator app, use it to provide a One-Time Passcode (OTP) to complete the 2FA registration. -A One-Time Passcode (OTP) must now be provided during the sign in process. +You must now provide a One-Time Passcode (OTP) during the sign in process. -2FA is highly recommended, but it is possible to be disabled. Clearing the "2FA login" checkbox -against the User account in the User Admin page will disable 2FA for the user. If a One-Time -Passcode (OTP) is not provided during the sign in process, one may be required when attempting -certain actions within Change Tracker for the first time during a session. +Netwrix highly recommends 2FA, but you can disable it. Clearing the "2FA login" checkbox +against the User account in the User Admin page will disable 2FA for the user. If you don't provide +a One-Time Passcode (OTP) during the sign-in process, Change Tracker may require one when you attempt +certain actions for the first time during a session. -If the root admin user is NOT able to use an authenticator app for 2FA on the first login, then set +If the root admin user can't use an authenticator app for 2FA on the first login, set the following configuration settings in `C:\inetpub\wwwroot\Change Tracker Generation 7 (NetCore) Hub\Configs\appsettings.json`: ``` security > auth > twoFactor > "registerAdmin": "false" -security > auth > twoFactor > "fallbackEnabled": "true" (default setting) +security > auth > twoFactor > "fallbackEnabled": "true" ``` +These settings appear in the `security` section of the configuration file: + ```json "security": { "xsrf": { @@ -70,8 +71,12 @@ security > auth > twoFactor > "fallbackEnabled": "true" (default setting) } ``` -A One-Time Passcode (OTP) may be required when attempting certain actions within Change Tracker for -the first time during a session. Without 2FA or an authenticator app, this OTP will be written to +:::note +Change only the `twoFactor` values. The surrounding settings provide context. +::: + +Change Tracker may require a One-Time Passcode (OTP) when you attempt certain actions for +the first time during a session. Without 2FA or an authenticator app, Change Tracker writes this OTP to the application log file (`C:\inetpub\wwwroot\Change Tracker Generation 7 (NetCore) Hub\logs\hubservice-log.txt`), -which is only accessible by local admins. +which only local admins can access. From 6378b27ab89aba21b026b566857fd7072ff033a1 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Tue, 5 May 2026 16:11:18 +0000 Subject: [PATCH 27/27] fix(vale): auto-fix style issues (Vale + Dale) --- docs/changetracker/8.1/gettingstarted.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/changetracker/8.1/gettingstarted.md b/docs/changetracker/8.1/gettingstarted.md index 6c52ae0281..a22b42b863 100644 --- a/docs/changetracker/8.1/gettingstarted.md +++ b/docs/changetracker/8.1/gettingstarted.md @@ -6,13 +6,13 @@ sidebar_position: 3 # Getting Started -After you have successfully installed Netwrix Change Tracker, and logged in for the first time (see [Two Factor Authentication](#two-factor-authentication)), you can start using it. Change Tracker can collect data for the +After you have installed Netwrix Change Tracker, and logged in for the first time (see [Two Factor Authentication](#two-factor-authentication)), you can start using it. Change Tracker can collect data for the reports with or without agents. By default, Change Tracker installs an agent on the machine, so you can check the data collection and reports using that agent. Alternatively, you can collect data from other devices in your network. In both cases, your starting point will be the [Device Tab](/docs/changetracker/8.1/admin/devices.md). -After you have established data collection, use the Reports tab to view reports on you device's +After establishing data collection, use the Reports tab to view reports on your device's configuration. Next, use the [Planned Changes Tab](/docs/changetracker/8.1/admin/plannedchanges/plannedchanges.md) manage change events and filter any @@ -26,7 +26,7 @@ Change Tracker, review the [Settings Tab](/docs/changetracker/8.1/admin/settings Sign in as the root "admin" account and follow the instructions to register Change Tracker with an authenticator app on your mobile device. -Once you have registered Change Tracker with your authenticator app, use it to provide a One-Time Passcode (OTP) to complete +After registering Change Tracker with your authenticator app, use it to provide a One-Time Passcode (OTP) to complete the 2FA registration. You must now provide a One-Time Passcode (OTP) during the sign in process.