5.3 Actions required when upgrading Ops I version

The following tasks need to be performed in conjunction with the Ops I upgrade.

(Table) Tasks required when upgrading Ops I

Item Conditions requiring action
Preserving the customized Ops I features When upgrading from v02-50 to v02-70, or from v02-70 to later versions
Changing the ticket notification function When upgrading from v02-50 to v02-70 or later
  • If you want to change the notification function from the notification function using the mail server set in v02-50 to the notification function in Ops I
Updating the AWX execution environment When upgrading from v02-50 to v02-70 or later
Displaying knowledge articles When upgrading from v02-70 or earlier to v02-80 or later
  • If you created knowledge article categories before the upgrade, and you want to display knowledge articles belonging to those categories in the knowledge application after the upgrade


[Changing the ticket notification function]

Ops I provides the following ticket notification functions.

  • Ops I notification function: Supported in Ops I v02-70 and later
  • Notification function using mail server: Supported in Ops I v02-00 and later

For details, see “Ticket notification function”.

The following actions are required when upgrading Ops I.

(Table) Ticket notification tasks to be performed when introducing or upgrading Ops I

Ops I version Action
When upgrading from v02-50 to v02-70 If notification settings are not configured in v02-50, the Ops I notification function will be set automatically. If you have configured the notification function using a mail server in v02-50, those settings will remain unchanged. Additional tasks are required only if you wish to change the notification settings.

For details on setting the notification method, see “Use Cases > Use cases for notifications and email-based ticket creation” in the “JP1 Cloud Service/Operations Integration User’s Guide (ITSM Operation Manual)”.



[Displaying knowledge articles]

In Ops I, the following access controls can be applied to knowledge articles and categories:

  • Validity of knowledge articles (show/hide in the knowledge application)
  • State Management knowledge articles (public/private for customer users and requester users)
  • Validity of categories (show/hide in the knowledge application)
  • Category separation by customer
  • Category separation by group

See “Access control of knowledge articles” for details.

Category separation by customer and by group are functions available from v02-80 onward, and when Ops I is upgraded from v02-70 or earlier to v02-80 or later, these settings are not applied. To prevent knowledge articles from being displayed to unintended users, categories created before the upgrade and set to “[invalid] (show)” are automatically changed to “[invalid-temporarily] (hide)” at the time of upgrade. The Validity status and State Management of knowledge articles are carried over from before the upgrade.

When upgrading Ops I from v02-70 or earlier to v02-80 or later, the following actions are required.

(Table) Knowledge management tasks to perform when upgrading Ops I

Ops I version Action
Upgrading from v02-70 or earlier to v02-80 or later As necessary, perform customer separation and group separation of categories, and change the settings of the categories to which the knowledge articles you want to publish belong to "[invalid] (show)".

For how to enable (display) categories, see “[FAQ] > [Category Management]” in the “JP1 Cloud Service/Operations Integration User’s Guide (ITSM Operation Manual)”.

Section structure

5.3.1 Preserving the customized Ops I features
5.3.2 Updating the AWX execution environment