{"version":"1.0","provider_name":"Sherweb","provider_url":"https:\/\/www.sherweb.com\/blog","author_name":"The Sherweb Team","author_url":"https:\/\/www.sherweb.com\/blog\/author\/the-sherweb-team\/","title":"Must Know of Workflow Scope and Security in Dynamics 365 | SherWeb","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"hzNNojxoFa\"><a href=\"https:\/\/www.sherweb.com\/blog\/microsoft-ecosystem\/dynamics-365\/workflow-scope-security-dynamics-365\/\">Workflow Scope and Security in Dynamics 365<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/www.sherweb.com\/blog\/microsoft-ecosystem\/dynamics-365\/workflow-scope-security-dynamics-365\/embed\/#?secret=hzNNojxoFa\" width=\"600\" height=\"338\" title=\"&#8220;Workflow Scope and Security in Dynamics 365&#8221; &#8212; Sherweb\" data-secret=\"hzNNojxoFa\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script type=\"text\/javascript\">\n\/* <![CDATA[ *\/\n\/*! This file is auto-generated *\/\n!function(d,l){\"use strict\";l.querySelector&&d.addEventListener&&\"undefined\"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!\/[^a-zA-Z0-9]\/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret=\"'+t.secret+'\"]'),o=l.querySelectorAll('blockquote[data-secret=\"'+t.secret+'\"]'),c=new RegExp(\"^https?:$\",\"i\"),i=0;i<o.length;i++)o[i].style.display=\"none\";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(\"style\"),\"height\"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):\"link\"===t.message&&(r=new URL(s.getAttribute(\"src\")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(\"message\",d.wp.receiveEmbedMessage,!1),l.addEventListener(\"DOMContentLoaded\",function(){for(var e,t,s=l.querySelectorAll(\"iframe.wp-embedded-content\"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(\"data-secret\"))||(t=Math.random().toString(36).substring(2,12),e.src+=\"#?secret=\"+t,e.setAttribute(\"data-secret\",t)),e.contentWindow.postMessage({message:\"ready\",secret:t},\"*\")},!1)))}(window,document);\n\/\/# sourceURL=https:\/\/www.sherweb.com\/blog\/wp-includes\/js\/wp-embed.min.js\n\/* ]]> *\/\n<\/script>\n","thumbnail_url":"https:\/\/www.sherweb.com\/blog\/wp-content\/uploads\/csp_bible_what_are_the_requirements.png","thumbnail_width":770,"thumbnail_height":230,"description":"When creating an automatic workflow in Dynamics CRM\/365, it is very important to specify the scope of the process. This is to ensure that only exact records that are affected when the workflow is triggered. The best time to define the scope of your workflow is during the design phase before moving on to creating the workflow."}