This is a list of changes to Jarvis that are planned, in progress and have been completed by Simplus Managed Services Team
JIRA | High Level Description | Link to Tech Doc | Date Released to PROD |
|---|---|---|---|
Purpose: Campaign Influence provides insight into the impact marketing activity held in Campaigns is having on the pipeline held in Opportunities. |
| ||
Enhancement to replicate special category alert from Advance in Jarvis. That is also, that the system should be able to flag the constituents accordingly as special category/categories when transactions are being made to the account attributable to contacts through GRC records. |
| ||
TAPSS-914 and TAPSS-1708 | Enhancement to fix the recurring issue when deceasing contact. The system should automatically put an end date to all active rating and relationship management team records and make then inactive. The utility should then run and the GA team should not have any error. Flow was built to query on all related records for the Contacts to be deceased to avoid any AQ validation errors when doing the deceasing utility where Death of Date might be greater than the start date on related objects namely:
| TAPSS-1708 deployed TAPSS-914 deployed | |
Business Value: Prevent the following internal salesforce technical error during Batch closing:
This is a permanent fix to the previous temporary work around of manually deactivating the Process Builder/Flows then update the Batch/Transaction records and re-activating afterwards. This will also avoid implications of data not being updated correctly during the deactivation of the batch/transaction records flow/PB |
|