How does one go about building a moon sized death star? That's a lot people and supplies to keep track of for a project with a budget over 1,000,000,000,000 galactic credits. Putting together a system to help manage the build is going to be a major project in and of itself. Or is it?
Build a Battle Station App
Lucky for us the Salesforce Trailhead team has the timely launch of the Build a Battle Station App Trailhead project.
Highlights you'll learn from completing this project:
- How do you keep the Exhaust Port Inspectors from dropping the ball again and letting magic space wizards drop bombs to the core.
- How to track all the required supplies. Tractor beams, ultra fast hydraulic units for the doors. Don't forget the light bulbs and toilet paper. Handling the guard rail shortage will be left as an exercise to the readers.
- Get a quick summary of how many people are actually working on the project.
- Use Lightning Process Builder and Chatter to announce when you've got a fully armed and operational death star!
- How to help your fat fingered boss use the mobile app.
- Test the mobile app in Chrome using the Salesforce1 Simulator app.
As an added bonus, there is also a competition running for those who finish the badge by 2015-12-31 11:59pm PST
Just noticed Model Complex Products with Hierarchical Assets in the Spring `16 release notes. That could be useful in this project.
Apex Integration Services
There is also the new Apex Integration Services module. If you can get past the SOAP bashing there is some good information in there.
How's this for clicks not code? (Or at least minimal code to meet the ceremony required by the challenge)
- Take the URL for the SOAP WSDL from the Apex SOAP Callouts Challenge. No need to save it to disk first.
- Put it through the FuseIT SFDC Explorer custom WSDL2Apex implementation. Call the output ParkService and check the option to generate test cases.
- Rename the generated mock class "ParkServiceMockImpl"
- Rename the generated test class "ParkLocatorTest"
- Make the ParkLocator class with the static country method to call the generated class.
- In ParkLocatorTest duplicate one of the assertions to also call the ParkLocator.country method to give the required coverage.
- Add the remote site setting for the callout URL.
- Run the generated ParkLocatorTest test case.
- Smugly pass the challenge test
OK, maybe not so smugly. There are more steps above than I care for, but most of those are to satisfy the ceremony of the challenge with regards to naming etc... There is also something odd about this WSDL the is throwing off the generated apex_schema_type_info members and requires the elementFormDefault="qualified" boolean (second to last one) to be manually changed from 'true' to 'false'.
Still, show me the same level of initial setup from a REST API in Apex and I'd be impressed.
