mediact/robinhq-hooks

There is no license information available for the latest version (2.3.3) of this package.

Maintainers

Details

github.com/mediact/magento-robin-integration

Source

Installs: 608

Dependents: 0

Suggesters: 0

Security: 0

Stars: 0

Watchers: 3

Forks: 8

Type:magento-module

2.3.3 2018-12-05 13:04 UTC

Requires

Unknown License ca75d70eb72671ad93661a427733c0280e80ffea

This package is auto-updated.

Last update: 2024-12-06 10:03:30 UTC

README

THIS README NEEDS MORE UPDATING

Magento Robin integration

This package is designed as a starting point and a way to show how you could use the ROBIN API in your Magento shop. It currently sends over data to ROBIN when a customer and/or order is created or updated through the front- and back-end. The module is tested in Magento 1.7, 1.8 and 1.9.

Dependencies

Please ba aware that this package depends upon https://github.com/jkowens/magento-jobqueue. Please install it first before installing and using this package, otherwise this package won't be usable. You also need to have magento cron enabled to make the queueing work.

Setup

Make sure you have your ROBIN API key and API secret. If you don't have the API secret, [You can request it here][request-api-key-secret]. You can also ask the ROBIN people what your API key is if you don't know where to find it.

Installation

  • Clone or download the git repo
  • If you downloaded the repo, unpack it
  • Copy over the files, preferably using rsync (rsync -rtlv --progress /location/of/package_files/ /location/of/magento/)
  • Log out of admin, flush cache, log back in

What's installed?

The module gets installed inside the app/code/community/Robinhq/Hooks folder and the package settings file is located inside app/etc/modules/Robin_Hooks.xml. The admin design files are: design/adminhtml/default/default/layout/Hooks.xml and design/adminhtml/default/default/template/hooks/hooksbackend.phtml The module does not have it's own sql file or database, the api key and secret are saved through Magento's config.

What's next

If you didn't get any errors, that's good! Now log out and back in again to be sure Magento takes note of the changes. You can now turn Compilation back on if you turned it off during installation. Also disable Configuration under Cache Management. Again I want to make sure you have your [api key and secret][request-api-key-secret] otherwise the module won't work!

Now go to System -> Configuration -> ROBINHQ -> Settings -> API Settings and fill in your API key and API secret. The API base url is already provided for you, as are the fields Seconds to wait and Bulk Limit these settings are there for when you want to do a bulk import. After you have filled in both keys click save config and you are done! All future orders and customers will be automatically send to ROBIN when they are created and/or changed.

Initial data

You might have noticed the new Robin tab in your back-end menu bar. This is to send over existing customers and their orders to ROBIN. To start the process, simply go to Robin -> Mass Send and click on the Run button.

Warnings and Logging

By default the package will log what's happening and give the admin page notifications when something went good or bad. To see the log file, log in to your web server through ssh and navigate to your Magento root folder.

To see the contents of the log file do the following var/log/Robinhq_hooks.log Use tail to keep an eye on it.

Be sure you have logging enabled in the developer settings from Magento.

Development

The events

This module listens to the following events:

  • customer_save_after
  • sales_order_place_after
  • sales_order_save_after

customer_save_after

This event gets called when a customer is created, it's information changed or when the customer places an order. On this event Robinhq_Hooks_Model_Observer::customerHook gets executed as defined in etc/config.xml

<config>
    <global>
        <events>
            <customer_save_after> <!-- identifier of the event we want to catch -->
                <observers>
                    <customer_save_after_handler> <!-- identifier of the event handler -->
                        <type>singleton</type> <!-- class method call type; valid are model, object and singleton -->
                        <class>hooks/observer</class> <!-- observers class alias -->
                        <method>customerHook</method>  <!-- observer's method to be called -->
                        <args></args> <!-- additional arguments passed to observer -->
                    </customer_save_after_handler>
                </observers>
            </customer_save_after>
        </events>
    </global>
</config>

