PL-500 flashcards
PL-500 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Attended desktop flow
- A desktop flow that runs inside a signed-in user's session, so the user can watch and intervene. It requires a Power Automate Premium user license and Power Automate for desktop installed on that machine.
- Unattended desktop flow
- A desktop flow that runs without any signed-in user on a registered machine. It requires a Power Automate Process license, stored Windows credentials, and the machine runtime installed.
- Machine group
- A logical grouping of machines that share unattended run capacity. A machine can belong to only one machine group, and queued runs are distributed across the group's available machines.
- Work queue
- A Dataverse table holding items to process, each with status, retry count, and deadline. It is used when every item must be processed exactly once, typically across repeated unattended runs.
- Run queue pattern
- A cloud flow design that retrieves pending work queue items and calls a desktop flow for each one, then updates item status so parallel runs never process the same record twice.
- Premium connector
- A connector such as Dataverse, HTTP with Azure AD, SQL Server, or a custom connector that requires premium licensing. Any flow containing it needs a premium or process license.
- Environment strategy for RPA
- The practice of separating development, test, and production environments. Makers build in unmanaged solutions in development and promote managed solutions to test and production.
- On block error action
- A container that wraps actions and defines failure behavior: jump to a label, continue the flow run, or retry a specified number of times with a fixed interval between attempts.
- Input and output variables
- Desktop flow variables flagged in the variables pane as input or output so values can be passed in and returned when a cloud flow calls the flow with Run desktop flow.
- Run desktop flow action
- A cloud flow action that starts a desktop flow on a machine or machine group. It maps input and output variables and offers wait for completion and timeout settings.
- UI element repository
- A per-flow store of UI elements and their selectors. Actions reference these elements, so editing a selector in the repository updates every action that uses it.
- Run from here
- A debugging command in Power Automate for desktop that begins execution at the selected action instead of the first action. It is commonly combined with breakpoints for step-by-step inspection.
- Subflow
- A reusable block of actions that can accept arguments and return values. It is called with the Run subflow action, and recursion within subflows is not supported.
- Parse text action
- A text action that extracts substrings using regular expressions or text between delimiters, returning matches or a list of matches for use in later actions.
- Connection reference
- A solution component that points flows at a connector connection. After import it must be bound to an actual connection in the target environment before the flow can run.
- Environment variable
- A solution component that stores configuration values. It has a default value shipped with the solution and a current value that can differ in each environment.
- DLP policy
- A data loss prevention policy that classifies connectors as business, non-business, or blocked. It prevents a single flow from combining business and non-business connectors.
- Run-only sharing
- A sharing permission on a desktop flow that lets another user execute the flow without opening or editing its actions, protecting the underlying logic and credentials.
- Desktop flow run history
- Run records stored in Dataverse and displayed in the Power Automate portal's desktop flow activity pages, showing status, duration, machine, and error message for each run.
- CoE Starter Kit
- A set of Power Platform solutions that provide inventory, compliance, and usage reporting across environments. It supports governance but is not required for licensing.
- Solution checker
- An analysis tool that reviews a solution for hard-coded URLs and credentials, deprecated connectors, and missing dependencies, and produces a downloadable report of findings.
- Managed solution
- A packaged solution installed as a read-only layer in the target environment. It cannot be edited there, and uninstalling it removes the components it added.
- Publish all customizations
- An import option that publishes solution changes immediately so they become available to users. It is usually combined with overwrite unmanaged customizations.
- Deployment pipeline
- A Power Platform feature that moves solutions through preconfigured stages, typically development to test to production, using a host environment with Dataverse configured.
- Stage for upgrade
- An import option that installs the new version in a holding state so components dropped from the new version are deleted during the subsequent upgrade step.
- Solution dependency
- A relationship where one component requires another, such as a flow needing a connection reference. The import fails if the required component is absent in the target.
- Invoke web service action
- A desktop flow action that sends an HTTP request to a REST or SOAP endpoint with custom headers and body, then parses the JSON or XML response for later actions.
- Custom connector
- A wrapper around a REST API built from an OpenAPI definition or Postman collection, exposing it as a flow action with authentication such as API key or OAuth 2.0.
- On-premises data gateway
- Software installed on a local server that relays traffic between cloud flows and on-premises data sources such as SQL Server, file shares, and SharePoint.
- Send HTTP request to SharePoint
- A standard SharePoint action that issues REST API calls for operations not covered by built-in actions, such as tenant-level or list property changes. It is not a premium connector.
- Dataverse List rows filter
- An OData query built with filter, select, expand, orderby, and top parameters to retrieve only matching Dataverse records and their related rows in a single call.
- Azure Service Bus connector
- A connector that sends and receives messages on Azure Service Bus queues and topics from cloud flows, enabling decoupled asynchronous integration between systems.