Challenge Summary
Welcome to "ABC - Portal Missing details Wireframe Challenge". In this challenge, we need your help to create wireframes that able to define the best user experience and workflow for our new Missing Info Portal. The expectation is that all the queries will be logged through this portal in a standardized manner, removing email, Skype or phone requests logging, and having instant reporting capabilities.
We are looking for your ideas and the best user experience. Ask any questions in the forum, and have fun!
01) Login (All Roles)
02) Delivery User Features
03) Management User Features
04) Contract Admin Features
05) Super User Features
- Note: Submit as much application features as you can for early review.
01) Login (All Roles)
02) Delivery User Features
03) Management User Features
04) Contract Admin Features
05) Super User Features
- Note: please address Checkpoint Feedback for your Final Round Submission
Background Overview
Our Business has reported revenue leakages due to the number of unbilled documents and the lack of visibility on the owner of the pending actions for overdue invoicing cases. Invoicing backlog completion depends on getting the missing information from many parties and the inputs/feedback cannot be automatically tracked. Workflow management and customer follow up are challenges for Operations due to manual interactions and obsolete ticket management technology using SharePoint.
Challenge Goal
Create a Missing details Portal workflow for all user roles that able to:
- Manage and process all missing info queries for invoicing in a standardized manner
- Able to remove email, Skype or phone requests logging
- Improves our way to provide reporting, tracking and managing query
Challenge Forum
If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum:
https://apps.topcoder.com/forums/?module=ThreadList&forumID=630727
Flow and UX Consideration
- Focus on general navigation between all required screens and functionalities
- Easy and intuitive use for tech and non-tech users.
- The target device for this application is Web/Desktop.
- We are looking for your ideas here!
Wireframe Expectations
- You must create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- The application must be very easy to use and intuitive. Keep that in mind when creating your solution for the layout and flow information
Screen/Features Requirements
01) Login (All Roles)
- All Users will have to log into the portal using their company credentials (Emp ID + Virtual badge pin)
- We needs to provide login error scenario
- Global login form, the user roles will be managed by the back end (Delivery user, Management User, Contract Admin, or Super User)
02) Delivery User Features
- After successful login, Delivery User will see a dashboard screen and will be able to see all the missing info queries that were assigned to their names
- Basically, This app will do a lookup in the DB and display only those queries that have the User's email address filled in the "SDM" field
- The queries assignment by default will be done by a contract admin using the online standardized form for raising queries to ADMs/SDMs/Client Managers or a desktop automation which will upload the requests directly into the portal DB
- The Delivery User roles will be able to do the following features on the queries:
-- Sort/filter based on all the fields available in the header view
-- To expand the view and see additional queries details
-- To download any attached file in the queries
-- To export the queries data in .xls format
-- To re-assign queries to a different Delivery User, if somehow it wrongly assigned by the CA or Management User
-- To add "Watchers" to any of the open queries
-- Select multiple queries and answer all of them at once; the comment and attachments for all answered queries will be common.
- If the Delivery User is a back-up for other Delivery Users, they will have the option to select "See all queries" and filter based on the assigned to/requestor name, and then they will be able to re-assign the open queries to themselves in order to be able to respond or receive responses for those ones.
- When clicking on the "See all queries" button, all the queries with "New" and "Open" status will be visible on the Delivery User screen, even if they are assigned to another person. Only the "SDM" field will be editable and the Delivery User will have the possibility to re-assign the queries on the Delivery Username by changing the email address in the "SDM" field. Then all the fields will become editable and the Delivery User will be able to respond to them
- The Delivery User should be allowed to do single or multiple selections for the re-assignment features
- Expandable view, This option (can be via button, or else) will allow Delivery Users to expand the user view and see all the details/fields that will be available for each and every queries.
- Responding single queries, When clicking on the Queries ID hyperlink, a pop-up screen will show up; all the details of that queries will be displayed, as described in the data documentation. Any text added in the Comments field will be stored in the DB on the "SDM comments" field. Any file attached by the Delivery User (SDM) will be stored in the DB in the "attachments" field. Once clicking on the "Submit" button, the portal will update the field "Status" in the DB, from Open to Closed
- Rejecting single queries, The Delivery User will be able to add the response comments in a comments field. When clicking on the "Reject" button, the list of "Rejection reasons" will pop-up and the user will have to select one in order to be able to close the query. The comments and the rejection reason will have to be updated in the "comments" and "Rejection reason" fields, that should be done via the interface and directly connected with the DB. Closure timestamp will also be captured in the "Closed time & date" field and the "Status" field will be changed from Open to Rejected.
- Multiple queries closure, When clicking on "Respond multiple queries" button, a selection box will be made available for each and every open queries. When selecting multiple lines and clicking on "Respond" the responding pop-up screen will show-up, displaying the list of selected queries. The "Comments", "Attachments" and "Rejection reason" (where applicable) will be common for all selected queries and will be stored in the DB accordingly. When clicking on "Submit"/"Reject", the "Status" field value will have to be updated in the DB for all the selected queries.
- When clicking on Download, the portal app will record the fields from the Delivery User view (it might be expanded or collapsed view) and allow the user to save a .csv / .xls offline copy. If data is filtered on the user screen, the .csv file will contain only the filtered data.
- Need to be able to view all the opened queries,f with their due-dates, and generate a report out of it
- Need to be able to view all aged queries by country, owner, team, query type
- Need features to receive notifications for new/pending queries
03) Management User Features
- View all Open/Closed/Rejected Queries
- Re-assign Open Queries to Delivery User
- Extract/Generate/Download Reports
04) Contract Admin Features
- The app will check into the DB and display only those queries that have the user's email address filled in the "Requestor" field (saw only data assigned to the Contract Admin)
- Single Queries creation, Contract Admin (CA) will have the ability to log into the portal, access an online request form and update all the fields related to my missing information query (you can find the list of fields marked in green below in the "Data Fields" embedded file). If any additional information will be needed, they will have the ability to attach documents. they will have a button for creating new individual queries, which will open a pop-up screen with an online form, containing the fields marked with Green in the documentation file. The Submit button on the form will automatically update a new entry in the DB and will record timestamps
- Bulk Queries creation, A desktop automation (xls macro tool) will have to be able to connect to the portal DB and write new entries; creation timestamps will have to be updated on the entries. Contract Admin will have various contracts with missing information and they will want to send all the queries at once, Contract Admin will access the Desktop automation app, import all open invoicing tickets from the SharePoint, select the ones with Missing Information and update the "Query type", "Comments" and attach files (if needed). Then they will click on "Create Portal queries" and the app will connect to the Portal DB and create a list of queries. Once done, the server/app will send a completion report, to ensure that all missing info queries have been created.
- Bulk Queries creation fallouts, If there's going to be any error during the bulk query creation process, the portal will have to send an email to the requestor, referencing the items that were not created. Assumption: the desktop automation will use CA email addresses when connecting to the DB
- Create with reference, Contract Admin (CA) will have the ability to create a new queries on the Portal, with reference to a closed/rejected one. All the details, except for Attachments, from the referenced query will be copied to the new query.
- Expandable view, This option (button) will have to allow Contract Admin to expand their view and see all the details/fields that will be available for each and every queries.
- When clicking on Download, the portal will record the fields from the Contract Admin view (it might be expanded or collapsed view) and allow the user to save a .csv / .xls offline copy. If data is filtered on the CA screen, the .csv file will contain only the filtered data.
- Contract Admin (CA) will be able to "Download Report" in .xls format for the selection that they are currently viewing.
- Need the ability to upload attachments as user input method;
- Need the ability to upload attachments when responding in pop-up screen.
- Needs to be able to see all submitted queries
- Re-assign open queries
- Receive notifications for closed/rejected queries
- Extract reports
05) Super User Features
- E-mail notifications, Set Delivery and Management User email notification, The portal will have scheduled batch jobs (the frequency has to be defined; assumption: twice per day) which will lookup in the DB and retrieve all the queries with "New" and "Open" status assigned to each Delivery User (SDM) user. Then will send an email to each user, providing the number of "New" and "Open" queries for each "Query Type"
- E-mail notifications, Set Contract Admin user email notification, The portal will have scheduled batch jobs (the frequency has to be defined; assumption: twice per day) which will lookup in the DB and retrieve all the queries with "Closed", "Rejected" and "Open" status. Then will send an email to a generic email address, providing the number of "Closed", "Rejected" and "Open" queries for each "Requestor"
- The Business logic will be maintained in a table; we need the ability to update the table in the Front-end, not in the DB.
- TAT based on SLA table – should be updated in front by Super User
Documentation
- Download All Documentation from this link: https://drive.google.com/drive/folders/17BrOxsnzf19gWfbzi6BL9rmGqqmKBh-N?usp=sharing
New to axure RP, get started right-away!!
- Here are some quick tutorials to help you get started: http://www.axure.com/support
Screen Size
- Desktop: 1366px(w) & height up to your design
Target Audience
- Contract Admin User
- Delivery User
- Management User
- Super-user
Judging Criteria
- User experience and information architecture
- Expanding upon and creating unique features for the provided concepts
- Visual-driven, clear, concise, and meaningful data display
- Capture all the required fields on every page
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
- IMPORTANT! Make sure all the content is listed and the pages are linked together to show page flow.
- Wireframes should be clickable and can be opened in all major browser without issue (HTML/CSS/JS).
- Keep your source files out from this submission folder.
Source Files
- All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file
- You can built the wireframes using Plain HTML/CSS/JS or you can generate from Axure application. Other option is using Sketch with Black/White theme (needs to be clickable).
Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.
We are looking for your ideas and the best user experience. Ask any questions in the forum, and have fun!
Round 1
Initial Wireframe for these following features:01) Login (All Roles)
02) Delivery User Features
03) Management User Features
04) Contract Admin Features
05) Super User Features
- Note: Submit as much application features as you can for early review.
Round 2
Final Wireframe for these following features:01) Login (All Roles)
02) Delivery User Features
03) Management User Features
04) Contract Admin Features
05) Super User Features
- Note: please address Checkpoint Feedback for your Final Round Submission
Background Overview
Our Business has reported revenue leakages due to the number of unbilled documents and the lack of visibility on the owner of the pending actions for overdue invoicing cases. Invoicing backlog completion depends on getting the missing information from many parties and the inputs/feedback cannot be automatically tracked. Workflow management and customer follow up are challenges for Operations due to manual interactions and obsolete ticket management technology using SharePoint.
Challenge Goal
Create a Missing details Portal workflow for all user roles that able to:
- Manage and process all missing info queries for invoicing in a standardized manner
- Able to remove email, Skype or phone requests logging
- Improves our way to provide reporting, tracking and managing query
Challenge Forum
If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum:
https://apps.topcoder.com/forums/?module=ThreadList&forumID=630727
Flow and UX Consideration
- Focus on general navigation between all required screens and functionalities
- Easy and intuitive use for tech and non-tech users.
- The target device for this application is Web/Desktop.
- We are looking for your ideas here!
Wireframe Expectations
- You must create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- The application must be very easy to use and intuitive. Keep that in mind when creating your solution for the layout and flow information
Screen/Features Requirements
01) Login (All Roles)
- All Users will have to log into the portal using their company credentials (Emp ID + Virtual badge pin)
- We needs to provide login error scenario
- Global login form, the user roles will be managed by the back end (Delivery user, Management User, Contract Admin, or Super User)
02) Delivery User Features
- After successful login, Delivery User will see a dashboard screen and will be able to see all the missing info queries that were assigned to their names
- Basically, This app will do a lookup in the DB and display only those queries that have the User's email address filled in the "SDM" field
- The queries assignment by default will be done by a contract admin using the online standardized form for raising queries to ADMs/SDMs/Client Managers or a desktop automation which will upload the requests directly into the portal DB
- The Delivery User roles will be able to do the following features on the queries:
-- Sort/filter based on all the fields available in the header view
-- To expand the view and see additional queries details
-- To download any attached file in the queries
-- To export the queries data in .xls format
-- To re-assign queries to a different Delivery User, if somehow it wrongly assigned by the CA or Management User
-- To add "Watchers" to any of the open queries
-- Select multiple queries and answer all of them at once; the comment and attachments for all answered queries will be common.
- If the Delivery User is a back-up for other Delivery Users, they will have the option to select "See all queries" and filter based on the assigned to/requestor name, and then they will be able to re-assign the open queries to themselves in order to be able to respond or receive responses for those ones.
- When clicking on the "See all queries" button, all the queries with "New" and "Open" status will be visible on the Delivery User screen, even if they are assigned to another person. Only the "SDM" field will be editable and the Delivery User will have the possibility to re-assign the queries on the Delivery Username by changing the email address in the "SDM" field. Then all the fields will become editable and the Delivery User will be able to respond to them
- The Delivery User should be allowed to do single or multiple selections for the re-assignment features
- Expandable view, This option (can be via button, or else) will allow Delivery Users to expand the user view and see all the details/fields that will be available for each and every queries.
- Responding single queries, When clicking on the Queries ID hyperlink, a pop-up screen will show up; all the details of that queries will be displayed, as described in the data documentation. Any text added in the Comments field will be stored in the DB on the "SDM comments" field. Any file attached by the Delivery User (SDM) will be stored in the DB in the "attachments" field. Once clicking on the "Submit" button, the portal will update the field "Status" in the DB, from Open to Closed
- Rejecting single queries, The Delivery User will be able to add the response comments in a comments field. When clicking on the "Reject" button, the list of "Rejection reasons" will pop-up and the user will have to select one in order to be able to close the query. The comments and the rejection reason will have to be updated in the "comments" and "Rejection reason" fields, that should be done via the interface and directly connected with the DB. Closure timestamp will also be captured in the "Closed time & date" field and the "Status" field will be changed from Open to Rejected.
- Multiple queries closure, When clicking on "Respond multiple queries" button, a selection box will be made available for each and every open queries. When selecting multiple lines and clicking on "Respond" the responding pop-up screen will show-up, displaying the list of selected queries. The "Comments", "Attachments" and "Rejection reason" (where applicable) will be common for all selected queries and will be stored in the DB accordingly. When clicking on "Submit"/"Reject", the "Status" field value will have to be updated in the DB for all the selected queries.
- When clicking on Download, the portal app will record the fields from the Delivery User view (it might be expanded or collapsed view) and allow the user to save a .csv / .xls offline copy. If data is filtered on the user screen, the .csv file will contain only the filtered data.
- Need to be able to view all the opened queries,f with their due-dates, and generate a report out of it
- Need to be able to view all aged queries by country, owner, team, query type
- Need features to receive notifications for new/pending queries
03) Management User Features
- View all Open/Closed/Rejected Queries
- Re-assign Open Queries to Delivery User
- Extract/Generate/Download Reports
04) Contract Admin Features
- The app will check into the DB and display only those queries that have the user's email address filled in the "Requestor" field (saw only data assigned to the Contract Admin)
- Single Queries creation, Contract Admin (CA) will have the ability to log into the portal, access an online request form and update all the fields related to my missing information query (you can find the list of fields marked in green below in the "Data Fields" embedded file). If any additional information will be needed, they will have the ability to attach documents. they will have a button for creating new individual queries, which will open a pop-up screen with an online form, containing the fields marked with Green in the documentation file. The Submit button on the form will automatically update a new entry in the DB and will record timestamps
- Bulk Queries creation, A desktop automation (xls macro tool) will have to be able to connect to the portal DB and write new entries; creation timestamps will have to be updated on the entries. Contract Admin will have various contracts with missing information and they will want to send all the queries at once, Contract Admin will access the Desktop automation app, import all open invoicing tickets from the SharePoint, select the ones with Missing Information and update the "Query type", "Comments" and attach files (if needed). Then they will click on "Create Portal queries" and the app will connect to the Portal DB and create a list of queries. Once done, the server/app will send a completion report, to ensure that all missing info queries have been created.
- Bulk Queries creation fallouts, If there's going to be any error during the bulk query creation process, the portal will have to send an email to the requestor, referencing the items that were not created. Assumption: the desktop automation will use CA email addresses when connecting to the DB
- Create with reference, Contract Admin (CA) will have the ability to create a new queries on the Portal, with reference to a closed/rejected one. All the details, except for Attachments, from the referenced query will be copied to the new query.
- Expandable view, This option (button) will have to allow Contract Admin to expand their view and see all the details/fields that will be available for each and every queries.
- When clicking on Download, the portal will record the fields from the Contract Admin view (it might be expanded or collapsed view) and allow the user to save a .csv / .xls offline copy. If data is filtered on the CA screen, the .csv file will contain only the filtered data.
- Contract Admin (CA) will be able to "Download Report" in .xls format for the selection that they are currently viewing.
- Need the ability to upload attachments as user input method;
- Need the ability to upload attachments when responding in pop-up screen.
- Needs to be able to see all submitted queries
- Re-assign open queries
- Receive notifications for closed/rejected queries
- Extract reports
05) Super User Features
- E-mail notifications, Set Delivery and Management User email notification, The portal will have scheduled batch jobs (the frequency has to be defined; assumption: twice per day) which will lookup in the DB and retrieve all the queries with "New" and "Open" status assigned to each Delivery User (SDM) user. Then will send an email to each user, providing the number of "New" and "Open" queries for each "Query Type"
- E-mail notifications, Set Contract Admin user email notification, The portal will have scheduled batch jobs (the frequency has to be defined; assumption: twice per day) which will lookup in the DB and retrieve all the queries with "Closed", "Rejected" and "Open" status. Then will send an email to a generic email address, providing the number of "Closed", "Rejected" and "Open" queries for each "Requestor"
- The Business logic will be maintained in a table; we need the ability to update the table in the Front-end, not in the DB.
- TAT based on SLA table – should be updated in front by Super User
Documentation
- Download All Documentation from this link: https://drive.google.com/drive/folders/17BrOxsnzf19gWfbzi6BL9rmGqqmKBh-N?usp=sharing
New to axure RP, get started right-away!!
- Here are some quick tutorials to help you get started: http://www.axure.com/support
Screen Size
- Desktop: 1366px(w) & height up to your design
Target Audience
- Contract Admin User
- Delivery User
- Management User
- Super-user
Judging Criteria
- User experience and information architecture
- Expanding upon and creating unique features for the provided concepts
- Visual-driven, clear, concise, and meaningful data display
- Capture all the required fields on every page
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
- IMPORTANT! Make sure all the content is listed and the pages are linked together to show page flow.
- Wireframes should be clickable and can be opened in all major browser without issue (HTML/CSS/JS).
- Keep your source files out from this submission folder.
Source Files
- All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file
- You can built the wireframes using Plain HTML/CSS/JS or you can generate from Axure application. Other option is using Sketch with Black/White theme (needs to be clickable).
Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.