Versions Compared

Old Version 23

changes.mady.by.user Greg Walsh

Saved on

compared with

New Version 24

changes.mady.by.user Greg Walsh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

  1. Owner Configuration: Owner Currencies which your organization supports
    Must match values in Salesforce (the Salesforce configuration steps can be found under the 'Salesforce (Pre App Installation Process)' section below) 



  2. Regional Settings: Countries (country and state relationships, city is optional)
    Must match values in Salesforce (the Salesforce configuration steps can be found under the 'Salesforce (Pre App Installation Process)' section below) 



  3. Accounts: Contact Types and Contact Points
    Image Removed
    Add an additional contact point to each contact type
  4. Name: sfdcid
  5. Data Type: Text
  6. Allow Multiple: False
    7. Required: False
    Accounts: Account Status Types
    Image Removed
    Accounts: Note: if Contact Types and Contact Points are configured as 'Required' in LogiSense Billing then they should also be set as required in Salesforce. The 'Contact Field Mapping' section below explains how to map LogiSense fields to Salesforce fields. Referencing which fields are mapped to Salesforce will tell you which Salesforce fields need to be set as required in order to match the LogiSense Billing configuration
    Image Added
    1. Add an additional contact point to each contact type
      • Name: sfdcid
      • Data Type: Text
      • Allow Multiple: False
      • Required: False

  7. Accounts: Account Status Types
    Image Added

  8. Accounts: Account Types
    Must match values setup under the Salesforce Account "Type" field (the Salesforce configuration steps can be found under the 'Salesforce (Pre App Installation Process)' section below) 



  9. Billing: Bill Groups


  10. Dunning Process: AR Terms


  11. Custom Fields

    1. Account:
      • Entity: Account
      • Field Type: String(255)
      • Name: sfdcid
      • Column Name: sfdcid
      • Description: Salesforce Account Id
        • Layout: Account Settings (optional)
        Image Removed
    If any additional fields are required to be synced to LogiSense during an account sync they should be added as well. Keep in mind when creating custom fields in LogiSense that the 'Column Name' value must match the Salesforce's native or custom field's API name.
      • : sfdcid
      • Column Name: sfdcid
      • Description: Salesforce Account Id
      • Layout: Account Settings (optional)
        Image Added


    1. Package Frequency:
      • Entity: Package Frequency Must match values in Salesforce (Product 'Product Family' field)
      • Field Type: String(255)
      • List: True
      • Lookup: False
      • Allow Multiple Selection: False


      • Name: Product Family
      • Column Name: family
      • Description: Salesforce Product Family


      • List Values: add the values listed in Salesforce (Setup → Object Manager → Product → Fields & Relationships → Product Family Picklist Values)


      • Layout: Add to Package Frequency Layout

    Note: any additional custom fields setup on package frequencies will not sync to Salesforce by default, to . To configure syncing of custom fields see the 'Package Field Mapping' section below

  12. Packages

    • Only packages / package frequencies that are "Active" will be synced to Salesforce
      • IMPORTANT! 
        • A product will be created in Salesforce for each Package Frequency
        • The product's name will be constructed by concatenating the following LogiSense fields, "PackageName PackageFrequencyName CurencyCode". For example, "ABC 1m GBP". It is important that all stakeholders are aware of this naming convention so that the names given to packages are user friendly for both Salesforce reps and LogiSense Billing Admins
      • If a package was already synced to Salesforce and then becomes inactive on the LogiSense side and resynced, it will be disabled on the Salesforce side and not available to be added to opportunities
      • Any package services whose Status pricing is NULL will not be synced to Salesforce
      • Rate plans (if applicable) must be attached at the package service level
      • Contracts (if applicable) must be attached to the package frequency
      • There should be a value in the SKU field. This field is mapped to the Product Code native field on the Product object in Salesforce. When a product is added to an opportunity a unique LogiSense Package Product Code will be assign to the opportunity product (SKU-ID). For example, if the SKU was ABC the product code will become, ABC-1. The next product added to any opportunity would be "SKU"-2, and so on. If no SKU is provided in LogiSense Billing and the product catalog is synced with Salesforce, then the product code for each product added to an opportunity would become, -1, -2, -3, ... (no SKU prefix).
      • Select the correct Product Family custom field value on the package frequency
      • The current Salesforce app doesn't support tiered pricing. The package will be synced however the tiered structure will not be displayed in Salesforce

  13. Optional Configuration depending on deployment
    • Product Catalog Contracts - these can be attached to package frequencies and will be shown on the Salesforce Product Object. (Custom Field: "Minimum Term", LogiSense_Minimum_Term__c)
    • Usage Buckets - these can be attached to services and populate the Usage Bucket custom object installed with the Salesforce App. The connection between the usage bucket and service will also be established in Salesforce and show as a read-only "allowance" on the custom Opportunity Product Service Visual Force page
    • Rate Plans - standard configuration of Rate Plan/Rate Group/Rates. These must be attached to Package Services and not Package Frequencies in order to allow Salesforce users to override rate amounts

