Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Microsoft Dynamics 365 December 2016 release (version 8.2) included some significant changes to Dynamics CRM Business Process Flow data model and entities structure.
In the new Model, every time a business process flow is activated, a custom entity is automatically created to store the activated business process flow instances.
Before that, every time you create a business process flow, it is stored in the Workflow entity (https://msdn.microsoft.com/en-gb/library/mt622427.aspx).
The Workflow entity stores the business process flow definition. So once the entity is created, it is always in Draft state and its definition is stored in Workflow entity. XAML property is where the definition is stored and is mandatory/required.
Once you activate a business process flow definition (by changing the state of the corresponding Workflow entity record), a custom entity with the following name is automatically created to store the activated business process flow instances:
More details can be found in this MSDN Article here:
There is also the Process Stages Entity which contains: Step metadata for process stage (Client Data). It also contains stage Category (Qualify, Develop, Propose, etc.) as well as the Stage Name.
Properties represent fields of data stored in the entity. Some properties are read-only.
Display Name: Client Data
Display Name: Owning Business Unit
Display Name: Primary Entity
Display Name: Process Stage
0 : Qualify
1 : Develop
2 : Propose
3 : Close
4 : Identify
5 : Research
6 : Resolve
7 : Approval
Display Name: Stage Category
Display Name: Process Stage Name
Display Name: Version Number
More information on the ProcessStages entity is here:
Finally, here is a Dynamics Community post with few more information and discussion on this subject:
Business Applications communities