ServiceNow FAQ
Yes. The v3 app supports unlimited BigPanda organizations from a single ServiceNow instance. Each organization requires its own configuration record, integration user, and credentials.
Credentials are stored as Password2 fields on the x_bip_panda_config table. They are encrypted at rest, never included in the config_json field, never logged, and never transmitted to the browser.
By default, changes to the incident status, assigned user, severity, tag values, and linked alerts trigger updates to ServiceNow. The set of fields that can be updated is controlled by the Update Fields setting on the Incidents module.
BigPanda sends an incident payload that includes the incident ID, status, severity, all linked alerts, incident tags, and metadata such as environment and sender. The Transform Rules Engine and ShareIncident transform map determine which fields are written to the ServiceNow incident record.
ServiceNow triggers sending change data. When a change request or change task transitions states, a business rule posts the change payload to BigPanda.
In CMDB v1 mode, the entire configured CMDB table set is sent on each scheduled sync. In CMDB v2 mode, only records that changed since the last sync are sent, based on hash-based change detection.
ServiceNow triggers sending maintenance plan data. Scheduled business rules post change-based and outage-based maintenance windows to BigPanda.