/
Release Notes for IFS Workflow 1.1

Release Notes for IFS Workflow 1.1

Search the IFS Workflow Wiki
 

 

Release Type

Minor

Release Date

July 27, 2018

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.1.

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 both the workflow engine and the following workflows: 

  • IFS Enterprise Upstream Initial Division Order

  • IFS BOLO Ownership Update

  • IFS Reporting Credential Configuration

  • IFS Enterprise Upstream JVA Approval

  • IFS API Token Update

This release includes enhancements to the following workflows:

  • IFS Enterprise Upstream New Well

  • IFS Enterprise Upstream Revenue Audit

This release includes updates to the following installers:

  • Engine Installer

  • Content Installer

Going forward, the workflow engine will only need to be updated when ProcessMaker has a new release that is incorporated into IFS Workflow. Workflows will be released more often when they are created.

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, 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

CentOS

7.2

x86_64

Supported

Certified

Y



Interoperability Certification

Target Product

Rest Service

Target Version

Certification Status

Target Product

Rest Service

Target Version

Certification Status

IFS Enterprise Upstream

IFS Enterprise Upstream Revenue Audit Submit Concurrent Process

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream Revenue Audit Request Sets

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream New Well Counties

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream New Well Nations

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream New Well Roles

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream New Well Code Types

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream New Well Fields

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream New Well Completions

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream New Well Wells

1.1

Certified

IFS Reporting

IFS Reporting Credential Configuration

1.1

Certified

IFS Enterprise Upstream

IFS Revenue Close Audit Find Report Output

1.1

Certified

IFS Enterprise Upstream

IFS Revenue Close Audit Find all Children Report Outputs

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream Revenue Close Audit Find Child Request ID’s

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream JVA Processing JVA Transaction Information

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream JVA Processing JVA Transaction sources

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream JVA Processing RC Missing Processing Party

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream JVA Processing JVA Processing Parties

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream JVA Processing Associate RC With Processing Parties

1.1

Certified

IFS Enterprise Upstream

IFS Enterprise Upstream JVA Processing Request Set Submission

1.1

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

Apache 2.4

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, Internet Explorer 11



Release Contents

Enhancements

Feature Name

Summary

Feature Name

Summary

IFS Enterprise Upstream Initial Division Order 

The IFS Enterprise Upstream Initial Division Order feature releases the new Initial Division Order workflow, which facilitates the steps that need to be completed to track the process of creating the initial division order when a well's spud date is populated. It is designed to gather documents to send to a division order attorney, and upon the receipt of the title opinion have a checklist form of all necessary fields in IFS Land and IFS Enterprise Upstream. Once all the appropriate fields are completed, the Division Order report will be automatically executed from IFS Reporting and uploaded to the case. Finally, given successful distribution of the Division Order and approval, all files are exported to a shared drive location with all documents uploaded and an audit trail.

IFS Reporting Credential Configuration 

The IFS Reporting Credential Configuration provides a process for configuring your IFS Reporting credentials within IFS Workflow, so that any workflow can utilize IFS Reporting reports within the workflow itself. It needs to be run only once for the credentials to remain. Should you switch your IFS Reporting server, it would need to run again.

IFS BOLO Ownership Update

The IFS BOLO Ownership Change is a manually-initiated workflow that begins with the source document and the LD1350 authorization number being emailed to all departments that will need to work on an ownership change. Once the ownership change is approved, the notified departments will save their reports to the workflow, showing that the update has been made, and upon completion, all documents (including source documents) will be saved to a network shared drive.

IFS Enterprise Upstream JVA Approval

The IFS Enterprise Upstream JVA Approval is the new Joint Interest Billing (JIB) workflow that gives a JIB Accountant the ability to sweep transactions from E-Business Suite (EBS) into the IFS Enterprise Upstream – Joint Venture Accounting module, and automatically process those transactions through GL Sweep to JVA, Financial Sweep, Distribution, and Invoicing with little user intervention. It allows an Accountant to review transaction counts, total debits, total credits, transaction sources, and, if necessary, add report centers that are missing from Processing Parties Profiles prior to submitting the transactions into workflow for downstream processing. Email notifications are generated throughout the process to keep the user informed as to the progress of the transactions through a workflow case. Additionally, the successful processing of transactions from GL Sweep to JVA through Invoicing creates output files that are emailed to the user group, exported, and uploaded to a shared drive location.

IFS Enterprise Upstream Revenue Close

Added IFS Context authorization to allow for ODP functionality within the IFS Revenue Processing Workflow. The External_API_Table was also configured to consume the Organization Token from IFS Enterprise Upstream.

IFS Enterprise Upstream New Well

Added IFS Context authorization to allow for ODP functionality within the IFS Revenue Processing Workflow. The External_API_Table was also configured to consume the Organization Token from IFS Enterprise Upstream.

IFS API Token Update

IFS Workflow has a workflow designed to automatically generate a token daily to automatically conform to the Auth0 Security Model.


Additional Reference Material

You may find the following documents useful:




Copyright© 2024 IFS AB. Copying prohibited. All rights reserved.