revert ability to clear specific keys from triggerNameToInfoMap from outside of the package, to allow tests to re-run triggers.

Release Notes

revert ability to clear specific keys from triggerNameToInfoMap from outside of the package, to allow tests to re-run triggers.

Changes

• CPCCM-8590 - [revert] rh_escal__BaseTrigger.triggerNameToInfoMap.clear() is not visible outside of the managed pacakge.

Allow removal of trigger from triggerNameToInfoMap from outside of the pacakge.

Release Notes

Add ability to clear specific keys from triggerNameToInfoMap from outside of the package, to allow tests to re-run triggers.

Changes

• CPCCM-8590 - rh_escal__BaseTrigger.triggerNameToInfoMap.clear() is not visible outside of the managed pacakge.

removed testMethod token from tests and replace with @istest annotation to ensure continued compliance with Salesforce standards

Release Notes

removed testMethod token from tests and replace with @istest annotation to ensure continued compliance with Salesforce standards

Changes

• CPCCM-8301 - Replace testMethod notation in escalations base package to remain compliant with Salesforce standards.

1.9

Release Notes

make basetrigger.triggerNameToInfoMap global

Changes

• CPCCM-6836 - Make basetrigger.triggerNameToInfoMap global so that tests in dependent packages can inspect it's state

1.8

Release Notes

make basetrigger.cls global

Changes

• CPCCM-6836 - Make basetrigger.cls global so that tests in dependent packages can inspect it's state

1.7

Release Notes

Make code in rh_escal__EscalationTeamTrigger.teamDupCheck() easier to read and maintain.

Changes

• CPCCM-6496 - The logic in rh_escal__EscalationTeamTrigger.teamDupCheck() is ugly and should be improved

Allow changing escalation case team member status

Release Notes

'Allow changing escalation case team member status'

Enhancement

Release Notes

Changes related to 'Create a new escalation case record when primary case on an escalation is not null'

Removal of Bad Fields

Release Notes

This release removes fields from the Case and Escalation Comment objects that were accidentally or improperly added to the package

Updates

• Removal of
  • Case.rh_escal__EngineeringReqNumber__c
  • Case.rh_escal__PotentialLiability__c
  • Case.rh_escal__Product__c
  • Case.rh_escal__SLAViolation__c
  • rh_escal_EscalationComment__c.rh_escal__LastModifiedBy_Contact__c

Enhancements

Release Notes

This release includes addition of some fields to escalation comments and rectification of some bugs.

Updates

• Do not allow addition of duplicate team members on an escalation.
• Do not allow addition of duplicate cases in escalation case list.
• Auto populate the account on escalation if a primary case is set and the account is unset.
• Addition of new fields in escalation comment object