Configure SDx to work with j5 - j5 - 30 - Help - Hexagon

SDx and j5 can be configured to view information from either system in the other. The j5 Control of Work application can be used to display work permits related to a tag or work package in SDx, so that you can confirm the required permits are in place before work is carried out. The j5 Operations Logbook application can be used to display any events recorded for a unit or maintenance unit, such as shift handover reports, in SDx. Also, the information from SDx can be made available in various j5 IndustraForms®.

The following describes how to display work permits and logbook entries from j5. You can also link to other screens in j5 as described in Display other j5 applications within SDx.

1. In the Desktop Client, relate the J5Integration access group to the Planner role. For more information, see Manage roles.

2. To enable work permits:

   1. Search for the SOPSShowPermits method.

   2. Update the method, setting the URL to custom page to point to the j5 Control of Work application.

      For example, https://j5.domain.com/j5_Hexagon_pages/SpfClientExtensibility/cow_permits/view?logbook_app=ControlOfWork. Where https://j5.domain.com is the URL of the j5 application.

3. To enable the logbook:

   1. Search for the SOPSShowShiftlogbook method.

   2. Update the method, setting the URL to custom page to point to j5 Operations Logbook application.

      For example, https://j5.domain.com/j5_Hexagon_pages/SpfClientExtensibility/general_logbook/view. Where https://j5.domain.com is the URL of the j5 application.

4. Edit the HxGN SDx server Web.config file as follows:

   1. Under the appsettings node, add the following:

      <add key="FrameOptionsWhiteList" value="https://j5.domain.com"/>

      Where https://j5.domain.com is the URL of the j5 application.

   2. Under the integraph.webApi node, edit the cors element so that allowedOrigins includes the URLs required to access j5, and allowCredentials is set to true.

When the Web.config file is changed, you must restart the Web Client server for the changes to take effect.