Flow Connect

General

This document will provide guidance on installing and configuring the Mobile Work Order application package. The Mobile Work Order package contains seven separate applications.

Applications

App	Required Connectors/Services
Invoice Generation (Seed Inbox)	REST, Email
My Tasks (Seed Inbox)	REST, Azure AI Document Intelligence*, Help Lightning**
New Work	REST
Objects	REST
PO Receipts	REST
Pool Tasks (Seed Inbox)	REST
Service Quotation	REST

* Azure AI Document Intelligence(former Azure Form Recognizer) is only needed for automatically scanning receipts.

** Help Lightning is only needed for remote assistance functionality. If this functionality is not needed, it can manually be removed from the application.

System and Version

System	Version
IFS Applications	IFS Cloud 23R2
Novacura Flow Connect Hub	n/a
Novacura Flow Connect Designer	1.0.0.125
Connector Agent	1.0.0.303
Connectors	REST

Microsoft Azure Services

Azure AI Document Intelligence

If you plan to utilize the My Tasks - Create Expense - Scan Receipt functionality, set up a Azure AI Document Intelligence, Set Up Azure AI Document Intelligence. More information on Azure AI Document Intelligence pricing can be found here.

Flow Connect Connectors

REST Connectors

IFS REST Connector

If you do not have a connector set up, you can see an example here.

If you already have an IFS Cloud REST connector setup, you can skip this step and use the existing connector instead.

If you have other Flow Connect environments such as Test, QA, Prod you need to set the connector for each environment.

Used Projections in applications

Get User Defaults Cloud

• CompanyHandling

• FrameworkServices

• UserHandling

• SitesPerUserHandling

My Tasks

• FrameworkServices

• TaskAddressAssistantHandling

• WorkTaskHandling

New Work

• ActiveWorkOrdersHandling

• AssignWorkHandling

• CustomerHandling

• EquipmentAllObjectsHandling

• FailureAnalysisSetupNavigatorHandling

• HistoricalWorkOrdersHandling

• ItemClassesHandling

• PrepareWorkOrderHandling

• SitesPerUserHandling

• WorkOrderFaultTypeCodeHandling

Objects

• EquipmentAllObjectsHandling

• SitesPerUserHandling

Pool Tasks

• AssignWorkHandling

• FrameworkServices

• SitesPerUserHandling

• WorkTaskHandling

Assignments Component

• AssignWorkHandling

• WorkAssignmentsHandling

• WorkTaskDemandsHandling

• WorkTaskHandling

Edit Task Component

• WorkTaskHandling

Materials - Unissue Component

• WorkTaskHandling

• WorkTaskUnissueMaterialAssistantHandling

Materials Component

• InventoryPartDefaultLocationsHandling

• InventoryPartInStockHandling

• MaintenanceMaterialRequisitionLinesHandling

• ManualIssueAssistantHandling

• WorkTaskHandling

• PartSerialReservationsHandling

Measurements Component

• ActiveWorkOrdersHandling

• EquipmentAllObjectsHandling

• FrameworkServices

• MeasurementsForObjectHandling

• WorkTaskHandling

Object Component

• ActiveWorkOrdersHandling

• EquipmentAllObjectsHandling

• EquipmentObjectStructureNavigationHandling

• HistoricalWorkOrdersHandling

• WorkTaskHandling

Time Component

• WorkTaskHandling

Journal Component

• EventLogAttachmentHandling

Azure AI Document Intelligence REST connector

A REST Connector must be set up to utilize the Azure AI Document Intelligence.

If you do not have a connector set up, you can see an example here.

If you already have an Azure AI Document Intelligence REST connector setup, you can skip this step and use the existing connector instead.

Create a new REST Connector named "Document Intelligence" (or similar) in Flow Connect Hub.

• Select your Agent Group.

• Set your Base URL to your endpoint.

• Select "Api Key Credentials" as your Authentication Type.

• Set your API Key Name to "Ocp-Apim-Subscription-Key".

• Set your API Key Value.

• Set Api Key Option to "Header".

• (Optional) Set description for this connector.

• Click "Save" button.

If you have other Flow Connect environments such as Test, QA, Prod you need to set the connector for each environment.

Email Connector

If you don't have a connector set up, you can see an example here.

Variables

Before installing the applications, it is required to create several variables within Novacura Flow Connect Hub.

Variable Name	Example Value	Description
ExpenseDocClass	EXPENSE	Document class for the expense receipt document that will be added to the expense detail line.

Installation

Make sure that you have created all connectors and variables before importing the application package.

1. Import Application Configuration Packages

Before installing the applications, it is required to import the Application Configuration Package into your IFS Cloud instance.

Import the file “MWO Flow App - Application Configuration Package.zip”, refer to Import Application Configuration Packages for more information.

To read more on page properties please refer to the IFS documentation here.

• Upon successful importing of the custom field in the configuration package, navigate to the Solution Manager -> Configuration -> Entity Configurations window. Search for JtTask entity.

• Click on Additional Views button, edit the lines, and set all the necessary views to Approved.

2. Import Application Package

Import application package using your "share link" this will initiate an import wizard.

For details see Import Application Package

3. Setting User Groups

Together with the imported application package, you need to set up a user group. Add users to your user group, grant the user group access to the application package from the Application Package screen to make the applications available for your users.

For details see Create User Groups and Manage User Groups

4. Deploy Application

Within the Application Package screen, click on the button "Deployments" to go to the "deployment overview" screen. From here you can select which applications to deploy to your available environment.

The applications will now be available to execute on your chosen Flow Connect client. For instructions on individual Warehouse Management functions, please consult the function individual documentation provided separately.

For details see Deploy Application