Enabled
The Enabled section, in Portal, displays a list and block representation of the microservices available for the selected organization. These microservices can be configured to run from Workspaces, either at the system or session level, or to be run by the end user.
Microservice detail
Clicking on a microservice in the table allows access to its detailed view, divided into seven tabs:
Overview
It displays general information about the microservice, including its description, development language, compatible operating system, execution context, author, and creation date, among other relevant data.
From this tab, three main actions are available:
-
Go to designer
Allows editing the microservice configuration through the following tabs:
- Overview. General data of the microservice.
- Code. Source code of the microservice.
- Privacy. Information about the visibility of the microservice.
- Targets. Conditions for the execution of the microservice.
- FlexxWorkspaces Execution
Shows the roles with permissions to execute the microservice in Workspaces. The column Allow execution indicates the roles authorized to execute it at the Workspace group level, while Allow execution (individual) shows roles with permission for execution on individual devices. Both can be modified using the
Edit
button. - End-user Execution
Specifies if the microservice is enabled to be executed directly by the end user. This permission can also be modified using theEdit
button.
- FlexxWorkspaces Execution
Shows the roles with permissions to execute the microservice in Workspaces. The column Allow execution indicates the roles authorized to execute it at the Workspace group level, while Allow execution (individual) shows roles with permission for execution on individual devices. Both can be modified using the
- License. Allows configuring the microservice's license type.
-
Clone
Allows the general configuration of the microservice to create a new one, based on its current information.
-
Enable/Disable
Shows the current status of the microservice. When enabled, the microservice becomes visible and can be executed from the Workspaces module: in the
Workspaces
section (context System) and in theSessions
section (context Session), according to the configuration defined in the Designer section.
Code
Displays the source code of the microservice, including the logic and instructions that define its behavior.
Targets
Defines the conditions for the execution of the microservice.
Execution of FlexxWorkspaces
Shows the roles with permissions to execute the microservice in Workspaces. The column Allow execution indicates the roles authorized to execute it at the Workspace group level, while Allow execution (individual) shows roles with permission for execution on individual devices. Both can be modified using the Edit
button.
End-user execution
Specifies whether the microservice is enabled to be executed directly by the end user. This permission can also be modified using the Edit
button.
A configuration change in an existing end-user microservice may take up to 15 minutes to apply to all linked devices.
Settings
Reports the estimated time (in minutes) that the use of the microservice has saved the user compared to a manual solution for the same situation.
Alert Configuration
Presents a table with alerts linked to the microservice. For more information, please consult the documentation on Alert Settings.
License
Shows the type of license configured for the microservice.
Enabled Tenants
Allows enabling/disabling the microservice in bulk for the selected tenants and suborganizations.
The table contains the following information:
- Name. Tenant name. If it has sub-organizations they are presented in tenant*>*sub-organization format.
- Enabled. Displays if the microservice is enabled for the tenant.
- Minimum individual execution. Minimum roles with execution permissions in Workspaces at the level of individual devices.
- Minimum group execution. Minimum roles with execution permissions in Workspaces at the level of Workspaces Groups.
- Enabled on. Date and time when the microservice was enabled for the tenant.
- Enabled by. Name and email address of the user who enabled the microservice for the tenant.
- Disabled on. Date and time when the microservice was disabled for the tenant.
- Disabled by. Name and email address of the user who disabled the microservice for the tenant.
Considerations
-
The list of available tenants depends on the privacy configuration of the microservice and the permissions the user has.
-
Although the microservice can be enabled/disabled, the configuration of Targets is done independently for each tenant.
Steps to enable/disable a microservice for tenants
- Go to
Portal
->Enabled
. - Go to the
Enabled Tenants
tab. - Select the desired tenants in the table.
- Click
Enable
orDisable
, as applicable. - Read the warning message.
- Click on
Confirm
.