Update the MuleSoft and Salesforce Solution to change the primary key for citizen contact creation from email to Niche occurance

Opportunity overview

Update the MuleSoft and Salesforce solution to change the primary key for citizen contact creation from email to Niche Occurrence. 1 The MuleSoft query to identify victim has a loophole that allows a Suspect classified as "16: VICTIM DECLINES/WITHDRAWS SUPPORT" to be classified as a Victim if they are added to the occurrence first and the Victim has not added a portal account. This results in the potential for Suspects to create accounts and see report case data for other citizens. 2 OICs using Niche may, during the lifecycle of the case, update the primary victim in a case. This results in the new victim being allowed to register for the portal and see details of the case on the portal. This means that two person accounts are associated with the case account. If the original victim had previous occurrences related to this account, these would be visible to the new primary victim. 3 Within the Force there is intermittent use of generic emails for nominal creation in Niche; this means that when the subsequent report case is created in Salesforce an account contact with a generic email address is created. Subsequent nominal creation using this generic email address means that the contact details will rotate across multiple users and become associated with multiple occurrences. There is also a small risk that the generic emails can be used to create a user account providing access to citizen data 4 Currently, in the iHub Data model, Victim's Email is a mandatory field for iHub, so for any victim that doesn't have an email, the request will not be accepted by iHub and the API will reject the request. Humberside requirements are to have email as an optional field and having the mobile number as mandatory. The following changes have been impact assessed to achieve the following: • Infomentum to pass a static dummy value in the email field to get through the iHub Data Model. • iHub has existing logic in the Process API transformation to handle the dummy email iHub needs to ensure account and contact records on the case are updated when passing data to Salesforce.

Awarded to

Amounts belong to published awards or contracts. Where several suppliers share one value, it is labelled as shared and is not a supplier-specific allocation.

Classification

No classification was supplied.

Lots

• Lot 1Value not stated

Documents and notices

• Contract details notice on Find a TenderOpen source ↗