Description of problem:

When a locked webhook template is cloned using Hammer, the cloned template remains locked.
However, when the same locked webhook template is cloned via the Web UI, the cloned template is created in an unlocked state.

This results in inconsistent behavior between Hammer and the UI.

How reproducible:

Always

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

• Identify an existing locked webhook template.

• Clone the template using Hammer:

Actual behavior:

The cloned webhook template is created as locked when cloned via Hammer.

Expected behavior:
The cloned webhook template should be unlocked

Business Impact / Additional info:

• Requires manual unlocking of templates cloned via Hammer.

• Breaks parity between CLI and UI behavior.

• Impacts automation and scripted workflows.