Wednesday, February 25, 2015

SAP Cloud for Customer: February 2015 release update

SAP Cloud for Customer moves fast, each quarter a new release is made available with new functionality and updates to existing functionality. Two weeks ago all test tenants were upgraded to the newest release (1502) and last weekend all production tenants were upgraded. So excellent timing to take a more detailed look into some of the new features of SAP Cloud for Customer. 

Wednesday, February 18, 2015

Closing the gap between Sales and Marketing

Your Customers are no longer interested in endless sales pitches. They tend to investigate thoroughly online, before placing their order. This calls for a shift in the collaboration between sales and marketing. The two departments will have a greater overlap than ever before.

Wednesday, February 11, 2015

Two very useful XML namespaces in SAPUI5 XML views

If you are familiar with developing SAPUI5 / Fiori applications, you are probably also familiar with XML Views and the namespaces that are involved. Most of the namespaces refer to the different libraries that SAPUI5 has. When you want to want to use components form a specific library, you have to refer to that library using a namespace. In this weeks blog I will describe two other namespaces that can be useful while developing SAPUI5 applications. Both namespaces can be found in the SAPUI5 documentation, but are easily missed as well.

Wednesday, February 4, 2015

How (not) to use optimization rules in actions

Actions in SAP CRM are used to trigger processes based on events.

For example, when a lead is created in the system, you can implement an action on the event 'Lead created' to send an email to the person responsible for the customer the lead was created for.

Once the event is raised, the implemented schedule conditions will be evaluated. The system will check if the subject (in this case the lead) complies to the set of conditions. If this is the case, the action will be planned. If not, obviously nothing happens.

After scheduling the action (depending on the action setting 'process time'), the start conditions will be evaluated. This set of conditions determines if the action is allowed to be executed now, or if the system should wait for a different state (i.e. the object changing to another status, or, more likely, a certain moment in time).

Previous articles on actions can be found here.

Let's take a look at a more complicated requirement. Let's say we would like the following action to take place.

Send an email to the responsible employee 10 days before a lead's end date, but only if the lead has status open and is qualified as 'checked'.

This would require us to do the following:
- Create the [enddate - 10] date in the date profile.
- Create the action to send the email
- Create a schedule condition to determine whether the lead meets the requirements for sending the email at all (for instance qualification = 'checked' and status = 'open').
- Create a start condition to determine whether the action should be sent yet.