Day: October 11, 2017

In release 1708 the Recipient Determination to “Reporting Line Manager” in Opportunity is available: However for Account application, there are only six available determination rules available in standard. Suppose we need to support the following scenario: Max is Jerry’s manager. When Jerry has changed a given kind of Account in system, Max will get an email notification triggered by workflow. The general idea to fulfill this requirement is to introduce a logic which could automatically make Max as one member in Account Team table in Account TI by a small development in Cloud Application Studio, so that the existing functionality provided by Workflow framework could be leveraged to send notification. Here below is the solution. 1. Create a new custom Party Role Code and define it as Recipient determination in Workflow rule edit UI by following this blog Custom recipient determination in workflow rule done on Account BO. Of course you can also use standard role code. 2. Create a beforeSave script file on Root node of Customer Business Object: import ABSL; import AP.PC.IdentityManagement.Global; var managerExists = this.CurrentEmployeeResponsible.Where(x=>x.PartyRoleCode.Contains(“ZJE”)); if( managerExists.Count() http://bit.ly/2y99nGK #SAP #SAPCloud #AI

Every developer has the intent to write good quality code, but there are always unknowns which can result in errors. How developers handle errors depends on them.

MuleSoft provides various options for handling all different types of errors. Mule has various exception strategies available which can be configured while building your applications in Anypoint. https://goo.gl/EbW2e8 #DataIntegration #ML

We launched DB-Engines five years ago. This is a little summary of how it started and what we have achieved. https://goo.gl/2KAwBi #Cassandra #NoSQL

The UK government has unveiled plans for an internet safety strategy to protect the British public from ‘worrying or nasty’ content online https://goo.gl/dFn9v8 #Technology #IoT