Create a business process in Unifier

Automatically create a business process in Unifier directly from an Aconex mail, including attachments.

If you manage your project in both Aconex and Primavera Unifier, we've saved you some time.

Sometimes correspondence in Aconex results in a change or cost impact. This requires a business process, such as a Change Request to be created in Unifier. To save time and reduce errors, you can start the business process automatically from the Aconex mail, including all details and attachments. This ensures both systems are connected with accurate information.

You can start a business process from any Aconex mail that your organization has sent or received. 
 

Requirements:

  • The project in Aconex and Unifier (Multi-tenant) must be linked in the Lobby.
  • You must have access to the project in both Aconex and Unifier.
  • You'll need to have the Start Unifier Business Process permission granted to your Aconex user role.
  • You must have permission to create a business process in Unifier.

Tip!

This feature is only available to projects on the KSA1 instance following the October 2025 release. We'll continue to develop the feature based on feedback and announce availability for other Aconex instances at a later date. Make sure you subscribe to Release Highlights to be notified.
  1. To start, create and send a new mail, or find an existing mail.
  2. From the mail, click Start Unifier Business Process.
  1. Select the Unifier project.
  2. Select the business process you want to create in Unifier.
  3. Select the workflow name for the process.
  4. Click Continue.
  1. The Aconex mail will be attached to the business process as a PDF. Choose if you want the selected mail, or all mails/replies in the thread to be attached.
  2. Select mail attachments to be included in the business process record.
  3. Click Finish.
  1. Click View in Unifier to view the draft record in Unifier with the included attachments.
  2. Complete the business process in Unifier. See Working with Business Processes.

What's next?