cfme.intelligence.reports.menus module¶
Module handling report menus contents
-
class
cfme.intelligence.reports.menus.
EditReportMenus
(obj, navigate_obj)[source]¶ Bases:
cfme.utils.appliance.implementations.ui.CFMENavigateStep
-
VIEW
¶ alias of
EditReportMenusView
-
prerequisite
¶ This is a helper descriptor for destinations which are linked to an attribute of the object.
For instance, imagine you have an object that has an attribute(parent) which has a ‘ViewAll’, destination that needs to be visited before you can click on ‘New’. In this instance, you would need to make the ‘New’ destination use ‘ViewAll’ as a prerequisite. As this would need no other special input, we can use NavigateToAttribute as a helper, supplying only the name of the attribute which stores the object to be used in the navigation, and the destination name. This will set prerequisite to be a callable that will navigate to the prerequisite step.
-
-
class
cfme.intelligence.reports.menus.
EditReportMenusView
(parent, logger=None, **kwargs)[source]¶ Bases:
cfme.intelligence.reports.CloudIntelReportsView
-
cancel_button
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
commit_button
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
default_button
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
discard_button
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
is_displayed
¶
-
manager
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
report_select
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
reports_tree
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
reset_button
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
save_button
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
title
¶ This class handles instantiating and caching of the widgets on view.
It stores the class and the parameters it should be instantiated with. Once it is accessed from the instance of the class where it was defined on, it passes the instance to the widget class followed by args and then kwargs.
It also acts as a counter, so you can then order the widgets by their “creation” stamp.
-
-
class
cfme.intelligence.reports.menus.
ReportMenu
(appliance=None)[source]¶ Bases:
cfme.utils.appliance.Navigatable
This is a fake class mainly needed for navmazing navigation.
-
add_folder
(group, folder)[source]¶ Adds a folder under top-level.
Parameters: - group – User group.
- folder – Name of the new folder.
-
add_subfolder
(group, folder, subfolder)[source]¶ Adds a subfolder under specified folder.
Parameters: - group – User group.
- folder – Name of the folder.
- subfolder – Name of the new subdfolder.
-
get_folders
(group)[source]¶ Returns list of folders for given user group.
Parameters: group – User group to check.
-
get_subfolders
(group, folder)[source]¶ Returns list of sub-folders for given user group and folder.
Parameters: - group – User group to check.
- folder – Folder to read.
-
manage_folder
(*args, **kwds)[source]¶ Context manager to use when modifying the folder contents.
You can use manager’s
FolderManager.bail_out()
classmethod to end and discard the changes done inside the with block. This context manager does not give the manager as a value to the with block so you have to import and use theFolderManager
class manually.Parameters: - group – User group.
- folder – Which folder to manage. If None, top-level will be managed.
Returns: Context-managed
widgetastic_manageiq.FolderManager
instance
-
manage_subfolder
(*args, **kwds)[source]¶ Context manager to use when modifying the subfolder contents.
You can use manager’s
FolderManager.bail_out()
classmethod to end and discard the changes done inside the with block.Parameters: - group – User group.
- folder – Parent folder name.
- subfolder – Subfolder name to manage.
Returns: Context-managed :py:class: widgetastic_manageiq.MultiBoxSelect instance
-