-
-
Notifications
You must be signed in to change notification settings - Fork 0
12 Planned Features
Features not yet implemented, ordered by target release.
SecureConfig values, step/workflow enable-disable state, and environment variable/connection reference
values are either secrets that can't live in source or legitimately differ per environment. Flowline does
not currently apply any of this after flowline deploy — it's manual and undocumented today.
flowline configure <env> will reconcile per-environment component state from a configure file, plus an
ad-hoc inline toggle for one-off changes:
flowline configure prod
flowline configure prod flow "Approval Flow" --onSecure config deploy-time injection and ordered flow activation are being evaluated separately and may land later, if at all.
Until then: apply SecureConfig, activation state, and connection reference values manually via the
maker portal, or pass pac solution create-settings/--settings-file through at import time.
After flowline deploy, workflows (classic processes and Power Automate cloud flows) in the target
environment may be deactivated. Flowline does not currently restore their activation state post-import.
--restore-state will re-activate workflows that were active before the import.
Workaround until then: re-activate manually via the maker portal or Dataverse API after deploying.
Greenfield setup currently requires visiting the maker portal to create a publisher and solution before flowline clone can run. flowline init will do both from the CLI:
flowline init ContosoSales --prod https://contoso.crm4.dynamics.com --publisher-prefix csUntil then: follow the Greenfield workflow in Getting Started — two manual maker portal steps, then flowline clone.