New Action: WS1 EnableLostMode #249
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
✅ Valid PR for ActionPack Thank you for your contribution. This PR complies with the CONTRIBUTING.md. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details
Action Name: ws1EnableLostMode
Purpose: Enable Lost Mode on a Workspace ONE–managed device using its UUID, providing a simplified alternative to the default WS1UEMLostMode action.
🔑 Inputs
deviceUUID — Unique identifier of the device in Workspace ONE UEM
Authentication handled through a Connection & Credential Alias (OAuth provider using client_id and client_secret)
📨 Request Body
{
"footnote": "Device UUID : ",
"message": "Device set to Lost mode. Please call Service Desk for further queries.",
"phone_number": "+1-888--*"
}
📤 Outputs
httpStatusCode — HTTP response code indicating whether Lost Mode was successfully enabled.