Dev0 Fall 2021 Release Notes – improveit! 360

The improveit 360 Fall 2021 Release includes a number of Enhancements to existing feature functionality along with a few critical Bug Fixes. Be sure to read all Setup steps, in order to take advantage of these Features and Bug Fixes. These release notes apply to all systems with i360 Pro package version 33.7 and above.

Enhancements

Attachment Manager: Multiple Attachment Upload

With the Fall 2021 Release, each User is able to upload multiple attachments directly from the Attachment Manager itself, rather than from each object's view page. Users are able to select multiple files of different types, and upload them directly to either the object of origin, or the object's related Prospect.

Go to any Prospect, Appointment, Sale or Project and click on the Attachment Manager button.

Click on the 'Upload Attachments' Accordion section to see the Attachment Manager Upload Attachment panel. Note the 'Upload to...' field, this is the location your Files will be attached to, either the object of origin or the related Prospect, depending on which is selected.

Click the 'Choose Files' button to upload single or multiple files.

Browse and select the Files you'd like to upload. Note: you can select files of different types (ie: PDFs, jpegs, xls and more). Once all files are selected, click Open

The Attachment Manager will show a preview of the Files you will be uploading. Be sure to select which record to Upload To... choose either the record of origin or the related Prospect record.

Click Upload

NOTE: If a User sees "undefined" in the Upload To field, check the User's Profile. Be sure the Profile has access to the VisualForce Page for the Attachment Manager.

elead JSON Endpoint

The previous version of the eLead Endpoint only accepted query strings, and then built a new eLead based on those strings. The new version (v34.0 and above) accepts either query strings or JSON. After creating the new eLead, a note is added to the body containing the JSON information.

Replication: Follow the directions outlined here: eLead REST Service v2

The eLead REST Service v2 also includes eLead Verification Settings, which can be toggled on/off in Custom Settings > Public System Settings

eLead Required Field Validation - (for first name and last name validation)
eLead Contact Method Validation - (for email/address/phone validation)

Required Fields

i360__Last_Name__c
i360__First_Name__c
At least one of the following:
- i360__Email1__c
- i360__Address_1__c
- i360__Phone__c

Note: Though only the Address_1/StreetAddress is required for Contact Method Validation, it is suggested to include Address, Zip (both needed for Smarty Streets verification), AND email or phone, to prevent elead conversion issues. If only the Address is included as a contact method in the POST, an eLead WILL be created, but will not convert successfully.

Prospect Timeline displays new objects:

The Prospect Timeline now displays Outbound Text Messages that lookup to the Prospect. And Inbound Text Objects from related Outbound Text Messages are also displayed.

Create an Outbound Text Message related to a Prospect. Go to that Prospect's View page, scroll down and click the Prospect Timeline Tab. Wait for the timeline to load. Here you will see any Outbound Text Messages sent to this Prospect.

NOTE: To see Inbound Text Messages, expand the Outbound Text Message that notes "Response Received" as the Inbound Text is a related record of the original Outbound Text Message:

NOTE: Status field Capitalization: New package version installation would not update the Picklist Values on Custom fields. If you would like Status values to be Capitalized, follow these steps:
After package installation, navigate to Objects > Outbound text Message > Fields > Status > Edit the Picklist values and Capitalize the first letter in both Labels and API names
After updates, should look like below:

A Salesforce to Salesforce connection discovered a problem with a breadcrumb object chain at the top of the Project View page. If the Project's related Sale has no product categories, the breadcrumb renders incorrectly.

Go to a Sale with no Sale Items, and therefore no product category.

Create a Project on that Sale. Go to that project's view page and ensure that the breadcrumb loads properly, and that you are able to click on that object's upstream of the Project.

Smarty Streets Address Verification - prevent verification recursion

If Smarty Streets is enabled in Custom Settings, when an eLead comes in with a valid address, the prospect address should be Verified and updated with the County on the Prospect. The Smarty Streets Verified field checkbox will be checked, preventing recursion of address verification each time a Prospect record or Appointment record is edited/saved.
Note: Valid Address for verification requires at least a full Street Address and Zipcode.

