Known Issues · Workflow
When using Approval Merge Fields, the values may be incorrect when used as approval related emails (final approval/rejection, immediate email alert). Note: the approval merge fields work correctly in the Approval Assignment Email.
In Review ·Reported By 277 ·Updated 4 days ago
When an approval process updates the Record Owner to a Queue and sends out an Email Alert to the Record Owner, it is sending to each individual member of the queue and the queue email itself. This should not send out an email to them because the "Notify Assignee" and "Send Email to members" of queue...
In Review ·Reported By 128 ·Updated 4 days ago
An Email Alert on Task or Event with "Account Team" recipients does not send an email to those Account Team Members, even when triggered by a Task/Event that is related to an Account.
In Review ·Reported By 54 ·Updated 2 days ago
Editing a user can disable the Partner Super User permission if there is a workflow/process builder on User object.
In Review ·Reported By 10 ·Updated Today
A user will receive the following error message when updating or creating a case in Lightning that triggers an email alert: "insufficient access rights on cross-reference id" This occurs when the email folder that the email template is contained in is not public or shared with the user and the...
In Review ·Reported By 6 ·Updated Yesterday
For orgs with a large number of users, the Edit page for Workflow Email Alerts templates times out or loads slowly
Release In Progress - Winter '19 ·Reported By 2 ·Updated 3 days ago
When a flow component has custom fields in its property editor, it does not work properly in Communities. A gack is thrown for all users. Error will look like: "Customer is seeing below flow Component Error in Community Unfortunately, there was a problem. Please try again. If the problem continues,...
Release In Progress - Winter '19 Patch 5.4 ·Reported By 29 ·Updated 4 days ago
When deploying an Approval Process which has a queue as approver an error is received: Approval step Step_1 references <Queue_Name>, which doesn't exist as a queue . This error still occurs if the queues exists in the destination org or in the package.
In Review ·Reported By 10 ·Updated 4 days ago
The “else Approve Record” option for Approval Processes only works if it’s specified on Step 1 of an Approval Process. When this option is specified in a subsequent Step, it automatically Rejects records instead of Approving them.
In Review ·Reported By 79 ·Updated 7 days ago
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.