Skip to content

dev to main #324

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jth-nw merged 5 commits into from
Feb 26, 2026
Merged

dev to main #324

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ee0c8cb
Update okta.md (#318)
tay-caliguiri Feb 26, 2026
06a3a0b
Update 'When' field description with datetime formats (#315)
pavelshabanov2025 Feb 26, 2026
7e85d52
Merge pull request #320 from netwrix/doc-reviewer-full-scan
jth-nw Feb 26, 2026
88a23ea
Switch documentation reviewer to claude-opus-4-6
Feb 26, 2026
737547e
Merge pull request #323 from netwrix/doc-reviewer-opus
jth-nw Feb 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions .github/workflows/claude-documentation-reviewer.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,10 +85,15 @@ jobs:
prompt: |
Review the following markdown files that were modified in this PR: ${{ steps.changed-files.outputs.files }}

Use `gh pr diff ${{ github.event.pull_request.number }}` to identify which lines were added or modified by this PR.
Use the Read tool to read each file in full.
Follow these steps in order:

Identify ALL issues in each file. Categorize each issue as either:
1. Use the Read tool to read each file in full. Do not look at the PR diff yet.

2. Identify ALL issues throughout the entire document — every sentence, every paragraph, every section. Do not stop after finding a few issues. Do not limit yourself to areas that look like they were recently changed.

3. Use `gh pr diff ${{ github.event.pull_request.number }}` to get the list of lines that were added or modified in this PR.

4. Categorize each issue you found in step 2 as either:
- Issues in PR changes: the issue is on a line that was added or modified in this PR
- Preexisting issues: the issue exists on a line that was not changed by this PR

Expand All @@ -103,7 +108,7 @@ jobs:
Then fix ALL issues directly in the files using the Write and Edit tools. Do not post a PR comment. Do not commit or push.

claude_args: |
--model claude-sonnet-4-5-20250929
--model claude-opus-4-6
--allowedTools "Read,Write,Edit,Bash(gh pr view:*),Bash(gh pr diff:*)"
--append-system-prompt "${{ steps.read-prompt.outputs.prompt }}"

Expand Down
2 changes: 1 addition & 1 deletion docs/accessanalyzer/12.0/install/application/reports/okta.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ Access Analyzer Okta application.
Analyzer server and port into the **Webserver.exe.config** file as:

```
<add key="WsFederationMetadata" value="INSERT URL HERE" />
<add key="WsFederationReply" value="INSERT URL HERE" />
Copy link
Contributor

@github-actions github-actions bot Feb 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<add key="WsFederationReply" value="INSERT URL HERE" />
<add key="WsFederationReply" value="INSERT URL HERE" />

```

**Step 4 –** Restart the Access Analyzer Web Server.
Copy link
Contributor

@github-actions github-actions bot Feb 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Step 4 –** Restart the Access Analyzer Web Server.
**Step 4 –** Restart the Access Analyzer Web Server.

Expand Down
6 changes: 3 additions & 3 deletions docs/auditor/10.8/api/activityrecordreference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ Records.
| Who | Yes | nvarchar 255 | A specific user who made the change (e.g., _Enterprise\ Administrator_, _Admin@enterprise.onmicrosoft.com_). |
| Action | Yes | — | Activity captured by Auditor (varies depending on the data source). |
| What | Yes | nvarchar max | A specific object that was changed (e.g., _NewPolicy_). |
| When | Yes | dateTime | The moment when the change occurred. When supports the following datetime formats. |
| Where | Yes | nvarchar 255 | A resource where the change was made (e.g., _Enterprise-SQL_, _FileStorage.enterprise.local_). The resource name can be a FQDN or NETBIOS server name, Active Directory domain or container, SQL Server instance, SharePoint farm, VMware host, etc. |
| ObjectType | Yes | nvarchar 255 | A type of affected object or its class (e.g., user, mailbox). |
| When | Yes | dateTime | The moment when the change occurred. This field supports the following datetime formats: `YYYY-MM-DDTHH:mm:ssZ` (UTC), `YYYY-MM-DDTHH:mm:ss+HH:mm` (positive UTC offset), and `YYYY-MM-DDTHH:mm:ss-HH:mm` (negative UTC offset). |
| Where | Yes | nvarchar 255 | A resource where the change was made (e.g., _Enterprise-SQL_, _FileStorage.enterprise.local_). The resource name can be a FQDN or NetBIOS server name, Active Directory domain or container, SQL Server instance, SharePoint farm, VMware host, etc. |
| ObjectType | Yes | nvarchar 255 | A type of affected object or its class (e.g., _user_, _mailbox_). |
| Monitoring Plan | No | nvarchar 255 | The Auditor object that is responsible for monitoring a given data source and item. Sub-elements: Name and ID. If you provide a monitoring plan name for input Activity Records, ensure the plan is created in Auditor, the Netwrix API data source is added to the plan, and enabled for monitoring. This ensures data is written to the database associated with this plan. |
Copy link
Contributor

@github-actions github-actions bot Feb 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| Monitoring Plan | No | nvarchar 255 | The Auditor object that is responsible for monitoring a given data source and item. Sub-elements: Name and ID. If you provide a monitoring plan name for input Activity Records, ensure the plan is created in Auditor, the Netwrix API data source is added to the plan, and enabled for monitoring. This ensures data is written to the database associated with this plan. |
| Monitoring Plan | No | nvarchar 255 | The Auditor object that is responsible for monitoring a given data source and item. Sub-elements: Name and ID. If you provide a monitoring plan name for input Activity Records, ensure the plan is created in Auditor, the Netwrix API data source is added to the plan, and is enabled for monitoring. This ensures data is written to the database associated with this plan. |

| DataSource | No | nvarchar max | IT infrastructure monitored with Auditor (e.g., _Active Directory_). For input Activity Records, the data source is automatically set to Netwrix API. |
| Item | No | nvarchar max | The exact object that is monitored (e.g., a domain name, SharePoint farm name) or integration name. Sub-element: Name. The item type is added inside the name value in brackets (e.g., _enterprise.local (Domain)_). For input Activity Records, the type is automatically set to Integration, you do not need to provide it. The output Activity Records may contain various item types depending on the monitoring plan configuration: <ul><li>AD container</li><li>NetApp</li><li>Computer</li><li>Office 365 tenant</li><li>Domain</li><li>Oracle Database instance</li><li>EMC Isilon</li><li>SharePoint farm</li><li>Dell VNX/VNXe</li><li>SQL Server instance</li><li>Integration</li><li>VMware ESX/ESXi/vCenter</li><li>IP range</li><li>Windows file share. If you provide an item name for input Activity Records, ensure this item is included in the monitoring plan within the Netwrix API data source. If you specify an item that does not exist, data will be written to the plan's database anyway but will not be available for search using the Item filter.</li></ul> |
Expand Down
Loading