Integration

Release 24.12

Enhanced Record Security when Removing a User from a Selected Record Workflow

When a partner company user is removed from a record and that user is the only representative from that company on that record, the company's permission to access the record is also removed.

Release 24.10

API to Lock and Unlock the Cost Sheet

Two new REST services are added, allowing integration user to get and put the cost sheet lock status. This allows for API updates to the cost sheet without forcing the user to navigate to the cost sheet via the application interface and lock or unlock it manually.

The new REST API services are accessible for an integration user who has Create, Update, and Get permissions on the CBS service. An integration user with Full Access permissions can access all the REST API services to create and get data from the Cost Sheet in any shell.

Integration permissions for cost sheet locking and unlocking.

Update Business Process Records with Attachments

You can now update a document type business process record with new attachments. Only a single attachment may be included, and it cannot be a revision to an existing record attachment.

REST API to Terminate Records

Integration users are now able to terminate multiple workflow and non-workflow records that are not required.

A terminate record will have an entry in its Audit Log, with Event and Action fields indicated a termination via REST.

This API is not supported for Reservation BP, single-record BPs, and any BPs that do not have integration defined.

Contract BP audit log, showing that the record was terminated via integration.

Improved Handling of Duplicate Full User Names

When creating or updating business process records via REST or CSV, the presence of multiple users with the same full names is handled as follows:

Support for Activity Sheets

New API functionality is added to enable the creation and updating of a manual activity sheet, including rescheduling a project, creating activity dependencies, re-costing a project, and creating/updating a baseline schedule.

You can define OIC integration for GET and SEND of manual and system activity sheets.

OIC Integration Enhancements

OIC is now integrated for non-workflow business processes so that the OIC API call will be invoked when a non-workflow record is submitted from the Unifier user interface.

Release 24.6

API to Create Work Packages

Create work packages through a REST API, using GET to retrieve available work packages in a shell, POST to create a new work package in the shell, and PUT to update an existing work package in a shell.

Release 24.5

Behavior Change in Picker Evaluation through REST API

Prior to 24.5, the system updated auto-populated values from picker even if you didn't include a picker value in your input request. Now, if you don't send a picker value or send a null value, the system won't update the auto-populated values based on the picker data element.

Release 24.4

Consistent Behavior when Adding Partner Users

When a partner user is added to a project via user data picker, integrations, or the user interface, behavior will be consistent:

Oracle Integration Recipe: Activity Sheet

This enhancement provides the ability to invoke an integration between a Unifier Activity Sheet and Oracle Integration. Additional functions include checking the status of the integration and performing a test execution of the Oracle Integration.

Oracle Integration Recipe: Master Rate Sheet

A Unifier Master Rate Sheet can be integrated with Oracle Integration providing you with a Get Data action to retrieve Roles and Resources data from an external system.

API Support for Snapshots in Summary Curves

Create snapshots at the summary curve level using REST API services, allowing you to automate the steps needed to create snapshots across multiple projects.

XLSX Default for UDR Excel Output

An Excel output for a user-defined report is now provided in .xlsx format, rather than the previous .xls format.

There are no changes to the user interface, and this export format is used for saved results as well as documents published to the Document Manager.

Behavior Change in Picker Evaluation through Rest API

If the value of a picker is not sent in an input request or if a null value for picker is sent in an input request then system will ignore picker data and will not auto populate values based on the picker data element.

Release 24.2

New Back-End Fields

Three new fields are added to most business processes to facilitate integrations. These fields are hidden on the forms for end-users, but may be populated by Web Services, spreadsheet upload or bulk edit by an Administrator.

These fields were previously added to the Estimate, Initial Budget, and Vendor BPs.

The integration fields are now added to the following BPs: Action Item, Actual, Actuals Importer, Architect's Supplemental Instructions, Budget Change, Budget Transfer, Change Directive, Change Order, Change Request, Communication, Contract, Daily Report, Document Approval, Estimate, Field Observation, Forecast, Fund Appropriation, Incident Management, Initial Budget, Invoice, Issue, Journal Entry, Lessons Learned, Master Service Agreement, Meeting Minutes, Miscellaneous Cost, Notice to Proceed, Owner Walk Through, Payment Application, Permit, PO Amendment, Potential Change Order, Project Closeout Checklist, Project Note, Project Request, Project Status, Project Timesheet, Punch List Item, Purchase Order, Request for Information, Risk, Role, Submittal, Submittal Package, Timesheet, Vendor, Warranty, and Work Release.

This enhancement is included in the Configuration Package. Additional columns will be added to CSV and Excel import templates. Existing import templates will need to be adjusted to add the new columns.

Image of a hidden block named Integration, with the three new integration fields visible.

Image of a bulk edit screen, with the three new integration fields highlighted.

Image of a import spreadsheet template, with the three new fields in column headers.

Release 24.1

New RESTful Service to Add Assignees to a Workflow BP Record

An integration user with Update permissions can now add assignees to a workflow business process record via RESTful service. An event of this type will be recorded in the BP audit log.

Image of an audit log, showing that an assignee was added to a BP record via REST.



Last Published Monday, December 23, 2024