Changelog
Start typing to search…
Back to All

Maximizer CRM (cloud) 2024 M1 release

January 24th, 2024
✈️

Release date: January 24, 2024

Octopus API version: 2.39
Database version: 18.14.0

Bug Fixes

  1. Lead Search Email Address Issue
    Resolved an issue where searches for an email address in Lead Search failed when the address contained more than one number. This was due to an invalid SQL query generated when a Lead $PHRASE search was issued with a term that was identified as both an email (term contains '@' and '.') and a phone (term contains at least three numeric values) simultaneously.
  2. Opportunities Search by Close Date
    Fixed a bug specific to Cloud customers, where searching for Opportunities by Close Date = "This Fiscal Quarter" used the range between the second day of the fiscal quarter to the day after the fiscal quarter. The issue was resolved by correcting the logic for converting local time to UTC time, ensuring that Opportunities closed one day after the upper bound date are not incorrectly returned.
  3. API Date Format Issue for Locale en-CA
    Addressed an issue where the API returned the Note DateTime field's Display Value for the Short date incorrectly when the Locale was set to en-CA. The resolution involved fixing the date formatting for single-digit days when the date format is set to "short date" in Advanced Settings, ensuring correct date display (e.g., "2022-05-5 3:27 PM" now correctly displays as "2022-05-05 3:27 PM") for certain locales, including CA, SK, and PT.
  4. MaAccess Error for New UDF in 2023.2 On-Premise DB
    Resolved a MaAccess Error encountered when adding a new User-Defined Field (UDF) for an Opportunity or Campaign in a new 2023.2 On-Premise DB, specific to On-Premise customers. The issue was fixed by removing the creation of the outdated "Udf Detail View" (old security mechanism) from the UDF creation process, aligning with the current security mechanism that does not rely on those detailed views.
  5. Import - Search by Key Issue
    Fixed an issue where the Import object could not be queried by Key due to an incorrect implementation of the json transformer, which failed to translate the request into the actual database query. The query by Key is now fully operational for the Import object.
  6. OAuth - Validate /Token requests before processing
    Added validations to the /Token endpoint on the Authentication API (OAuth), to ensure the data provided in the request is correct before processing it. If no data is provided, it fails with an error message: "Authorization was attempted with no data provided." If the "client_id" parameter is not provided, has more than 20 characters, or is not alphanumeric, it fails with "Authorization was attempted with an invalid client_id." When the "grant_type" parameter is "authorization_code," and if the "code" parameter is not provided, has more than 20 characters, or is not alphanumeric, it fails with "Authorization was attempted with an invalid code." When the "grant_type" parameter is "refresh_token," and if the "refresh_token" parameter is not provided, has more than 20 characters, or is not alphanumeric, it fails with "Authorization was attempted with an invalid refresh_token." If the "grant_type" parameter is not "authorization_code" or "refresh_token," it fails with "The value of the grant_type parameter is not valid."

New features and improvements

  1. Case - New Field "Overdue"
    Added a new "Overdue" flag (BooleanField) to the Case object. This field is calculated based on the FollowUpDate field and will be: "null" when the FollowUpDate field is not set (null), "true" when the FollowUpDate field is past the current datetime, and "false" when the FollowUpDate field is not past the current datetime. The new field is available when searching on both Legacy and SQL drivers. The field is not assignable, meaning it cannot be set to a specific value when creating, updating, or deleting a Case.
  2. Support Teams for Revenue Targets
    Added support for SalesTeamKey as ParentKey for the QuotaRevenue object. It's now possible to assign quota targets for Sales Teams and also individual users (UidKey was already supported previously). For CUD (create, update, delete) operations, there is no change in the request, except that ParentKey now recognizes SalesTeamKey formatting. For Read operations, there is additional information that can be added to the "Scope", making it easier to differentiate when a ParentKey is for a Sales Team and when it's for an individual user. The API will automatically set the response using the desired format depending on the ParentKey associated with each entry.
    See an example below:

"Scope": {
  "ParentKey": {
    "SalesTeamKey": {
      "Id": 1,
      "Value": 1,
      "DisplayValue": 1
    },
    "UidKey": {
      "Uid": 1,
      "Value": 1,
      "DisplayValue": 1
    },
    "Value": 1
  }
}

Notes