What’s New in FortiManager v5.2 : FortiManager v5.2.0 : Workflow mode
 
Workflow mode
Workflow mode is a new global mode to define approval or notification workflow when creating and installing policy changes. Workflow mode is enabled via the CLI only. When workflow mode is enabled, the admin will have a new option in the admin profile page to approve/reject workflow requests.
For administrators with the appropriate permissions, they will be able to approve or reject any pending requests. When viewing the session list, they can choose any sessions that are pending and click the approve/reject buttons. They can add a note to the approval/rejection response. The system will send a notification to the admin that submitted the session. If the session was approved, no further action is required. If the session was rejected, the admin will need to log on and repair their changes. Once they create a session, the admin will make their repair on top of the last session changes.
When you want to start a workflow, go to the Policy & Objects tab, select the ADOM from the drop-down list, lock the ADOM, and click the Start Session button. You can then proceed to make changes to policies and objects. When you are done making changes, click the Save button and then the Submit button. Once the session is submitted, the lock is released and other administrators may initiate a session.
The session list allows user to view any pending requests for approval or active sessions. The session list displays details of each session and allows you to browse the changes performed for the selected session.
To enable and disable workflow mode:
1. Select the System Settings tab in the navigation pane.
2. Go to System Settings > Dashboard.
3. In the CLI Console widget type the following CLI command:
config system global
set workspace-mode {workflow | disabled}
end
4. The FortiManager session will end and you must log back into the FortiManager system.
 
When workspace-mode is workflow, the Device Manager tab and Policy & Objects tab are read-only. You must lock the ADOM to start a workflow session.