[36hr] GnG - Core Trip Scheduler Job listing

Challenge Overview

Challenge Objectives

• Angular app UI prototype development

Project Background

• We’re building a series of ‘calculator’ apps with similar workflow - input data, calculate, view results.

• Our client has developed a specific method of scheduling core trip from the bottom of the reservoir to the surface.

• In this challenge we’ll update the UI for the core trip scheduler calculator.

Technology Stack

• Angular

Code access

The base code and marvel app link are available in the forums. See the code style requirements also available in the forums.

Individual requirements

1. Job runs listing page

Screens in scope 59768476 - 59768478
To implement a job listing page for a new calculator, follow these guidelines:

• use job-runs-list component to render the job listing page and implement the data fetching callbacks (updateParams, paramsChange, fetchJobRuns, visibilityChange)

• update routing to follow similar structure as NCS: /calculatorName (job listing), /calculatorName/job (create new job), /calculatorName/job/id (view/edit existing job)

This page is common for all the calculator apps. Expected workflow is that the user would go into the dashboard, select an existing well (or enter custom well data) and then go to the individual calculator app where we’ll show a job runs listing for the selected well, with options to view a job run, update it, delete or copy. In case the user doesn’t select the well, we should display all the runs (ie, not filter by groupId).

 

When clicking the “New Job” button, use the “well-selection/well-selector/well-selector.component” component to show a dialog to select the well or use already selected one (see an example in ui\src\app\klinkenberg\pages\job-runs-page\job-runs-page.component.ts

 

2. Units and conversion
On the new job page, not all the units should be displayed as “feet” - see the details in the forums for each field. Only fields that are actually length should be converted between feets and meters when clicking the units toggle. Api should always get the feet values.
 

General requirements

 

• Unit/e2e tests are not required for now

• Make sure to follow coding style requirements and guidelines provided in the wiki page

• Place all shared code in src/app/shared directory (not src/app/utils)

• Place all routing code in src/app/routing

 

What To Submit

 

• Git patch

• Verification guide

 

Final Submission Guidelines

See above.