Hi All,
We are testing flow creation using the ServiceNow SDK through Claude Code and have noticed different behavior between the Global scope and a custom application scope.
Observed behavior:
- When attempting to create a Flow in the Global scope, the flow either:
- does not get created successfully, or
- gets created but contains no actions/steps.
- When performing the same operation in a new custom application scope, the Flow is created successfully, and some actions are added as expected.
We are trying to understand whether there are any known limitations, restrictions, or scope-specific considerations when creating Flow Designer artifacts through the SDK.
Questions:
- Are Flow creation and Flow action definitions fully supported in the Global scope when using the ServiceNow SDK?
- Are there any additional permissions, roles, or configurations required for Global scope?
- Has anyone experienced flows being created without actions when targeting Global scope?
- Is Flow creation through the SDK currently intended to be used only within custom application scopes?
Any insights or documentation references would be greatly appreciated.
Thank you!
