cloudanswers

CloudAnswers

for-developers

For Developers


## **What is a Hackathon?**

A hackathon is an event usually put together by a tech organization. The event brings programmers together over a specific period to collaborate on a project. It is typically a competition that brings out the creative prowess of the individuals involved. To learn more about hackathons, check out our blog post on [how and why we run hackathons](/blog/how-and-why-we-run-hackathons/). In this post we’ll highlight Paul Fox’s entry from the February hackathon focused specifically on the Salesforce Spring ‘21 release. 

## **Batch Apex Error Handling**

In Spring ‘21 Salesforce added the BatchApexErrorEvent to ISV applications (apps for the AppExchange). Since CloudAnswers has a handful of apps on the AppExchange, and is constantly building apps, Paul decided to build a library that would make this easier for us to use on all of our projects. 

## **What is Batch Apex?**

If the last paragraph was completely confusing, here’s a quick summary of how batch apex works and how batch apex error handling is accomplished with and without this functionality. If you’re a seasoned Apex developer, you can skip this section.

Hopefully you’re familiar with Apex, which is the language Salesforce uses for server-side code. Batch Apex is code that runs asynchronously and facilitates processing large volumes of records. For example, if you wanted to automatically merge all the duplicate contacts on a weekly basis you might write a batch class that queries all the duplicate record sets and merges them. If you tried to do this without batch apex you may hit a lot of Salesforce errors due to the amount of queries and other database changes that happen when you merge each group. With batch apex you can split it up into batches (one group of duplicates, for example) and use batch apex to process all of the batches and reduce the chance of hitting any limits.

## **The General Syntax of Batch Apex**

**Start Method**\- the start method defines what records to process and often initializes some data that is needed during execution. 

**Execute Method**\- This is typically where most of the logic resides, and this code determines what happens with each batch of records. It’s important to catch any errors here and then process them in the finalize method for most error handling. 

**Finish Method** – this is mostly the post-processing details. Usually this is where we put our error handling, creating records or sending an email whenever something happens.

## **Error Handling in Batches**

The best practice when writing batch apex is to try and anticipate any errors that could happen and catch them within the execute or finish methods and handle them appropriately. However, there are two main problems with that:

1. Not all errors can be caught
2. No developer is perfect and can anticipate every error, especially since new problems can be added with any release or package installation.

So, what’s a developer to do? Well, check out BatchApexErrorEvent. 

## **Features of Batch Apex Error Event**

- It is a platform event that contains details about asynchronous processes that failed (batch and scheduled jobs).
- It is automatically created if an asynchronous process fails, **as long as that class implements Database.RaisesPlatformEvents.** 

## **Building a Batch Error Framework**

Since platform events allow triggers and other workflows, that means we can automatically have logic fire when these platform events are created. Looking at how a lot of people do error handling already, Paul came up with the following features that most people would want when doing batch error handling.

- Email batch errors to the admin or support team for evaluation and processing.
- Stores batch errors in a custom object, including the class that failed, full stack trace, and the records that were in the Batch.

And all that with just a few set up steps. 

## **Setup Instructions**

