Q: Where can we see the past recorded webinars? A: Much content of this nature may be found online at:

Transcription

1 Q: Can I get a recording of the Webinar and / or a copy of the slides? A: Yes! Webinar and slides are both are available at: Q: Is there a general Winter 16 release webinar in general being planned? A: Yes! Please see the below link or contact your AE for more information: Q: Where can we see the past recorded webinars? A: Much content of this nature may be found online at: Q: Is the Apex Debugger Available now? A: The Apex Debugger (and Eclipse Plugin) are generally available (GA) for purchasing right now, it was launched as part of Winter 16 and is fully available and out of pilot and beta. Contact your AE for more information. Q: When might the Debug API be open for developers? A: Pilot in Winter 16 - Contact your AE to learn more. Q: How does one request a trial of the Apex Debugger? A: Contact your AE Q: Is the debugger available in Dev Orgs? A: Presently the debugger is available in Sandbox orgs, (Developer, Developer Pro, Partial or Full) we hope to move it into the free Developer Edition account in the future. Q: Is there a link of the debugger plug-in for eclipse that you can share? A: Yes! See: Q: Are breakpoints only available for use in the developer console? A: Presently breakpoints are available in Eclipse we hope to extend this functionality in future releases. Q: Beyond the SF IDE plugin, are there any additional plugins for Eclipse required for this? A: No, you just need to have the Force.com IDE installed and configured as described here: Q: Can you please show us where in Eclipse you specified which env this is connected to? debugging in sandbox & live is not same.. most of the time problem is due to some data in live.. A: The connection is defined when you create a Force.com project. See instructions/screenshots here: Apex Debugger can only be used in Sandbox environments.

2 Q: How do you connect your Eclipse instance to SF instance? A: The connection is defined when you create a Force.com project. See instructions/screenshots here: Q: I can't set checkpoints in my Eclipse (Juno). Do I need to install something for this to be functioning? A: Please ensure you have Eclipse configured as defined here: Also ensure you have upgraded to the latest Force.com IDE. Q: In order to avail debugger in eclipse. Which version of eclipse we need to use? configuration requirements. Please also update your Force.com IDE as described here: Q: Is there a particular version of Eclipse that will have the debugger capability? configuration requirements. Please also update your Force.com IDE as described here: Q: Is event monitoring separate from debugger? A: Yes, it is a separate product. Q: Where can I find documentation on deploying (in more detail)? A: Please see documentation here: The developer forums may be useful for addressing specific challenges. Q: Safe to assume the debugger should not be used on a Production org? A: The Apex Debugger is available in Sandbox Pods. Q: None of the debugging features are available, until it s purchased? A: Correct, interactive debugging features require Apex Debugger. Access to the debug logs is standard. Q: When working in the Sandbox, will the new debugger identify if a fail is occurring because a Process Builder flow has been invoked? A: The debugger is intended to debug Apex code. If you are calling Apex from a Process, you can use this to step into code for debugging, though. Q: What is package of this debugger in ide? A: Please ensure you have the latest version of the Force.com IDE and have updated all items named Force.com IDE and Force.com debugger.

3 Q: What version of force.com ide has this feature? And is it free? A: Upgrade to the latest version of the Force.com IDE and in the Name and Version list, select all items named Force.com IDE and Force.com IDE Debugger. Apex Debugger is an add-on product; contact Salesforce to purchase. Q: What will happen if there are multiple developers developing in the same sandbox? A: You can have only one active debugging session per org across all the org s sandboxes. However, you can purchase more sessions for your parent org. Each sandbox org can have only one active session. Q: Will there be an option to purchase additional debugging sessions? A: You can purchase more sessions for your parent org. Q: Any suggestions on tools for CI? like Jenkins? A: Many customers use Jenkins Q: Are there any expectations to have the debug available with other dev apps, such as mavensmate? A: Safe-Harbor - The debugger API will be released to Salesforce tooling partners. Partners will need to incorporate the feature into their UI. Q: Can you please show us where in Eclipse you specified which env this is connected to? A: The environment is specified when you create a Force.com project, as outlined here: Q: Debugger will be available in salesforce developer login environment? A: Due to the nature of this product, we are not able to make it available in the free Developer Edition environments. Force.com IDE latest version? A: The IDE functionality is packaged with the latest Force.com IDE version. Contact Salesforce to purchase the debugging license. Q: What version of Eclipse is it compatible with? configuration requirements. Q: Will there be an option to purchase additional debugging sessions? A: Currently, you can purchase up to 3 debugging sessions. Q: Can we do this Debug Breakpoints in PROD? A: No, Apex Debugger is limited to Sandbox environments.

4 Q: Can we enable the debugger to multiple sandbox? A: While only one debugging session can be open at any given time, you can use the debugger in any sandbox connected to your production org. Q: Is there any Guide for the Debugger usage? A: You may find this tutorial interesting and useful: Q: Can agile accelerator be used to build applications on Salesforce? A: It not for building applications but rather for managing development in monitoring or assisting with organizational ALM Q: Do you have more details on the Agile Accelerator? Perhaps in a Youtube? A: It is an app available on the AppExchange - the listing there contains details and a demo. Q: Do you recommend using any external source control tool? A: Many customers leverage Git and GitHub related tools. Q: For good practices: how often do you refresh your full sandboxes? A: They can be refreshed every 29 days, customers use case determine how frequently they are refreshed (training vs UAT etc) Q: How do we access the Wave Analytics from SFDC Classic? Is there an extra cost for this? A: Wave Analytics is a separately Licensed Product. When you are licensed, it is available in the App Dropdown menu (top right of your org). Q: What was the name of the source control app used? A: GitHub Q: Any utilities for copying select data into a dev sandbox? A: There is a built in migration tool in sandbox or one can use apex data loader Q: Agile Accelerator does it have any release management tools with it or can it work with Version Mgmt and Jenkins? A: It can help with versioning and can also be leveraged in conjunction with Jenkins Q: Is there a way to move records created in UAT into Production? Our users may test at a customer site and do not want to lose their entered data. It would help us so much. Consider setting up a docker container for it. Support for junit testing thru the Eclipse UI A: Data cannot be migrated upstream using change sets. One could explore leveraging apex data loader. Q: More sandboxes would be available on EE licenses? Can anyone let me know if this is true or where I can find the info?

5 A: Yes! We want to enabled every developer to convert ideas to app on the platform. In light of this effort we are increasing the number of dev copies that come with each edition. EE from 1 to 25 UE from 15 to 50 PxE from 30 to 100 This change will plan to happen with the Spring '16 major release. Q: My question is, how can I refresh a sandbox to another? I have a System integration sandbox and I need to create another one with the same configurations and metadatas. A: One can leverage change sets which are built into our migration tool to move data between environments.