Configuring ACP Settings

​

Introduction

​

Prerequisites

• Access to the ACP Manager Lightning App in Salesforce.
• Appropriate Salesforce permissions to modify ACP system settings (typically an administrator profile).

​

Accessing ACP Settings

1. Navigate to the ACP Manager App:
   • Open the App Launcher in Salesforce.
   • Search for “ACP Manager” and select it.
2. Go to the “Settings” Tab:
   • Within the ACP Manager app, click on the Settings tab. This tab displays the available ACP system settings.
   (Placeholder: Screenshot of the ACP Manager UI, Settings tab)

​

Common ACP Settings

• Logging Level:
  • Description: Controls the verbosity of logs generated by the ACP system, including the Activity Log and potentially Apex debug logs.
  • Common Options:
    • ERROR: Logs only critical errors.
    • WARN: Logs errors and warnings.
    • INFO: Logs errors, warnings, and informational messages (e.g., successful tool executions).
    • DEBUG: Logs detailed debugging information, including potentially sensitive data like request/response payloads. (Use with caution in production).
  • Impact: Higher verbosity helps in troubleshooting but consumes more storage and can slightly impact performance. Lower verbosity is generally recommended for stable production environments.
• Default Timeout for Tool Execution (milliseconds):
  • Description: Sets a default maximum time ACP will wait for an external tool to respond before considering the operation timed out. Individual tools or connections might override this.
  • Impact: Prevents indefinite waiting for unresponsive external services.
• Enable/Disable Specific Connectors Globally:
  • Description: Allows administrators to quickly enable or disable all tools associated with a particular connector type (e.g., temporarily disable all Slack tools).
  • Impact: Useful during maintenance of an external system or for phasing out a connector.
• Activity Log Retention Period (days):
  • Description: Defines how long Activity Log entries are kept before being archived or deleted.
  • Impact: Balances the need for historical data with storage considerations.
• Sensitive Data Masking in Logs:
  • Description: A boolean setting to enable or disable the masking of potentially sensitive fields (e.g., API keys, passwords, PII) in log entries.
  • Impact: Enhances security and compliance but might make debugging certain issues harder if critical data is masked.

​

Modifying Settings

1. Identify the Setting: Locate the setting you wish to change on the “Settings” tab.
2. Adjust the Value:
   • For dropdowns (like Logging Level), select the desired option.
   • For text fields (like Timeout), enter the new value.
   • For checkboxes (like Enable/Disable flags), check or uncheck as needed.
3. Save Changes:
   • Look for a “Save” or “Apply Changes” button. Click it to persist your modifications.
   • You should receive a confirmation message indicating that the settings have been updated.
   (Placeholder: Screenshot showing a setting being changed and a save button)

​

Considerations When Changing Settings

• Impact Assessment: Understand the potential impact of changing a setting before you modify it. For example, setting a very low timeout might cause frequent failures for tools that legitimately take longer to respond. Setting Logging Level to DEBUG in production can generate very large logs.
• Documentation: Refer to any internal ACP documentation or consult with your ACP development team if you are unsure about what a specific setting does.
• Testing: After changing a setting, especially a critical one like a logging level or a global connector disable, it’s good practice to test relevant ACP functionality to ensure it behaves as expected.
• User Communication: If a setting change significantly impacts end-users or other integrations (e.g., disabling a connector), communicate this change appropriately.