New API Endpoint - Patch Enquires

[jazzlall]

There's a requirement for an extension to the current Enquires endpoint to provide the ability to update existing enquires in Agency Cloud to actioned/added and therefore no longer appear in Agency Cloud to be actioned.

This is relates to the IRE integration into Agency Cloud where they'll be processing these leads through their platform.

Specification

• Project: Reapit.Services.Enquiries
• New endpoint PATCH /enquiries/{id} protected by scope enquiries.writes
• Support update to the status only which should be one of the existing enumeration values

Payload

{
   "status": "added",
   "applicantId": "ABC123456"
}

Behaviour

• When status = 'added' applicantId must also be specified. This should be stored in appimp.aExtra.aCode
• When status = 'added' and there is a user in context, store the negotiator code of the user changing the status in appimp.aExtra.aCode

Validations

• Status must be valid enum value
• When status is changed to added, applicantId must also be provided (domain validation)

[github-actions[bot]]

Thank you for raising a feature request. Feature requests will be prioritised in accordance with our roadmap, customer and developer priorities. This request will be reviewed in our weekly refinement sessions and assigned to a specific project board or column, depending on the nature of the request and the development work required. For more information on our processes, please click here

[plittlewood-rpt]

Hi @jazzlall presumably it's just the ability to update the status of the enquiry they need here (ie added/spam/reject)

[jazzlall]

That's correct @plittlewood-rpt

[plittlewood-rpt]

Hi @jazzlall we've spec'd this out above. One question that came up was removing the call to action from the user (ie they aren't clicking Add anymore) have we considered how the agents will know they have new applicants on their system (other than the obvious to call list etc)

[github-actions[bot]]

This issue has been updated and moved to our ‘Near Term’ column (typically completed within 0 - 4 months). We have assessed the effort required and outlined a technical specification - please take the time to review this detail. When we're ready to schedule the issue, it will be assigned to the relevant board where you can continue to track its progress to completion. For more information on our processes, please click here

[jazzlall]

In this particular use case, they're being checked off in Internet Registrations because they've been have a appointment created for a viewing/valuation so the branch staff we be notified by other means as part of the that process.