Deleted transfers

This minor release fixes deleted transfer:

• Cancelled Transfers should be considered "deleted" ie should no longer show up in the tables.

Data Migration and Fixture

N/A

Implemented Trello Cards

• Trello 591 Credit Transfer | Cancelled Transfers

Technical information

• This minor release is deployed on test at May 8, 2018 and on prod at May 10, 2018

Adds a new fixture for Vancouver Island Propane Services

This release includes:

Trello #590 New Fuel Supplier

Fixture:

organization_vancouver_island_propane_services.json loaded on all three environment
test_tfrs_users_MichaelRensing.json loaded on test and prod

Technical Information:

This release is deployed on Test and Prod both at May 1, 2018
This release is merged back to develop at 2018-05-03, PR#267

Backup - Tagging Develop before merging with v0.1.0.4

This tag is a backup for develop branch and created before merging release-v0.1.0.4 to develop.

Hides the government row from the list of Fuel Suppliers

This release includes:

Trello 575 UX Refactor | Hide / Adjust Parts of the Fuel Suppliers Page to IDIR Users

Technical Information:

This release is deployed on Test at Apr 26, 2018 and deployed on prod at May 1, 2018.

Compliance period

This minor release adds the compliance period dropdown to the Historical Data Entry:

• Added Compliance Period column in Historical Data Entry Table
• Added Compliance Period column dropdown in Historical Data Entry Form
• Credit From, Credit To and Transfer Type are all disabled in Historical Data Entry Form Edit*
• Added backend code to support the Compliance Period

Data Migration and Fixture

The following migrations are included:

• 0005_auto_20180424_1445.py
• 0006_auto_20180424_1527.py
• 0007_credittradehistory_compliance_period.py

The fixture loaded is

• compliance_periods.json

Implemented Trello Cards

• Trello 578 Historical Data Entry | Add compliance period to the entry

Technical information

• This minor release is deployed on Test at Apr 26, 2018.
• The pull request merges from release-v0.1.0 branch to master is:
  PR 240 Release v0.1.0.2

Updated the Fuel Suppliers Tab

This minor release updates the Fuel Suppliers page:

• Use the same table style as Credit Transactions and Historical Data Entry
• Unused buttons and filters are hidden
• Credit Balance are displayed properly for each organization
• Other columns are also populated

Implemented Trello Cards

• Trello 574 UX Refactor | View Company Credit Balances as Gov User
• Trello 575 UX Refactor | Hide / Adjust Parts of the Fuel Suppliers Page to IDIR Users

Technical information

This minor release is deployed on Test at Apr 25, 2018.
The pull request merges from release-v0.1.0 branch to master is:

• PR 236 Release v0.1.0.1 merge to master

Historical Data Entry

User Features

Government Analyst can:

• enter historical credit transfers,
• enter historical credit validations from the supply of fuel,
• enter historical part 3 credit awards,
• enter historical credit reductions
• process approved credit transfers
• view credit balances for fuel suppliers
• view pending, approved and completed credit transfers

Technical Changes

• The docs folder is moved from tfrs report to tfrs-docs repo
• Https communication between proxy server and pathfinder route has ben established. Non-secured route is blocked
• The number of Gunicorn worker thread has been limited in case it consumes too many recources
• Asset files have been remapped to use absolute path to fix refresh issue

Credit Transfers - alpha

Foundation Development:

• Identify the current user and organization
• allow login through siteminder
• utilize the siteminder header information after the user logs into the bc government common logon page
• configured pipeline with to orchestrate unit testing, static code analysis, code coverage report, publishing of results to sonarqube, update of the schema spy, build,
• pipeline waits for user input to click deploy to test, and deploy to prod
• the system allows for the authenticated user to initiate the creation of a new credit transfer
• the credit transfer workflow options are controlled based on the status of the credit transfer transaction
  • statuses: draft, deleted, submitted, accepted, approved, completed, rescinded, rejected, recommended
• you are only able to see the transactions that your organization is a part of ( #184 )
• Created a Developer Manual (#189, #190, #192, #193, #197, #198, #199, #200, #201, #202, #203, #204, #205)

Credit Transfers -alpha

FRONT END DEVELOPMENT

• Develop the screens in REACT using the balsamiq wireframes with the following directions:
  • Implement a Client REST web service to consume the provided Swagger REST API Specifications
  • Use the Gov 2.0 Bootstrap Skeleton for look and feel,
  • implement the provided Behavior Driven Development scenarios and system messaging,
  • create the NavUnit templates for automated functional testing,
  • create functions for validation of form data,

BACK END DEVELOPMENT:

• A Python/Django server was developed that implements a REST interface and database design for the initial specification of the TFRS application. Additional back-end development work is needed to refine the server by reusing a Swagger Code Generator mechanism to generate the code for a revised Swagger specification and refactor/add custom functions as needed to implement the new REST API.
• One key path in the Swagger specification is the /api/User. Extend the User API implementation to associate a user with their authentication information received in the HTTP header information. Specifically, all users in the system will be authenticated by Siteminder (via an independent process) such that Siteminder information (UserID, UserGUID) will be available in the HTTP header. Extract that information and use it to find in the database information about the user accessing the application.
• The Swagger Code Generator currently generates (amongst other code) Python/Django Models for the definitions defined in the Swagger specification. Django's ORM capabilities are subsequently used to generate the Database Model from those generated Models. Work is needed to extend the Code generator and to override some Django ORM capabilities to alter the behaviour of the generated database model. This effort will mimic comparable features implemented in the C#/.NET Core/Entity-Framework version of the generator.
  • Change the item naming style to meet the NRS Standard (e.g. all upper case names with '_' separators, no table prefixes)
  • Push comments describing the items in the design (e.g. tables and attributes) into the database metadata
  • Force the database to use UUIDs as keys vs. traditional sequential IDs
  • Extend tables to include standard auditing fields, populated via application and/or database triggers.

Credit Transfers -alpha

User Stories

As a trading partner I need to be able to navigate through a series of self-service screens to:

1. view information regarding past, proposed and pending credit-related activity including a real-time credit balance and list of activities that may impact that balance.
2. enter and submit the information required to propose a credit transaction to a trading partner; accept a proposed trade from a trading partner and submit that transaction proposal to the Director for approval.
3. view the information entered by the user on Transaction Details screen before proposing it to a trading partner or submitting it to the Director for approval.
4. review before authorising the transaction and submitting it to the Director for approval or saving it for future.
5. post a credit tranfer opportunity, offer or advertisement. The offer needs to have the same information that a credit transaction proposal would have, without the transfer partner. Offer and credit transfers are separate entities.

The Low Carbon Fuels Branch staff need to be able to:

1. Input transactions to award credits for a "Part 3 Agreement" or to add validated fuel supply credits or to retire credits used for offsets in annual compliance reporting.
2. Sort and search the list of all transactions and be able to export/download the tabular data for analysis in excel.
3. Add companies, contacts, users, roles and permissions through the Swagger API