In the chatter publisher, there is a Upcoming and Overdue tasks section in which a checkbox is shown in front of task, when I check it the task status will change to Completed.
I need to do some steps after I click on that checkbox, Since it is Salesforce out-of-the-box functionality I tried seeing what happens when checkbox is checked using Lightning Inspector Extension, I found one Event being fired:
function(a,b,c,d,e) {
var f = $A.getEvt("markup://runtime_sales_activities:taskStatusChange");
f.setParams({
// some params
)}
f.fire()
}
I tried adding a aura:handler in an aura component which is in same flexipage as chatter publisher for this event.
Tried following ways but unable to deploy:
1.
<aura:handler event="runtime_sales_activities:taskStatusChange" action="{!c.someMethd}">
Error while deploying -> NO EVENT named runtime_sales_activities:taskStatusChange found
2.
<aura:handler event="c:taskStatusChange" action="{!c.someMethd}">
Error while deploying -> NO EVENT named markup://c:taskStatusChange found.
Can anyone help with this?
Related
I'm using react-ga4 to send custom events to Google Analytics 4. I can see the events in the real-time dashboard and I can see an event with the made up name I'm using in the select of events when creating a custom event with the ui, but I can't find my data in the events tab or anywhere else outside the real-time section.
Is there something I should do on Google Analaytics and/or where can I find the custom data I'm sending?
It takes 24 hours to appear on the events tab
You can also confirm the correctness of your code by checking the event's hit from the networks tab in the dev console of your browser.
The API to GA for your event should start with https://analytics.google.com/g/collect?v.... In the payload tab here, you should be able to view the following fields for your event:
ep.category
ep.action
ep.label
NOTE: It takes upto 24hrs (as mentioned in above answer) for the event to appear in the events section of your GA4 property
I am trying to figure out why/how certain fields are auto-populating on my Opportunity object when I complete a Docusign.
The issue: On an Opportunity record I click a custom button that sends a DocuSign to a list of signers. When the last signer completes signing the document, and the DocuSign Status is marked as completed I refresh the Opportunity record and 2 custom fields have been populated with today's date.
Here are the items I have already looked into to trouble shoot the issue:
On the fields themselves, I have clicked the 'where is this used?' button, and the only places these fields are used are in Page layouts and reports. It is NOT referenced in any apex classes or process builders.
I have looked through all my workflow rules, and field updates on those workflow rules. These fields are not referenced in any of the workflows/field updates.
I have set field history tracking on the fields and found that the change is being made by an integration user. I then set up a debug log on the integration user and in all of the debug logs there is no reference to the fields being updated there.
In a sandbox I tried deleting the field to see if it might be referenced by a Custom metadata type, and no errors were thrown saying it was. I have also looked into the custom settings and custom metadata types to see if the reference to these fields could be in there.
Hoping someone can let me know if they've seen this issue before, or know any other ways to troubleshoot this issue.
It sounds like there's been some custom configuration setup, out of the box the package shouldn't add new fields to the opportunity record that are updated upon completion of an envelope. All of that information should only be found on the DocuSign Status object initially.
I would recommend reaching out to the DocuSign support team and have them take a look at the configuration with you to see what may be happening. https://support.docusign.com/
I have an request data action in nintex workflow, am unable to configure that action because of the disability of the ribbon which consist action,task reminder etc. how can i configure that action or is there any replacement for that action.
If you're using a browser other than IE it can cause this effect.
I've just had the same issue when trying to edit the Nintex workflow in Firefox.
When I switched to IE it worked ok and was once again editable.
I hope that this helps you.
I'm really stucked at my final stage of coding. I've created a custom button in lead section and i'm calling custom setting url in javascript code.
It works very well in my developer organization but it fails when I installs this in other developer organization.
Here is the code for your reference;
{!REQUIRESCRIPT("/soap/ajax/26.0/connection.js")}
var uname = encodeURI('{!$Setup.UserDetails__c.UName__c}');
var ukey= encodeURI('{!$Setup.UserDetails__c.Sha1Key__c}');
try{
var rurl= escape('/handleapprequest?email={!Lead.Email}&fname ={!Lead.FirstName}&lastname={!Lead.LastName}&company={!Lead.Company}');
window.open('{!$Setup.UserDetails__c.Url__c}login/' + uname + '/'+ ukey +'?returnurl='+rurl, 'Send Email', 'height=600,location=no,resizable=yes,toolbar=no,status=no,menubar=no,scrollbars=1', 1)
}catch(err)
{alert(err);}
When I install my package to different developer organization, the button which executes onClick javascript, thows an exception 'A problem with the OnClick JavaScript for this button or link was encountered: Field Setup.UserDetails_c.UName_c does not exists check spelling'
Please, let me know what is going wrong here? I've already created Beta package and I can not change or remove code from my developer org.
Thanks a lot.
Firstly, you should check whether you actually included the Custom Setting in your package. If you don't do that then it just won't exist in the new org.
Even if you do have the Custom Setting in the package, you still have to put a value in it in the destination org. Packages include metadata only, not data, and so you'll have to add a row to this custom setting for your button to pick it up. You can do this manually in the destination org, or you can do it automatically with a post-install trigger. Even if you've got a beta managed package, you can still add objects and code to it, by the way.
I have an EPiServer project which is using the sequential workflow to validate content changes. This works fine, however we have a slight issue where content reviewers are just clicking Publish when they are happy with an editor's work. What they should be doing is using the workflow task window and indicating their approval through that.
To enforce this behaviour I would like to disable the Publish button in the content editor under certain circumstances (i.e. when there is an outstanding workflow task linked to the current page).
Does anyone have any ideas how I can do this, or even an alternative solution to the problem altogether?
Actually, I think you may want to revisit your workflow logic.
If a user with publishing rights publishes a page: that should be considered an approval. You could easily hook up to the Published event to see if the page is part of a currently running workflow.