Introduction

This document provides detailed information on the CONO (Company Number) field functionality and its enhancements across Version 1 and Version 2 of the CONO implementation for workflows. This guide is intended to help users understand and utilize the CONO field effectively in various scenarios.

Version 1: Initial CONO Implementation

1. CONO Field in Connection

Description:

The CONO field is designed to accept only numerical digits and is an optional field within the Connection screen. It allows users to specify a company number for data retrieval or updates during workflow execution.

Field Characteristics:

• Allowed Characters: Digits only (0-9).
• Optional Field: Users can choose to leave this field blank.

Functionality:

• Creating a Connection Without CONO:
  • Users can create a connection without specifying a CONO.
  • The absence of a CONO means that workflows associated with this connection will not be restricted to a specific company number.
• Creating a Connection With CONO:
  • Users who are part of multiple companies can specify the CONO to indicate which company’s data should be managed.
  • During workflow execution, the data retrieval or update will be based on the specified CONO.

2. M3 User ID Check Box

Description:

The M3 User ID check box provides an alternative method for determining the company number if the CONO field is not used.

Functionality:

• M3 User ID Check Box Selected:
  • If the CONO is not specified in the connection, selecting the M3 User ID check box will use the default CONO assigned to the M3 User ID from the user profile.
  • Data operations (retrieval or updates) will be based on this default CONO.
• M3 User ID Check Box Not Selected:
  • If neither CONO nor the M3 User ID check box is present, data operations will default to the CONO associated with the service user in the connection.

3. Version 2: Enhanced CONO Configuration

In Version 1, the CONO field was tied to the Connection screen, allowing only one company number per connection. This created inefficiencies when users needed to execute workflows across multiple companies, as they had to create separate connections for each. Additionally, the process was dependent on the M3 User ID for company identification if CONO wasn't specified, limiting flexibility and creating unnecessary complexity in multi-company environments.