Kickstart My Development


What not to do with this guide

Please do not take the example “ugottaride” solution and publish it as-is to the Platform with your tenant or someone else’s tenant.

But why?

The Platform is not like AppDynamics cSaaS from the perspective:

In AppDynamics cSaaS:

  • You can create an application with a unique name in your controller.
  • You can delete the application you created if you named it wrong or something went haywire.

In the FSO Platform:

  • You can create a new solution with a unique solution name and namespace and push it.
  • You cannot delete the solution with a unique solution name and namespace once you push it, even if it’s with a dev tag.
  • Once you push a solution with a unique solution name and namespace, it will not only be there in your own tenant, but it will be there across ALL TENANTS in the platform.


How should I use this guide?

Follow the steps in this guide to create your new solution. However:

  • Choose your own unique solution name and namespace name.
  • Choose them with your solution’s permanent name and namespace in mind.
  • Choose them carefully since they will be permanent!
  • It is considered best practice to create a solution name and namespace that consists of your production solution name and namespace with a “dev” suffix for development.
  • Example:
    • Permanent solution name and namespace = salesforcedc
    • Development solution name and namespace = salesforcedcdev
    • Execute the fsoc solution lifecycle commands with your unique solution name and namespace!

Other things to be aware of:

  • While you can play around with most all the fsoc solution lifecycle commands in this guide without worrying about burning up a solution name and namespace (except fsoc solution push), you won’t be able to see any of your results in your tenant’s user interface until you actually push the solution (fsoc solution push).
  • Solution names and namespaces should be all lower case, no spaces, and no special characters.


Next  

We will walk through the steps to configure the FSOC Command Line Utility to access your platfrom tenant with the appropriate profiles.