sales_order_place_after

This event gets called after an order is placed. On this event Robinhq_Hooks_Model_Observer::orderPlacedHook gets executed as defined in etc/config.xml

<config>
    <global>
        <events>
           <sales_order_place_after> <!-- identifier of the event we want to catch -->
               <observers>
                    <sales_order_place_after_handler> <!-- identifier of the event handler -->
                        <type>singleton</type> <!-- class method call type; valid are model, object and singleton -->
                        <class>hooks/observer</class> <!-- observers class alias -->
                        <method>orderPlacedHook</method>  <!-- observer's method to be called -->
                        <args></args> <!-- additional arguments passed to observer -->
                     </sales_order_place_after_handler>
               </observers>
            </sales_order_place_after>
        </events>
    </global>
</config>

sales_order_save_after

This event gets called after an orders status changes or when any other type of order related changes gets saved. On this event Robinhq_Hooks_Model_Observer::orderStatusChanceHook gets executed as defined in etc/config.xml

<config>
    <global>
        <events>
           <sales_order_save_after> <!-- identifier of the event we want to catch -->
                <observers>
                    <sales_order_save_after_handler> <!-- identifier of the event handler -->
                        <type>singleton</type> <!-- class method call type; valid are model, object and singleton -->
                        <class>hooks/observer</class> <!-- observers class alias -->
                        <method>orderStatusChanceHook</method>  <!-- observer's method to be called -->
                        <args></args> <!-- additional arguments passed to observer -->
                    </sales_order_save_after_handler>
                </observers>
                </sales_order_save_after>
        </events>
    </global>
</config>

The Code

