Spending quality time with Custom Process Actions (which is shared in the Demystify of  Demystify of Custom Process Action articl e), it is given an insight about the action and it's a really awesome feature that I usually miss during solution design. Custom Process Actions are the declarative way to design a solution with many different behavior business logic (JavaScript, workflow, and custom code).  It allows creating custom messages that extend the capabilities of defining new domain specific functionality to combine multiple message requests into a single request. I am going to share few facts about Custom Process Action or Custom Action which will be helpful to design a CRM Solution. It allows for creating new message that can be called from web service. Custom Process Action will continue to provide a no code way to declaratively define synchronous business logic. Custom Process Actions have been synchronous real time workflow and therefore not suitable to be converted to us

During a technical conversation with a colleague of mine, he asked about the actual behavior and uses of this functionality, but I was unable to explain the feature and found it to be the most mysterious and least used by me, so I Decided to reveal the custom process action and share it with everyone. After a long and marathon studies, I succeed to get some knowledge about it. Microsoft categorize it as Automation feature and named "Action" which is generally known as Custom Process Action or Custom Action.  This component is kept with workflow and it is defined by a XAML window workflow foundation document which is transported as part of a solution, but it can't edit or update by workflow designer. The Action means a series of commands that can be organized as a business process. Actions behave like workflows, but there are some features that make it different from workflows. Custom Process Action does not have a trigger. This is usually triggered by a workflow, business

Solutions is the key component for Dynamics CRM since CRM 2011 that moves the deployment process from environment to environment. If we talk about the solution, then it is defined as a container that contains various components (for example, table, sitemap, column, process, plugin and others). When the solution comes to mind that there is no confusion, we fully believe that this container will aid in component movement from one instance to another. A solution is a container for the components of an application that acts as a transport unit to enable applications to move between environments. But the optimization of unmanaged and managed solutions always poses a dilemma for standard practices. The CRM/CE world is always in a state of confusion as to which is best for their deployment process. This is the best interview question for interviewer about solution behavior and best selection solution types. In addition they also want to know about the modification of managed solutions. In thi