=== ServicePress Connector Core ===
Contributors: harmediastudios
Tags: servicenow, multisite, enterprise, automation, security, observability
Requires at least: 6.0
Tested up to: 6.9.4
Requires PHP: 8.0
Stable tag: 2.0.1
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Text Domain: servicepress

Enterprise operational integration platform connecting WordPress and ServiceNow environments.

== Description ==

ServicePress Connector Core transforms WordPress into an enterprise operational integration edge for ServiceNow.

Built for enterprise WordPress environments, ServicePress provides centralized operational visibility, inventory synchronization, event-driven workflows, multisite governance, and controlled integration patterns between WordPress and ServiceNow.

ServicePress supports:

* Single WordPress installations
* WordPress Multisite networks
* Large distributed WordPress environments
* Enterprise operational workflows
* Security and vulnerability visibility
* Controlled transport and synchronization pipelines

Unlike earlier inventory-only integrations, ServicePress 2.0 introduces:

* Controlled outbound transport architecture
* Queue-based synchronization workflows
* Enterprise multisite governance
* Scoped payload management
* Privacy and data filtering controls
* Role-aware administrative operations
* Diagnostic and operational tooling
* Optional legacy pull API compatibility

== Enterprise Features ==

* WordPress multisite inventory synchronization
* Controlled ServiceNow integration workflows
* Queue-based payload processing
* Configurable transports and systems
* Payload inspection and previewing
* Event simulation and operational testing
* Privacy and data scope controls
* Multisite diagnostics and operational governance
* Optional `/spnow/v1` compatibility layer for legacy pull integrations
* Application Passwords disabled by default
* Capability-protected administrative workflows

== ServiceNow Integration ==

ServicePress integrates with certified ServiceNow applications and workflows to provide:

* WordPress operational visibility
* Site inventory synchronization
* Plugin and theme visibility
* Event-driven operational workflows
* Vulnerability intelligence integrations
* Enterprise observability pipelines

Additional ServicePress integrations may include:

* Wordfence
* WooCommerce
* LearnPress
* Enterprise publishing workflows
* Operational control extensions

== Security Model ==

ServicePress 2.0 introduces a significantly hardened architecture compared to earlier releases.

Security improvements include:

* Capability-protected REST routes
* Controlled multisite context switching
* Optional legacy compatibility APIs
* Application Passwords disabled by default
* Request sanitization helpers
* Scoped payload controls
* Privacy-aware synchronization settings
* Queue isolation and controlled transport workflows

Legacy compatibility APIs are disabled unless explicitly enabled for migration or integration compatibility purposes.

== Legacy Pull API Compatibility ==

ServicePress 2.0 optionally supports legacy `/spnow/v1` pull endpoints for backward compatibility with existing ServiceNow integrations.

Supported compatibility routes include:

* `/spnow/v1/sites`
* `/spnow/v1/networks`
* `/spnow/v1/network_info`
* `/spnow/v1/site_settings`

These routes are:

* Capability protected
* Multisite aware
* Governed through the new 2.0 architecture
* Intended for migration and compatibility workflows



== Enterprise Multisite Safety ==

ServicePress 2.0 was designed specifically for enterprise and large multisite WordPress environments.

The platform introduces controlled multisite context handling, scoped synchronization workflows, capability-protected administrative operations, and optional compatibility APIs designed to minimize operational risk in large distributed WordPress networks.

ServicePress does not perform uncontrolled recursive synchronization or unmanaged background crawling across multisite environments.

== Screenshots ==

1. ServicePress Dashboard
2. Transport Management
3. Queue and Retry Monitoring
4. Multisite Diagnostics
5. Payload Preview
6. Privacy and Data Scope Controls


== Installation ==

= WordPress =

1. Upload the plugin to `/wp-content/plugins/`
2. Activate the plugin network-wide for multisite environments
3. Configure systems, credentials, transports, and synchronization settings
4. Configure optional ServiceNow compatibility workflows if required

= ServiceNow =

1. Install the associated ServicePress ServiceNow application
2. Configure import or event transport endpoints
3. Configure credentials and synchronization workflows
4. Validate payload connectivity and operational synchronization

== Frequently Asked Questions ==

= Does ServicePress support WordPress Multisite? =

Yes. ServicePress was designed specifically for enterprise multisite operational visibility and synchronization workflows.

= Does ServicePress expose REST APIs? =

ServicePress 2.0 primarily uses controlled outbound transport workflows. Optional compatibility pull APIs may be enabled for migration or legacy ServiceNow integration support.

= Are Application Passwords required? =

No. Application Passwords are disabled by default and are not required for standard outbound integration workflows.

== Upgrade Notice ==

= 2.0.0 =

Major architectural release introducing:

* Enterprise governance controls
* Queue-based transport workflows
* Controlled synchronization architecture
* Privacy-aware payload management
* Optional legacy compatibility APIs
* Hardened multisite operational handling

== Changelog ==

= 2.0.1 =
- Maintenance release.
- Preserves ServicePress 2.0 architecture and compatibility updates.



= 2.0.0 =

* New - Enterprise operational integration architecture
* New - Queue-based synchronization workflows
* New - Configurable transport and system management
* New - Payload inspection and preview tooling
* New - Event simulation framework
* New - Privacy and data scope controls
* New - Multisite diagnostics framework
* New - Optional legacy `/spnow/v1` compatibility APIs
* New - Capability-protected REST route architecture
* Updated - Hardened multisite context handling
* Updated - Application Passwords disabled by default
* Updated - Improved enterprise governance and operational controls

= 1.4 =

* Updated - Legacy inventory synchronization improvements
* Updated - ServiceNow compatibility updates

== Legal Disclosure ==

ServicePress facilitates operational integration workflows between WordPress and ServiceNow environments.

Each organization is responsible for:

* The configuration of synchronization workflows
* Data governance and transport policies
* ServiceNow operational workflows
* WordPress administrative governance
* Compliance and operational review processes

ServicePress does not store or control customer operational data outside configured synchronization workflows.

== External Links ==

ServicePress Website:
https://servicepress.app

ServiceNow Store:
https://store.servicenow.com/

Harmedia Studios:
https://harmediastudios.com

