senaduka/old-new-wiaas
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Order delivery flow integration with order fields and order organization participants #53

Merged
akrdzic merged 16 commits from order-delivery-flow into master 2018-11-04 23:16:39 +01:00
Conversation 17 Commits 16 Files Changed 56 +5295 -2567
akrdzic commented 2018-11-02 15:46:26 +01:00 (Migrated from gitlab.com)
Copy Link

Order delivery flow integration with order fields and order organization participants

Details:

  1. Support order organization mapping to process step assignee
  2. Add fields to map order properties to delivery process step
  3. Add form for order questionnaire validation step
  4. Add form for installation step
  5. Add logic for order questionnaire validation step handling from customer frontend acccount

Smoke test:

Execute composer update-db

  1. Login as admin on backend

  2. Go to Forms tab and check that new action forms have been imported and also sample form for order delivery process.

  3. Duplicate Example process form and rename it as you wish

  4. Go to workflow settings and add steps:

    1. Validate Customer configuration (uses ACTION: Validate Customer Questionnaire)
    2. Procure components (Manual which means no form action is needed) and set that it is not visible for customer
    3. Wait for installation to be scheduled and confirmed (Manual)
    4. Procure installation (Manual)
    5. Installation (ACTION: Complete Installation And Upload Test Protocol)
    6. Customer acceptance (ACTION: Customer Acceptance)
    7. Customer training (Manual)
    8. Set start/stop dates for contracts (Manual)

  5. Create two supplier organizations and user for each of them (update user mail in database to our own for test purpose)

  6. Create commercial lead organization and user for it (update user mail in database to our own for test purpose)

  7. Create customer organization and user for it (update user mail in database to our own for test purpose)

  8. Create following simple products

    1. Hardware x2 with attached installation guide documents for every one
    2. Software x1
    3. Installation x2 (different suppliers)

  9. Create two bundles

    1. One bundle has one installation simple product, both hardware and software products
    2. Second bundle has two installation simple products, both hardware and software products
    3. Attach template agreement and template questionnaire documents for both bundles

  10. Set prices for bundles and make them available for customer to order

  11. Login as customer on frontend and order both packages in single order

  12. Go to order page and check that new process is available to assign to the order

  13. Assign process to order

  14. Check that process flow is created

  15. Go to process flow page

  16. Validate that all steps are present together with automatic (Order placed and Assign process)

  17. Validate that Validate Customer configuration step is present

  18. Check that two workflows are present (one for each bundle) and document can be downloaded

  19. Check your email and validate that two emails Validate Customer Configuration are received for each validation

  20. Open order as customer and check that steps are listed

  21. Validate that current active step is Validate Customer configuration

  22. Validate that both questionnaire documents that customer uploaded are being validated and they can be downloaded

  23. Go to admin interface and reject one of the documents and check that next step will ask from you to
    enter validation reason (enter it and submit). Validate that next step is pending user input form customer.
    Since you put your email for customer user validate that you received email informing you about rejected document.

  24. Go to customer interface and validate that pending action is listed for uploading this file

  25. Go to order details and validate that file upload field is present for that file and status is invalid

  26. Upload new file and validate that status is changed to not-validate

  27. Go to admin interface and open action workflow for this step and validate that your approval is pending. Also validate that you received email about pending validation for this document.

  28. Accept document and validate that workflow for this action is completed

  29. Go to customer interface and check that status of that document is validated

  30. For second validation workflow just accept document and check that status is updated on customer interface.

  31. Validate that two mails informing customer that documents are validated got sent.

  32. From admin interface go to next step and validate that process workflow went to Procurement step. Download Procurement order report and validate that it contains delivery info, billing info, simple products and info about their suppliers.

  33. Go to customer interface and validate that this step is not visible on customer interface.

  34. From admin interface go trough * Wait for installation to be scheduled and confirmed* to Installation step

  35. Validate that action step workflows are created

  36. Validate that for bundle that had two installation products pending action step is to select one of the installation
    companies. Select installation company and validate that next step is for installation company to confirm installation.

  37. Validate that for bundle that had one installation product pending action step is for installation company to confirm installation is completed.

  38. Since you set your email for users of these companies check that you received email informing you that you should confirm that installation is completed.

  39. Login as these users and confirm installation.

  40. Validate that next step is to upload test protocol. Upload test protocol and validate that action workflow is completed.

  41. Go to admin interface to main workflow process and validate both actions are completed.

  42. Go to next step Customer acceptance and check email is sent for pending customer acceptance upload.

  43. Go to customer interface and check that file input for uploading acceptance is present.

  44. Upload new customer acceptance and accept installation.

  45. From admin interface validate customer acceptance can be downloaded.

  46. Go to final process step and complete delivery.

  47. Go to customer interface and check that order status is changed to completed.

