Tag Archives: salesforce configuration

Salesforce Real Time Integration with Boomi: Prerequisite

If you are interested to set this up, check out the list below:

  • License. SOA framework is required. It’s included in Boomi Enterprise license and can be added as an add-on in Professional license.
  • Atom installation. The Boomi Atom is installed in a machine that has internet connection.
  • Windows security setup. If you are using Windows, make sure that the Atom executable is not blocked and the port is open. For example: 9090.
  • Network setup. Configure your router/firewall to redirect package to the server that hosts the Atom.
  • Configure the Shared Web Server Setting in AtomSphere to get your Atom ready for port 9090.
  • Has basic knowledge in Salesforce to setup the Outbound Message workflow.

Once you have built the process in Boomi, you are all set to go!

Salesforce Integration: Monitoring Outbound Message

If you are using the Outbound Message to trigger a real-time integration, you can monitor the status by navigating to Setup > Administration Setup > Monitoring > Outbound Messages.

If there is an error while sending the outbound message, Salesforce will automatically retry it for you. Alternatively, you can also retry it by clicking the Retry link.


Salesforce: Schedule Apex Job

In this blog, we will explain on another method to execute job at a specific time which is not achievable with a trigger.

With the assumption that an Apex Schedulable class has been created, the user can utilise the Schedule Apex feature to set up a time for the job execution. This feature is available via Force.com Home > App Setup > Develop > Apex Classes > Schedule Apex. From the interface:

  • provide the job name
  • select the schedulable class that has been created
  • set the configuration according to user preference

Once the scheduled job has been added, the user can continue to monitor the job execution status via Force.com Home > Administration Setup > Monitoring > Scheduled Jobs.

Salesforce : Person Account for Lead Conversion

By default, the Company field is mandatory in the Lead layout.

You can only make it a non-required field if you have Person Account activated. If Person Account is activated, the conversion behavior will work like this:

If Company field is populated, the conversion form will allow you to create a Business Account and a Contact.

If Company field is not populated, the conversion form will allow you to create a Person Account.

When a Person Account is created, it will also create a Contact record using the same information. Some of the Contact fields will also be available in the Person Account object. For example, the Contact Mailing Address and Contact Other Address.

Salesforce: Customized PDF Quote with e-Signature

Salesforce has an out of the box Quote feature which include allowing users to customize the Quote form template. However, there are some restriction when customizing the Quote form appearance.

More flexibility can be achieved using our custom-made Quote form instead. Following are some of the highlights of our custom-made Quote form:

  • Customizable layout appearance (related fields, images and etc. can be displayed in any position)
  • Signature can be signed on the form electronically via computer, smart phone, tablets, and etc.
  • Quote can be saved as PDF with or without the signature

Example of signing a signature electronically during the Quote creation:

The signature inserted is then included in the PDF sample of our customized Quote:


Salesforce: Junction Object as Parent Object

In Salesforce, a junction object cannot be the parent in a master-detail relationship.

Use case: A company that sells water heater will install their product for different owners in different locations. We will use the Account object to represent the Owner. Location object is like a city/state. One Account can have multiple Location and One Location can have multiple Owners. To achieve the many-to-many relationship, we create Account Location as the junction object. If you create another object called “Installation” and park this object as a child under Account Location using Master-Details relationship, Salesforce will not allow this. Below are the behavior you will encounter:

Behavior #1:
  1. Account object is already exist in Salesforce.
  2. Create a new custom object named Location.
  3. Create a new custom object named Account Location (this will be the junction object).
  4. Create 2 master-detail relationship on Account Location object link to Account and Location.
  5. Create a new custom object named Installation.
  6. Create a master-detail relationship on Installation link to Account Location. The Account Location object will not be listed as an option.
Behavior #2:
  1. Create a new custom object named Installation.
  2. Create a new custom object named Account Location.
  3. Create a master-detail relationship (Account Location) in Installation object.
  4. Account object is already exist in Salesforce.
  5. Create a new custom object named Location.
  6. Create 2 master-detail relationship on Account Location object link to Account and Location. When you trying to create the second master-detail relationship in Account Location, you will see the following:
To overcome this, you can use normal Lookup relationship between Account Location and Installation object.