A client needs a custom quicklink, which only managers can launch, in order to launch a simple workflow. Is this a valid step to take during the…

This is a valid and necessary step. In SailPoint IdentityIQ, a QuickLink object is used to create custom links in the user interface. To make a quicklink launch a business process (workflow), its action attribute must be set to workflow. Subsequently, the workflow attribute of the QuickLink object must be populated with the exact name of the workflow to be initiated. This configuration directly tells IdentityIQ which business process to execute when the user clicks the link. While controlling visibility for managers requires a separate configuration step (e.g., using AllowedRights), specifying the workflow name is a fundamental part of the solution.

B. No: This is incorrect. Failing to enter the workflow name in the quicklink object would result in the quicklink not knowing which workflow to launch, thereby failing to meet the core requirement.

1. SailPoint IdentityIQ 8.1 Object Model: In the documentation for the sailpoint.object.QuickLink class, the workflow attribute is explicitly defined as: "The name of the workflow to launch when the action is 'workflow'." This confirms that specifying the workflow name is the correct procedure.

2. SailPoint IdentityIQ 8.3 Administration Guide: The "User Interface Configuration" chapter details the creation of custom quicklinks. It provides examples showing the action="workflow" and workflow="WorkflowName" attributes being used together to launch a business process from the UI, validating this as a standard implementation step. (Refer to sections on QuickLink configuration).