Open achille005 opened 7 years ago
No , I am not Saving the data in database from Screen to Screen .But data is saved locally from Screen to Screen and validations also , data insert in database n the last page after satisfying all validation of client side .
That is good! That way you can restructure the UI, without really impacting the backend.
Sorry Previous comment was also done by me with my another account
I think while saying backend you are considering only database right ?
but we need to check many things like on every page all required fields should be filled ,previous page should be filled, when we go back data should not clear , server side logic will be change .When we change in the Css it might effect the css of other element we need to check that also .
by backend i meant the objects and the tables in which you are saying those objects... those should still the same, but of course because you are introducing new pages, you will need to do some validation and front end twinkling. NOTE: this change has to go in before the first release because it was based on feedbacks... It is ok if it took couple more days to get it right - it will impact the deadline. Ok. Should we consider as new feature. no. I agree it requires additional effort from your part but it is to get the original design right. It is up to us to be generous about that effort and we will :-)
Thanks Achille,
The payment flow You can check Payment flow
The Search Algorithm Please Specify on which task you are pointing
social media Sure, I will double check that
Please Specify on which task you are pointing the query that compare that match Jobsseeker to a recruiter and vice versa.. ( see suggested pseudocode)
Which Credential you are using and Please check if payment is not done Previously for that account.
If you have been saving the data into database from screen to screen or you save the data to db after the last screen?