Create and hook up asynchronous database

@Nikodem Graczewski – I'm ok with closing this ticket without QA // I'm sure issues will come up in implementation // and we can deal with those then...

@Nick Reid As this ticket cannot be QA'd do you think it is ready to be closed?

@Nikodem Graczewski sounds good to me

I have also removed the A/C about implementing the database

@Nick Reid

I've pushed the changes to master. I think that using this database in https://openlmis.atlassian.net/browse/OLMIS-3318#icft=OLMIS-3318 would make a lot of sense and would be great as a testing environment for it. What do you think?

CC @Brandon Bowersox-Johnson

@Nikodem Graczewski We this morning that modifying requisitions to use the database service was going to be risky and lots of work – and after reviewing the individual files, I agree that this work is too risky to take on right now.

Many of the files that you mentioned don't use the localStorageService in a meaningful way, and the underlying design of the batch requisitions screen is confusing.

If it were simple to remove the instances that use the localStrorageService for 'requisitions' – replacing these calls in requisition.js and requisition.service.js is less than ideal, as there is a ton of technical debt that if removed and refactored would result in more maintainable code.

The last requirement of this ticket was to actually use pouchDb somewhere in the system

• We can remove that AC,

• Or you can implement the database into the permissionService (which should be very quick)

Also, I'll make tickets for doing refactors to the requisition functions – but not when we are about to release

CC @Brandon Bowersox-Johnson @Mary Jo Kochendorfer

Notes from checking out the code
There is a difference between our offline requisitions and batch requisitions --> I am not sure why there is a difference between these items

Its also worth noting the the requisition batch approval sequence doesn't work OLMIS-3072, and that a user must be online to actually approve a requisition

requisition-approval-list.controller.js
There is only one feature that uses offlineRequisitions, and that is used to show/hide the "View Requisitions" button
--> remove isFullRequisitionAvailable function & replace view button with link to requisition
We might also want to consider removing everything that uses the OfflineService from this page

requisition-batch-approval.controller.js
Access to 'requisitions' offlineStorage can be removed here
localStorage access for 'batchRequisitions' should be move into batchRequisitionsApprovalService

requisition-batch-save-factory.js
offlineRequisitions reference can just be removed – if there is an outdated version, it will be caught at some other point

requisition-search.controller.js
offlineRequisitions here should be removed. The removeOfflineRequisition function should be added into requisition.js or requisitionService

requisition-view.controller.js
localStorage reference should just be removed here

requisition.service.js
requisition.js
Both are just littered with old code that is repetitive between the two files.