All branches pushed except ui-stripes-registry and dashboard which are pending platform-complete.

There is an issue with having ui AND stripes in name that is causing conflict, though this was previously advised by John M. 

Adi to discuss on #devops options to either change repository name or amend code that does name checking. 

Dashboard is unreleased, but dependent on the decision for ui-stripes-registry. 

Proceed with merge depending on whether deprecation happens before Stripes merge

Estimate 1d

May need update to filter.js 

When an agreement references more than 10 PO lines, we construct a query that caps results to 10. We should now show all requested lines. 

Add new CONST to manifest similar to RecordsPerRequest for orderlines from 100 to 1000. 

Starting points are AgreementLineRoute and AgreementLineViewRoute, and make changes to ask for higher maximum return limit parameter. 

Apply to view and edit. 

May need changes to toolkit also, so best done by a K-Int resident.

Could have conflicts with core vagrant update. 

Will require stable vagrant - latest version should be sufficient to develop with.

Frontend can be done in anticipation. 

Presentation should be similar to existing pattern, so no new wireframes needed. 

TODO: 

• Add new example to custom properties (0.5h backend)
• Changes to ui-agreements and erm-components (1h + overnight build on snapshot/testing)

TODO:

• Modify to remove duplicate entries
• Enhance integration test to match issue 

Branch for stripes-components reviewed by John C.

Edge cases to be handled STCOM-865.

Minor changes needed to 1345-1349

New tests prepared and submitted for Boulder user testing.