Options related to the Agvance connection are available on the Settings page. These options may change how the integration functions and depend on how a company utilizes Agvance.
Found under “Settings” on the left-hand navigation bar, this page holds controls for the integration to connect to an Agvance database and ways this connection can function. This page is normally configured during onboarding and only infrequently visited for regular operation.
API Connection information
Database ID: This number is provided by Agvance and entered during Integration onboarding. It is usually a seven-digit number; any leading alphanumeric characters should be ignored.
Username: This is a three-letter alpha identifier “User ID” from Agvance. Customers should create a dedicated user specifically for the Kahler API, separate from those used for routine tasks performed by individuals in Agvance.
User Password: This is the password associated with the Agvance user created for the Kahler API. Customers should use a strong, secure password and document it in a safe place for future reference.
Configuration Options
Do not mark orders as loaded after dispensed: When unchecked, orders will be set as “Loaded” in Agvance as part of recording final amounts. If checked, final amounts will be recorded but status will not be changed as part of the process.
Destination Source: Companies may use different fields in Agvance to note the destination for an order. On import of an order, this option controls what field should be used for the order destination. Default option of “Ship to” will use Agvance's “Ship to” field as the order destination while “Field Description” will use the “Field Description” field from Agvance.
Import Agvance On-Hold Orders: When enabled (checked), orders set to On-Hold in Agvance’s blend settings will be brought into Constellation and displayed on the Orders page. When disabled (unchecked), orders set to On-Hold in Agvance will not be brought into Constellation or displayed on the Orders page until their status is updated.
Disable exporting orders: Constellation provides the ability to temporarily disable orders from flowing to Agvance. When this setting is enabled, a warning message will notify the admin that the integration is disabled. If a large number of orders are sent simultaneously, the system will ensure all orders successfully reach Agvance, and a notification mechanism will alert the user if any orders fail to transfer.
Only export when blend ticket is Unlocked: Agvance may lock orders during fulfillment for several reasons. Enabling this option will cause the integration to wait for an order to be unlocked prior to sending values back.
Only export when blend ticket has a Dispatch status of "Completed": Agvance may lock orders during fulfillment for several reasons. Enabling this option will delay reporting final amounts back to Agvance until the status is “completed”. Otherwise amounts will be reported back immediately on order completion.
Only wait for Dispatch status of "Completed" for Custom Applied Blend Tickets: Agvance may lock orders during fulfillment for several reasons. Enabling this option will delay reporting final amounts back to Agvance until the status is “completed” for custom applied blend tickets. Otherwise amounts will be reported back immediately on order completion.
Save
Click “Save” to apply changes.
Further Reading
- Constellation Agvance Integration
- Constellation Agvance Integration – Site Mapping
- Constellation Agvance Integration – Product Mapping
- Constellation Agvance Integration – Orders
- Constellation Agvance Integration – Branch Mapping
Still Need Help?
Submit an online web ticket or call us at Kahler Automation 507-235-6648 Option 2.