Edit an IBM Cloud Function action

Introduction

Edit actions

Edit the caseworker action

1. From Functions > Actions > curam-rest package, select the caseworker action.

2. From the left navigation section, select Code.

3. Copy the content of the caseworker.js and paste it into the code section.

4. Click Save.

5. From the left navigation section, select Endpoints, select Enable as Web Action and click Save.

6. Copy the URL under Web Actions.

7. Go back to the Code section, and update the value for the cfEndpoint const to paste the value of the URL.

8. Remove the caseworker.json at the end. For example:

   https://eu-gb.functions.appdomain.cloud/api/v1/web/<name>ie.ibm.com_org_dev/curam-rest/
   Copy to clipboard

9. Click Save.

Edit the person and verifications actions

1. From Functions > Actions > curam-rest package, select the person action.

2. From the left navigation section, select Code.

3. Copy the content of the person.js and paste it into the code section.

4. Update the value for the env const to point to your environment. For example:

   https://<server-name>
   Copy to clipboard

5. Click Save.

6. From the left navigation section, select Endpoints, select Enable as Web Action and click Save.

7. To edit the verifications action by using the content from the verifications.js, repeat the steps.

Customizing an action

• The caseworker action is the entry point into the actions, and is what gets invoked from Watson Assistant. It determines which other underlying actions to call. If you add a new lower level action, you will need to update the caseworker action to call your new action and pass along any required parameters.
• If you create a new action which calls to a REST API in SPM, you will need to ensure you add the authorization and referer headers to the API request. Details of how to retrieve the value for the authorization header from the webhook and pass along through the actions and to the REST API may be copied from the sample code. The referer header should be set to a value of curam://<name>.
• The sample code does not send an accept-language header when calling the REST API in SPM, and so the default fallback of en will be used by the API. If you require the REST API to return attributes that contain localizable text in another language or locale, you can update the sample code to add an accept-langauge header to the API request.