ServiceNow Integration

Whenever a blueprint is updated, the integration (servicenow) needs to be unattached, thus wiping any servicenow processes’ and would need to be rebuilt for the/updated new blueprint. When the integration is attached, the catalog is auto created at v1.0.0. Is there a way a new version could be pushed when blueprint is updated instead of just deploying a new catalog each time.

Workaround
-
Problem
-

Please authenticate to join the conversation.

Upvoters
Status

👀 In Review

Board

💡 Feature Requests

Date

About 5 hours ago

Subscribe to post

Get notified by email when there are changes.