- Deploy the contents of the [batch apex error handling repo](https://github.com/cloudanswers/batch-apex-error-handling) into your org.
- In the batch class of interest, implement Database.RaisesPlatformEvents. This causes the BatchApexErrorEvent to fire when something fails.  

```
public with sharing class YourSampleBatchJob implements

Database.Batchable<SObject>, 
Database.RaisesPlatformEvents { 
  // class implementation 
} 
```

- Set up at least one org-wide email address; you'll need to use this from the address on the emails.
- Go to Setup > Custom Settings and create a new record for the Batch Apex Error Settings and specify how you want the errors to be handled. 

That’s it, now you’re on your way to better error handling!

## **Using the Tool** 

Once you get a batch to fail, you should get an email or have a record created with the error details. If you set it up to create custom objects then check out the Batch Apex Error tab to see the errors, otherwise check your email. 

If you're interested in seeing how you could customize this product for your organization, contact us, and let's see what we can build!

Lastly, if you haven’t seen them yet, check out some of the apps that we developed for Salesforce (some of these will be using this code in the future)

- [Report Sender](/report-sender/) 
- [Marketing Calendar](/marketing-calendar/)
- [Potential Duplicates Component](/merge-duplicates/)
- [Opportunity Team Edit Override](/opportunity-team-edit-override/)
- [Approval Process Reminder](/approval-process-reminders/)


A hackathon is an event usually put together by a tech organization. The event brings programmers together over a specific period to collaborate on a project.

batch-apex-error-event-cloudanswers-hackathon

Batch Apex Error Event - CloudAnswers Hackathon

for-everyone

For Everyone


At CloudAnswers we regularly run internal hackathons. If you haven’t read about how we do this, check out our blog post: How and Why We Run Hackathons. Read on to hear about our hackathon winner from our February 5th hackathon, Avinava’s Shipment Scanner.

## Introduction

The hackathon theme this time was “Salesforce Spring ‘21 release.” In other words, competitors had to build a solution that used at least one feature from the new release. Avinava decided to use the new API for barcode scanning in Lightning Web Components combined with a third-party library for generating QR codes to create a better way to generate shipping labels and receive packages. Scanning is essentially a non-destructive method of identifying and inspecting any goods (items). On a broader scale, security in the commercialization of goods and services has never been more crucial. This app can be customized and plugged into any Salesforce system and makes it easier for everyone to track packages.

![](/uploads/contactless-payment-qr-code-smartphone-screen.jpg)

If you look closely at most shipping/courier services, they have their API that you can integrate to track the shipped packages. These integrated systems come as a barcode and other shipping information on the packages. With our new shipment scanner app, we want to curtail the need for manual entry of shipments received. Hence, removing errors and inconsistencies from the picture.

## **Processing a Shipment**

To process a shipment with the app, you simply scan the packing slip that is attached to the item. If your organization is providing the shipping labels the QR code generator can be used to add an easily scannable QR code to the shipping label. Otherwise, the scanner app can be connected to the appropriate API to get details about the scanned item. Here’s an example of how it would work for a company processing returns:

- A customer requests a return
- The company generates a packing slip that has a QR code and the other necessary info such as their receiving address.
- The customer prints out the shipping label and mails the returned item.
- An employee at the receiving address opens the shipment scanner app on their device.
- They click on the scan button and point the camera at the package.
- Within a few moments, they have all the information about the item on the screen.
- They can now accept the return, submit it for processing, or whatever next actions would be appropriate for the workflow.

![](/uploads/qr-code-scaning.png)

In the end, this scanning workflow can be used for a wide variety of applications even beyond sending and receiving shipments. We’re excited to see this scanner library available for Lightning Web Components and we hope to customize this app for some customers in the very near future.

## **Features of the App**

- Significantly reduce the amount of time needed to accept shipments.
- Reduce costs and avoid customer issues by skipping manual data entry.
- Risk reduction for customers and sellers.
- Creates a shipping alternative that lets your business work with as many logistics companies as you desire.
- A user-friendly interface follows a step-by-step pattern that helps you focus on what to do per time.
- Scanning apps within the Salesforce apps allow companies to leverage all of their existing pages and workflows to process the shipment, notify the right parties, and update other information in the system.

## **Learn More**

If you’re interested in seeing how this could be customized for your organization, contact us, and let’s see what we can build! Here you can find the apps that we developed for Salesforce: -[Report Sender](https://cloudanswers.com/report-sender/) [-Marketing Calendar](https://cloudanswers.com/marketing-calendar-2/) -[Potential Duplicates Component](https://cloudanswers.com/potential-duplicates-component/) [-Opportunity Team Edit Override](https://cloudanswers.com/opportunity-team-edit-override/) [-Approval Process Reminder](https://cloudanswers.com/approval-process-reminders/)

Find us on [AppExchange](https://appexchange.salesforce.com/appxSearchKeywordResults?keywords=CloudAnswers)


Hackathon Highlights: Shipment Scanner. new API for barcode scanning in Lightning Web Components combined with a third-party library for generating QR codes to create a better way to generate shipping labels and receive packages.

hackathon-highlights-shipment-scanner

Hackathon Highlights: Shipment Scanner


As a consulting company with a growing AppExchange portfolio, we rarely have a shortage of things to do at CloudAnswers. But every month or two, we adjust one of our sprints slightly so that everyone can take a day and work on something new. Usually, we run 24-hour hackathons. They have been a big success: we have received great feedback from the team, launched several products, solved customer problems and our own. So we thought we’d share why and how we run these.

# What Is a Hackathon?

In case anyone has not heard of a hackathon, it’s a small competition where we try to build the best software within the constraints and timeframe provided. For example, in January, we did a hackathon where individuals had 24 hours to create something using at least one of the Salesforce Spring ‘21 release features. The results were judged based on pre-defined criteria that we’ll explain later, and a winner was chosen. In this case, the winner just won bragging rights, but often we’ll throw in prizes for some extra incentive.

# Why Do Hackathons?

If you read this and say, “this will never work at my company”, then this paragraph is for you. Because at first, we had no idea if this would work for us. The concept of taking most, or all, of our team and telling them to stop doing customer work and to just build something, anything, is a decision that took some consideration. But after doing these semi-regularly for a few years, we’ve realized more value than we expected, and we plan to keep doing these.

First of all, it has been great for teamwork and morale. We are a distributed company with offices around the world, and the hackathons have been a way to bring everyone together for a short period. When we do team hackathons, people get to work together that might not communicate much during their everyday work. And since hackathons typically deal with new technology and don’t have to be production-ready, it’s an excellent way to take the pressure off since we are otherwise shipping code almost daily.

Secondly, we realized that our team has many great ideas, and sometimes they need the space to work on them. When you’re constantly working on products and customers’ projects, sometimes you never take the time to build that great idea that nobody has asked for. But with our hackathons, those ideas have become products on the AppExchange, tools we’ve provided to clients, and internal tools to help speed up our workflow. It’s been quite amazing to see what people build when giving them only a few constraints and letting them make whatever they want.

Lastly, and probably most importantly, it’s a great time to learn. One thing that often separates great developers from the rest is that they naturally try things - often spending a large portion of their free time just “hacking” on things. A hackathon can be a way to get all developers to set aside some time and try something new. More often than not, the hackathon demos include some lesson about how the team tried to build X but ended up building Y because of something they learned. We also use the hackathon themes to encourage particular learning topics; for example, we have a hackathon for almost every Salesforce release where you have to use at least one new feature.

# How do we do Hackathons?

We take a pretty lightweight approach to hackathons. We’ve found that you need a certain amount of constraints to get the best ideas, but beyond that, any rules you add can limit the output and make it harder for new employees to understand and participate. And if you make a complex process for running the hackathons, you’re less likely to do them. So as much as possible, keep this process simple. Here’s a summary of our process.

## Planning the Hackathon

1. **Choose someone to organize it**. For large hackathons, this can be a group of people. Feel free to rotate who’s in charge. For us, it’s usually our founder James picking the date, and then we organize it together.
2. **Pick a good time and duration.** Talk to the team and figure out what time and duration work best for your team and your customer demands. Some organizations do theirs after work one evening; some dedicate a weekend. Since we’re a distributed team, we’ve found it works best to schedule ours for Thursday at 9 AM EST to Friday at 9 AM EST. This gives everyone 24 hours, aligns with the teams’ standups, and allows people worldwide to join the same hackathon.
3. **Pick a theme.** You can do a hackathon without a theme, but we’ve found it’s often more challenging for teams to decide what to build when there are no constraints. So we ask for ideas in Slack and consider everyone’s input when planning hackathon themes. Some themes we’ve done and ideas that we’ve heard: Industry-specific solutions, Salesforce new features from a release, client-specific solutions, health and wellness, and non-profit solutions.
4. **Plan your judging.** Judging comes down to two things: judges and scoring method. For judges, you can either have teams vote for each other or invite guest judges that are not in the competition. We’ve done both, and while it’s always nice having a guest panel, sometimes it’s just easier to skip that extra step.

## Hackathon Rules

We recommend keeping the rules as simple as possible. Both to make sure that you can enforce them and to make sure that everyone knows them. Here is an example of our rules:

1. All code must be written during the hackathon period unless the code was freely available to all participants before starting. In other words, you can use shared libraries or open-source libraries, but you can’t start working on your project ahead of time.
2. Your solution must meet the theme. For our Salesforce Spring ‘21 hackathon, the solution had to include at least one feature from the new release.
3. Code must be submitted to a GitHub repo for review by judges/other teams. This doesn’t have to be done until the end but helps us verify that no one is cheating.

For an example of what this looks like when it’s all put together, you can check out one of our old hackathons where we invited other companies to join: [CloudAnswers Open Hackathon](https://hackathon.cloudanswers.com/).

# What Next?

If you’re looking to run internal hackathons at your company, share this article with the people who can approve it and ask for a simple experiment. Getting everyone to agree can be a bit of work at first, but believe us, it’s worth it. Try starting with a small hackathon - even a few hours one afternoon can be a great way to prove that it’s worth doing. If management doesn’t approve, see if some of the team members want to do a hackathon outside of work hours anyway and then see if management changes their mind after showing them some demos.

If you can’t get it approved or don’t work at a company with enough developers to host an internal hackathon, there are plenty of other hackathons to join. You can check [a variety of online websites](https://medium.com/@jonathanallengrant/the-7-best-websites-to-find-a-hackathon-the-hacklife-guide-3e420f2a565b) or look for local developer groups that might host hackathons.

If you’re interested in hearing more about our Hackathons, stay tuned for future blog posts on our hackathon results.


CloudAnswers team every month or two, run 24-hour hackathons. They have been a big success: we have received great feedback from the team, launched several products, solved customer problems and our own. So we thought we’d share why and how we run these.

how-and-why-we-run-hackathons

How and Why We Run Hackathons


# The CloudAnswers open hackathon

At CloudAnswers we've been having 24 hour hackathons on a monthly basis for almost a year. It has proven to be a great way for developers to take a break from the normal customer projects, learn new technologies, and solve problems that affect many of our clients. And now several of the previous hackathon apps are going through the Salesforce security review process and will join our other [AppExchange Apps](https://cloudanswers.com/products/) online!

Now that we've run this successfully internally, we wanted to invite others from outside the company for fresh ideas and to make it more fun and engaging. So we set up a website and invited some colleagues to join us in seeing what can be created. For the month of December, developers from around the world joined in on our [Open Hackathon](https://hackathon.cloudanswers.com/) to build Salesforce apps.

Teams were challenged to build apps according to the following guidelines:

- Projects must be open source.
- Projects must be related to Salesforce or use Salesforce technology.
- Projects must be committed to GitHub so that we can verify that contestants complied with the project guidelines.

On Friday, January 4th we held our judging webinar. Contestants from around the world had 5 minutes to present their projects to the judges. The judging panel was made up of people with extensive Salesforce experience, including several Salesforce MVPs and people who have experience publishing apps on the AppExchange. Contestants were judged on the following criteria:

- 25% originality: please don’t make a slightly better de-dupe tool. Let's see some creativity.
- 25% tech chops: are you a true hacker?
- 25% polish: is it easy to understand and use, or does it have errors everywhere?
- 25% business viability: is this a real product?

After seeing lots of great demos, the judges chose the following two projects as our first and second place winners, getting $1,000 and $500 in prize money!

## First Place: James Sullivan, Org Health Check

James took first place with a comprehensive and super simple way to monitor changes to a Salesforce org. Using Amazon and JSforce, James created an app that anyone can sign up for in just a few seconds.

![DB Saver Website](/uploads/DB-Saver-Website.png)

After they've given permission for the app to log in to their Salesforce org, the app will log in on a daily basis, run a variety of tests, and email the admin with important information about the security of their org.

Some of the various things that it monitors:

- Where people are logging in from (to detect unexpected locations)
- Newly installed apps (to monitor for unexpected installs)
- Unit test failures (in case configuration changes broke your code)

image: /uploads/

## Second Place: Avinava Maiti, Smart Alerts

In a very close second, Avinava created a system for admins to create record alerts for their users. Sometimes, a validation rule is just too much, and you want to allow people to save the record but still get a warning of sorts. Well, with Smart Alerts you can setup formulas that display warnings to the users, like when they don't have a Next Step on an Opportunity or don't have a phone number for a Contact.

![Smart Alerts List](/uploads/Smart-Alerts-List.png)

Using a custom object and a lightning component, Avinava built a system that will use lightning data service to evaluate formulas and display alerts to the user. The system is fully customizable and works on any object with a little bit of setup.

![Smart Alerts](/uploads/Smart-Alerts.png)


CloudAnswers open hackathon happens on a monthly basis. Teams are challenged to build apps that are related to Salesforce

winners-of-the-first-cloudanswers-open-hackathon

Winners of the First CloudAnswers Open Hackathon

Salesforce apps, powerful components, development and consulting. Our experienced team helps you to create and modify workflow processes in salesforce.

Hackathon

Batch Apex Error Event - CloudAnswers Hackathon

Hackathon Highlights: Shipment Scanner

How and Why We Run Hackathons

Winners of the First CloudAnswers Open Hackathon

Partners

Company

Get in touch