NOTE: To take advantage of this new feature, you must Activate two Remote Sites used by Smarty Streets

Navigate to Setup, in the QuickFind locate Remote Site Settings:

Open the two Sites with Smarty Streets in the name:

Click Edit and check the Active checkbox, then Save.

Repeat this process for the following Smarty Streets Sites:

Smarty Streets US Autocomplete
Smarty Streets US Street Address

Test the new Site settings: Create an eLead through Postman or initiate an eLead to be sent via a lead provider. Make sure the eLead converts to Prospect and contains a full Street address including Zipcode. After the Prospect conversion, check the Address is populated with State, City, County, and the Smarty Streets Verified checkbox field is checked (True).

Smarty Street Dynamic host Keys

To overcome the current limit of 100 Hosts per Smarty Streets Account Key, improveit 360 will be using this new feature to create Multiple Keys and add Hosts as needed.
The Key is present in the Custom Setting: Smarty Streets API
This new Custom Setting allows improveit 360 Staff to create new Host Keys in Smarty Streets Account and update the Live Address Key field in each customer's Salesforce Org.

Once a new Live Address Key has been created in Smarty Streets, login to the customer's Org to change the Live Address Key in the Smarty Streets API.

Go to Setup > Custom Settings > Smarty Streets API > Manage > update field "Live Address Key"

Permission Set for Multifactor Authentication User Logins

As of February 1st, 2022 Salesforce is implementing and enforcing a Multi-factor Authentication process for EVERY User of improveit 360. Users will be required to download the Salesforce Authenticator App to authenticate their identity when logging into improveit 360.

Users who not completed the authentication, you will see this message beginning on 2/1/22 when attempting to Login to improveit 360:

In this release, improveit 360 created a new Permission Set.
This Permission Set is required to allow Users to use the MFA feature released by Salesforce for logging into any Salesforce Organizations.

NOTE: System Administrator Users will need to complete the User Setup Steps here: https://support.improveit360.com/hc/en-us/articles/4406676414999-Multi-factor-Authentication-

Bug Fixes

Lookup Relationship on Prospect record - Resolved issue of PDF generation recursion loop and generating incorrect Prospect Data

The Print/Email button in improveit 360's managed package can get stuck in a recursive loop when a customer has related a Prospect to another Prospect (lookup Field to Prospect on the Prospect object).

The information on the document could be generated to show the incorrect prospect's information.
If two prospects are related to one another via a custom lookup relationship, the code did not assure that the correct customer's information shows up correct in the PDF generated.

The updates within this release assures that PDF generation pulls data from the appropriate Prospect (the record where Print/Email was clicked from).

Open any Prospect (Prospect1), Populate the "Referred By" field on the prospect with a different prospect record (Prospect2).

Click on the Print/Email Button on Prospect1 and choose any document (Example: Envelope). PDF should be generated without infinite loop and generated PDF should have details of the Prospect1 record.

Follow the steps above to create a PDF from Prospect2, the PDF should be generated without issues and should have details from the Prospect2 record.

Proximity Search Page - Map doesn’t load pin drops

MapQuest has changed their API Key. In order to take advantage of Proximity Search using MapQuest pin-drops, improveit 360's Dev team has created a new Public System Setting to allow the API Key to change over time (rather than being hard-coded within the Visualforce page). The API Key cannot be populated when the Release is pushed however, a default value has been set (and can be changed). To adjust or set the MapQuest API Key, go to Setup, in the QuickFind locate Custom Settings > Public System Settings > click Manage > click Edit

Clear out the Value in the MapQuest API Key field. Save the Public System Settings. The system will auto-generate the default value for the current (as of Fall 2021) MapQuest API Key.

If the MapQuest API Key is left blank, the Visualforce page for Proximity Search will display the following message:

MapQuest API servers are down message

When the User is on the Proximity Search Visualforce page and if MapQuest API servers are down, currently there is no message displayed to the user about a potential service interruption. The resolution is to add an Information message letting Users know on the Proximity Search Page - When Map doesn’t load, MapQuest API servers are down.