The class Robinhq_Hooks_Model_Observer is the entry class for all events that we are hooking into. From there the api gets called by using Robinhq_Hooks_Model_Api::orders() or Robinhq_Hooks_Model_Api::customers()`.

Robinhq_Hooks_Model_Api::orders()

This method goes through all orders given to it, maps it to a RobinOrder as required by the [Robin API][robin-api] and sends it to the orders API endpoint. To generate a RobinOrder the method Robinhq_Hooks_Model_RobinOrder::factory() is used. This method collects order details like the products, shipments and invoices and formats them according to the details_view object required by the [Robin API][robin-api].

{
  "orders": 
  [
    {
      "email_address":  "email@address.com",
      "order_number":  "RHQO1234",
      "url":  "http://shop.com/order/RHQO1234",
      "order_by_date" : "2014/01/29",
      "list_view": 
      {
         "order_number":  "RHQO1234",
         "date":  "29-01-2014 12:34",
         "status":  "In progress"
      },
      "details_view": 
      [    
        {
          "display_as": "details",      
          "data": 
          {
             "date":  "29-01-2014 12:34",
             "status":  "In progress",
             "payment_status":  "Partially paid",
             "shipment_status":  "Partially shipped"
          }
        }, 
        {
          "display_as": "columns",
          "caption": "products",
          "data" :
          [
            {
              "product":  "iPhone 5S",
              "quantity":  "1",
              "price":  "$695.50"
            },
            {
              "product":  "iPad 3",
              "quantity":  "2",
              "price":  "$898.00"
            },
            {
              "product":  "Shipment",
              "quantity":  "",
              "price":  "$10.00"
            },
            {
              "product":  "Total",
              "quantity":  "",
              "price":  "$1603.50"
            }
          ]
        },
        {
          "display_as": "rows",
          "caption": "shipments",
          "data":           
          [
            {
              "shipment":  
                 "<a href=' http://shop.com/shipment/RHQS01'>RHQS01</a>",
              "status":  "Shipped"
            },
            {
              "shipment":  
                 "<a href=' http://shop.com/shipment/RHQS02'>RHQS02</a>",
              "status":  "Not shipped"
            }
          ]
        },
        {
          "display_as": "rows",
          "caption": "invoices",
          "data":           
          [
            {
              "shipment":  
                 "<a href=' http://shop.com/invoice/RHQI01'>RHQI01</a>",
              "status":  "Paid",
              "amount":  "$1200.00"
            },
            {
              "shipment":  
                 "<a href=' http://shop.com/invoice/RHQI02'>RHQI02</a>",
              "status":  "Not paid",
              "amount":  "$403.50"
            }
          ]
        }
      ]
    }
  ]
}

Robinhq_Hooks_Model_Api::customers()

This method goes through all customers given to it and maps them to a RobinCustomer as required by the [Robin API][robin-api] and sends them to the customers API endpoint. To generate a RobinCustomer the method Robinhq_Hooks_Model_RobinCustomer::factory() is used. This method makes a customer object required by the [Robin API][robin-api].

{
      "email_address":  "email@address.com",
      "customer_since":  "2014-01-28",
      "order_count":  12,
      "total_spent":  "$154.95",
      "panel_view":  
      {
         "Orders":  "12",
         "Total_spent":  "$154.95"
      },
      "name": "John Doe",
      "currency":"EUR",
      "phone_number":"0612345678"
}

The ROBIN API documentation also talks about optional data. This package sends those fields by default.

The panel_view contains a new object of key/value pairs that can be anything. As an example I've added the total orders and the total spent. How to use the panel_view array is explained in the [Robin API][robin-api] documentation.

Adding more order data to send to Robin

You can extend the data you want to be visible inside Robin by adding key/value pairs to the list_view or the data arrays each method inside Robinhq_Hooks_Model_RobinOrder::getDetailsView() returns. If you want to add a complete new details_view like the comments from a order, you can add the logic inside the Robinhq_Hooks_Model_RobinOrder::getDetailsView() method like this

private function getDetailsView(){
        $details = $this->getDetails();
        $productsOverview = $this->getProductsOverview();
        $shipments = $this->getShipments();
        $invoices = $this->getInvoices();
        $comments = $this->getComments(); //new line of code!
        return array($details, $productsOverview, $shipments, $invoices, $comments); //the order of this array determines the order of the different panel views you have inside the Robin conversation
    }

Now create a new method inside Robinhq_Hooks_Model_RobinOrder called getComments and let it return a array with the comments data with the following layout

{
    "display_as":"rows",
    "caption": "Order Comments",
    "data": []
}

Inside the data key you can add an array with objects containing key/value pairs like this

{
    "Date:":"Jun 24, 2014 2:35:41 AM",
    "Content:": "This is a comment from the admin",
    "Order Status:":"On Hold",
    "Customer Notified:":"Yes"
}

Note: the name of the key will also be displayed, so be sure to format it nicely.

Environment

This example code is all developed with the use of a Vagrant box. If you want to develop you own implementation based on this code, I strongly recommend to use a Vagrant box as a development environment as the setup is quick and easy. If you are new to Vagrant, please watch [this][magento-vagrant] little presentation to get you up to speed.

I recommend to use [this one][magento-vagrant-github]. Simply follow the instructions provided there and you should have a virtual Magento installation in no-time.

Git and Magento module development

The easiest way to install is to use modman:

The latest version of Magento 1.9.3.3 disables the use of symlinks and thus stops this installation method from working or should at least not be used anymore.

cd your_magento_project_dir
modman init
modman clone https://github.com/graciousstudios/magento-robin-integration.git

And enable symlinks by going to System -> Configuration -> ADVANCED -> Developer -> Template Settings and set Allow Symlinks to Yes. The idea here is to create a separated folder that only contains the module files and folders and link that to the magento installation. This way your magento installation won't have to be a git repository and you won't have to do some weird .gitignore magic.

Now you can develop inside the .modman/magento-robin-integration folder.

Links

Modman to install the module easily modman

Magerun lets you enable symlinks, generate phpstorm helper file, run module setup, etc. A must have! magerun

request-api-key-secret

robin-api

License

The code is licensed under the [GPL v3 licence][gpl-v3-licence] gpl-v3-licence