![]() | |
Breaking Cases |
Epic Version | Area | Description |
---|---|---|
2020 | Get_Rating has been changed to Rating. This is to provide a more restful way to get the rating for a policy line. | |
2019 | Only 100 Direct Bill Reconciliation Record items can be updated at a time. This is to help ensure data entirely gets rolled back upon error and to avoid time outs. | |
2019 | The validation has been added to prevent user insert attachment to the folders that are not accessible by the account the attachment associates to. | |
2019 | Epic and SDK where updated to allow more than one “Email Address” to be added and displayed on a Certificate holder by adding the Email recipients property. A program written with Epic SDK 2018 or earlier will continue to work with Epic 2019 or later, but the behavior will be as follows: On a Get call, the first email address of “Email recipients ” in the database will be displayed in the “Email” property. On an Update call, If no “Email recipients” exist in the database for the specified holder and the value in the “Email” property is set to a valid email address string, then one “Email recipient” will be insert to Epic system. On an Update call, If multiple “Email recipients” exist in the database for the specified holder and the value in the “Email” property is set to an empty string, then no “Email recipients” will be blanked out or deleted to prevent unintentional data loss in the Epic system. | |
2018 | Update method cannot be used for adding new detail items to disbursement since the Insert flag on DetailItem is now ignored. | |
2017.2 | Due to fixing issues related to the Canadian Habitational - Applicant, SDK no longer accepts blank values in cases where Epic would require values. This change has caused previous versions of Epic SDK to break. So, the new behavior to accommodate this change will be as follows: On clients up to and including the 2017.2 client: When updating or inserting Contact Number Items, the ContactNumberNumber property needs to be populated. | |
2017.2 | As part of changes in the Claims Payment/Expense Screen, fields under "Totals" and "Subrogation" headers were made modifiable. SDK no longer can assume that a modifying payment expense item should modify the "Total" and "Subrogation" fields. This change has caused previous versions of Epic SDK to break. So, the new behavior to accommodate this change will be as follows: On clients up to and including the 2017.2 client: Inserting, Updating, or Deleting payment/expense items will no longer automatically calculate the "Total" and "Subrogation" fields. If the user fields wants these fields updated, they will have to perform the desired calculations manually and update the now modifiable fields. | |
2017.2 | Due to scalability concerns, SDK no longer supports using the 'contains' comparison type when querying either Receipts, Vouchers or Disbursements by 'Refer #'. | |
2017.2 | Due to fixing issues related to the action "Move Marketed Lines to Current Policies", SDK no longer accepts blank values in cases where Epic would require values. This change has caused previous versions of Epic SDK to break. So, the new behavior to accommodate this change will be as follows: On clients up to and including the 2017.2 client: When populating the object for Action_MarketedPolicy_MoveMarketedLinesToCurrentPolicy, if UpdateStageToOption property is to set to 'Issued', then the PolicyNumber property needs to be populated. | |
2017.1 | As part of changes in the Opportunity Screens, the StageGroup was made a required field. This change has caused previous versions of Epic SDK to break. So, the new behavior to accommodate this change will be as follows: With the 2017 Client: On an Insert the StageGroup is required and needs to be set to a valid value. On an Update, the value for StageGroup can be changed to any provided by the user. |