Code Challenge - Workflow for ADM Notification

[scchapma]

USE CASE #1 - SUBMISSION
Given that I am a program area manager
And I have finished drafting a new opportunity
When I click on the "Submit" button
Then the opportunity transitions from the "Draft" state to the "Pending" state
And I am directed to a view that request the ADM's email address, Divisional Financial Staff's email address and Branch Financial Staff's email address

// Email wizard
Given that I have entered emails for my ADM, Divisional Financial Staff and Branch Financial Staff
When I click on the submit button
Then email is sent to the ADM
And the email addresses are saved to your profile (and used to autopopulate email fields for next opportunity)

// Need template email for ADM (NB - try to use existing CWU notification email)

• Unique ID
• Associated RFP control
• Posting date
• Value of opportunity
• Required Skills
• Closing date
• "Agree" and "Disagree" buttons

[scchapma]

Question #1 re Code Challenge - "What does ADM stand for?"

Answer: "ADM" stands for "Assistant Deputy Minister". For the purposes of the code challenge, assume that the ADM is a person whose email address is of the form "[email protected]".

[scchapma]

Q2 re Code Challange - "Does "Given that I am a program area manager" presume that I am logged in as [email protected]/govgov?"

A2 - Yes, presume that you are logged in with "gov" credentials (that is, in a "gov" role).

[scchapma]

Q3 re Code Challenge - "Has the Submit button been implemented already?"

A3 - No, that button has not been implemented.

Currently, the basic CWU opportunity publication workflow is:

1. Initiate new opportunity (i.e., click on "Create Opportunity" button)
2. Draft opportunity
3. Publish opportunity

This challenge modifies the first two steps of the basic workflow as follows:

1. Initiate new opportunity (i.e., click on "Create Opportunity" button)
2. Draft opportunity ("Draft" state)
3. Submit opportunity to ADM for review ("Pending" state)

Note that any additional modifications to the workflow (e.g., opportunity approved/rejected by ADM) are OUT OF SCOPE for this code challenge.

[scchapma]

Q4 re Code Challenge - "On installation, the dev.sh contains a command "docker stop mean_devex". When I pulled the /devex/develop branch, the "mean_devex" container didn't come through.

A4 - The mean-devex container is built when you run setup.sh and run when you run dev.sh.