**Order delivery flow integration with order fields and order organization participants** Details: 1) Support order organization mapping to process step assignee 2) Add fields to map order properties to delivery process step 3) Add form for order questionnaire validation step 4) Add form for installation step 5) Add logic for order questionnaire validation step handling from customer frontend acccount Smoke test: Execute `composer update-db` 1. Login as admin on backend 2. Go to Forms tab and check that new action forms have been imported and also sample form for order delivery process. 3. Duplicate Example process form and rename it as you wish 4. Go to workflow settings and add steps: 1. Validate Customer configuration (uses ACTION: Validate Customer Questionnaire) 2. Procure components (Manual which means no form action is needed) and set that it is not visible for customer 3. Wait for installation to be scheduled and confirmed (Manual) 4. Procure installation (Manual) 5. Installation (ACTION: Complete Installation And Upload Test Protocol) 6. Customer acceptance (ACTION: Customer Acceptance) 7. Customer training (Manual) 8. Set start/stop dates for contracts (Manual) 5. Create two supplier organizations and user for each of them (update user mail in database to our own for test purpose) 6. Create commercial lead organization and user for it (update user mail in database to our own for test purpose) 7. Create customer organization and user for it (update user mail in database to our own for test purpose) 8. Create following simple products 1. Hardware x2 with attached installation guide documents for every one 2. Software x1 3. Installation x2 (different suppliers) 9. Create two bundles 1. One bundle has one installation simple product, both hardware and software products 2. Second bundle has two installation simple products, both hardware and software products 3. Attach template agreement and template questionnaire documents for both bundles 10. Set prices for bundles and make them available for customer to order 11. Login as customer on frontend and order both packages in single order 12. Go to order page and check that new process is available to assign to the order 13. Assign process to order 14. Check that process flow is created 15. Go to process flow page 16. Validate that all steps are present together with automatic (Order placed and Assign process) 17. Validate that `Validate Customer configuration` step is present 18. Check that two workflows are present (one for each bundle) and document can be downloaded 19. Check your email and validate that two emails *Validate Customer Configuration* are received for each validation 20. Open order as customer and check that steps are listed 21. Validate that current active step is `Validate Customer configuration` 22. Validate that both questionnaire documents that customer uploaded are being validated and they can be downloaded 23. Go to admin interface and reject one of the documents and check that next step will ask from you to enter validation reason (enter it and submit). Validate that next step is pending user input form customer. Since you put your email for customer user validate that you received email informing you about rejected document. 24. Go to customer interface and validate that pending action is listed for uploading this file 25. Go to order details and validate that file upload field is present for that file and status is *invalid* 26. Upload new file and validate that status is changed to *not-validate* 27. Go to admin interface and open action workflow for this step and validate that your approval is pending. Also validate that you received email about pending validation for this document. 28. Accept document and validate that workflow for this action is completed 29. Go to customer interface and check that status of that document is *validated* 30. For second validation workflow just accept document and check that status is updated on customer interface. 31. Validate that two mails informing customer that documents are validated got sent. 32. From admin interface go to next step and validate that process workflow went to *Procurement step*. Download Procurement order report and validate that it contains delivery info, billing info, simple products and info about their suppliers. 33. Go to customer interface and validate that this step is not visible on customer interface. 34. From admin interface go trough * Wait for installation to be scheduled and confirmed* to *Installation* step 35. Validate that action step workflows are created 36. Validate that for bundle that had two installation products pending action step is to select one of the installation companies. Select installation company and validate that next step is for installation company to confirm installation. 37. Validate that for bundle that had one installation product pending action step is for installation company to confirm installation is completed. 38. Since you set your email for users of these companies check that you received email informing you that you should confirm that installation is completed. 39. Login as these users and confirm installation. 40. Validate that next step is to upload test protocol. Upload test protocol and validate that action workflow is completed. 41. Go to admin interface to main workflow process and validate both actions are completed. 42. Go to next step *Customer acceptance* and check email is sent for pending customer acceptance upload. 43. Go to customer interface and check that file input for uploading acceptance is present. 44. Upload new customer acceptance and accept installation. 45. From admin interface validate customer acceptance can be downloaded. 46. Go to final process step and complete delivery. 47. Go to customer interface and check that order status is changed to completed.
akrdzic commented 2018-11-03 11:16:01 +01:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 8d4f75cc - Handle process navigation better

