Integration Profile Configuration
The following outlines the settings for Databuild Orders integration .ini file profiles.
Default initialisation filename:
- Int_DatabuildOrders_Default.ini
Settings
...
Key
...
Description/Setting
...
IntegrationType
...
Description:
Specifies the type of integration to be performed. This is a fixed value that should not be changed.
Setting:
Databuild Ordering
...
UseWizard
...
Description:
Specifies whether Integration will be run manually or automatically.
Setting:
0: Integration will be run based on the values in the ini file and can be run automatically without user intervention.
1: Integration will be run using a wizard allowing users to modify the details of the integration.
...
ODBCConnectionType
...
Description:
Indicates if the Databuild database is SQL Server or Microsoft Access.
Setting:
1: SQL Server
2: Microsoft Access
...
YieldMilliSeconds
...
Description:
Length of time to pause the program in milliseconds.
Setting:
0 (default)
Databases
...
Key
...
Description/Setting
...
ODBCDSN_Framework
...
Description:
ODBC DSN name for the Framework database.
Setting:
FworkSQLEcm
...
ODBCConnect_Framework
...
Description:
ODBC DSN connection string for the Framework database.
Setting:
None
...
ODBCDSN_FrameworkLicense
...
Description:
ODBC DSN name for the Framework Licence database.
Setting:
FworkSQLLic
...
ODBCDSN_DataBuildSys
...
Description:
ODBC DSN name for the Databuild system database.
Setting:
FworkDBuildSys
...
DatabaseName_DataBuildSys
...
Description:
Databuild system database name.
Setting:
DataBuildSys
...
ODBCConnect_DataBuildSys
...
Description:
ODBC DSN connection string for the Databuild System database.
Setting:
"uid=enterUserName;pwd=enterPassword"
...
ODBCDSN_DataBuildJob
...
Description:
ODBC DSN name of the Databuild Job database.
Setting:
FworkDBuildJob
...
DatabaseName_DataBuildJob
...
Description:
Databuild Job database name.
Setting:
DataBuildJob
...
ODBCConnect_DataBuildJob
...
Description:
ODBC DSN connection string for the Databuild Job database.
Setting:
"uid=enterUserName;pwd=enterPassword"
Mail Configuration
...
Key
...
Description/Setting
...
Mail_System
...
Description:
Email delivery method.
Setting:
0: no email will be sent.
1: email will be sent using MAPI.
2 (default): email will be sent using SMTP.
...
Mapi_Profile
...
Description:
Microsoft Outlook user profile name.
Setting:
(default): Outlook
...
Mail_From
...
Description:
The name or email address of who/where the email is being sent from.
Setting:
FrameworkIntegration
...
Mail_Recipient
...
Description:
These are the mail recipients of integration logs. Multiple addresses can be added if separated with a semi-colon (;). Spaces are not necessary before or after the semi-colon.
Setting:
enterRecipientEmail@yourDomain.com.au;integrationsupport@insulagroup.com.au
...
Mail_Subject
...
Description:
Email subject heading.
Setting:
"Framework Integration : Databuild Ordering"
...
SMTP_Server
...
Description:
If using Mail_System 2 (SMTP), add the SMTP Server name.
Setting:
enterSMTPServerName (replace this text with your SMTP Server name)
...
SMTP_UseSecurity
...
Description:
Is security used for the STMP server?
Setting:
0 (default): A username or password is not required.
1: A username and password is required. If this setting is used, the SMTP_UserName and SMTP_Pwd fields must have a valid username and password.
...
SMTP_UserName
...
Description:
A valid username for the SMTP server.
Setting:
enterUserName (replace this text with a valid SMTP Server User Name)
...
SMTP_PWD
...
Description:
A valid password for the SMTP username.
Setting:
enterPassword (replace this text with a valid SMTP Server Password)
Criteria
...
Key
...
Description/Setting
...
CriteriaMethod
...
Description:
Determines which data for Databuild Ordering is updated.
Setting:
1: CostCentre
2: Entity
3: Items
4: Orders
5: All
...
OrderCriteria
...
Description:
Criteria for selecting which jobs are updated.
Setting:
1: AllJobs
2: ByConstructionManager
3: BySupervisor
4: SingleJob(JobNumber)
...
OrderCriteriaID
...
Description:
The ID for the construction manager, supervisor, or single job as indicated in the OrderCriteria.
Setting:
0 (default)
...
Context
...
Description:
The Region Division ID if users only want to process Integration for a certain context.
Setting:
0 (default): All Region Divisions will be processed.
...
ProcessApprovals
...
Description:
The type of process approval process.
Note: Only applies if the CriteriaMethod is 4 or 5.
Setting:
1: OrdersAndApprovals
2: OrdersOnly
3: ApprovalsOnly
Note: If the setting is 1 or 3 then orders in Framework that are not found in Databuild will have their status in Framework set to Cancelled.
...
OnlyIntegrateNew
...
Description:
Instructs Integration to only process job orders that have dates within the range specified below.
Setting:
True: Only records within the date range will be included.
False: All records will be included.
...
StartIntegrationDate
...
Description:
If OnlyIntegrateNew is True (above), then we retrieve Databuild orders with dates >= to the StartIntegrationDate.
If StartIntegrationDate is None, then Integration continues as if OnlyIntegrateNew was set to False.
Setting:
None
dd/mm/yyyy
...
EndIntegrationDate
...
Description:
If OnlyIntegrateNew is True (above), then we retrieve Databuild orders with dates <= EndIntegrationDate.
If EndIntegrationDate is None, then today's date will be used.
Setting:
None
dd/mm/yyyy
Actions
...
Key
...
Description/Setting
...
LinkPOsToLogisticsItems
...
Description:
- Unlinks cancelled Orders from uncalled Construction Logistics Activities.
- Links valid Orders to Construction Logistics Activities based on criteria.
Setting:
True: Link function is switched on
False: Link function switched off
...
ApproveReceiptedInvoices
...
Description:
The Payment Approval status for a Purchase Order made on the Construction Logistics tablet is automatically set to Payment Authorisation in Databuild.
Setting:
True: Approval function is switched on
False: Approval function switched off
Integrated Fields
The integration of Databuild Purchase Orders to Framework is fixed in the content that is exchanged between the systems. There are no user-configurable integrated fields available to this type of integration.
...