Overview

by using extract() function, we can create variables with associative arrays elements

varaible names are element keys and variable values are element values

<?php
$arr=array('x'=>10,'y'=>20,30,'abc'=>'scott');
extract($arr);
echo $x;  //10
echo $y;  //20
echo $abc;  //scott
?>

Sometimes you might find yourself in a situation where you have to send a bunch of text obtained from a database query, to jQuery or JS script to insert it into the DOM.

One of the ways to do that is to convert the data obtained from a PHP query, into a JSON object, and then inject this into the DOM asynchronously ( using AJAX, of course). This can be done as follows :

First lets talk about the structure of a simple json object :

1. {

2. “name”: “Solomon”,

3. “age” : “67”,

4. “sex”: “male”

5. }

Its similar to an associative array with some “key” : “value”  pairs. Both the keys and values are written in quotes. To access these values in Javascript, this json object is assigned to a variable :

1. var json =  { “name”: “Zara Ali”, “age” : “67”,”sex”: “female”};

2. console.log(json.name);       //this prints “Zara Ali” on the browser’s console

Management Reporting Integration

Okay, so in a shameless attempt to boost SEO we’re starting a blog. That said, as we’re doing this we may as well share some meaningful content with you…. You can see more about what we do at our site.

Our first blog is going to be on integrating your CRM (see, shameless SEO boosting) or dialler (be it a predictive dialler or automated) into a cloud based reporting suite.

We’re getting a lot of requests at the moment from businesses, not just the ones using our systems, but people who already have a solution such as Salesforce CRM or Davika dialler.

So What’s The Problem?

Off the shelf is the problem. Businesses such as SAP, Siebel, Salesforce, Davika (the list could go on) work on a high volume principle: “We need out of the box products that can be sold quick). The issue here is that…

The Summer ’13 release brought an interesting new feature in the area of identity management – Multi-Provider Single Sign-On. The general principle being (to my initial reading of the release notes) that a single Salesforce org can perform federated authentication to multiple identity providers. Useful indeed where SSO is desirable but the Salesforce implementation spans multiple IT environments within a single enterprise. For example a subset of the user base may have their identities managed by Active Directory whilst the remainder are Google Apps users and have no AD user principal. Prior to Summer ’13 an org could only be configured as a service provider in relation to a single identity provider (IdP), therefore in the example the Salesforce SSO settings could be configured to point to an ADFS endpoint, enabling authentication by AD but what about the Google Apps users?

So, Summer ’13 seemingly addressed this limitation enabling multiple…