In this section, we will review the actions implemented in the customer model. Three custom actions (Add customer, Make active, Make inactive) have been implemented in the actions perspective. In addition to these custom actions, the default action to delete an instance has been included as a button in the customer form.

What are the actions in customer model?

• "AddCustomer" to create a new customer - Custom action
• "MakeActive" to set the customer as active - Custom action
• "MakeInactive" to set the customer as inactive - Custom action
  
• "DeleteCustomer" to delete an existing customer - Default action

Add Customer       Click on the actions tab to open the actions perspective. Open the "AddCustomer" action. The page as shown in the screen capture will be displayed. This action must perform the following set the customer status as active. create a new user instance to enable customer login. submit to proceed to the next workflow activity.

Set the new customer as active       An "Update" command has been used to update the customer model parameters "CustomerStatus". Param: CustomerStatus Value: ="Active"     "Update" command is used to update current model parameters (public cells) What parameters must be configured for "Update" command? Fields to update

Create an instance in the UserChanges model for the new customer        A "New" command has been used to create an instance in the UserChanges model for the newly added customer.       Fields to be updated in the new instance: UserId FirstName LastName Designation Company PhoneResidence     "New" command creates a new instance in the specified model. What parameters must be configured for "New" command? Model Name Fields to update

Create a user for the new customer        A "CallParentAction" command has been used to call an action in the UserChanges parent model. The parent action to be invoked: Save     Call parent action command is used to call a parent model action. The parent model action will be executed. What parameters must be configured for "CallParentAction" command? Parent Model Parent Action Name Context Cell Name

Move the customer instance to the "CustomerList" workflow activity       A "Submit" command has been used to submit the customer instance from the "Draft" workflow activity.       The submit command moves the instance to the next workflow activity "CustomerList".       Click here to refer workflow process for customer     "Submit" command is used to submit the instance from the current workflow activity to the next workflow activity. What parameters must be configured for "Submit" command? Submit from activity

Make Inactive       An "Update" command has been used to update the value of the customer model parameter "CustomerStatus" to "Inactive".

Commit the changes made by the user       A "Submit" command has been used to submit the customer instance from "CustomerList" activity. Since the next activity in the process is a goto "CustomerList" activity, the instance will be available in the "CustomerList" activity queue.       The only requirement is to commit the changes made by the user. The instances are already in the desired "CustomerList" activity, so there is no need to move the instance to the next workflow activity. Instead of using a submit command, the default dummy update action could also be used to commit the changes made by the user.       Click here to refer workflow process for customer

Make Active       An "Update" command has been used to update the value of customer model parameters "CustomerStatus" to "Active".

Commit the changes made by the user       A "Submit" command has been used to submit the customer instance from "CustomerList" activity. Since the next activity in the process is a goto "CustomerList" activity, the instance will be available in the "CustomerList" activity queue.       The only requirement is to commit the changes made by the user. The instances are already in the desired "CustomerList" activity, so there is no need to move the instance to the next workflow activity. Instead of using a submit command, the default dummy update action could also be used to commit the changes made by the user.       Click here to refer workflow process for customer     What's the next step? Explore action design perspective.