Actions22
- Agent Actions
- Assignment Actions
- Attachment Actions
- Case Actions
- Pulse Actions
- User Actions
User → Mark as Active
AI-generatedSummary
Reactivates a Pega Launchpad user object by sending a PATCH to its MarkAsActive action, with optimistic concurrency via an If-Match ETag and an optional reason.
Inputs
- Authentication — Authentication method; only OAuth2 is available (uses the pegalaunchpadOAuth2Api credential).
- Base URL (required) — Base URL of the Pega Launchpad instance, without a trailing slash (a trailing slash is stripped anyway).
- Object ID (required) — ID of the user object to mark as active. It is inserted into the request path /dx/api/application/v2/objects/{objectId}/actions/MarkAsActive.
- If-Match (required) — ETag from a prior GET of the object (e.g. w/"2" or W/"3"). It is trimmed and a leading uppercase W/ is converted to lowercase w/ before being sent as the If-Match header.
- Reason — Free-text reason sent as content.ReasonForStatusUpdate. If left empty, an empty string is sent.
Output shape
One item per input item, containing the parsed JSON response body from Pega, plus a responseHeaders object with the HTTP response headers.
The body is an empty object if Pega returns none. Errors throw a node API error, or, if Continue On Fail is enabled, return an item with an error message. Base URL is read from the first item. The If-Match ETag must be current, otherwise Pega will likely reject the request. This is inferred from the header usage, not from the source.
Examples
Example 1: Reactivate a returning employee's user account after fetching its current ETag.
Base URL=https://acme.pegalaunchpad.com, Object ID={{$json.ID}}, If-Match={{$json.responseHeaders.etag}}, Reason="User account reactivated"