I constantly receive a warning "A category is required" in the Actions Console for some Smart Action (Deploy -> Directory information).
As I understand category could be set in the Deploy -> Directory information -> Additional Information. But there I see only "Smart Home Business Partnership Requirements" with an invitation to fill out the "Brand Permissions Form". Following this link leads to a 403 error.
How can I set the category to Smart Actions?
Note: some other Actions with the same settings do not show such a warning.
It seems like your project might not be set up properly as the category field is not present for smart home Actions and it is automatically selected for every project. Please set up a new project in the AoG console (https://console.actions.google.com/), and select Smart Home project type at creation.
The. If you’re still facing any issues after that then please file an issue in the public bug tracker
Related
The UI to send emails from Salesforce (including Subject, Body, etc.) is not displaying:
This Activity section is visible on the right of a Contact Record.
On the Related List "Activity History", the button "Email" is showing the same empty UI.
I am logged as a System Admin, I have all the permissions to access the object EmailMessage;
The UI displays as expected when using Saleforce Classic:
Any idea of why the send Email UI is not displaying the normal set of fields (Subject, Body, To, etc.) with Lightning Experience?
Is it in same org, same user? You may have org-wide email ban (Setup -> Deliverability -> No access) or on profile are you sure you have "send email" selected?
Have you viewed same object in classic and lightning? maybe what you viewed in lightning doesn't have "allow activities" ticked in object's definition.
It sounds like it's "just" the email composer rich text area because the send button is there. And couple more (but not all) buttons, interesting.
I'd expect 6 buttons: attach, merge field, template, preview, popup, discard
Any errors in Javascript console when you view this menu in lightning? (depends on browser, Windows users typically F12 or Ctrl+Shift+J, Mac users... command+option+J I think)
The root cause of the issue was that the Layout of the Global Action Email (API Name=SendEmail) did NOT contain any field.
After dragging-dropping the fields into the Global Action Layout, the functionality started working smoothly without the "error on parameter record: ava://sfdc.uisdk.connect.api.output.RecordRepresentation "
This resolves this issue.
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 installed a 2sxc version 11.11.3 Inside a fresh dnn 9.3.2.
After this I created a content Module with the simple test view inside. After this I granted this module the edit permission to the Registered Users Group on dnn module Level.
If I log in as a registered user I can see the 2sxc toolbar (blue symbols when hovering the item of the module) of the Module and the items. If I press the edit icon I get the Message "had an Error Talking with the Server (Status 403)".
Has anyone an idea what I am doing wrong?
Thank you very much
Robert
Edit1
The browser console shows following content in the ERROR object:
error: "Permission denied. required permissions for this request are not given"
headers: t
lazyInit: ƒ ()
lazyUpdate: null
normalizedNames: Map(0) {}
__proto__: Object
message: "Http failure response for https://.../api/2sxc/cms/edit/load?appId=2: 403 OK"
name: "HttpErrorResponse"
ok: false
status: 403
statusText: "OK"
url: "https://.../api/2sxc/cms/edit/load?appId=2"
Edit2
After this I wanted to explore, if the behavior is 2sxc Content module related or if it is related to all apps (in my understanding the 2sxc Content module is an app too). I installed the "FAQ" app, granted the dnn "Edit" permission to the "Registered users" group and logged in as a registered user and pressed the edit icon on the 2scx toolbar - and had the same behavior like described in the origin post.
But: I got it running for the "FAQ" app, but not for the "Content" app. Here are my steps to get it running for the "FAQ" app:
click on "Apps management" (available in the dnn edit action or in the 2sxc toolbar)
"Features" - add feature - enable "Permission by Group / Role" - Activate feature
"Apps" - "FAQ" (or another except Content)
"App" - "App Permissions" (click on the icon) - "create new permission" - Identity=xx (xx=RoleId of the Group in table dbo.Roles) - Grant=Edit (in my case I want that the current registered user is able to edit an item) - Save (Ctrl+S)
After this I was able to edit the item of the "FAQ" module.
The "App Permissions" icon is disabled by default for the "Content" module on App level (and on view and data level too). Does anyone know if this is by design or is there a possibility to activate this option? Otherwise I have to migrate my content views to an app to get the permissions running.
Edit3
I ended up by migrating the content of the "Content" app to a new custom app. The effort is very less and getting the possibility to grant permissions was worth doing it.
In a conclusion I'll answer my question by myself. I suppose that the "Content" app has not the possibility granting the dedicated permissions. But the app itself has the posibility - so it could be a good idea, to create content inside an app.
Just some background: The content-app is meant for simple content and behaves differently from normal apps. Example:
when you add a content-app, the dialog asks for you to choose what content-type, and what view
when you add an app, the dialog asks you for which app, and then what view
Basically the content-app has various optimizations to make it lighter and simpler, but we wanted to prevent people from "shooting themselves in the foot" because they will usually start with content, and then make it increasingly complex (never separating different concerns) and end up with a big mess.
This is why the content-app has some forced limitations (like no app-permissions) to guide people to place more complex functionality in own apps.
Now note that this doesn't explain your original issue: apparently edit-permissions didn't work as expected. That seems to be a bug, not an intension. If you think that should be followed up, best create an issue on github.
I am using the below Share Plugin of LinkedIn in my ReactJS app:
<script src="https://platform.linkedin.com/in.js" type="text/javascript">lang: en_US</script>
<script type="IN/Share" data-url="https://www.linkedin.com"></script>
From LinkedIn Docs: https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/plugins/share-plugin
It is working completely fine on Chrome/Firefox/Safari. But, on clicking the LinkedIn Share button (generated by the above scripts), the LinkedIn Share Popup appears and I get an error in my app console which says:
[object Error]: {description: "[Messenger] Required property 'target'
was not provided", message: "[Messenger] Required property 'target'
was not provided", nr#seenError: true, stack: "Error: [Messenger]
Required property 'target' was not provided at Anonymous function
(https://platform.linkedin.com/xdoor/scripts/in.js:7:55143) at
Array.prototype.forEach (native code) at t
(https://platform.linkedin.com/xdoor/scripts/in.js:7:54936) at e
(https://platform.linkedin.com/xdoor/scripts/in.js:7:56462) at e
(https://platform.linkedin.com/xdoor/scripts/in.js:7:34661) at value
(https://platform.linkedin.com/xdoor/scripts/in.js:18:23834) at s
(https://platform.linkedin.com/xdoor/scripts/in.js:18:38221) at
nrWrapper
([MY_SITE_LINK_ADDRESS]:9:16587)"}
Note: I hid the [MY_SITE_LINK_ADDRESS].
The problem here seems to be that you're relying on the plugin's JS, CSS, and HTML to handle every browser. Take a look: Here's someone else posting in 2018 having the same exact problem, Issue on IE with LinkedIn Share plugin. And, officially from LinkedIn, if you want this plugin to work, you need to ask your users to do this:
Open Internet Explorer.
Click Tools and select Compatibility View Settings.
Uncheck the box next to "Display all websites in compatibility view".
Click Close.
Is it reasonable to ask your users to reconfigure their browser just to be able to click one, single button on your website? Answer: No.
You don't need to rely on the LinkedIn Share Plugin. All you really ought to need is...
https://www.linkedin.com/sharing/share-offsite/?url={url}
Then making sure it works cross-browser is in your hands.
Source: Microsoft LinkedIn Share URL Documentation.
Sure, everyone says: Don't Reinvent the Wheel! I totally agree! But when you find a car that has square, cubic wheels, then maybe you want to reconsider!
If you are interested in a regularly maintained GitHub project that keeps track of this so you don't have to, check it out! Social Share URLs
I'm new to Wagtail, and I'm exploring the Bakery demo [that is a great demo, by the way!]. I can produce an AttributeError, 'NoneType' has no attribute 'startswith'".
The problem is that the Preview code in the Admin UI assumes that there is a site for every Page. But in my case there is no site yet.
I got to this point by not paying enough attention to the warnings in the Admin UI. But still, a little defensive programming in the Wagtail admin code will protect against this error.
Steps to reproduce:
Get the Bakery demo up and running.
Wonder about creating my own site, as a sibling of the Bakery site. Note the absence of a 'Sites' entry in the Admin UI sidebar, and decide to create a new HomePage thing via Pages -> Add child page (to Root) -> select HomePage as the type of the new child of Root.
Read this warning, but pay no attention: "These is no site set up for this location. Pages created here will not accessible at any URL until a site is associated with this location. Create a site now"
Create a new HomePage thing.
Click "Preview".
Uh-oh.
The problem is that the Preview code in the Admin UI assumes that there is a site. But in my case there is no site yet.
It seems to me that the code that does the Preview operation can check in advance for an associated Site. Or perhaps the code can catch the AttributeError and compose an error response of its own.
Moved to github, as suggested by gasman. I apologize - I misread the wagtail.io website about where to get support.