Skip to main content



Upgrading to InRule SaaS from Prior Versions (5.7.3 - 5.8.1)

If you're migrating to InRule SaaS from version 5.7.3, 5.8.0, or 5.8.1, your environment moves to 5.9.0+ as part of migration. Because ongoing SaaS releases are continually folded in, the exact version you land on depends on your migration date. The four considerations below apply to all three starting versions. For the full case-by-case changelog, see the 5.9.0 release notes, Upgrade Considerations section.

note

Not sure which version you're currently on? You can find it in:

  • Catalog Manager – Select the gear icon, then Configuration, then check the Catalog Manager version.
  • irAuthor Desktop – Select File, then Help, then About irAuthor.

Retirement of the classic irServer Rule Execution Service​

If you're still using the classic irServer Rule Execution Service, you need to move to Decision Services, either the Decision API or the Rule Execution API. See the Decision Services API Guide for the full guide. The Decision API is simpler and more modern. The Rule Execution API is backward compatible with the classic irServer request/response format.

The main question is whether you need XML-based requests and payloads, which Decision Services doesn't support. If you do, open a support ticket or email support@inrule.com to discuss your options.

Moving to Decision Services​

  • Decision Services URLs are now found under the gear icon, Provisioned Resources, Execution - Decision Services.
  • The Rule Execution Service - irServer provisioned resource no longer appears.
  • Primary and Secondary API keys are now found under the gear icon, Configuration, Execution Server Settings, Authentication.
  • The API key header is now inrule-apikey.
  • Change all calling applications to use the new Decision URL and API key header format and test.
  • See Locating Decision Services in the InRule Portal for the full walkthrough.
warning

The Rule Execution Service - irServer URL remains active for a limited time after migration, for precautionary rollback. You must update every calling application to the new Decision Services URL and API key header format before that window ends. Once the URL is turned off, any application still using the old URL will begin seeing runtime errors.

Removal of Author Studio​

  • Author Studio is removed as part of this upgrade and will no longer appear in the navigation menu or Provisioned Resources.
  • irAuthor Web, its replacement, is rolling out in phases. Reach out to your Customer Success Representative for the latest on availability.

Primary/Secondary API key rotation​

A Secondary API key is now available alongside the Primary API key, to support key rotation. This applies to Decision Services, and the Dynamics and Salesforce Execution Services. You manage both keys in the Portal Configuration UI.

Transition to the new Dynamics Rule Execution API​

The new Dynamics Rule Execution API replaces the Azure WebJob/Relay model. This is mostly transparent for you, but you need to configure the execution service URL and API key in your InRule solution within Dynamics.

See the InRule for Dynamics Deployment Guide, Appendix L: New Releases and Upgrading Versions, for more information.