Hi, Sudhir! Here is the wireframe for the "create/edit/track job order' page. This page would differ according to the status of the project, but the concept is the same, so we decided to make one page instead of many.
1)Fields from "Job order name" to "Mini Quiz" are empty when client creates new job order. In all the other statuses all these fields are editable, but after editing it client should receive a notification, that he made changes and the changes will be applied to the project immediately. Changes do not apply to the locations with status "Completed" or "in progress".
2)Locations should have filters. Let's start only with the "Location status" filter, maybe we will add more later. Statuses are : "Not assigned", "In progress", "Completed (awaits approval)", "Completed (approved)" Each location has fields: -Location -Amount -Assigned agent -View report/approve/reject (it can be combined it one field) -Location status
Fields for some locations can be empty (f.e, not assigned location will have an empty "assigned agent" field)
3) On the right side of the page are situated the notes for every field to help the client to understand everything.
4)Not sure where to put the pie chart, but it has to be somewhere
5)We also need an "export order" button , which will allow the client download all the photos, videos and audios and questionnaires made until the moment, he pressed the button.
6)Buttons in the bottom of the page would differ according to the job order status: -When job order will be posted for the first time, buttons "Post order" and "save draft" should be displayed -When client opens the draft for the , buttons "Post order" and "save draft" should be displayed -When job was already posted, only button "Submit changes" should be displayed.
We have a query related to the Location status when it is in "In Progress" as well as "completed" state, i.e, point no 2)
Say we have a Job Jname1 where the Job status is "In Progress"
Jname1 has 4 locations allocated, in which the corresponding location statuses are:-
Location 1 - Not Assigned Location 2 - In Progress Location 3 - In Progress Location 4 - Completed and approved
In this case when client does an edit action, which can be done only when client selects "Not Assigned"(which is Location1), does this mean client can change all the Job order related fields for Location 1 or does this mean on selection of Not assigned, location1 and its amount can be changed or removed. Can you please elaborate more on this?
Victor Metelskiy on August 10, 2012:
<<which can be done only when client selects "Not Assigned">>
Wrong. Changes in the description fields can be made with any filter settings. Changes apply to ALL "not assigned" locations. Client will receive a warning about this and will be able to cancel his action.
Sudhir Kelappan on August 13, 2012:
Hi Victor
One last query,if we apply changes for all location statuses in case when a job status is in "In Progress" state, can you please let us know how should the agents be notified about this, especially in the case when location status is in In progress and Completed state.
When we looked through the flow,
Job name, description and End Date are common for all jobs at different locations.. However, If we change the job name/description,this will affect all locations.
If want to edit description for a job at location alone, we need to keep different description for each location or else we cant track technically.
Victor Metelskiy on August 13, 2012:
Hi Sudhir!
1) Changes don't apply to the locations, that are "in progress", because it is hard to let all the agents know about these changes. Changes only apply to "not assigned tasks.
2)You have it right concerning description edit. If we change the description, it will be different for "not assigned" tasks. I agree, that we need to keep different description for each location. However, there may be another solution.
I would suggest to create a new job order and transfer all "not assigned" tasks to the new job order and leave all "completed" and "in progress" tasks in the old job order. We will elaborate this.
First let me know, what you think about my suggestion.
Sudhir Kelappan on August 13, 2012:
Hi Victor
Related to this suggestion, for every edit in case of a "Not Assigned" scenario for Job Status "In Progress", we have to create a new Job. What happens here is at some point of time, for the same location , many jobs need to be created and there will be lots of approval process in this case.
Sudhir Kelappan on August 13, 2012:
Hi Victor
PFA the revised screen shots.Except for a job when a Job order is "In Progress" status and location "Not Assigned"( as mentioned in top query), we have completed for the remaining
1) Please, place "money limit" field next to the "total amount"
2) I will quote what i have written before:
"Each location has fields: -Location -Amount -Assigned agent -View report/approve/reject (it can be combined it one field) -Location status
Fields for some locations can be empty (f.e, not assigned location will have an empty "assigned agent" field)"
So, the table is always the same, but, depending on the status of task in location, some fields in this table will be empty. Do you understand, what i mean?
Please send us a wireframe with "location status" set at "all"
3) We decided not to let client edit job order at all after it was posted. Job order can only be edited while it is in draft.
4)Please, add "add location" button after the table with the list of locations.
Sudhir Kelappan on August 16, 2012:
Hi Victor
We will make the necessary changes. Regarding point 4 we have already added a Add button for adding new locations. So will there be any need for "Add location" button
Victor Metelskiy on August 16, 2012:
Hi Sudhir!
I can only see it on wireframe #13. There is no such button on wireframes 14, 15, 16,20,21, right?
When client adds location on pages 14, 15, 16, 20, 21, "location status" filter automatically changes to "all".
Once again, please send us a wireframe with "location status" set at "all".
Just to clarify: we decided not to make any changes to the description after the job order was posted. Client still can add/delete locations and edit price.
Sudhir Kelappan on August 16, 2012:
If we either add/delete locations, the corresponding price will be update accordingly. These are the following concerns from our 1. For every update action, the changes should get approved by organizer. 2. Depending on the update action (add/delete), payments need to be tracked accordingly. Since it's an already approved job, organizer will not be in scene of any update action after the approval.
Victor Metelskiy on August 16, 2012:
1)Organizer shouldn't approve locations and prices changes. It is ok. 2)And what is it with the payments? I didn't quite understand it.
Sudhir Kelappan on August 16, 2012:
Hi Victor
PFA the revised screen shots of all Job Status details, which also includes screenshot where location status filter is selected as "All"
I didn't quite understand the client_viewjob(approved) wireframe. On which stage will it be displayed to client? Please, remind me.
About the pie-chart. I think. the pie-chart should always be the same (same parts), but the parts, not chosen in the location filter should be semitransparent.
Everything else is ok.
Sudhir Kelappan on August 20, 2012:
Hi Victor
This screens appears, when the organizer has approved the Job and Job status changes to "Approved" state.
Regarding the pie chart,can you please explain more on that.
We had gone through the comments that was posted by you for the Client interface wire frames(V3.2). Following comment was placed in basecamp:-
Page 15_Client_ViewJob (Approved) This page doesn't exist. The funds are reserved on the client's account right after he posts a task and organizer approves it. No need to make any notifications. The next job status after "Pending" is "In progress"
In our initial discussion, a job status name "Approved" was mentioned in which organizer will approve the job that was sent across by the client and Job status will be updated from "Pending" to "Approved". Also, the Organizer would remain inactive, as he just needs to track record of the Job's progress. Then, Client would submit the approved job to the available agents based on their locations.
And related to the payment, we felt once the organizer has approved a job, only then the client will do the final payment. Which is why this "Approved screen" has been displayed.
Please verify and let us know if any changes need to be implemented.
Victor Metelskiy on August 24, 2012:
Hi Sudhir!
Approved status was mentioned indeed, but it is an interim status in the real time this job order will only be in this status for a few moments.
The payment should be made with a deposit. The money is reserved for the job order when client posts it. Reservation amount = total amount of jobs posted if money limit field is empty, = money limit field if this field is filled.
Reserved means that it will not be allocated to any other projects. The payment will actually be done when agent completes the task execution and it gets approved.
Let me give you an example. Client makes a deposit of 1000$ and posts first job order with total amount of 300$. 300$ will be allocated to this project. So, if client tries to post the second task with total amount of 800$, he will receive a notification, that he has only got 700$ available, because 300$ is allocated to another project.
Sudhir Kelappan on August 24, 2012:
Hi Victor
PFA the screen shot of Completed and Approved status. We had provided earlier in this discussion thread(
Client_ViewJob(Completed&Approved).png) and
Client_ViewJob(JSCompleted).png)
"Please, send us a wireframe for the "completed and approved" task" We ment the report. It should be a bit different from the "completed and awaits approval" report.
Sudhir Kelappan on August 24, 2012:
Hi Victor
PFA the screen short of the View Report module for Completed and approved task
Comments
Sudhir Kelappan on August 6, 2012:
PFA the snapshots of all job listings for all job status in the client interface
Victor Metelskiy on August 9, 2012:
Here is the wireframe for the "create/edit/track job order' page. This page would differ according to the status of the project, but the concept is the same, so we decided to make one page instead of many.
1)Fields from "Job order name" to "Mini Quiz" are empty when client creates new job order. In all the other statuses all these fields are editable, but after editing it client should receive a notification, that he made changes and the changes will be applied to the project immediately. Changes do not apply to the locations with status "Completed" or "in progress".
2)Locations should have filters. Let's start only with the "Location status" filter, maybe we will add more later. Statuses are : "Not assigned", "In progress", "Completed (awaits approval)", "Completed (approved)"
Each location has fields:
-Location
-Amount
-Assigned agent
-View report/approve/reject (it can be combined it one field)
-Location status
Fields for some locations can be empty (f.e, not assigned location will have an empty "assigned agent" field)
3) On the right side of the page are situated the notes for every field to help the client to understand everything.
4)Not sure where to put the pie chart, but it has to be somewhere
5)We also need an "export order" button , which will allow the client download all the photos, videos and audios and questionnaires made until the moment, he pressed the button.
6)Buttons in the bottom of the page would differ according to the job order status:
-When job order will be posted for the first time, buttons "Post order" and "save draft" should be displayed
-When client opens the draft for the , buttons "Post order" and "save draft" should be displayed
-When job was already posted, only button "Submit changes" should be displayed.
Feel free to ask any questions concerning this.
Sudhir Kelappan on August 10, 2012:
We have a query related to the Location status when it is in "In Progress" as well as "completed" state, i.e, point no 2)
Say we have a Job Jname1 where the Job status is "In Progress"
Jname1 has 4 locations allocated, in which the corresponding location statuses are:-
Location 1 - Not Assigned
Location 2 - In Progress
Location 3 - In Progress
Location 4 - Completed and approved
In this case when client does an edit action, which can be done only when client selects "Not Assigned"(which is Location1), does this mean client can change all the Job order related fields for Location 1 or does this mean on selection of Not assigned, location1 and its amount can be changed or removed.
Can you please elaborate more on this?
Victor Metelskiy on August 10, 2012:
Wrong. Changes in the description fields can be made with any filter settings. Changes apply to ALL "not assigned" locations. Client will receive a warning about this and will be able to cancel his action.
Sudhir Kelappan on August 13, 2012:
One last query,if we apply changes for all location statuses in case when a job status is in "In Progress" state, can you please let us know how should the agents be notified about this, especially in the case when location status is in In progress and Completed state.
When we looked through the flow, Job name, description and End Date are common for all jobs at different locations.. However, If we change the job name/description,this will affect all locations.
If want to edit description for a job at location alone, we need to keep different description for each location or else we cant track technically.
Victor Metelskiy on August 13, 2012:
1) Changes don't apply to the locations, that are "in progress", because it is hard to let all the agents know about these changes. Changes only apply to "not assigned tasks.
2)You have it right concerning description edit. If we change the description, it will be different for "not assigned" tasks. I agree, that we need to keep different description for each location. However, there may be another solution.
I would suggest to create a new job order and transfer all "not assigned" tasks to the new job order and leave all "completed" and "in progress" tasks in the old job order. We will elaborate this.
First let me know, what you think about my suggestion.
Sudhir Kelappan on August 13, 2012:
Related to this suggestion, for every edit in case of a "Not Assigned" scenario for Job Status "In Progress", we have to create a new Job.
What happens here is at some point of time, for the same location , many jobs need to be created and there will be lots of approval process in this case.
Sudhir Kelappan on August 13, 2012:
PFA the revised screen shots.Except for a job when a Job order is "In Progress" status and location "Not Assigned"( as mentioned in top query), we have completed for the remaining
Sudhir Kelappan on August 14, 2012:
Sorry for the trouble.
We have again made some changes for the Job details View.
Please look into it and let me know your feedback
Victor Metelskiy on August 15, 2012:
1) Please, place "money limit" field next to the "total amount"
2) I will quote what i have written before:
"Each location has fields:
-Location
-Amount
-Assigned agent
-View report/approve/reject (it can be combined it one field)
-Location status
Fields for some locations can be empty (f.e, not assigned location will have an empty "assigned agent" field)"
So, the table is always the same, but, depending on the status of task in location, some fields in this table will be empty. Do you understand, what i mean?
Please send us a wireframe with "location status" set at "all"
3) We decided not to let client edit job order at all after it was posted.
Job order can only be edited while it is in draft.
4)Please, add "add location" button after the table with the list of locations.
Sudhir Kelappan on August 16, 2012:
We will make the necessary changes.
Regarding point 4 we have already added a Add button for adding new locations.
So will there be any need for "Add location" button
Victor Metelskiy on August 16, 2012:
I can only see it on wireframe #13.
There is no such button on wireframes 14, 15, 16,20,21, right?
When client adds location on pages 14, 15, 16, 20, 21, "location status" filter automatically changes to "all".
Once again, please send us a wireframe with "location status" set at "all".
Just to clarify: we decided not to make any changes to the description after the job order was posted. Client still can add/delete locations and edit price.
Sudhir Kelappan on August 16, 2012:
These are the following concerns from our
1. For every update action, the changes should get approved by organizer.
2. Depending on the update action (add/delete), payments need to be tracked accordingly.
Since it's an already approved job, organizer will not be in scene of any update action after the approval.
Victor Metelskiy on August 16, 2012:
2)And what is it with the payments? I didn't quite understand it.
Sudhir Kelappan on August 16, 2012:
PFA the revised screen shots of all Job Status details, which also includes screenshot where location status filter is selected as "All"
Sudhir Kelappan on August 17, 2012:
PFA the new screenshot of the Approved Job status details
Victor Metelskiy on August 20, 2012:
I didn't quite understand the client_viewjob(approved) wireframe. On which stage will it be displayed to client? Please, remind me.
About the pie-chart. I think. the pie-chart should always be the same (same parts), but the parts, not chosen in the location filter should be semitransparent.
Everything else is ok.
Sudhir Kelappan on August 20, 2012:
This screens appears, when the organizer has approved the Job and Job status changes to "Approved" state.
Regarding the pie chart,can you please explain more on that.
Victor Metelskiy on August 20, 2012:
PFA an example
Sudhir Kelappan on August 24, 2012:
We had gone through the comments that was posted by you for the Client interface wire frames(V3.2).
Following comment was placed in basecamp:-
Page 15_Client_ViewJob (Approved)
This page doesn't exist. The funds are reserved on the client's account right after he posts a task and organizer approves it. No need to make any notifications. The next job status after "Pending" is "In progress"
In our initial discussion, a job status name "Approved" was mentioned in which organizer will approve the job that was sent across by the client and Job status will be updated from "Pending" to "Approved".
Also, the Organizer would remain inactive, as he just needs to track record of the Job's progress.
Then, Client would submit the approved job to the available agents based on their locations.
And related to the payment, we felt once the organizer has approved a job, only then the client will do the final payment.
Which is why this "Approved screen" has been displayed.
Please verify and let us know if any changes need to be implemented.
Victor Metelskiy on August 24, 2012:
Approved status was mentioned indeed, but it is an interim status in the real time this job order will only be in this status for a few moments.
The payment should be made with a deposit. The money is reserved for the job order when client posts it. Reservation amount = total amount of jobs posted if money limit field is empty, = money limit field if this field is filled.
Reserved means that it will not be allocated to any other projects. The payment will actually be done when agent completes the task execution and it gets approved.
Let me give you an example. Client makes a deposit of 1000$ and posts first job order with total amount of 300$. 300$ will be allocated to this project. So, if client tries to post the second task with total amount of 800$, he will receive a notification, that he has only got 700$ available, because 300$ is allocated to another project.
Sudhir Kelappan on August 24, 2012:
PFA the screen shot of Completed and Approved status.
We had provided earlier in this discussion thread( Client_ViewJob(Completed&Approved).png) and Client_ViewJob(JSCompleted).png)
Victor Metelskiy on August 24, 2012:
"Please, send us a wireframe for the "completed and approved" task"
We ment the report. It should be a bit different from the "completed and awaits approval" report.
Sudhir Kelappan on August 24, 2012:
PFA the screen short of the View Report module for Completed and approved task
Victor Metelskiy on August 24, 2012:
1)Put location name and agent name in the top of the page.
2)Please add agent's rating from client. (It was already approved)
Sudhir Kelappan on August 24, 2012:
PFA the screen shot for view Report
Changes have been made as per your feedback
Victor Metelskiy on August 24, 2012:
Please also add "Download task" button.
Sudhir Kelappan on August 30, 2012:
Can you please let us know what is the usage of "Download Task" button?
Victor Metelskiy on August 30, 2012:
Can you please let us know what is the usage of "Download Task" button?
To download all the pictures and questionnaire.
Sudhir Kelappan on August 30, 2012:
Thank you for the query.
We will implement the changes
Sudhir Kelappan on August 30, 2012:
PFA the revised screen shot of the View Report.
Position has been placed accordingly to maintain consistency.
Victor Metelskiy on August 30, 2012: