二次开发-调整门户-门户调整示例-增加仪表板
本帖最后由 adminlily 于 2020-12-16 15:08 编辑门户：如何添加仪表盘
在本操作方法中，我们将使用ManageBrick在门户中添加仪表盘。仪表盘可以是饼图，条形图，top_list或徽章。
名称：如何添加仪表盘
类型：[ ttps://www.itophub.io/wiki/page?id=type&dataflt%5B0%5D=type_%3DHow%20To]如何
听众：[ ttps://www.itophub.io/wiki/page?id=audience&dataflt%5B0%5D=audience_%3DAdministrator]管理员,[ ttps://www.itophub.io/wiki/page?id=audience&dataflt%5B0%5D=audience_%3DIntegrator]Integrator, [ ttps://www.itophub.io/wiki/page?id=audience&dataflt%5B0%5D=audience_%3DDeveloper]Developer
水平：[ ttps://www.itophub.io/wiki/page?id=level&dataflt%5B0%5D=level_%3DAdvanced]高级
持续时间：30分钟
关键词：[ ttps://www.itophub.io/wiki/page?id=keyword&dataflt%5B0%5D=keyword_%3DPortal]portal,[ ttps://www.itophub.io/wiki/page?id=keyword&dataflt%5B0%5D=keyword_%3DCustomization]Customization
iTop版本：[ ttps://www.itophub.io/wiki/page?id=itop_version&dataflt%5B0%5D=itop%20version_%3D2.5.0]2.5.0
该仪表盘现在带有iTop 2.5及更高版本。
先决条件您将需要：
[*]装有安装了演示数据和增强门户的iTop系统，
[*]可以访问具有足够权利的账号来连接到门户（通常这意味着拥有门户用户描述），
[*]有一种方法可以修改数据模型定义（创建扩展或使用ITSM Designer）
该教程的目的
在此教程中，您将学习如何：
[*]在现有的门户上添加一个新的仪表盘，如下图所示：
[*]饼形图：
https://www.itophub.io/wiki/media?media=2_7_0%3Acustomization%3Ascreenshot-localhost-2017-12-15-16-19-57.png
[*]条形图
https://www.itophub.io/wiki/media?media=2_7_0%3Acustomization%3Ascreenshot-localhost-2017-12-15-16-23-36.png
[*]排行榜
https://www.itophub.io/wiki/media?media=2_7_0%3Acustomization%3Ascreenshot-localhost-2017-12-15-16-25-29.png
[*]徽章
https://www.itophub.io/wiki/media?media=2_7_0%3Acustomization%3Ascreenshot-localhost-2017-12-15-16-27-02.png
[*]默认图块
https://www.itophub.io/wiki/media?media=2_7_0%3Acustomization%3Ascreenshot-localhost-2017-12-15-16-27-58.png
正在进行的工单ManageBrick的示例
要将饼图磁贴添加到标准用户门户的主页，以在饼图中显示未售票与被解决工单。将此XML代码放入扩展中，运行安装程序并在门户中检查结果。
[ ttps://www.itophub.io/wiki/page?do=export_code&id=2_7_0%3Acustomization%3Aportal_howto_add_manage_extended_brick&codeblock=0]production.delta.xml
<?xml version="1.0" encoding="UTF-8"?>
<itop_design xmlns:xsi="2001/XMLSchema-instance"version="1.0">
<module_designs>
<module_design id="itop-portal" xsi:type="portal">
<bricks>
<brick id="ongoing-tickets-for-portal-user-ext"
xsi:type="Combodo\iTop\Portal\Brick\ManageBrick" _delta="define">
<active>true</active>
<rank>
<default>20</default>
</rank>
<width>6</width>
<title>
<default>Brick:Portal:OngoingRequests:Title</default>
</title>
<description>Brick:Portal:OngoingRequests:Title+</description>
<decoration_class>
<default>fa fa-etsy fa-2x</default>
</decoration_class>
<oql><!]></oql>
<!-- Optional tag to define if the action should be done in a modal window
("modal"), a new window ("new") or the current window ("self") -->
<!--<opening_target>modal</opening_target>-->
<!-- Optional tag to define the how the objects should be opened. Values
can be edit|view. Note that even if this is set to edit, objects not allowed in
edition mode for the user (cf. scopes and security layers) will open in view mode
-->
<!-- <opening_mode>edit</opening_mode> -->
<!-- Can be either a class tag with the class name or an oql tag with the
query -->
<!-- <class>Ticket</class> -->
<!-- Optional tag to add attributes to the table by their code -->
<fields>
<field id="title"/>
<field id="start_date"/>
<field id="status"/>
<field id="service_id"/>
<field id="servicesubcategory_id"/>
<field id="priority"/>
<field id="caller_id"/>
</fields>
<!-- Optional: display type can be 'pie-chart', 'bar-chart', 'list' -->
<display_modes>
<!-- How the data can be displayed in the ManageBrick -->
<availables>
<mode id="list"/>
<mode id="pie-chart"/>
<mode id="bar-chart"/>
</availables>
<!-- How the ManageBrick get displayed by default when open -->
<default>pie-chart</default>
<!-- How the ManageBrick is displayed in the Homepage and in an
AggregatePageBrick -->
<!-- Possible values are text|badge|pie-chart|bar-chart|top-list -->
<tile>badge</tile>
</display_modes>
<!-- Optional: way to define the export to Excel -->
<export>
<!-- Optional tag to export attributes by their code -->
<fields>
<field id="title"/>
<field id="start_date"/>
<field id="status"/>
<field id="service_id"/>
<field id="servicesubcategory_id"/>
<field id="priority"/>
<field id="caller_id"/>
<field id="description"/>
</fields>
<!-- Optional way to tell that the export uses default fields -->
<!-- <export_default_fields>true</export_default_fields> -->
</export>
<grouping>
<!-- Mandatory -->
<tabs>
<!-- Optional. Show object count for each tabs. Available values are
true|false. Default is false. -->
<show_tab_counts>true</show_tab_counts>
<!-- Mandatory. Grouping by tabs -->
<!--<attribute>operational_status</attribute>-->
<!-- attribute xor groups tag -->
<!-- Optional way to limit the number of groups when grouping with
attribute -->
<!-- <limit>5</limit> -->
<!-- Optional when limit given, display the aggregation of the
remaining groups -->
<!-- <show_others>true</show_others> -->
<groups>
<!-- Can be used only with ../oql tag, not ../class tag. Reason is
that we can't know the class alias to apply to the condition's fields. We might
have an exception saying that the field in ambigious for the generated query. -->
<group id="opened">
<rank>1</rank>
<title>Brick:Portal:OngoingRequests:Tab:OnGoing</title>
<condition><!
IN ('closed', 'resolved')]]></condition>
</group>
<group id="resolved">
<rank>2</rank>
<title>Brick:Portal:OngoingRequests:Tab:Resolved</title>
<condition><!
'resolved']]></condition>
</group>
</groups>
</tabs>
<!-- Implicit grouping on y axis by finalclass -->
</grouping>
<data_loading>full</data_loading>
</brick>
</bricks>
</module_design>
</module_designs>
</itop_design>
当然，这只是一个示例，请播放并扭曲它以获得所需的内容。
启用导出至Excel
您可以在每个ManageBrick上添加“导出to Excel”特性。
特性支持两种方法来定义导出的属性：
[*]使用与页面中显示的相同的属性：
<brick xsi:type="Combodo\iTop\Portal\Brick\ManageBrick">
<export><export_default_fields>true</export_default_fields>...
[*]使用导出的特定字段列表，该字段列表将与列表中显示的字段不同：
<brick xsi:type="Combodo\iTop\Portal\Brick\ManageBrick">
<export><fields><field id="title"/>....
这将在相应页面上显示导出按钮：
https://www.itophub.io/wiki/media?media=2_7_0%3Acustomization%3Ascreenshot-localhost-2017-12-15-16-37-23.png
您必须选择显式字段列表或标签导出_default_fields才能允许导出。
页:
[1]