Approval Merge Fields Have Wrong Value for Approval Related Emails


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 293 ·Updated 3 days ago

Email Alert sending to all members of Queue and Queue email when "Send Email to Members" is not checked


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 144 ·Updated 5 days ago

Updating percentage fields with process builder using a referenced value from a percent formula field in the parent object produces incorrect value

Platform , Workflow , Process Builder

Updating percentage fields with process builder using a referenced value from a percent formula field in the parent object produces incorrect value

In Review ·Reported By 8 ·Updated 2 days ago

On IE11, Clicking Submit for approval doesn't result in any action and error seen in developer console

Workflow , User Interface

On IE11 compatibility mode when users are trying to submit records for approval nothing happens on the screen. When you run the developer console for IE 11 you see the error: Object doesn't support property or method 'sfdcconfirm' for window.sfdcconfirm

In Review ·Reported By 0 ·Updated 2 days ago

Validation Rule Field Names Are Not Resolved Correctly When Executed From A Managed Package Visualforce Page

AppExchange , VisualForce , Workflow

If an Org has a field with the same API name as a field in a managed package (eg. Account.Field_In_Package__c and Account.namespace__Field_In_Package__c) and a validation rules that utilizes the local field (eg. Account.Field_In_Package__c), the rule could use the incorrect field, or could fail with...

In Review ·Reported By 16 ·Updated 4 days ago

Workflow Rule Criteria Set to "Subsequently Meets" But Fires When Lookup Is Edited

Platform , Workflow , Summer 18

Suppose you have a workflow rule with criteria set to Created and Edited to Subsequently Meet Criteria. In this situation, a record initially meets the workflow rule and fires (as expected). If you do not change the value of the field used in the workflow criteria, you are not editing the record to 'subsequently'...

In Review ·Reported By 7 ·Updated 5 days ago

Existing customer info being removed with import in merge mode


We are seeing an issue where importing customers in MERGE mode is removing existing information from the customer record that was not specified to be changed in the XML file.

No Fix ·Reported By 5 ·Updated 6 days ago

Boolean translation in Report, List view and Workflow condition is wrong

Analytics , Workflow

Boolean translation in Japanese had been changed in Report, List view and Workflow condition page. Expected translation : True / False Actual translation : 該当する / 該当しない

Fixed - Winter '19 Patch 11.5 ·Reported By 2 ·Updated 8 days ago

Cannot deploy Work Order Approval Process with queue as approver

Workflow , Change Sets , Winter 18

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.

Scheduled - Spring '19 ·Reported By 10 ·Updated 9 days ago

Case Auto-Response Rule is not triggered when Case is updated from Workflow Field Update of Child Object during Email-To-Case Creation

Apex , Platform , Service , Workflow

Case Auto-Response Rule will not be triggered if a Child Record is created, and a workflow field update updates the Parent Case in the same transaction

In Review ·Reported By 0 ·Updated 9 days ago

1 to 10 of 94 | Next

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.