1 Summary of Changes
- 1.1 Compatibility Matrix
  - 1.1.1 Product Certification
  - 1.1.2 Interoperability Certification
  - 1.1.3 Minimum System Requirements
2 Release Contents
- 2.1 Enhancements
- 2.2 Issues Resolved
- 2.3 APIs
  - 2.3.1 API Usage
  - 2.3.2 API Modifications
- 2.4 Seed Data Modifications
  - 2.4.1 Seed Data Used
  - 2.4.2 Seed Data Changed
- 2.5 Datamodel Modifications
  - 2.5.1 PM Table Changes
- 2.6 Configuration Modifications
- 2.7 Additional Reference Material
3 Known Issues

Release Type	Minor
Release Date	November 1, 2019

Summary of Changes

The purpose of this document is to provide you with the latest information for the release of IFS Energy & Resources Workflow 1.6.

IFS Workflow is a complete, market-leading workflow engine that leverages ProcessMaker software to provide oil and gas workflows for IFS and other applications used in the industry.

This IFS Workflow release includes IFS Workflow Content 1.6.

Although IFS Workflow is a standalone release from other IFS products, some REST Services that are delivered with other IFS products may be required. Additionally, IFS AppLink, which is the routing and security tool for IFS’s REST Services, may also be required. Workflows that require a connection to data sources will always utilize REST Services for these connections.

Compatibility Matrix

Product Certification

Component	OS Name	OS Version	OS Architecture	Support Status	Certification	Tested

Component	OS Name	OS Version	OS Architecture	Support Status	Certification	Tested
Application Server	Red Hat Enterprise Linux	7	x86_64	Supported	Supported	Y

Interoperability Certification

Target Product	Target Version	Certification Status

Target Product	Target Version	Certification Status
IFS Workflow	Engine 1.2.0.0	Certified
IFS Enterprise Upstream	13.03.03	Certified
IFS Enterprise Upstream	12.49.03	Supported
IFS Reporting	Content 2.6.0.0	Certified
IFS Merrick	3.11.0.0	Certified
IFS Excalibur	8.3.23.0	Certified
IFS Excalibur	WebService 2.7.0.0	Certified

Target Product	Rest Service	Certification Status

Target Product	Rest Service	Certification Status
IFS Enterprise Upstream	IFS Enterprise Upstream Marketing Election Change	Certified
IFS Enterprise Upstream	IFS Merrick Gathering System Unlock	Certified

Minimum System Requirements

This section identifies the recommended hardware requirements for each machine.

Component	Recommended

Component	Recommended
CPU	8 Processor 2.4 GHz or Higher
RAM	32GB RAM minimum
Disk 1	500GB (OS, Application, Logging)
Disk 2	500GB (OS, Application, Logging)

Medium sizing for 295 User Peak:

Component	Recommended

Component	Recommended
CPU	12 Processor 2.4 GHz or Higher
RAM	48 GB RAM minimum
Disk 1	500GB (OS, Application, Logging)
Disk 2	2TB (Database Storage)

Large sizing for 400 User Peak:

Component	Recommended

Component	Recommended
CPU	16 Processor 2.4 GHz or Higher
RAM	64 GB RAM minimum
Disk 1	500GB (OS, Application, Logging)
Disk 2	3TB (Database Storage)

Server Machine:

Component	Recommended

Component	Recommended
OS	CentOS 7.2
PHP	5.6
Web Server	NGINX 1.x
Database	MySQL 5.5

Client Machine:

Component	Recommended

Component	Recommended
OS	Windows 7 (32 or 64-bit); Windows 10
Browser	Google Chrome (Recommended), Mozilla Firefox, Microsoft Edge, Microsoft Internet Explorer 11

Release Contents

Enhancements

Module	Feature Name	Summary

Module

Feature Name

Summary

Workflow

IFS Mail Call Log

The IFS Mail Call Log has been enhanced with integration to IFS BOLO and IFS Excalibur. Using a Suggest box, IFS Workflow will assist with locating a caller if they are in your accounting system, and will then obtain caller details from the system, and preload email and telephone numbers.

Supported: IFS Workflow Content 1.6, MidCap Web Services 2.7.

Productized Content

IFS BOLO Manual Journal Entry Automation

The IFS BOLO Manual Journal Entry Automation has been designed to save time on every manual journal entry a user completes.

Upon submitting a journal entry for approval, IFS Workflow will grab the HOLD file and attach it to a new case, which can then be routed to a supervisor.

The supervisor will have access to not only the Journal Voucher report, but details of the journal entry in a dynamic grid that is easy to view. Once the journal entry is approved within IFS Workflow, IFS Workflow will kick off the posting process within IFS BOLO, and will then grab and attach that HOLD file as well, completing the loop and creating an easy-to-follow audit trail.

Supported: IFS Workflow Content 1.6, IFS BOLO 13.9.

Issues Resolved

There were no issues resolved for IFS Workflow 1.6.

APIs

API Usage

Support ID	IN/OUT	API Name	Summary

IN/OUT	API Name	Summary
IN	GET Owners	Returns all names, addresses, and emails.
IN	Get Journal Entries	Returns one or more Journal Entries currently pending approval.
OUT	Post Journal Entry Approval	Starts the approval process for a given Journal Entry.
IN	Get Users	Returns SEC1235 User/Approval setup information.

API Modifications

There were no API Modifications included in IFS Workflow 1.6.

Seed Data Modifications

Seed Data Used

Schema	Action	Table Name	Column	Comments

Schema	Action	Table Name	Column	Comments
N/A	IN	Groups		The System Administrator group is the default provided access to the Manage Database Connections workflow.

Seed Data Changed

There was no Seed Data Changed in IFS Workflow 1.6.

Datamodel Modifications

PM Table Changes

Schema	Action	Table Name	Column	Comments

Schema	Action	Table Name	Column	Comments
N/A	NEW	BOLO_APPROVAL_USERS	Id, Approver, Primary Flag, Auto Approval, Users.	Stores IFS BOLO Approval rules within IFS Workflow.

Configuration Modifications

Please see IFS Workflow Installation and Setup.

Additional Reference Material

You may find the following documents useful:

These documents are available on the P2 Store and on this wiki.

Known Issues

There are no known issues with IFS Workflow 1.6.

Release Notes for IFS Workflow 1.6