One thing that seems obvious to me would be the ability to either: A) Assign a task to a queue or group of people, or B) assign a task to a user dynamically. For instance, we have a group of provisioners that look for Opportunities that haven't been worked yet. They will grab one of these Opportunities and update the status as in progress, which causes some tasks to be created. I want those tasks to be assigned to the provisioner.
Tasks can't be assigned to a queue or role (well, unless there's only 1 person in that role) or dynamically like explained above. To me, this makes their workflow extremely limited. How are others getting around this?
Hi all. I'm a new salesforce customer and am trying to modify an html page that is using the WebToLead servlet. The page is working but there are a couple of fields on the form that I don't see getting populated in the lead. I'm trying to find a definition of the servlet and what attributes can be sent to it. I found one message that had this link: https://na3.salesforce.com/lead/webtoleadtemplate.jsp
But that link doesn't seem to exist. Can anyone point me to the right location?
Hi all. I'm a new salesforce customer and am trying to modify an html page that is using the WebToLead servlet. The page is working but there are a couple of fields on the form that I don't see getting populated in the lead. I'm trying to find a definition of the servlet and what attributes can be sent to it. I found one message that had this link: https://na3.salesforce.com/lead/webtoleadtemplate.jsp
But that link doesn't seem to exist. Can anyone point me to the right location?
Yesterday I had deployed aan apex trigger from sandbox to production env. The trigger is an "before insert, before update" to check for duplicate account names. The trigger works fine in prodiuction for preventing duplicate Account names.
But today when I tried to mass update Accounts for some other field using Apex Data Loader, I get the following error:
Apex script unhandled trigger exception by user/organization: 00530000000nHi3/00D300000006QZD
Trg_Account_Name_Dedup: execution of BeforeUpdate
caused by: System.Exception: Too many SOQL queries: 21
Trigger.Trg_Account_Name_Dedup: line 1, column 143
Can anyone please advise on how to disable triggers in production env so that I can carry out other mass updates in Account using Apex Data loader tool.
One thing that seems obvious to me would be the ability to either: A) Assign a task to a queue or group of people, or B) assign a task to a user dynamically. For instance, we have a group of provisioners that look for Opportunities that haven't been worked yet. They will grab one of these Opportunities and update the status as in progress, which causes some tasks to be created. I want those tasks to be assigned to the provisioner.
Tasks can't be assigned to a queue or role (well, unless there's only 1 person in that role) or dynamically like explained above. To me, this makes their workflow extremely limited. How are others getting around this?
