Changelog
Start typing to search…
Back to All

Maximizer CRM (cloud) 2024 M2 release

February 21st, 2024
✈️

Release date: February 21, 2024

Octopus API version: 2.40
Database version: 18.15.0

Bug Fixes

  1. Completing Task with just Completed and Key set's WithKey to Null
    Fix the scenario when updating an existing Task without providing any related key field in the request (WithKey or AbEntryKey). The original WithKey was being incorrectly removed in this situation, and this fix ensures the original WithKey is kept as-is.
  2. User without "User/Group details" read rights and without the "Modify other users' private entries" privilege shows all fields as being Read only when retrieving Metadata for an Opportunity
    Users without User/Group read permission set were denied access to all fields (ReadOnly = false) on any Opportunity assigned to the SalesTeam that the user is a member of or even Opportunities in which the user is a leader. This fix ensures that users will be able to access the fields allowed for their SalesTeam even if they are denied User/Group Read permission.

New features and improvements

  1. Webhooks (BETA) - breaking changes
    After conducting a beta phase for AbEntry and Opportunities webhooks, it became evident that the initially chosen approach was not stable and led to increased issues. Consequently, a decision has been made to pivot and adopt an alternative approach.
    In the revised implementation, new events will be triggered without any delay when an Opportunity is created, updated, or deleted. However, for now, these events will include the Opportunity Key only. To retrieve additional details, consumers are required to call API.
    For further information, please refer to the Webhooks documentation.

  2. API - Return meaningful message for malformed JSON
    Added validation for malformed JSON payload request. Endpoints will now return a meaningful error message for malformed JSON, including details about the encountered issue and error codes.

  3. Prepare API for Health Indicators implementation
    AbEntry object now supports two new System Udfs:

    • Type_Id = 60066 => Table Udf to store the Health Indicator associated with that entry, calculated based on specific rules. The result can be any of these 3 values: Code_Id = 60001 (Healthy), Code_Id = 60011 (Concerned) and Code_Id = 60021 (At Risk).
    • Type_Id = 60067 => Alphanumeric Udf to store information about the rules contributing to the calculation of the Health Indicator.

    Two new items have been added to the ADMN_Config table for the Health Indicator Worker process:

    • KeyCode = HEALTH_INDICATOR_ABENTRY, SubKeyCode = SCRIPT => stores the script with the logic (formula) to calculate the health index.
    • KeyCode = HEALTH_INDICATOR_ABENTRY, SubKeyCode = CONFIGURATION => parameters for the calculations, including those set by the UI based on specific rules.

  4. QuotaRevenue - Add support for Parent object (SalesTeamObject)
    A New Parent field was added to the QuotaRevenue object, providing details of the object represented by the ParentKey. For example, when ParentKey represents a SalesTeam, the Parent will expose all fields related to SalesTeamObject.

  5. QuotaRevenue - Support querying by ParentKey EntityType
    Added the ability to read from the QuotaRevenue object by filtering ParentKey using EntityType, allowing filtering quotas assigned to Sales Teams or Users.

  6. Task - Change name/label for Activity and AssignedTo fields
    The schema definition for the Task object was updated to versions 1.8 and 2.2. The names of the following fields were changed:

    • /Task/Activity => Name changed from "Activity/Subject" to "Subject"
    • /Task/AssignedTo => Name changed from "Owner" to "Assigned to"

Notes