Add New Attributes to Business Objects to Customize Action Workflow Conditions
- by Conny Dahlgren, Senior Consultant, SAP Australia
- November 15, 2006
Understand how to add an attribute, such as a user-defined field, to an action workflow condition to customize how your system carries out an action.
Attributes are characteristics of business objects. Different business objects have different default attributes. You use attributes to define action workflow conditions, which control how the system executes an action, a planned activity or task that you assign to a business process. A person, group of people, or a system in the background can carry out an action.
It’s a month before one of your customer’s contracts expires. mySAP CRM sends you an activity with the category “telephone” to remind you to call the customer to ask if it would like to renew its contract. This is an example of an action.
You probably know that you can configure mySAP CRM to check certain action workflow conditions (manually or automatically) before it triggers an action. For example, you can set the system to ensure that a contract does not have any errors before it generates a credit memo. However, what if the attribute you want to include in your action workflow condition does not exist for it?
Here’s an easy way to extend the attributes that enable these action workflow conditions. I’ll describe how to add attributes to action workflow conditions by using the item category field, which does not exist as an attribute available for action conditions. This process works with any attribute that you create via Easy Enhancement Workbench. I’ve tested this process with mySAP CRM 2005. For more information about the overall concept of actions and how to use action workflow conditions, refer to the March 2006 CRM Expert article, “Send Alerts and Customer Confirmations Using Actions,” by Karen Lindholm.
Would you like to see this full item?