Challenge Overview
1. ��SFDC login credentials used for security
2. �����Add to Home Screen��� pop on initial login into the app
3. ��Default view of all open Opportunities permissioned to view by the user
4. ��Opportunities list defaults in order of probability, but sortable by CloseDate and Forecast Category as well
5. ��User can filter Accounts with Opportunities by
�� �� �� 5.1 ��Alphabet
�� �� �� 5.2 ��Probability
�� �� �� 5.3 ��Opportunity $$ amount
�� �� �� 5.4 ��Opportunity Owner
�� �� �� 5.6 ��Close Date
�� �� �� 5.7 ��Forecast Category
6. ��User taps on Opportunity and Opportunity detail screen appears
7. ��Opportunity Detail Screen contains:
�� �� �� 7.1 �� Opportunity Name
�� �� �� 7.2 �� Account Name
�� �� �� 7.3 �� Account Executive Assigned to Account Opportunity Owner
�� �� �� 7.4 �� Opportunity Owner Telephone # (user taps to call #)
�� �� �� 7.5 �� Opportunity Owner ��Email (user taps to send email using native iOS mail app)Opportunity $$ Amount
�� �� �� 7.6 �� Probability
�� �� �� 7.7 �� Forecast Category
�� �� �� 7.8 �� Current Stage
�� �� �� 7.9 �� Description
�� �� �� 7.10 ��Next Step
�� �� �� 7.11 ��Competitor
8. ��User can easily navigate back and forth from Opportunity list screen and Opportunity detail screen
Technical Requirements
9. �� Account object should have the following custom fields to support the mapping:
10. ��Please use the attached pdf files for the look & feel of the component and follow style guidelines in attached Mobile HTML Best Practices document
11. ��Built to work on tablet devices such as iPad, Samsung Galaxy, etc.
12. ��Built as a VF component.
13. ��Works with jquery and the jquery mobile framework.
14. ��Any logic should be done in the VF component (including Javascript). �� We don't want to get data from Controllers into VF. Please use RemoteAction Apex to get data directly to Javascript.
15. ��Please add any javascript and CSS into the same VF Component so its an all encompassing component. ��If an init javascript call is required outside of the component, that is ok. A callback function upon completion of init tasks is required.
16. ��App should automatically adjust for size with screen rotation from portrait to landscape and vice-versa
17. ��You are encouraged to use Mobile Components for Visualforce but this is not required