<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>invocable &#8211; Hamza Siddiqui</title>
	<atom:link href="https://www.mhamzas.com/blog/tag/invocable/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.mhamzas.com</link>
	<description>4x Salesforce MVP &#124; 26x Certified &#124; Salesforce App &#38; System Architect</description>
	<lastBuildDate>Thu, 18 Jun 2020 11:36:56 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
<site xmlns="com-wordpress:feed-additions:1">233526040</site>	<item>
		<title>Build Invocable Actions That Work for Multiple Objects</title>
		<link>https://www.mhamzas.com/blog/2020/06/18/build-invocable-actions-that-work-for-multiple-objects/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=build-invocable-actions-that-work-for-multiple-objects</link>
					<comments>https://www.mhamzas.com/blog/2020/06/18/build-invocable-actions-that-work-for-multiple-objects/#respond</comments>
		
		<dc:creator><![CDATA[hamza]]></dc:creator>
		<pubDate>Thu, 18 Jun 2020 11:32:48 +0000</pubDate>
				<category><![CDATA[Salesforce]]></category>
		<category><![CDATA[apex]]></category>
		<category><![CDATA[invocable]]></category>
		<guid isPermaLink="false">https://www.mhamzas.com/?p=3144</guid>

					<description><![CDATA[After Spring 20, you can now create reusable Apex actions that use the generic sObject and List&#60;sObject> data types. Build one action that works for multiple objects, rather than one for each individual object. Developers can build a filter or sort action <br /><a href="https://www.mhamzas.com/blog/2020/06/18/build-invocable-actions-that-work-for-multiple-objects/" class="more-link btn btn-primary">Read More</a>]]></description>
										<content:encoded><![CDATA[
<p>After Spring 20, you can now create reusable Apex actions that use the generic sObject and List&lt;sObject> data types. Build one action that works for multiple objects, rather than one for each individual object. </p>



<p>Developers can build a filter or sort action that works with any collection of records, from accounts and contacts to custom objects. Previously, developers couldn&#8217;t use polymorphic Apex structures in invocable actions because generic data types weren&#8217;t supported.</p>



<p>Create a custom action, or edit an existing one. Use the sObject or List&lt;sObject> data type in invocable methods and attributes.</p>



<script src="https://gist.github.com/mhamzas/6f9984bba86809037bbf7b9d47011363.js"></script>



<p>Previously, the example class would have been tied to the Account or Contact or myCustomObject__c object. But now developers create one action, and the Flow Builder admin chooses the object each time they use that action.</p>



<p class="has-text-align-center"><img data-recalc-dims="1" decoding="async"  src="https://i0.wp.com/releasenotes.docs.salesforce.com/en-us/spring20/release-notes/release_notes/images/224_rn_forcecom_flow_fbuilder_dynamic_types.png?w=640&#038;ssl=1" alt="A new action screen with contact specified as the object for “recordsToCheck” input, and Account as the object for “recordsToReturn”."></p>



<h4 class="wp-block-heading">Source</h4>



<ul class="wp-block-list"><li>https://releasenotes.docs.salesforce.com/en-us/spring20/release-notes/rn_forcecom_flow_fbuilder_dynamic_types.htm?edition=&amp;impact=</li></ul>



<p></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.mhamzas.com/blog/2020/06/18/build-invocable-actions-that-work-for-multiple-objects/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">3144</post-id>	</item>
	</channel>
</rss>
