You are an administrator of FortiGate devices that use FortiManager for central management. You need to
add a policy on an ADOM, but upon selecting the ADOM drop-down list, you notice that the ADOM is in
locked state. Workflow mode is enabled on your FortiManager to define approval or notification workflow
when creating and installing policy changes.
What caused this problem?
Another administrator has locked the ADOM and is currently working on it.
There is pending approval waiting from a previous modification.
You need to use set workspace-mode workflow on the CLI.
You have read-only permission on Workflow Approve in the administrator profile.
2 Comments on “What caused this problem?”
This should be A.
This is wrong, the correct answer should be A. Firstly, whether you are read-only or not has absolutely nothing to do with whether you can approve the workflow. You can in fact have NO access to FortiManager whatsoever and still approve things in workflow. Furthermore, even if you have read-only rights to the ADOM, the lock will not show on the ADOM if no one has locked it. You won’t be able to lock it, but it won’t show as locked.