Feature #644

add an order validation process

Added by Mérour Xavier over 5 years ago. Updated about 4 years ago.

Status:ClosedStart date:07/17/2015
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:SHOP
Target version:4.3.0
Sponsor: Ergonomic impact:
Functional impact:

Description

If an order is done with a third party (organism), this third party have to validate the order BEFORE it is sent to the supplier(s).

  • in backend

- add a new role "validation manager" in the "user" screen, tab "role" (the user can have the role in 0 to n organisms)

- in the organism management, there is a toggle for setting "can be selected as a third party" yes/no (it replaces the "eligible to order to" which has to be removed - see #700).

  • in frontend

- a new screen where the validation manager will be able to validate or reject an order done with third party = its organism
see gliffy attached 7.
--> with this, a new "remark" field must be attached to each order

- remark must be displayed in order's resume

- a notification email is send to the all the validation manager in the organism (third party selected) with a permalink (without any login) to the page with the order detail (see gliffy) 7.1

- in the basket, there will be possible to select the tiers. If one selected, three extra fields will appear below (see basket layout attached in #643 ). those fields are mandatory
the third party selec only appears if at least one organism is "can be selected as a third party" (toggle above)
the visibility of the 3 extra fields should be optionnal (in the backend)

- on the basket a texte can be added to give some explanations about third-party (the text is definable in the backend in SHOP parameters, juste like we have already one)

- it implies adding two new states in treatment order ("waiting to be validated" and "rejected" when defining tierce orgsnism) which have impact upon SHOP web service

- if rejected an email notification is sent to the order's author with reject's reason (remark)

7_gliffy_validation-screens.png (48.3 KB) Mérour Xavier, 04/24/2014 03:32 PM


Subtasks

Defect #1061: Orders status managmentClosed


Related issues

Related to easySDI - Defect #700: "Eligible to order to" - what is it exactly ? Closed

History

#1 Updated by Mérour Xavier over 5 years ago

Here are the screens (gliffy 7 and 7.1) coming along with description done above

#2 Updated by Mérour Xavier over 5 years ago

  • Description updated (diff)

#3 Updated by Magoni Bruno over 5 years ago

  • Priority changed from Normal to High

#4 Updated by Magoni Bruno over 5 years ago

  • Target version set to 150

#5 Updated by Mérour Xavier over 5 years ago

To the PSC.

The feature is ready to be coded in EasySDI : please vote !

#6 Updated by Mérour Xavier over 5 years ago

+1 for me

#7 Updated by Magoni Bruno over 5 years ago

+1

#8 Updated by Teixeira Jérôme over 5 years ago

+1

#10 Updated by Magoni Bruno over 5 years ago

  • Target version changed from 150 to Unplanned

#11 Updated by Magoni Bruno about 5 years ago

  • Status changed from New to Accepted

#12 Updated by Magoni Bruno about 5 years ago

  • Description updated (diff)

#13 Updated by Magoni Bruno about 5 years ago

  • Description updated (diff)

#14 Updated by Magoni Bruno about 5 years ago

  • Description updated (diff)

#15 Updated by Magoni Bruno about 5 years ago

  • Assignee changed from Magoni Bruno to Villemagne Jérôme

#16 Updated by Magoni Bruno about 5 years ago

  • Status changed from Accepted to Affected

#17 Updated by Magoni Bruno about 5 years ago

  • Target version changed from Unplanned to 158

#18 Updated by Blatti Yves about 5 years ago

The Gliffy flow that has been discussed when describing specs was not incorporated in the issue (omission).
You can find it in the wiki (a page has been created, as it'll be used as documentation in future),
here : https://forge.easysdi.org/projects/easysdi/wiki/4_shop_orders_and_products_status

#19 Updated by Villemagne Jérôme about 5 years ago

  • % Done changed from 0 to 50

#20 Updated by Villemagne Jérôme about 5 years ago

  • % Done changed from 50 to 60

#21 Updated by Villemagne Jérôme about 5 years ago

  • % Done changed from 60 to 50

#22 Updated by Magoni Bruno over 4 years ago

  • Target version changed from 158 to 4.3.0

#23 Updated by Villemagne Jérôme over 4 years ago

  • Status changed from Affected to Resolved

#24 Updated by Villemagne Jérôme over 4 years ago

  • Status changed from Resolved to Closed

#25 Updated by Van Hoecke Hélène about 4 years ago

  • Assignee deleted (Villemagne Jérôme)

Also available in: Atom PDF