Compare with previous version

added 1 commit <ul><li>8d4f75cc - Handle process navigation better</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26497820&start_sha=26f997abbc70a64231f91eabe2c0de55c7a79aca)
akrdzic commented 2018-11-04 11:17:54 +01:00 (Migrated from gitlab.com)
Copy Link

added 28 commits

  • 8d4f75cc...388f7df8 - 27 commits from branch master
  • e8a3668c - Merge branch 'master' into order-delivery-flow

Compare with previous version

added 28 commits <ul><li>8d4f75cc...388f7df8 - 27 commits from branch <code>master</code></li><li>e8a3668c - Merge branch &#39;master&#39; into order-delivery-flow</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26517861&start_sha=8d4f75cc41fb83ade3f141338104b07b192d38b7)
akrdzic commented 2018-11-04 13:20:23 +01:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • a6640548 - Update delivery process fields and sample form

Compare with previous version

added 1 commit <ul><li>a6640548 - Update delivery process fields and sample form</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26519593&start_sha=e8a3668c2594128c93d9a00a102436a89e2c28e0)
akrdzic commented 2018-11-04 13:21:16 +01:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
akrdzic commented 2018-11-04 13:26:44 +01:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
akrdzic commented 2018-11-04 13:27:27 +01:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

Compare with previous version

added 1 commit <ul><li>0b54ce54 - remove procurement order</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26519693&start_sha=a6640548efc6b3bd7fc27d737513c7fd3b211e32)
akrdzic commented 2018-11-04 14:15:10 +01:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

Compare with previous version

added 1 commit <ul><li>3011c494 - remove error logs</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26520823&start_sha=0b54ce54f827eb953a44c7590b7573f588bdb777)
akrdzic commented 2018-11-04 14:51:02 +01:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

Compare with previous version

added 1 commit <ul><li>27795387 - add dependencies</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26521404&start_sha=3011c49474a1cce3b0acc210ea641541442789d1)
akrdzic commented 2018-11-04 14:51:20 +01:00 (Migrated from gitlab.com)
Copy Link

unmarked as a Work In Progress

unmarked as a **Work In Progress**
akrdzic commented 2018-11-04 17:06:51 +01:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 5e55d296 - fix retrieval of process step action entries

Compare with previous version

added 1 commit <ul><li>5e55d296 - fix retrieval of process step action entries</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26523654&start_sha=27795387dfc83b36d13a9cdcf3b683dc68766e41)
akrdzic commented 2018-11-04 17:58:02 +01:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • b7e4f7f4 - Update db migration and remove unused files

Compare with previous version

added 1 commit <ul><li>b7e4f7f4 - Update db migration and remove unused files</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26532607&start_sha=5e55d296e543c984227a1973a7d3b991720a7f33)
akrdzic commented 2018-11-04 18:05:45 +01:00 (Migrated from gitlab.com)
Copy Link

assigned to @bilal.catic

assigned to @bilal.catic
akrdzic commented 2018-11-04 19:55:03 +01:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 1d097eda - Get supplier organization from order item

Compare with previous version

added 1 commit <ul><li>1d097eda - Get supplier organization from order item</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26534489&start_sha=b7e4f7f49b29490729801d58794968b921be955c)
bilal.catic commented 2018-11-04 21:59:13 +01:00 (Migrated from gitlab.com)
Copy Link

typo, missing 'n' in 'has bee rejected'

typo, missing 'n' in 'has bee rejected'
akrdzic commented 2018-11-04 22:14:01 +01:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 4e8b04fa - Handle order files download separately from delivery process files

Compare with previous version

added 1 commit <ul><li>4e8b04fa - Handle order files download separately from delivery process files</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/53/diffs?diff_id=26536620&start_sha=1d097eda6f1bbd38b77ab7f8ab5b5e2fdc0da260)
bilal.catic commented 2018-11-04 23:16:39 +01:00 (Migrated from gitlab.com)
Copy Link

merged

merged
bilal.catic commented 2018-11-04 23:16:40 +01:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit cedd4bf9e9

mentioned in commit cedd4bf9e90695b9cf080ca284eee0539818950b
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
senaduka
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: senaduka/old-new-wiaas#53
Delete Branch "order-delivery-flow"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?