openlmis-requisition

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
I have made changes to handle a null initiator, plus I added a unit test case for that scenario.

I have made changes to handle a null initiator, plus I added a unit test case for that scenario.

change to handle null requisiton initiator

What happens if we send a message to the notification service with initiator set to null?

What happens if we send a message to the notification service with initiator set to null?

added content to unskipped requisition line items email
added content to unskipped requisition line items email
changelog file update

merge with master

send unskipped requisition line items to initiator

added content to unskipped requisition line items email

Changed repository for jasper dependencies

Take a look at the comment below: "There is always maximum of one regular requisition for given period, facility and program". We can return a single requisition thanks to that, not a list.

Take a look at the comment below: "There is always maximum of one regular requisition for given period, facility and program".
We can return a single requisition thanks to that, not a list.

Looks like this needs an IT

Looks like this needs an IT

Any reason we only do this for regular requisitions, and not emergency?

Any reason we only do this for regular requisitions, and not emergency?

merge with master

merge with master

OLMIS-7273: Improve performance of Requisition initialization
OLMIS-7273: Improve performance of Requisition initialization
OLMIS-7273: Improve performance of Requisition initialization

removed localizedmessage as response in api definition

    • -1
    • +0
    /src/main/resources/api-definition.yaml
added unskip requisition line item integration test

unskipped requisition line items definition in message-properties

Bumped version to 8.3.3-SNAPSHOT

OLMIS-7276: Release 8.3.2

I don't think the response would have the same schema as a message resource.

I don't think the response would have the same schema as a message resource.

I don't understand why we are crafting the email like this. This would make it very difficult to translate the email sent to another language, if the system is configured with a different locale. T...

I don't understand why we are crafting the email like this. This would make it very difficult to translate the email sent to another language, if the system is configured with a different locale. The entire email subject and body should be message resources, so that they can be translated.

We should not hardcode the locale, but get it from the service's config. Please see other code in the service to see how locale is retrieved.

We should not hardcode the locale, but get it from the service's config. Please see other code in the service to see how locale is retrieved.