Skip to content

March 12, 2018 Release

Latest
Compare
Choose a tag to compare
@karamcintyre karamcintyre released this 13 Mar 00:51
5f22c2c

Release Overview

Please review this release document carefully (along with the affected documentation) before updating a current implementation of Interactions for Student Recruitment.

Bug Fixes and Enhancements

  • Fix the test class to prevent failures when record types are created for the Plan custom object
  • Fix the issue where Leads would be mismatched with Contacts during bulk loading
  • Remove redundant code to use Interaction mapping service instead of hard-coding Affiliation fields
  • Change when and how Campaign Members are created to prevent matching errors (after Lead/Contact upsert)
  • Enhance Interaction Mappings to allow fields from an existing Lead to map to an Interaction during Lead convert
    • Without this enhancement, Lead fields cannot be mapped to Opportunities, Affiliations, or Campaign Members.
    • Note that Lead fields can be mapped to Contacts using standard Lead Field Mappings.
    • This change affects your current Interaction Mapping object and fields if you are using an older version of the package. Please read the Technical Overview section in this release before installing updates.
  • Writing a converted Lead back to the Interaction so the ID can be used if needed.

Affected Documentation

Updating an org that has the previous package?

Unmanaged packages do not support updates via package links. Depending on how much customization you’ve added to your existing org with Interactions for Student Recruitment, use one of the following suggestions for updating:

  1. If you have minimal to no related records, configuration, and no code customization, you can uninstall the package and reinstall as you would when installing for the first time.

    Warning: Any setup or configuration you completed for components included in the package will be written over, and all Interaction Mapping and Interaction records will be deleted.

  2. If you have some related records and configuration but no code customization or configuration, you can use Workbench to deploy the new GitHub source code.

    Warning: Any setup or configuration you completed for components included in the package will be written over.

  3. If you have related records, configuration, and code customization, you must use the Force.com IDE to install portions of the package from the GitHub source code.

    Warning: All portions of the package you choose to deploy to your org without editing using the Force.com IDE tool will write over any custom configuration or development.

NOTE: Always install updates in a sandbox first and review changes to ensure you understand what will be deleted or overwritten and what records you will lose before attempting to move those changes to a production environment. Back-up related data before updating. Review the Technical Overview section (especially the changes related to Interaction Mappings) before proceeding.

Technical Overview

Code and Configuration Changes

This is a list of major changes to the code and components. To view more information and to compare the changes to the previous version, view the Pull Request in GitHub.

Fix test class to prevent failures if record types are created for Plan

  • Apex updates
    • INT_InteractionProcessor_TEST.cls

Fix Lead mismatch to Contact during bulk loading issue

  • Apex updates
    • INT_InteractionProcessor.cls

Use Interaction mapping service instead of hard-coding Affiliation fields

  • Apex updates
    • INT_InteractionProcessor.cls

Upsert Campaign Members after Lead Upsert and Contact Upsert

  • Apex updates

    • INT_InteractionProcessor.cls
    • INT_InteractionProcessor_TEST.cls
  • CampaignMember object updates

    • Updated field: Campaign_Member_Key__c description/help text
    • New field: Lead_Contact_ID__c
    • Updated workflow: Campaign_Member_Update_Campaign_Member_Key_for_Lead
    • Updated field update: Campaign_Member_Key_Update_to_Lead_Camp

Map fields from an existing Lead to an Interaction during Lead convert

  • Apex updates

    • INT_InteractionMappingService.cls
    • INT_Interaction_Mapping.trigger
    • INT_InteractionProcessor.cls
  • Interaction_Mapping__c object updates

    • New field: Source_Object_API_Name__c
      This new field is required. Any preexisting Interaction Mapping records must be updated to set the Source_Object_API_Name__c to "Interaction__c"
    • New field: Source_Field_API_Name__c
      This new field is a replacement for the Interaction_Field_API_Name__c field. Any preexisting Interaction Mapping records must have their values moved from the old field to the new field, then the Interaction_Field_API_Name__c field should be deleted.
    • Updated field: Target_Object_API_Name__c description/help text and picklist values.
    • New validation rule: Disallow_Interaction_as_Target_wo_Lead
    • New validation rule: Disallow_Lead_as_Source_wo_Interaction
    • New list view: “Lead to Interaction”
    • New list view: “Interaction to Lead”
      This list view is a replacement for the "Lead" list view on Interaction Mapping. The "Lead" list view can be deleted after you install this update.
    • Updated layout: Interaction Mapping Layout