Open a Prospect. Click the "Find nearby sale" button > Opens Proximity Search VisualForce Page

Select the Sale Date Field and Timeframe, and highlight Components (Products), then click Search

The Search Results will display a list of nearby Sales. The Map will display a pin-drop for each record in the Search Results.

This page will always display: "Note: If Map does not load, please try again later... MapQuest API servers may be down"

Project Activity Time Zone

Previously, the improveit 360 Calendar would reference a Project Activity's i360__Start__c and i360__End__c fields when a Project Activity was displayed. The system would not account for the Time Zone of the User. The System Admin can now choose to enable a feature that makes the Calendar calculate Start and End times based on the Record Owner's time zone.

Replication/Resolution Steps:

Go to Setup > Custom Settings > Calendar Preferences > Manage > make sure 'Project Activity: Record Owner Time Zone' is NOT checked. Make sure your current user is set in the Eastern Time Zone.

Create a project activity as the Easter Time Zone User. Switch your computer to the Central Time Zone. Go to Setup > Users >
and select a second user. Place this user in the Central Time Zone, and then log in as this user.

When you go to the calendar, the Project Activity's start time should have moved to match your current time zone, one hour earlier that the original user.

Go to Setup > Custom Settings > Calendar Preferences > Manage > check the box labeled 'Project Activity: Record Owner Time Zone.' Refresh the Calendar. The start time should move back one hour, matching what it would look like for the owner in the eastern time zone.

NOTE: New package installations would not update the help text on Custom fields.
So, after the package installation, navigate to Custom Settings > Calendar Preferences > Custom field : Project Activity: Record Owner Time Zone (Managed)
> Edit the field and update Help text: "Start and End Times are not record owner specific natively. Enable this feature so that Project Activity Start and End times adopt the Time Zone of the Record Owner."

Removed the PaySimple help icon from Users

Description: The information bubble which would direct a User to the PaySimple Marketing documents has been removed. This button was not configurable and could not be turned off when a customer integrated with PaySimple, or if a customer did not want their end Users to access the information.

Also, a Franchisor using improveit 360 may not allow their Franchisees to access and use the PaySimple Integration. This code update assures that end Users do not have access to see feature functionality which is inaccessible to them.

Replication step: Open any Sale and on the Sale view page the Information Bubble or Help Icon is not visible anymore near the Print/Email button.

Company Logo Bug Fix

This is both a bug fix and a new feature. The bug was that the Company Logo image was not loading in Email Templates. The new feature is the ability to ensure the logo shows up when a document is created from the Print/Email button instead of going through Templates in the setup menu. NOTE: You will need to download and replace your existing Document Templates with new HTML files. See below.

A new Company_Logo setting was added to Public System Settings, and a new field "Company Logo" has been added to Prospect and Purchase Order to transfer the image to the both types of document. The user must now add the image link in their Public System Settings to see the logo on their documents.

NOTE: Follow these three steps:

Step 1: Follow instructions in this article to set the desired Company Logo image. https://support.improveit360.com/hc/en-us/articles/4405725249559-Adding-a-Company-Logo-for-use-in-Documents-and-Email-Templates

Step 2: Next, replace the Document Templates within your system, by following along with this Article:

https://support.improveit360.com/hc/en-us/articles/4409359577367-New-Company-Logo-Document-Templates-v34-0-Dev0-Release-

Step 3: Once these steps are completed, go to any appointment, and hit the 'Print/Email' button. Open any document, such as hitting the '@' next to 'Thank You Email.' The Email should show the newly added logo. These documents are generated from either the Email Templates or from one of the Document objects in the document tab. The logo should load for both kinds of operations from the 'Print/Email' button.

Removed Referred By Field from Lead Source and Prospect

improveit 360 clients often add a Referred By field to either the Prospect record or the Lead Source record. improveit 360's packaged field was causing a duplicate field issue from some clients. Our team has removed this field from the Prospect and Lead Source objects in the managed Package.