Business Rules Example #263 – Dynamic Generation of UpdateRecord Attributes

A new knowledge base article has been published on our support portal.

Overview

In this scenario we have business rules which update 3 fields on an entity, however a specific field should only be updated when certain conditions are met. We want to simplify the decision logic and execute a single update, only changing the relevant fields. In essence we want to dynamically build the SetAttributes of an UpdateRecord function depending on conditions.

In this example we will have 3 custom option sets that, when set to true, will cause an update to their corresponding fields.  

We will use one UpdateRecord at the end of the Decision Table to encompass all outcomes .

Note: We have created three custom boolean option sets –  Set Credit Limit, Set No. of Employees & Set Annual Revenue and have added them to the Account form

North52 BPA Solution

The North52 BPA solution works like this:

• A Formula is set up on the Account entity that fires upon change of any of the three custom fields Set Credit Limit , Set No. of Employees & Set Annual Revenue 
  • This formula will check each field and change its corresponding field accordingly
    • For example if Set Credit Limit is set to True, the field Credit Limit will be set to 1000
       

View this article in full on our support portal