roos-fs tasks #488
Updated by Vadim Pariev 7 months ago
Underneath you would find the flow that is to be implimented on the backend side. THe same have to be applicabe on the Mobile end. ATTENTION Make sure that the old services created before the new feature release are still working. SERVICES and TASKS FLOW desciption the service when created receives the status CREATED the tasks in this service receive the state CREATED the service is then manually transferred to the stated BOOKED (the user is OBLIGED to set the date - it is mandatory. P.S. reuse the same form that was used for the task when set to the boked state) the tasks are AUTOMATICALLY change the status to OPEN from the OPEN state the user can set the planned date (OPTIONALLY) from the OPEN state with or without a date the user can set the task in status IN PROGRESS from IN PROGRESS the tasks can be set to COMPLETED the service could be set to COMPLETED only if all Tasks are in CANCELLED or COMPLETED state (there could be 1 in cancelled and 1 in completed so simply all tasks in one of the states) The task could be cancelled from any status starting from the OPEN Service can be cancelled at any time and the tasks would be outo cancelled FURTHER REQUIREMENTS Adjust the API for mobile and remove unnessesary endpoints. The main point is that the API for the mobile is mirrowing the Behaviour in web. Expected behaviour cancellation logic remain intact completion triggers the report creation activity log remains the same data validations from the tasks is removed all views of the tasks adn services remain the same old statuses are removed if not used All validations inside of the taks remains