2.0.2向2.0.3升级

从2.0.2到2.0.3的升级对您的终端用户应该是完全透明的。但是,两个版本之间发生了一些变化。依赖在使用应用的过程中,可能需要特别注意以下几点:

可用性

以下变更在用户体验上可能具有影响度:

  • 现在,全局搜索要求终端用户至少键入3个字符。以前没有这种限制。此限制(3个字符)可通过配置参数 full_text_needle_min.

REST/JSON API

检查RESTTJSON文档 适用于API的最新版本。以下更改可能会使您的集成具有影响度:

  • 核心运维的输出已更改。运维现在可以正确地报告已完成的操作。
  • “ CaseLog”属性的处理已得到改进。输出格式现在反映了案例日志的结构(案例日志中每个条目一项),并且在输入中,现在可以将多个项目添加到案例日志中,甚至完全替换它。
  • 引入了新的运维core/check_credentials,以检查给定用户的凭据。
  • 布尔属性的输出进行了更改:以前是“ 1”(表示真)和“”(空字符串,表示假),现在是“ 1”(表示真)和“ 0”(表示假)。
  • 现在为枚举字段返回的价值(例如工单的状况)始终是“代码”(即非翻译的价值),而不再是本地化标签。

由于安全的原因,iTop的下一个主要版本中将禁止用户帐户对简档门户用户使用RESTTJSON Web服务。如果仅使用一种Web服务来检查用户的凭据,请调整代码以使用新的core/check_credentials用户。

数据模型定制

如果您对iTop数据模型进行了自定义,请注意以下更改:

  • 更改了“管理工具查询手册”菜单的定义,以在顶部添加搜索表单。如果已经实现了自己的菜单(通常在itop-welcome-itil模块中定义),请确保更新菜单定义以在顶部也显示搜索表单。
  • 由于性能的原因,链接集上的默认tracking_level已更改。除非数据模型中另有说明,否则默认行为是现在禁用全新安装的1:n链接的历史记录跟踪。

数据清理

在升级期间,安装程序流程将清除历史记录跟踪中未使用的记录。依赖上priv_change表的大小和要删除的未使用记录的数量,这可能需要几分钟。

原创链接:https://www.itophub.io/wiki/page?id=2_7_0%3Ainstall%3A202_to_203_migration_notes


2.0.2 to 2.0.3 Migration Notes

The upgrade from 2.0.2 to 2.0.3 should be totally transparent to your end-users. However a few things changed between the two versions. Depending on the way you use the application you may want to pay special attention to the following points:

Usability

The following change may have an impact on the user experience:

  • The global search now requires the end-user to type at least 3 characters. There was no such limitation previously. This limit (3 characters) is configurable via the configuration parameter full_text_needle_min.

REST/JSON API

Check the REST/JSON Documentation for the latest version of the API. The following changes may have an impact on your integrations:

  • The output of the core/delete operation has changed. The operation now properly reports what was done.

  • The handling of “CaseLog” attributes has been improved. The output format now reflects the structure of the case log (one item per entry in the case log), and, in input it is now possible to add several items to a case log or even completely replace it.

  • A new operation core/check_credentials has been introduced… to check the credentials of a given user.

  • The output of boolean attributes changed: it was “1” (meaning true) and “” (empty string, meaning false) previously, it is now “1” (meaning true) and “0” (meaning false).

  • The value returned for Enumerated fields (like the status of a ticket) is now always the 'code' (i.e. a non-translated value) and no longer the localized label.

For security reasons, the use of REST/JSON webservices by user accounts with the profile Portal User will be disabled in the next major version of iTop. If you use one of the webservices only to check the credentials of a user, adjust your code to use the new core/check_credentialsoperation.

Data Model Customizations

If you performed your own customizations to the iTop data model, pay attention to the following changes:

  • The definition of the menu for “Admin tools / Query Phrasebook” changed to add the search form at the top. If you have implemented your own menus (normally defined in itop-welcome-itil module), make sure that you update the menu definition to show the search form at the top as well.

  • For performance reasons, the default tracking_level on link sets has been changed. Unless specified otherwise in the data model, the default behavior is now to disable the history tracking of 1:n links for fresh installations.

Data cleanup

During the upgrade, the setup process will perform a cleanup of unused records in the history tracking. Depending on the size of the priv_change table and the number of unused records to remove, this may take several minutes.

标签:
由 superadmin 在 2020/08/27, 15:59 创建
    

需要帮助?

如果您需要有关XWiki的帮助,可以联系:

深圳市艾拓先锋企业管理咨询有限公司