• Rainbow
  • 4 Points
  • Member since 2017

  • Chatter
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
  • 4
Challenge Not yet complete... here's what's wrong: 
There was an unexpected error while verifying this challenge. Usually this is due to some pre-existing configuration or code in the challenge Org. We recommend using a new Developer Edition (DE) to check this challenge. If you're using a new DE and seeing this error, please post to the developer forums and reference error id: IOXJGBJV
global class LeadProcessor implements 
    Database.Batchable<Leads>, Database.Stateful {
//     Database.Batchable<Sobject>, Database.Stateful {

    // instance member to retain state across transactions
    global Integer recordsProcessed = 0;

    global Database.QueryLocator start(Database.BatchableContext bc) {
        return Database.getQueryLocator([Select LastName From Leads ]);


    global void execute(Database.BatchableContext bc, List<Leads> scope){
        // process each batch of records
        List<Leads> leads = new List<Leads>();
            for (Leads:leads) {
                Leads.LeadSource = Dreamforce;
                // add Leads to the list to be updated
                // increment the instance member counter
                recordsProcessed = recordsProcessed + 1;
        update leads;

    global void finish(Database.BatchableContext bc){
        System.debug(recordsProcessed + ' records processed. Shazam!');
        AsyncApexJob job = [SELECT Id, Status, NumberOfErrors, 
            TotalJobItems, CreatedBy.Email
            FROM AsyncApexJob
            WHERE Id = :bc.getJobId()];
        // call some utility to send email
        EmailUtils.sendMessage(a, recordsProcessed);


Dear fellow developers, dear Force.com team,


I hope this finds you well. Thanks so much for the Flow Designer, it's such a cool tool. Yet, we're currently having som issues as we try to customize it a little bit. Does anyone know whether the following features are possible with the Flow designer or whether they are on the roadmap? We're currently a bit stuck here.


Thanks a lot in advance! Best regards, Ignacio




Feature #1: Customize the target page that the "Close" button in the Flow Designer redirects the user to.

The issue here is that if users click on close, they are redirected to the flow's standard Force.com object page with the sidebar and the header fully visible. If they then navigate to the flow overview, they can delete and modify any flows that exist on the platform - and they can see all the other things that go on in the background, like apex classes etc. Since this is a huge security loophole, it would be really cool if that redirect could be customized so we can point it to say, a custom VisualForce page.


Feature #2: Disable/customize the "Save As" button. This, again, will give more control over what flows the user can create.


Feature #3: Customize the types of standard and custom objects that the user can create/update/delete/look up values for. Again, it's the control and security argument.


Feature #4: Customize the set of (sub)flows that the user can integrate into her own flow. Again, it's the control and security argument.


Feature #5: Be able to change the header of the Flow Designer, i.e. replace the salesforce logo with a custom logo, custom text, remove the standard dropdown in the top right corner (including the logout option) etc.


Feature #6: Be able to run the flow designer in an iframe of a VisualForce page.