The SmartIQ API Action extends the standard Send to REST Service Action by automatically adding a SmartIQ authentication token for the current user running the action in Produce, or for a specified user to impersonate where configured. This allows authenticated requests to be made to the SmartIQ API.
Similar to the Send to REST Service Action, this action takes a URL describing the REST endpoint, and will send a supplied Action Document (JSON or XML) to the endpoint as the request body.
|Impersonation||The Action also supports the "As-User" impersonation, which allows the REST request to be handled as if the given user was the one making the request. In this case, the user running the action must have the "Impersonate" permission (which can be assigned to a Role in Manage). The impersonated user must have access to the resource(s) being accessed by the REST call as after audit logging the API call proceeds as if the impersonated user was the one making the call.To use the "As-User" impersonation, the "As-User (Impersonate)" input should be set to either the username or user GUID (whichever is available/convenient) of the user to be impersonated.|
|HTTP Method||The HTTP method to use for the request. Supported values are "|
|Output Path||A parameter that defines a path in the REST response that will be output as the Output Path Data parameter|
|Request Body||JSON request to be included in REST request. it can have a question reference (specially relevant to be used with formula |
If action also includes a Document, it will be ignored and Action Input.
When implemented, Action ignores Send as Multipart.
|Request Schema||Prevents unintentional JSON elements being included in a REST request due to injection from user input or specific parameters in the request. if Request Body action input is implemented, "Request Schema" needs to be supplied, validating the Body against the JSON Schema provided in this Action Input prior to sending the request.|
|URL (Mandatory)||The endpoint of the service.|
The SmartIQ User action creates and maintains user accounts.
While the entire user account can be configured, the only required fields are Preferred Username and Update Existing User.
|Custom Fields||One per line. Specify any custom fields against the user. These are in the form of "name=value".|
|Disabled (True|False)||If this is true, the user’s account has been disabled in Manage.|
|Display Info Messages in Manage (True|False)||If this is true, verbose messages describing what the action is doing will be written to the Management log. This may be useful during testing.|
|First Name/Last Name/Email/Address Details/Job Title/Organisation/Phone Number||Match up to the fields for a User.|
|Groups to Add||One per line. The user will be assigned to the groups specified.|
|Groups to Remove||One per line. The user will be removed from the groups specified, prior to being added to any groups.|
Note: A non-administrator user cannot add/remove other users (or themselves) from admin groups.
|Password||You may define a new password for the user.|
|Preferred Username (Mandatory)||Defines the username.|
|Reset Password (True/False)||If True, a new password will be generated for the user. This flag will be ignored if the Password input is defined.|
|Reset Password on Next Login||Defines whether or not the user should reset their password the next time they log in.|
|Theme||Defines the skin file name.|
|Update Existing User (True|False) (Mandatory)||If a username is found matching the username passed in, then this flag defines whether or not that user will be updated with the new details. If the flag is True, the user is updated. If the flag is False and a user is found, the Action Fails.|
|Existing User Updated||Returns True if the user was already in the system and False for a new user.|
|Password||If a new password was assigned to the user, it will be returned here.|
|User Guid/ User ID/Username||Returned if matched.|
To dynamically create a user and assign multiple groups via the SmartIQ user action, add a replace formula that breaks the string and separates the selected group on each line via an ASCII code.
This is because the group names are coming from multiple row data source so it will be one string with a pipe delimiter that separates each value. For example, with
GroupA|GroupB|GroupC, the action will be looking for the
GroupA|GroupB|GroupC group name which does not exist as the groups need to be 1 per line, and so this will not work.
=Replace([q37.GroupName], “|”, chr(10))
Then reference the formula to the Groups attribute.
This will bring the string into the Groups attribute as 1 per line.
Updated 5 days ago