Demystify of Custom Process Action

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 process flow, or custom code.
  • Custom Process Actions allow us to define input and output parameters so that we can exchange values with the calling service.
Microsoft provides capabilities to extend the behavior of the Microsoft Dataverse with the help of events (messages). The Event Framework provides the ability to register custom code to run in response to specific events (messages) and custom process actions to create new custom messages (events) that can be called from a web service.

Why do we need this feature?

As per my understanding, this action works as hook which combines workflow and plugin under one message and it can call from anywhere like workflow, business process flow or custom code (workflow extensions or plugins). This means that developers can create a new functionality or chain of commands in a single message to accomplish a domain specific new feature.

An action is a wrapper for multiple service side data operations.

Summary:

Custom process action or action allows to create new message by no/low  code way to declaratively define  synchronous business logic which combines multiple server side events in one wire.

Comments

Post a Comment

Popular posts from this blog

Powering Up Your Analytics: Exploring Power Query in Power BI

Image
Data is a valuable asset that has a profound impact on almost every aspect of modern life. Its proper collection, analysis and application can promote innovation, improve efficiency and solve complex challenges in various sectors. In data processing, ETL is a comprehensive process that includes data extraction, transformation, and loading, while Power Query is a specific tool that facilitates the "extract" and "transformation" aspects of ETL, allowing data to be collected and analyzed. Permission is granted to process. And reporting. is ready. It becomes easy to do this. Microsoft's ecosystem of products. Power Query is a data transformation and data preparation engine. Power Query is available in Microsoft Excel and Power BI. Power Query provides a user-friendly and intuitive interface for data professionals and analysts to access and manipulate data from various sources without the need for extensive coding or scripting. It allows users to connect to a wide ra
Read more

Power App Component Overview : Canvas App vs Model-Driven App

Image
The Power Platform is a suite of low-code/No-code tools and technologies developed by Microsoft and Power App is integral component of Power Platform. Power App is platform that enables users to build custom web and mobile applications with a visual interface and minimal coding. The platform support various data sources, including Microsoft 365, Azure Service, and many other, enabling users to integrate and interact with their existing data and systems. In Microsoft's Power Apps, there are two main types of apps that we can create: Canvas Apps: Canvas apps provide a blank canvas where you can design highly customizable applications with a drag-and-drop interface.  Model-Driven Apps: Model-driven apps are built on top of the Dataverse, which provides a set of pre-built data entities and business logic. There are few key technical difference between Canvas App and Model Driven App: During the usability analysis, these high-level technical differences need to be considered. The choi
Read more

Exam PL-400: Microsoft Power Platform Developer

 Create a technical design (10-15%) Validate requirements and design technical architecture design and validate the technical architecture for a solution design authentication and authorization strategy determine whether you can meet requirements with out-of-the-box functionality determine when to use Logic Apps versus Power Automate flows determine when to use serverless computing, plug-ins, or Power Automate determine when to build a virtual entity data source provider and when to use connectors Design solution components design a data model design Power Apps reusable components design custom connectors design server-side components Describe Microsoft Power Platform extensibility points describe Power Virtual Agents extensibility points including Bot Framework skills and Power Automate flows describe Power BI extensibility points including Power BI APIs, custom visuals, and embedding Power BI apps in websites and other applications describe Power Apps portal extensibility points incl
Read more