Using appRules® to Implement Round Robin Lead & Case Assignments in Salesforce

Assigning leads and cases to users using a formula that works for your company is a common requirement for most sales, marketing and customer service departments.

While most CRM and customer service solutions provide a rudimentary implementation of lead and case assignment, they do not offer support for the advanced schemes that most companies require.

appRules includes several workflow activities that can be used to implement a variety of advanced assignment schemes.  In this post, we will explore how you can implement round robin lead and case assignments in Salesforce without writing code.

Using the basic activities in appRules, the project below shows how you can implement a round robin lead assignment solution for Salesforce.

Initialization

The activities below are executed once to initialize the sources and targets used in the project.

# Activity Description
1 PreloadSalesforceUsers This activity is the InitializeSalesforceSource activity configured to load selected records from the User entity.
2 SalesforceLeadsSource This activity is the InitializeSalesforceSource activity configured to fetch selected records from the Lead entity one at a time.  These are the records to be assigned in a round robin fashion.
3 SalesforceLeadsTarget This activity is the InitializeSalesforceTarget activity configured for saving records in the Lead entity.

 

 

Record Iteration

The activities below are executed in a loop to assign the leads in a round robin fashion.  (Looping is implemented using the While activity with a simple App.Result condition.)

# Activity Description
1 AssignLead This activity is the UpdateSalesforceRecord activity configured to update the Lead OwnerId using the preloaded User.
2 GetNextUserFromList This activity is the GetNextPreloadedSalesforceRecord configured to get the next User record from PreloadSalesforceUsers.

Note: The EndOfListAction property is set to RestartList.  This is what implements the round robin scheme since it will continue cycling through the preloaded users.

3 GetNextLeadRecord This activity is the GetNextSalesforceRecord configured to get the next lead record.

 

By configuring only six out-of-the-box activities, we are able to compose a solution for implementing round robin lead assignment for Salesforce.  This solution can be run on premise or in the cloud.

You can download this project at: http://www.appstrategy.com/appRulesTrial

How to Implement a File Watcher Solution Using the appRules WatchFileSystem Activity

Many integration projects require monitoring of a directory on the file system for changes.  When a new file is added to a location or changes made to the location, the file system notification is utilized to process the file or to perform some other actions.

The system of watching a location on the file system is known as a “File Watcher System” or “File Drop System”.  appRules supports the quick implementation of a File Watcher Solution by utilizing the WatchFileSystem activity of the appConnector File System module.  You can specify the directory to monitor and when a file event occurs, you can directly launch a job or run a function to process the file or perform other actions.

Continue reading “How to Implement a File Watcher Solution Using the appRules WatchFileSystem Activity”

Business Rules 101: Configuring Actions and Conditions in appRules

In this Business Rules 101 post, we will cover Actions and Conditions – the building blocks of the appRules Business Rules Engine.

At an atomic level, the activities in appRules are based on Actions and Conditions.  A very simplistic description of appRules Actions and Conditions is shown below:

Action         – What to do

Condition    – When to perform the action

 

Actions, Conditions and composite activities based on them are accessible through the appRules Core Business Rules module:

We will take a look at the first two activities in the business rules module (Action and Condition).  The other activities will be considered in future posts since they are beyond the scope of this introductory post.

 

Action

To add an Action to your business rules project, drag and drop the Action activity on to the designer.  The Configure Action window will be displayed:

appRules includes thousands of Actions right out of the box.  Only the actions that you have licensed will show up in the Action Tree.

The Actions are organized in Action Categories.  The following are the available categories:

  • DataSource
  • Primitives
  • Data Quality
  • Execution

 

To configure an Action, expand the category on the action tree and drill down to select the action.

For example, to associate entities in Microsoft Dynamics CRM, expand the CRM group under the DataSource category.  Select DynamicsCRM, and then double-click on AssociateEntities as show below:

The following window will be displayed:

Set the properties and click the OK button.

Condition

To add a Condition to your business rules project, drag and drop the Condition activity on to the designer.  The Configure Condition window will be displayed:

appRules includes thousands of Conditions right out of the box.  Only the conditions that you have licensed will show up in the Condition Tree.

The Conditions are organized in Condition Categories.  The following are the available categories:

  • DataSource
  • Primitives
  • Data Quality
  • Execution

 

To configure a Condition, expand the category on the condition tree and drill down to select the condition.

For example, to verify if a date is the first day of a fiscal year quarter, expand the DateTime group under the Primitives category as show below:

Double click on IsDateFirstDayOfFiscalYearQuarter.  The following window will be displayed:

Set the properties and click the OK button.  Execution of a Condition activity returns a value (True or False) that you can evaluate in other activities such as the If, While, DoWhile, etc. activities.

 

 

Conclusion

The appRules Business Rules Engine is based on appRules Actions and Conditions.  With thousands of out-of-the-box, no-code activities, appRules makes it easy to compose powerful business rules projects without writing code.

Whether you are building a complex decision table, evaluating conditions for scoring and rating purposes, or adding rules to data quality projects, appRules actions and conditions make it easy to accomplish your task.

You can download appRules with sample business rules projects at: http://www.appstrategy.com/appRulesTrial

Data Integration 101: Anatomy of a Simple ETL Project Using appRules

In this Data Integration 101 post, we will do a quick tour of a simple ETL project using appRules.

The project which is shown below is used to perform bulk export of data from a SQL database to a CSV file.  No code was used to accomplish the task and it utilizes only three main activities.

The main activities are described below:

# Activity Description
1 InitializeSqlServerCeSource This activity is the initialization for the SQL Source.  You can select an activity from any SQL module – SQL Server, Oracle etc.  Configure the properties of this activity from any SQL module to select the records to export.
2 InitializeDelimitedTargetFile Configure this activity from the Delimited File module to define the Target CSV file and its attributes.
3 MapAndSaveRecords Use this activity to map data fields from the Source to the Target.  The activity also saves the records.

 

Conclusion

This example showcases the no-code ETL capabilities of appRules.  The same process can be used to export data from Accounting, CRM, ERP and other modules – without writing code.

 

You can download appRules with sample data integration projects at: http://www.appstrategy.com/appRulesTrial