From the Microsoft Power Platform blogs: Delegate shared business processes to agents; Hide subgrid button; Build managed apps; Convert vibe app to code app

In this week's Power Platform blogs: 

• Better delegation of shared business processes to agents with Microsoft Copilot Studio
• Hide a subgrid button based on parent record state
• Building managed applications with GitHub Copilot
• From prompt to pro-code: converting a Power Apps vibe CRM app into a code app

Better delegation of shared business processes to agents with Microsoft Copilot Studio

On the Microsoft Copilot Studio Blog, Jason Moore wrote that in September, Microsoft announced changes to Copilot to make it more personalized and better able to anticipate what users need.

Now, the company is introducing new features in Copilot Studio that allow businesses to create AI agents that can handle tasks and support everyday business processes.

Moore stated that unlike AI assistants designed for individual employees, these agents belong to the organization and can continue working even when employees change roles or leave the company. They can start tasks when needed, remember information from previous work, and improve over time.

He noted that the new features, including agent accounts and business process memory, allow companies to build AI agents that work alongside employees in the applications and services they already use.

In his post, Moore explained that triggers in GitHub Copilot can also allow agents to start tasks automatically when certain events occur or at scheduled times, without requiring employees to prompt them. Microsoft is rolling out the new features through its Frontier program, with additional capabilities expected in the coming months.

Hide a subgrid button based on parent record state

Writing on the Himbap blog, Mahender Pal stated that in model-driven apps, users sometimes need to show or hide a button based on the status of a related record. 

Pal wrote that one way to do this is to write custom JavaScript code and create a rule using Ribbon Workbench. However, there's a simpler option for certain situations: using the built-in Mscrm.EntityFormIsEnabled rule, which can control whether a button is available based on the record's status. Pal then discussed how to implement the solution.

Building managed applications with GitHub Copilot