Configure Service Actions and Plugins
Service actions can be referred to as internal service tasks in CA Identity Portal. They are configured almost the same way as module actions but they are not visible to end users. Instead they are referred to from scripts within other forms and are mainly used to retrieve data using service tasks on the connectors. For example: on the CA IM connected system build a service task that calculates and returns information then link it to a service action and call it from a script on one of the forms.
cis141
Service Actions
Service actions can be referred to as internal service tasks in CA Identity Portal. They are configured almost the same way as module actions but they are not visible to end users. Instead they are referred to from scripts within other forms and are mainly used to retrieve data using service tasks on the connectors. For example: on the CA IM connected system build a service task that calculates and returns information then link it to a service action and call it from a script on one of the forms.
Before configuring a service action, the task and form need to be configured so they can be linked to the service action.
Follow these steps:
- Navigate to the Admin UI.
- ClickElements,Service Actions,Create.
- Specify a title.The Tag value is populated automatically.
- Select the managed object type for the taskValues:User, Group
- Click theFormtab.
- Select the form that is linked to the service task.
- ClickCreate.The service action is created.
Plugins
Plugins are either Java or RhinoJS (server-side JavaScript) code executed on the CA Identity Portal server that can be used to enrich the business logic configured in CA Identity Portal.
Examples of using plugins:
- Fetching available form prop values from external database.
- Validating a file's content.
- Performing complex validation logic.
Refer to CA Identity Portal Developer Guide for more information about using Plugins.