New tickets are not logged in ServiceNow integration
Problem: New tickets are not logged in ServiceNow integration, even when new alerts are being created for the reported
monitor (Issue persists in Applications Manager builds lower than 14670)
Solution:
Ensure that Log a Ticket action is configured for Critical, Warning and Clear severity.
If there is no Action associated for Clear severity, Applications Manager will still maintain the initial ticket and update it, as it does not know whether the initial ticket was cleared or not.
New to ADSelfService Plus?
Related Articles
Service Now Event Integration using Webhook / Rest API Action
Steps to perform in Service Now 1) Login to your ServiceNow Instance(dev*****133.service-now.com) 2) Search for the Rest API Explorer and open it 3) In the Rest API Explorer page choose the Namespace and API Name with the proper API version. For ...Troubleshooting ServiceNow Add-On Integration Error
Problem: The following error pops up while trying to add a ServiceNow instance: Solution: Ensure that the ServiceNow instance is accessible from the AppManager server and the user account has itil, itil_admin and personalize_choices roles assigned.Configuring Zoho as an OAuth Provider in Applications Manager
Zoho's OAuth token is used to access services in Applications Manager like integration with Site24X7, integration with Service desk, access to Zoho Mail APIs etc. As it seems a daunting task to go through all the documentation of the product, here ...Pre-requisites for PAM Integration
1. Enable PAM Integration in APM: Insert the below global config keys as 'true' 1. 'am.password.manager.ui' (PAM360,PMP,CyberArk) 2. 'am.password.manager.pmp' (PMP) 3. ' am.password.manager.cyberark.ui' (CyberArk) 2. Get authentication key from PAM ...Add new Managed server with existing server ID
To add a new managed server with an existing server ID, follow these steps: 1. Install the App Manager Professional Edition (Ensure it's the same as the Admin version). Refer this link for more details. 2. Update the 'am.server.startresidrange' as ...