Challenge Summary
Welcome to "Appirio - Workday Data Toolkit Wireframes Challenge". This challenge purpose is to create flow for our upcoming data management application. We are looking forward to see your wireframes expertise in this challenge to create our application flow.
At the end of this wireframe challenge, we are looking to have a complete solution for the User Experience and flow of the application.
Round 1
1. Site Administrator Scenario.
2. Project User Scenario (1 - 7).
Round 2
All requirements as stated in challenge details with client feedback applied
The purpose of the challenge is to create a wireframes that give us solutions for user experience based on a few scenarios given below.
Appirio's Workday Practice would like to develop a Data Management application for assistance in Workday implementation projects. For more information about Workday Application, please read this link.
There are a set of data-related tasks which the practice is hoping to automate :
1. Producing a Schema Definition/Data Dictionary for a project
2. Producing Data Gathering workbooks for a project
3. Validating data from data gathering workbooks.
4. Mapping data from data gathering workbooks to ILoad sheets
5. Transforming data gathering workbooks to ILoad sheets.
This challenge will be focused on the first 3 high level requirements mentioned above. There are two scenarios needs to be create in this challenge, Please read more below to see details requirements :
Site Administrator Scenario :
1. Login to System using username/password. Please create error login condition too.
2. Site Administrators should be able to create users and assign users to projects.
3. Site Administrators will create projects.
4. There should be an admin interface which lists all projects in the system and allows the administrator to navigate to them.
5. There should be an admin interface which lists all users in the system and show which projects they’re assigned to.
Project User Scenario :
1. Login to System user username/password. Please create error login condition too.
2. User should only see projects to which they are assigned in the homepage.
3. User will be able to selects the project which he/she is working with in the homepage and and then viewing the different files by type – for ex. View different files in a directory structure (up to your judgement).
4. User will have an ability to load and retreive several different kinds of files which are :
- Data Gathering Workbooks,
- Schema Definitions
- Validation Reports
- Data Mapping Files and ILoad Templates (not necessary for this wireframes).
5. User should be able to perform search, so please provide a search feature in homepage as well to allow users to find a particular project, or files related to a particular entity (e.g. workers, or locations).
6. User will have an ability in the system to create schema definitions from user or Workday provided-excel files. Workday-provided Data Gathering Workbooks will typically provide the raw list of objects and fields that will be used in a particular implementation. There should be read and load ability in the system to open provided (excel) data workbooks to generate schema definitions. In a schema definition file the following fields of data are tracked about each data field in the workbook:
Name (e.g. FirstName, Street Address)
Object Type (e.g, Home Address Data)
Data Type (e.g, String, Number, Date, Boolean)
Format Mask (e.g, MM/dd/yyyy)
Required
Customer Field Name
Description
Name, Object Type, Data Type, Format Mask, and Required are provided by the upload, but all the fields should be editable to users. We're collecting data here about fields of data so the terminology gets a little confusing. User then will interact with the schema definition content that comes from data workbook to generate a new data gathering workbooks, Then it will be combined using some sort of mapping interface to generate the ILoad files. (mapping and Iload is not necessary for this challenge).
7. Users should have ability to manually add and edit fields into schema definitions. Input options for things like field types and date formats should be limited.
8. Please Include field definitions and context in the Schema definition. workday includes a large number of fields but each system/organization has its own definitions. Our dictionaries should include description fields so consultants can provide context
9. User should able to produce data gathering templates – excel documents (data workbook) after interacted with the schema definitions..
10. Ability to remove fields from schema defintion. Workday data gathering sheets provide large number of fields BUT only a subset are actually required.
11. Ability to override field name/column header in data gathering workbook output. Often WD terminology can be confusing. Sometime better for consultants to put column headers in client terms
12. The application will encrypt all customer data stored
13. Projects will have a workspace or directory structure where files type of different types are stored: Schema Files (or Data Dictionaries), Validation Reports, and Data Gathering Templates. (Later to add mapping documents and ILoad templates.)
14. User should be able to select Schema Definition/ Data Dictionary templates from previous projects.
15. Generate reports on validation errors
16. We need some Fields validation in the system to determine if a specific value in a data gathering document contains a valid value from a list. For example, a valid Country ISO values in the Country ISO field such as 'USA' or 'GBR'. There will need to be reference in the validation definition of the location of the list of valid values. If a field doesn't contain a valid value then we'll produce a summary report which shows statistics about the errors. We'll clone the loaded data (in excel format) -- assuming it was loaded into the application from excel - highlight the cell with the malformed data and put a comment in an "error" column. Besides that validation example, we also need more validations in the system :
- Boolean Field validation - Determine if specific data gathering document contains boolean values in the correct formats. iLoad sheets only accept Y|N for a boolean value. If a field doesn't contain the required boolean value then we'll produce a summary report which shows statistics about the errors. We'll clone the loaded data (in excel format) -- assuming it was loaded into the application from excel - highlight the cell with the malformed data and put a comment in an "error" column
- Date Format validation - Determine if specific data gathering document contains date values in the correct date formats. If a loaded document erroneously formed date values then we'll produce a summary report which shows statistics about the errorrs. We'll clone the loaded data (in excel format) -- assuming it was loaded into the application from excel - highlight the cell with the malformed data and put a comment in an "error" column
- Enumerated Value validation - Determine if a specific value in a data gathering document contains a valid value from a list. For example, a valid Country ISO values in the Country ISO field such as 'USA' or 'GBR'. There will need to be reference in the validation definition of the location of the list of valid values. If a field doesn't contain a valid value then we'll produce a summary report which shows statistics about the errors. We'll clone the loaded data (in excel format) -- assuming it was loaded into the application from excel - highlight the cell with the malformed data and put a comment in an "error" column
- Data Mask/Format validation - Let's allow users to define a mask or format for a certain text, numeric or currency value. _For example, we could define a mask of "#####" to validate postal codes or a mask of "###-####" to validate US phone numbers. It would also be helpful if we could make these validations conditional. For example, we might only want to mask for a postal code of "#####" only if ISO Country Code of record = "USA". If a field doesn't contain properly formatted value then we'll produce a summary report which shows statistics about the errors. We'll clone the loaded data (in excel format) -- assuming it was loaded into the application from excel - highlight the cell with the malformed data and put a comment in an "error" column. We should also created the capability of specifying "OR" validations. For example US postal codes might be valid in 5 digit or nine digit format: "#####" or "#####-####".
17. When users edit a file or create a new file, the files should appear in the directory structure in the appropriate place by file type, along with a timestamp and the user that modified the file last.
18. Each project folder (Data Gathering Workbooks, Validation Reports, Schema Definitions) when clicked should display a lists of files, the size of the file in bytes, kb, or mb, when they were last modified, and who modified the file last. The list should be sortable by each header.
IMPORTANT : Check our requirement clarification documents attached in challenge attachment for more information about the system flow. Got any questions or needs clarification? Post in forum and let's discuss it with us.
Target Audience
Appirio's Workday Practice Internal Team
Judging criteria
Your submission will be judged on the following criteria:
- User experience
- Completeness and accuracy of the areas of functionality and content
- Any additional scenarios which you come up with
- How well your wireframes provide a consistent user flow and clear information architecture for the application
Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
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.