Conversation
"WsFederationMetadata" was listed twice instead of "WsFederationReply"
* Update 'When' field description with datetime formats Clarified the datetime formats supported for the 'When' field in the Activity Record reference. * Apply suggestion from @github-actions[bot] Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Apply suggestion from @github-actions[bot] Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --------- Co-authored-by: Konstantin Melnikov <konstantin.melnikov@netwrix.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Doc reviewer full scan
Opus is significantly more thorough at careful editorial work than Sonnet, which should reduce the number of preexisting issues missed in each review. Generated with AI Co-Authored-By: Claude Code <ai@netwrix.com>
Switch documentation reviewer to claude-opus-4-6
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Documentation Review Summary
Issues in PR changes
None.
Preexisting issues
okta.md
-
Line 9: "Create an Access Analyzer Application in Okta Using the WS-Fed Template" is formatted as plain text but functions as a section title. It should use
##heading markup for consistency with the## Setting Up Multi-Factor Authenticationheading on line 166. -
Line 25: "Retrieve the Values to Paste into the Access Analyzer WebServer.exe.config File" is formatted as plain text but functions as a section title. It should use
##heading markup. -
Line 31: "Right click" should be "Right-click" (hyphenated as a compound verb).
-
Line 36: "the General tab" — "General" should be bold (
**General**) to match the formatting pattern used elsewhere in the document (e.g., "the Sign On tab" on line 29). -
Line 41: "ReplytoURL" has inconsistent capitalization. Should be "ReplyToURL" to match the PascalCase convention used elsewhere (e.g., "ReplyToURL" on line 100).
-
Line 45: "Edit the WebServer.exe.config File" is formatted as plain text but functions as a section title. It should use
##heading markup. -
Line 82: "Webserver.exe.config" has inconsistent capitalization. Should be "WebServer.exe.config" to match other references in the document (e.g., lines 47, 49, 58, 60).
-
Line 90:
**Configure the App Settings for the StealthAUDIT Application**uses bold text instead of proper heading markup. It should use##heading markup. Also, "StealthAUDIT" is the old product name; the rest of the document uses "Access Analyzer". -
Line 92: "General Tab" — "Tab" should be lowercase "tab" for consistency with other references in the document.
-
Line 96: Missing space between "format:" and the backtick. Should be "format: `https://...`".
-
Line 100: "Webserver.exe.config" has inconsistent capitalization. Should be "WebServer.exe.config" to match other references in the document.
-
Line 121: Typo in image alt text: "Atrribute" should be "Attribute".
-
Line 141: "click on the Provisioning tab" — "on" is unnecessary. Should be "click the Provisioning tab".
-
Line 168: "multi-factor-authentication" — the second hyphen is incorrect. Should be "multi-factor authentication".
activityrecordreference.md
-
Line 24: "ensure the plan is created in Auditor, the Netwrix API data source is added to the plan, and enabled for monitoring" — missing "is" before "enabled". Should read "and is enabled for monitoring".
-
Line 28: "IsArchiveOnly allows saving Activity Record to the Long-Term Archive only" — missing article. Should be "saving an Activity Record".
There are two ways to apply fixes:
- View them in the comments and apply them individually or in a batch. This only applies to changes made to the file.
- Reply with
@claudehere, followed by your instructions (e.g.@claude fix all issuesor@claude fix only the spelling errorsor@claude fix all other existing issues). You can use this option to fix preexisting issues.
Note: Automated fixes are only available for branches in this repository, not forks.
|
|
||
| ``` | ||
| <add key="WsFederationMetadata" value="INSERT URL HERE" /> | ||
| <add key="WsFederationReply" value="INSERT URL HERE" /> |
There was a problem hiding this comment.
| <add key="WsFederationReply" value="INSERT URL HERE" /> | |
| <add key="WsFederationReply" value="INSERT URL HERE" /> |
| <add key="WsFederationReply" value="INSERT URL HERE" /> | ||
| ``` | ||
|
|
||
| **Step 4 –** Restart the Access Analyzer Web Server. |
There was a problem hiding this comment.
| **Step 4 –** Restart the Access Analyzer Web Server. | |
| **Step 4 –** Restart the Access Analyzer Web Server. |
| | 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. | |
There was a problem hiding this comment.
| | 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. | |
3 participants
No description provided.