This integration starts by executing a FatTail saved report. For each record:
- A iMeet® Central Account will be created for each FatTail Client
- A iMeet® Central Workspace will be created for each FatTail Order
- A iMeet® Central Milestone will be created for each FatTail Drop
References to the FatTail object will be retailed in iMeet® Central and references to iMeet® Central objects will be stored in FatTail to minimize duplication.
This integration requires that the "Account View" feature is enabled on your iMeet® Central account. Please contact support@centraldesktop.com for more information on this topic.
You will need to create the following customer fields in the iMeet® Central interface before continuing.
Account:
- c_client_id
Workspace:
- c_order_id
- c_campaign_status
- c_campaign_start_date
- c_campaign_end_date
Milestone:
- c_drop_id
- c_custom_unit_features
- c_kpi
- c_drop_cost_new
All custom fields can have any name, but must be of type text and when entering the API ID must not contain "c_" (this will get prepended automatically).
You can create these custom fields under "Company Setup" then the "Custom Fields" tab as the Company Admin. Here you will add the above custom fields by adding property fields under the "Account Properties", "Workspace Properties", "Milestone Properties" tabs.
Your generated FatTail report must also contain the following columns:
- Client ID
- Client Name
- (Campaign) CD Workspace ID
- Campaign ID
- Campaign Name
- IO Status
- Campaign Start Date
- Campaign End Date
- Sales Rep
- (Drop) CD Milestone ID
- Position Path
- Drop ID
- Drop Description
- (Drop) Custom Unit Features
- (Drop) Line Item KPI
- Start Date
- End Date
- Sold Amount
Please ensure that your FatTail account is also set up with the following:
- Orders have a dynamic property named "H_CD_Workspace_ID" with type Text
- Drops have a dynamic property name "H_CD_Milestone_ID" with type Text
- Copy cd_config.yml.tpl as cd_config.yml and fill in the settings.
- Copy fattail_config.yml.tpl as fattail_config.yml and fill in the settings.
To get your API client_id and private key, please navigate to Company Setup > Advanced > API. Select a user that has the appropriate permissions to create accounts and workspaces. You may want to create a new user specifically for this purpose.
After clicking on "Create new Client ID," your browser will download a file with the necessary information to create a trust relationship between this application and iMeet® Central.
The client_id and the private_key that are required in cd.config.yml are found in this json file.
You'll need to use our API in order to fetch the workspace_template_hash as well as the sales_role_hash.
This application manages its dependencies with Composer. For more information, including install instructions, please go to https://getcomposer.org/
composer install -o
php bin/run.php sync