...

  1. Install the latest version of the LogiSense Billing for Salesforce App in your production/sandbox Salesforce instance (Classic or Lightning are both supported).

    IMPORTANT! If this is the first time installing the app on a fresh Salesforce instance follow the steps below during the install process



    1. Select the third option Install for Specific Profiles

    2. Scroll down on the Install page and configure the profiles which will have LogiSense Standard User vs. LogiSense Standard Admin permissions
      • LogiSense Standard User - Provides full access to all sales related objects (i.e. accounts, contacts, opportunities) however users do not have access to sync products, price books or create custom field mapping
      • LogiSense Standard Admin - Provides full access to the application including ability to sync products, price books, custom field mapping as well as access to API request logs
    3. Click Install


  2. After installing the app switch to either LogiSense Lightning or LogiSense in the App Launcher






    Note    : the following steps assume that you are creating a custom section for all LogiSense related fields. However, you can mix the fields in with existing one on your current layouts. ID fields are not required and used mainly for testing and support. All other fields require values and therefore must be added to your layouts are you can create a custom trigger that sets default values

  3. Configure Account Page Layouts to display relevant LogiSense Billing data

    1. Load the Object Manager

    2. Access Page Layouts and modify the layouts that need to present LogiSense Billing data


      Custom data can be grouped into a 'LogiSense' section or added to existing layout sections as needed. The following fields are available:

      Note: bold fields below are required in order to sync data successfully with LogiSense Billing
      Note: if ID's are displayed on Layouts it is important not to alter them (these values are set by the LogiSense Billing application)

      • Tenant

      • AR Term

      • Bill Group

      • Account Status

      • Subscription Invoice Recipient

      • Usage Invoice Recipient

      • Sync With LogiSense

      • LogiSense ID

      • Parent LogiSense ID

      • Account Price Plan Id's

    3. Create a new section to display LogiSense Billing invoice data, and add the 'InvoiceList' Visualforce page to that section:

      • Edit the properties of the InvoiceList and enable scrolling

        For more information how to configure which columns will be displayed, refer to the 'Account Invoice List' section below.         To view the invoice, click on the Invoice Name/Id in the Visualforce page on the account object and it will launch a PDF version of the invoice as it appears in LogiSense Billing

    4. Add the 'Sync With LogiSense' button/action under Buttons or Mobile & Lightning Actions

      Lightning:



      Classic:



  4. Contact Object Layout

    1. Create a new section on the Contact page layout and add the following fields:

      • Contact Type

      • LogiSense Id

      • Contact Point LogiSense Ids

      • Address LogiSense Id


  5. Opportunity Object Layout

    1. Create a new section on the Opportunity page layout and add the following fields:

      • LogiSense Id

      • Buttons or Mobile & Lightning Actions

        • Sync With LogiSense

  6. Opportunity Product Layout

    1. Create a new section for LogiSense and add the following fields:

      • Minimum Term

      • Account Product Code Name

    2. Create a new section (e.g. 'LogiSense Product Services') and add the following Visualforce page:

      • OpportunityProductServicesListing

      • Enable 'Show scrollbars' on OpportunityProductServicesListing

  7. Product Layout

    1. Create a new section for the LogiSense data and add the following fields:

      • Minimum Term

      • Base Time Unit

      • Base Frequency

      • LogiSense Id

      • Product Currency

Connecting Salesforce to LogiSense Billing

...

  1. Navigate to the LogiSense Integration tab within Salesforce


  2. Click on the Edit button in the top right
  3. Enter the LogiSense instance URL in the Endpoint URL field. This should be the same one you entered in Remote Settings
  4. Set the Client Id value to: 044b8ad6006845c29446b2f18e5b5909
  5. For User Name and Password enter the LogiSense Billing credentials supplied by LogiSense
  6. Click the Test Connection button
  7. Once you receive a Success response, click Save

...