- Updated on 08 Jan 2019
- 1 minute to read
A portal administrator has responsibilities and access to all of the administrative functions in Decisions. They have capabilities of customizing, setting restrictions, starting and stopping deployed flows as well as many other functions. This document describes a few of the general responsibilities of a portal administrator.
In Decisions there are different options specifically designed for the use of administrators to gain insight into the health of each environment, understand the features that are available, as well as many other capabilities. Information like portal user rights, how to deploy, portal configuration and options for viewing the environment's data are all customizable for the user's particular needs. All of these features are configured in Decisions.
- Even in a Cloud setup environment, the administrator has the capabilities to communicates to its on-premise systems.
- Installation requirements can be found in the documentation. For further instruction on how to start and configure Decisions, the support team is available to help an walk through the installation process with you.
- Upgrade the Installation version of Decisions and use support rolling upgrades. Upgrade a multi-node cluster or one node unit it is outgrown. Database structures are maintained by the Decisions platform. Database updates or scripts are not required.
- There are different administration and logging functionalities that can be adjusted to different levels.
- Within the framework, a dashboard that displays a system report of data usage acts as a tool to identify potential bottlenecks within the system. This can help the administrator to identify specifics flows or rules of deployment using the profiler to locate the cause. and need to be located.