Set Up/Change Customer Web Self-Service Password

The following is an example of the steps necessary to implement a script that transfers a user to the page on which they can set up / change a customer's web self-service password.

Step No.	Step Type	Text Displayed In Script Area	Additional Information On The Step
10	Perform script	Press OK after the dashboard contains the person in question	Subscript: CI_FINDCUST Note, this step performs a script that contains the steps that ask the user to find the customer on control central.
20	Move data		Source Field Type: Predefined Value Source Field Value: %CONTEXT-PERSONID (note, this is a global variable that contains the ID of the current person) Destination Field Type: Page Data Model Destination Field Name: PER_ID
30	Navigate to a page		Navigation Option: Person - Web Self Service (update)
40	Set focus to a field	Press continue after changing the customer's self service values and saving the changes	Destination Field Name: WEB_PASSWD
50	Perform script		Subscript: CI_SAVECHECK Note, this step checks if the user remembered to save their changes
60	Display text	Script complete

Note the following about this script:

Step 10 invokes a "subscript" that asks the user to let the script know when the dashboard contains the person in question.
Step 20 and 30 are examples of steps step that navigate a user to a specific tab on the person transaction for the person currently displayed. This works because the system automatically passes the person ID from the current page to the destination page.
Step 40 is an example of a step that moves the insertion point into a field on a page. It also asks the user to save the person. While it's possible to introduce a step that pushes the save button for the user, we recommend that you ask the user to do this. Why? Because validation logic occurs whenever you save an object and this could result in a pop-up if errors or warnings are issued. We feel that it's better for the user to understand why this window is popping up (because they pushed the save button) rather than have the pop-up appear out of thin air.
Step 50 invokes a "subscript" that reminds the user to save their changes (in case they didn't do this).
Step 60 is simply good practice. It lets the user know that the script is complete.