Installing 4Industry

Owned by Michiel van Beers
Last updated: 10-01-2024

The estimated installation duration of 4Industry is roughly 1 day.

Prerequisites

  • An OEM ServiceNow instance

  • An account with admin privileges

Installation steps

  1. Install the 4Mation Installer Global version 1.0.6

The 'My Company Applications' module is not always available on a clean OEM instance. You can directly navigate to the module by going to <your instance URL>/nav_to.do?uri=%2F$mycompanyappsmgmt.do

  1. Install the 4Mation Installer version 1.0.13

  2. Go to the ‘4Mation Installer' module and click 'Sync’

  3. All relevant installation configurations will be synchronised

  4. Go to sys_properties, x_ap4_4mation_inst.role and set the value to slave

  5. Go to Published Configuration

  6. Open the record “4I | Installer | [ Version that you want to install ] | Plugins“

  7. Click on Install (this will take a couple of hours)

  8. Manual install 'Playbook Experience' from the ServiceNow app store ([instance url]/nav_to.do?uri=$allappsmgmt.do?sysparm_search=playbook%26sysparm_filter=Listing%20type=show_products_only)

  9. Open the record “4I | Installer | [ Version that you want to install ] | Applications “

  10. Click on Install

  11. Activate the Next Experience UI

  12. Copy the Client Secret for the ‘4Industry Mobile', ‘4Industry Mobile DEV’ and '4Industry Mobile TST’ from an existing instance into the Client Secret field.

  13. (Optional) Install 4Industry content and/or language packs

  14. In case any 4Industry assets are needed: create an update source on the DEV instance to UAT 3, so you can easily retrieve the update sets from there and updates on the assets can be retrieved in the same way. From the client DEV you can go to higher instances in the regular way.

    Set system property 'glide.update_set.retrieve_days' on DEV to '0' to make sure you retrieve all update sets, otherwise you only retrieve the last 90 days.

Version-specific upgrade notes

Release 12.0

  • Upgrade to Vancouver Patch 4 Hot Fix 1 before running the installer.

  • Make sure to update all store applications after installing. Check out this repository for a helpful script.

Release 11.0

  • important Upgrade to (at least) the Utah - Patch 4 release before upgrading.

  • important After upgrading Translation Management, a series of Fix Scripts should be executed manually. These scripts should be run on every instance. Do not start the next script until the previous script is actually finished. Please execute the following Fix Scripts in predefined order starting from the top:

    • AP4 - Delete Duplicate Keys

    • AP4 - Delete Duplicate Translations

    • AP4 - Migrate To Translation Mgmt V2

    • AP4 - Move Translation To Scope

  • important For customers which have created their own translated text searching solution (JDE), this should be removed, since this is no longer allowed due to mass data creation restrictions.

  • Note Configuring the banner in the top left corner changed. Please refer to the ServiceNow documentation for more details.

Release 10.0

  • important Upgrade to (at least) the San Diego - Patch 4 release before upgrading.

  • important Make sure to first install all language packs (from the 4Mation installer), before installing the applications. The Translation Management scope will migrate the Translations to the different Translations packs.

  • If you experience any broken links between the new back-end driven list lay-out and your table configuration, please reference this article to get a mapping of the sys ids and tables.