-
Notifications
You must be signed in to change notification settings - Fork 58
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
Business Search: Add Good Standing in COLIN #15978
Comments
do we need a design ticket for this? |
For the API and to meet MoForests needs, no. For the UI, I think it would save a lot of grief to do that up front. |
So for the UI this would be adding a good standing indicator inside each row of the results right?
I think we do, yes |
Could we add to the API call sooner than later? It has a big impact on the MoFor workflow, so a large business value |
I think in order to do this well in the UI we will have to add it to the api response, which will mean adding it to the solr index, etc. MoFor are wanting that information in the facets response right? |
Yep, I don't think it's a particularly small add, since it touches everything in the chain |
Ok - I'd need to get a design ticket in and prioritised |
@janisrogers we want to release this COLIN API change (in good standing) next week but we will need some help to test it from someone who knows the business rules around good standing for BCA companies. Would you be able to help us with this or point us to who can? @kialj876 @patrickpeinanw @gunanagar |
Oracle trigger change in linked merged PR below |
Business Search: Add Good Standing
BACKGROUND
Given The user is logged in
And has the appropriate payment methods enabled
Scenario: API returns Good Standing
When a search has been done on a business
Then the results has the Good Standing field set as either True or False for all modernized businesses and all COLIN BCA businesses not in the NWPTA agreement. For all other business types the field will not be present in the response.
Details
Create job/event that calculates good standing for LEAR (run daily)? Might not need - could be covered in importer changesverified covered by importerThe text was updated successfully, but these errors were encountered: