Add CollNote properties in Tenancies

[abrahamseni]

We need to access an extra field in the tenancies like this one in AC

Describe the solution you'd like Add properties CollNote in tenancies.

Specification

• Project: Reapit.Services.Tenancies
• Add new string property feeNotes to TenancyModel that exposes semi structured field ten.extra.tCollNote
• Add new string property feeNotes to UpdateTenancyModel and CreateTenancyModel that allows semi structured field ten.extra.tCollNote to be written to. We should validate that the length of this field does not exceed 300 characters

[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]

To discuss with lettings team

[plittlewood-rpt]

Reached out to lettings team to understood intended use of this field so we can evaluate how best to expose and label this property

[MatthewGoddard]

@plittlewood-rpt This is used to records notes and and additional information about the fees that are being charged on a tenancy. In this example, we're going to be storing whether the fee collection is a 6-4-6 month schedule.

[plittlewood-rpt]

HI @MatthewGoddard thanks and I agree, my main concern is that it's not that obvious that it's meant to be a note relating to the fees so it's likely we've got customers out there using it for something different which will look confusing if we add a field called feeNote to the API (or similar)

[MatthewGoddard]

Thanks @plittlewood-rpt Is it Ross or Nicky you're waiting on?

[plittlewood-rpt]

I've had a response and we are in discussions :)

[MatthewGoddard]

I'll butt out then :)

[plittlewood-rpt]

We just need to determine what validation rules to place around this field. AC lets you put whatever you like in that field, but that's bad practice for the API and we should introduce a sensible limit.

[johnpenrose]

@plittlewood-rpt do you have an update on this?

As far as what values will be added to the field, we expect the app to set it to one of the following three values at any given time:

• Do not edit - Not 646 Deal
• Do not edit - 646 Deal
• null / empty string

Hopefully this will inform your thinking on the validation rules to apply in the API.

If the field can be made non-editable/disabled in the core software, even better.

[HollyJoyPhillips]

Hi @johnpenrose this is with our Foundations team currently. As soon as we have more information or an update will update the ticket. Thanks.

[johnpenrose]

@HollyJoyPhillips Thanks. What sort of timescales should we expect for a response?

[johnpenrose]

@HollyJoyPhillips if you could let me know by Wednesday mid-afternoon, I'd appreciate it as it is a hot topic on our daily update call/ Thanks

[HollyJoyPhillips]

Hi @johnpenrose this has been approved by the Foundations team and will be moved into our current sprint. Any updates as development progresses will be automatically sent. Thanks.

[johnpenrose]

@HollyJoyPhillips according to Ross, your current sprint ends on Friday 28th. Should we hope for this to be complete by then? Or have we got the wrong dates?

[HollyJoyPhillips]

Hi @johnpenrose that is correct, you can view our sprint dates here: https://github.com/reapit/foundations/projects?type=classic

I shouldn't see a reason for this not to be completed this sprint.