Skip to main content
Creates a template Role Members Plan File from workspace roles on the OPA instance. These are the runtime roles shown in the OPA UI after an application is activated. Design-area roles may reflect only what is defined in the artifact, while this plan updates workspace roles. The source Process Application must be activated so that role membership is available through the data-access API. System-defined roles are not included. Workspace roles are not version-specific. The plan keys do not include a version, membership is managed by application name and role name, consistent with how roles are managed in the OPA UI. The roleMembersPlan.properties file lists users, groups, and external applications for each Process Application role. Each entry specifies the members that should be applied to the corresponding application and role on the target environment. The same application export (.expx) is typically deployed across multiple environments, where role membership may differ between Dev, Test, and Production. The plan file stores these environment-specific members so FlexDeploy can update them automatically during deployment. After the application is imported and activated, FlexDeploy reads the plan file, identifies entries for that application, and updates the matching workspace roles on the target. For APPLICATION roles, membership becomes exactly the set defined in the plan, members are added or removed as needed. For GLOBAL roles, plan members are added only. Existing members are not removed because removing a global member could affect access to other applications. If no plan file exists, or if a role has no member entries in the plan, that role is left unchanged. Role member overrides run only when the application is activated. Keep only the role entries that you want to override and remove the remaining entries.
Either FDOPA_CLOUD_ACCOUNT_CODE Target property value or FDOPA_INP_CLOUD_ACCOUNT_CODE plugin input value should exist. When both exist, the plugin input value will take precedence. See Creating/Editing a Cloud Account and Provider for details on how to setup a Cloud Account for OIC.

​
Target Properties

Property Name

Property Code

Required

Description

OPA Account

FDOPA_CLOUD_ACCOUNT_CODE

No

The OPA account includes essential properties such as the URL, Username, Password, and OAuth details for the OPA instance. You can manage the OPA account via the Integrations > Cloud page.

See Configuring OPA Cloud Account for additional details.

​
Inputs

Input Name

Input Code

Required

Description

OPA Account

FDOPA_INP_CLOUD_ACCOUNT_CODE

No

The OPA account with all the required properties like Base URI, Username and Password for running OPA Instance.

Application Identifiers

FDOPA_INP_APPLICATION_NAME

No

CSV list of application identifiers (for example APP1,APP2). Do not include version. Leave blank to export roles for all process applications.

Role Members Plan File

FDOPA_INP_ROLE_MEMBERS_PLAN

No

Optional input to specify a different role members plan file name. Default ‘roleMembersPlan.properties’.

​
Artifacts

This operation doesn’t consume or produce any artifacts.

​
Endpoint Selection

This operation will select all available endpoints associated to the Target.

​
Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.