For the Heroku App Name, we’ll use sfdc-contact-editor. You’ll be asked to provide some information: Then, run node scripts/deploy.js, and a CLI prompt will take over. First, make sure you’re authenticated to your Salesforce Dev Hub by running sfdx auth:web:login. Setting up a project structure that favors convention over configuration. Using Bolt to abstract away details with authentication. Setting up and deploying a sample application to Heroku. The primary goal of the Starter Kit is to get your environment set up for building, testing, and deploying a Slack App that integrates with Salesforce. With the Salesforce Starter Kit available and its dependencies installed, it’s time to take a look at what the Starter Kit can do. Walking through the Salesforce Starter Kit Install the dependencies there with npm install then pop up a folder, and install those dependencies: Next, clone the Slack Starter Kit, and then navigate to the scripts directory: If you get an error about a URL being unverified, don’t worry-we’ll address that soon! Paste the following YAML into that box, overwriting what was there by default:ĭescription: shows Salesforce org detailsĬlick Save Changes. Your App Manifest defines some metadata about your app, such as the permissions it requests and the events it handles. On the left side nav bar, click on App Manifest. We’ll be referring to these in the next section. That’s it! If you scroll down, you’ll see your App Credentials. Set the name of the App to SFDCContactEditor, and choose a workspace where the App can be installed. 
In the prompt that pops up, select From scratch. We’ll first create a Slack App, which will provide us with tokens and other Slack-specific information we’ll need before building our app. A Slack workspace where you can install Apps. The Heroku CLI, as well as an existing Heroku account. The sfdx CLI-this is a tool designed by Salesforce to simplify platform interactions. In this first post, we’ll go through the SDK and set up your development environment for future work! Prerequisitesīefore we begin, make sure you have the following software installed on your machine: In this series of posts, we’ll show you how to use the Slack Starter Kit and Bolt to create an application that allows users to view and change Salesforce records-entirely in Slack.īy the end of this series, we’ll have a fully functional Slack app that communicates with the Salesforce platform. It’s an opinionated scaffolding framework designed to make it easy to build Slack Apps that integrate with Salesforce data. Taking into account Bolt’s development principles and tooling, they developed the Slack Starter Kit. Salesforce Admin vs.The folks at Salesforce have done one better. If you are in mobile and have badges/banners on for the Salesforce app, you may also see that appear.Īnd there you have it, your notification alert out to users is all set up! Enjoy this wonderfully simple, but powerful, new tool. You will see a (1) show up in the corner on the little bell icon in either application. Depending on if you set your Notification Type to Mobile or Desktop, that’s where you are going to look out for the notification. Go to the object that you chose in Process Builder and do the action(s) that would cause it to fire. Click Save, and then click Activate for the Process Builder Lastly, and probably most importantly, fill out the Title and the Body of the notificationĩ. Select the Recipient Type: this can be the User or someone on the record – up to you!Ĩ. Select the Notification Type that you made in Step 1ħ. Create New Action → select Send Custom NotificationĦ. Add any relevant criteria that should be followed in order for the notification to fire. Select your initiating object, and if this should fire only on create or create and edit. Go to Setup → Process Builder → Create new. This is the step to trigger the notification to go out. In some cases, if the user is both the person causing the notification to go out and the receiver of the notification, and Mobile and Desktop are selected, the user will only see the notification on the Mobile device when entering the app itself, assuming they have not already clicked on it in the Desktop app. and, that the user actually looks at the app. The application having notifications turned on. The user installing the app on their phone. This is important if you decide to have more than one Type available.īear in mind that for the Mobile notifications, some restrictions apply. 
Click New and then give the Notification Type a name.
Go to Setup → Notification Builder → Notification TypeĢ. The purpose of this step is to create a notification that will either go to the Mobile or Desktop app, or both.ġ.
0 kommentar(er)
