Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-property specific preinstruction checks API endpoint #10623

Open
david-silverink opened this issue Jan 24, 2024 · 7 comments
Open

Non-property specific preinstruction checks API endpoint #10623

david-silverink opened this issue Jan 24, 2024 · 7 comments
Labels
agency-cloud Relates to Agency Cloud back-end Relates to back end issues external-request External request feature-request User requested feature

Comments

@david-silverink
Copy link

We need to regularly check the completion or otherwise of preinstruction checks but currently this data cannot be queried without a property code (e.g. /properties/HEO240000/checks). Ideally, similarly to offers, appointments and properties, we could periodically query only recently updated checks using modifiedFrom parameters and reduce the frequency and volume of data requested.

Copy link
Contributor

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

@AshDeeming AshDeeming added feature-request User requested feature back-end Relates to back end issues refinement To be included in a future refinement session and removed needs-triage labels Jan 25, 2024
@AshDeeming AshDeeming added this to To review in Platform Backlog via automation Jan 25, 2024
@plittlewood-rpt plittlewood-rpt added agency-cloud Relates to Agency Cloud and removed refinement To be included in a future refinement session labels Jan 25, 2024
@plittlewood-rpt
Copy link
Contributor

Hi @david-silverink this will need some input from one of the other engineering teams. We'll need to reach out and speak about this internally before we'll be able to decide if this is something that can be introduced or not.

@plittlewood-rpt plittlewood-rpt moved this from To review to Not ready in Platform Backlog Jan 25, 2024
Copy link
Contributor

As this issue relates to AgencyCloud, we are unable to process this through the Platform in accordance with our Developer Processes.
Issues relating to AgencyCloud should not be submitted via the Foundations GitHub repo but should be raised via the Reapit Service Desk by a Reapit Customer.
Please ask a Reapit Customer to raise this issue via the Reapit Service Desk.
For more information on our processes, please click here

@HollyJoyPhillips HollyJoyPhillips moved this from Not ready to AgencyCloud in Platform Backlog Jan 29, 2024
@HollyJoyPhillips
Copy link
Contributor

Raised with the Foundations team 29/01 (FYI @neilpellowe)

@david-silverink
Copy link
Author

Just a quick one on this - my understanding was as a workaround that updates to property checks would trigger a 'dateModified' timestamp on the parent property record and we could refer to our own database for recently updated properties instead of cycling through all properties searching for updates. Is this not the case? Our client has been making checks updates to a test property but if the above is not the case, then we have no way of knowing these have been actioned unless we check the actual properties/checks endpoint for that particular property. Thank you.

@HollyJoyPhillips
Copy link
Contributor

Hi @david-silverink I've reached out again to the product team to understand what the current position is. I'll update this ticket as soon as possible.

@HollyJoyPhillips
Copy link
Contributor

Hi @david-silverink I now have an internal reference to track. No immediate updates at this stage but I'll keep checking and update this ticket when I do.

Internal ref: PBI-5576

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agency-cloud Relates to Agency Cloud back-end Relates to back end issues external-request External request feature-request User requested feature
Projects
Platform Backlog
AgencyCloud
Development

No branches or pull requests

4 participants