Enable a client script to trigger a flow, subflow, or action.
始める前に
- Role required: security_admin
- Consider the implications of making a flow, subflow, or action client callable,
such as whether it exposes protected data or bypasses validation logic.
このタスクについて
By default, the flows, subflows, and actions can only be called by the FlowAPI within a server script. Flow and action designers can make individual flows, subflows, or actions available to
client calls by enabling the Client callable option during the design process.
手順
-
Elevate privileges to security_admin.
-
Navigate to .
-
Click New.
-
Create an access control.
| Field |
Description |
| Type |
client_callable_flow_object |
| Operation |
execute |
| Admin overrides |
Selected |
| Name |
Enter a name for the ACL. |
| Requires role |
Create a role to provide access to the APIs. For example,
create a flow_api_access role. |
-
Assign the role to the user you would like to grant access to.
-
Enable a client script to trigger the flow, subflow, or action.
-
Open the flow, subflow, or action you want to make client
callable.
-
In the More Actions menu, select
Manage security.
-
Select Callable by Client API.
-
Add the access control record created earlier to the
ACLs field.
-
Click Update.
タスクの結果
The user with the designated permissions can trigger a
client callable flow, subflow, or action from a client script using the GlideFlow API.