Salesforce IdeaExchange
Winter_09_Known_Issues
For any release (for any software) there are known bugs.
I want to be able to go to trust.salesforce.com/Winter_09_Known_Issues (or someplace, it doesn't have to be trust)
and be able to search through known bugs.
I don't want or need access to a complete bug database, etc. I just want to be able to search so that when I come across some bizarre behavior (like the thread below demonstrates) I don't have to beat my head against a wall when somebody else already has the bruises.
http://community.salesforce.com/sforce/board/message?board.id=Visualforce&thr...
Specifically, I'm more concerned with programming bugs in VisualForce, Apex, etc. as opposed to weird application behaviors.
Use VisualForce email templates in Mass Emails and in Apex Outbound email method
Visualforce email teamplates are awesome, but we can't use them in mass emails or from Apex code. Please allow that in a future release!
Visual force as Custom related list
Allow developers to view visualforce pages as related-List item in the related list section of an object.
Not always each and everything needed to be displayed in the related-list section would necessarily need to have a direct relationship with the object.
Allow APEX triggers on junction tables like CampaignMember
The Apex developer preview currently allows triggers on most objects, but key Salesforce.com objects are left out. CampaignMember and OpportunityContactRole should have triggers allowed so that we can fire Apex code when a person is added to a Campaign or added as a Contact Role on an Opportunity. Having these triggers would be huge for allowing application development on the platform.
Sites: Allow Unauthenticated Users to Edit Standard Objects
We can use Salesforce Sites to create simple interfaces for Contacts to edit their information. However, this is against the current Sites license agreement--unauthenticated Sites users can't modify standard objects.
Check out this video for an example use case showing lightweight email preferences management.
Allow VisualForce Detail Page to be an edit form
I would like to create a VisualForce page to override the Edit page for my objects. I can do this now, but I have to build the form by hand. Please enable the "Detail" component, which renders the correct page layout for the object/profile combo, to be put into edit mode.
This would be incredible, because I could then put a conditions-based redirect after the save action to send my User to the next action. This could be:
* a page for next steps on a recently won Opportunity
* a page outlining research steps for a newly created Account
This is a very powerful platform feature I'd love to see!
Developer Directed Dreamforce Sessions
Allow the community to determine the content for one or more sessions at Dreamforce. In an effort to make the most out of Dreamforce, it would be great to have Developers of the platform, whether they plan on attending Dreamforce or actually will attend Dreamforce, weigh in on what topics to cover in the Developer Tracks.
There are many more topics available now than in previous years and only a finite time available at the conference. To provide the maximum value to attendees, it would be great to allow the attendees to determine what it is they are most interested in, struggling the most with or need more inspiration or information about.
IDE: Line Numbers on test results
Test results in the IDE can quickly become thousands of lines long when we are debugging. Please add line numbers to the test log viewer to make review easier.
Inline Debugging Eclipse
It would be very nice to have real debugging functionality in eclipse to debug Apex code.
if you could set breakpoints to see what value a certain variable has that would be very nice.
Regards Sven
XSL:FO support for Visualforce PDF generation
Visualforce PDF support is fantastic but using HTML to generate a printed page is less than ideal.
Adding xsl:fo support would allow for headers, footers, page numbering etc on generated pdfs, and is designed for generating printed content as distinct from html which is designed for on-screen content.
Invoke Assignment Rules with Apex
It would be great if we could invoke assignment rules (Case & Lead) with Apex.
We are forwarding leads to our Partners and if they want to then register this Lead they are sent to a custom VF page that gathers the necessary info. Upon saving this record we have had to build a custom object and logic that duplicates the normal assignment rules so this deal reg can be assigned to the correct ISR.
With force.com sites coming and the ability to capture leads with VF landing pages I would think this functionally would be required.
Developer-accessible bug database
If I find a bug in the Salesforce platform, I want a bug database search for an existing bug and, if none exists, log a new bug. Such a bug database would have the following features:
1. A defined bug cycle (report/reproduce/resolve)
2. Viewable/searchable by other developers on the platform
3. Direct interactions with with Salesforce's engineers, PMs, and QA
4. Specifically for developers, specifically about bugs in the platform
Without such a database, developers on the salesforce platform have two choices for reporting bugs - opening a support case, or starting a thread on the discussion boards. Neither meets our requirements (support cases provide (1) but nothing else; the discussion boards provide (2) & (3) but not 1 & 4).
Of the two existing options, opening cases with support has been the less useful for me. My support cases are often closed immediately by Tier 1 support with a comment "we don't support partner apps" - apparently T1 support doesn't realize that I am the partner, requesting support for a bug in the platform. More to the point, requiring T1 support to be capable of handling highly technical developer bug reports isn't realistic.
The discussion boards have been great for direct interaction with salesforce's developers, but lacking the defined bug cycle their usefulness is highly time-limited. If I log a bug through the boards, I often get a "we're aware of that and working on it" response, but that response isn't always followed up with "that is now fixed". As a result, as a developer, I have to specifically re-test a bug to find out if it's been fixed. The upshot is that, if I try to use a feature and find it has a bug, I'll often avoid that trying that feature again for much longer than I should.
Now that salesforce is a platform, not just an app, it's time to open the kimono a bit.
Subscribe
POST IDEA