Salesforce Send Email UI not displaying - salesforce

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.

Related

How to change the Read Access to the users on custom Visualforce page in Salesforce

The question is about the custom visualforce page in Salesforce. The page is created for getting contacts, opportunity, loans all are at a single dynamic link on the account named "Manage portal Access" Which comes under "Customer Portal Access" Tab like details and related list under "Account" Tab.The page was created to Manage the customer account, contacts and opportunities relationship. The page contains Email, Role, Last Login and a Toggle button as "Enabled".When this toggle button is enabled, those users have access to this portal relationship. It has respective apex class also.
The task here is, the toggle button can be enabled/disabled by some users, this want to be changed here by providing Read only access and assign two permission sets for edit access on this portal enable/disable.
" As a user I want Read Only Access to the portal tab. I want to be able to view all information on the tan and click through any dynamic links, but not be able to toggle the portal enable or un-portal enable any contacts. All Salesforce users should have a minimum of read only access to the Customer Portal Access Tab. The two permission below currently and should continue to provide edit access to the customer portal access section.
Create Customer Portal User
Document Manage Portal Admin "
Whether there is any customization option like providing access to objects in Salesforce through (Layouts, Fields FLS, Validation Rule)?
Or
-This can be achieved only through code on Visual force page and it's respective apex class, if this is the case how can I do it, whether there is any certain command or method for providing access or through controller class?
The "normal" object permissions (Create/Read/Update/Delete) and field level security (Read/Update) can be referenced in Visualforce. Something like this might be enough for you:
<apex:commandButton disabled="{!$ObjectType.Contact.fields.Role__c.updateable}">
Check the DescribeFieldResult in Apex reference. There's also something mentioned in VF developer guide but it's bit hidden and not as detailed: https://developer.salesforce.com/docs/atlas.en-us.234.0.pages.meta/pages/pages_variables_global_objecttype.htm
If you need more control than just whether field is editable or not - maybe look into Custom Permissions. They're your own checkboxes you add to Profile/Permission Set and you can check them in pure VF too, no apex required.
So... you decide. If most of the page is supposed to be identical, "just" about the button being enabled/disabled (or maybe even not rendered at all) - it's best to put the condition in the button. If it sounds like you need 2 different layouts - having 2 big blocks of code and one or another rendered might be cleaner to maintain and test.
P.S. Remember that good tester can activate the button using browser's developer tools. You should make similar "is field accessible / is custom permission assigned" check in Apex that runs on button click.

Is it possible to return the messages that are generated and shown in SSMS to the calling application(page, console app, etc)?

We are planning to add a feature to an Admin page of our website that will allow us to trigger the "Index Reorganization" in SSMS with a progress bar. We would love to be able to return the generated messages to a text box on the page and then base the progress off of those instead. I've seen the options to have them sent to a file, but we are wanting the user to be able to perform this from the website solely. Is this a possibility?

Webform: how to set confirmation message

I'm trying to set a confirmation message on my webform.
I'm using the standard redirect to confirmation page option when a form is submitted.
I clicked every single link in my webform backend and can't find it anywhere. All search results regarding this issue lead to programming a custom module to display a confirmation message in a popup or redirect to a different confirmation page. I don't want to do any of that, just a simple edit of the standard confirmation message.
I've looked through the webform-confirmation.tpl.php file in the module and see that it just prints a $confirmation_message variable. I don't want to edit it there as I want to be able to translate the string in the drupal admin section.
Surely this must be available somewhere?
When you edit the webform there are four tabs at top right side: Display, Edit, Webform and Results (look at screenshot: https://dl.dropboxusercontent.com/u/207644/screenshot-webform.jpg). Click on Webform tab. If you don't see this tab you have problem with user rights maybe.
On Webform tab are 3 subtabs: Form components, E-mails and Form settings. You must click on third - Form settings. Finally there is section "Submission settings" where you can setup confirmation message.

Can I add a custom widget to Salesforce Service Cloud Console?

I need to have a custom widget on Salesforce Service Cloud Console. I don't really care where it is as long as it's easily accessible (kind of like the Softphone widget).
I need this for two reasons:
I need a quick way for users to change their "status" (a custom field on user).
I need to execute some custom javascript to hide certain elements from some page layouts.
Any idea if this can be done?
Note: when I say "Service Cloud Console" I mean this kind of console:
I think Custom Console Components may be what you are looking for? (Here is how to add them to the console once you made them. Note that after the 11 steps, it says 'Before you can access ...'.)
I have implemented similar thing using a custom console component , there you can add a visual-force page and add a button on it "Change Status". Once user clicks it get who is the logged in user .
String userid = UserInfo.getUserId()
rest is the simple logic to change the status on User record on the page controller.

Data shows when page accessed from internally, but not on public site

I have been following the salesforce Recruiting App tutorial, and reached the section on creating a public site:
http://www.salesforce.com/us/developer/docs/fundamentals/Content/adg_composite_app_public_sites.htm
I have built a simple page to display open jobs as described here:
http://www.salesforce.com/us/developer/docs/fundamentals/Content/adg_composite_app_create_public_jobs_try_it_out.htm
This is displaying the open jobs correctly when I view it through our "internal" URL: https://c.ap1.visual.force.com/apex/PublicJobs
But when I view this same page through our "external" URL: http://servian-developer-edition.ap1.force.com/careers, the page still renders, except that now the list of jobs is empty.
I don't think this is a permissions error, as if so it would surely prompt me to log in. What do I need to do to make the data show on the "external" URL?
Make sure the "guest" user for the site has Read permission for the Positions object on its profile. You can't access the profile for the guest user through the normal Profile list page in Setup; instead, click on the Public Access Settings button from your site's detail page. On the profile, go all the way to the bottom of the page and make sure the Read permission is checked. If its still not working, ensure the Field Level Security settings also correct for that profile. The FLS settings are controlled about mid-way down on the same page.
In addition to above, ensure the object, if it is a custom object is in "Deployed" status. This fixed the issue for us.
Additional Information (from help.salesforce.com):
While developing a custom object or external object, you might not want users to see and interact with it. Because users might get frustrated with changes in layout or lose data when you delete custom fields, control visibility of the new object until you are finished.
Use the Deployment Status setting in the object definition to control when users can see and use the object and its associated custom tab, related lists, and reports.
Choose “In Development” as the Deployment Status when first creating your custom object or external object. Doing so hides it from users while you are designing and testing it. Only users with the “Customize Application” permission can see the object tab, search results, related lists, and report data types.
Change the Deployment Status to “Deployed” when you want to allow all users to use the object and any associated custom tab, related lists, and reports.
If you make more enhancements after deploying a custom object or external object, you can change the Deployment Status back to “In Development.”

Resources