Litle & Co

• Litle & Co. is now fully part of the Vantiv brand family.
• Vantiv and Litle & Co.Two Great Names, One Powerful Company.
• We remain committed to delivering you timely, relevant information on the payments industry and our solutions at vantiv.com.
• Now you can collect credit card and ACH revenue right in Salesforce.
• With Litle & Co., A Vantiv Company, and AppFrontier, makers of Chargent Payment Processing for
• Litle & Co., A Vantiv Company.
• Payment processing solutions that contain costs, generate revenue, and manage risk
• Comprehensive, best-in-breed payments management platform
• Combat fraud, manage chargebacks, and secure cardholder information through tokenization
• Real-time reporting and analytics to track data at transaction level
• AppFrontier

Makers of Chargent Payment Processing for Salesforce

100% Salesforce native Credit Card / ACH payments

One-time payments or Recurring billing schedules

Connects in seconds to Litle & Co., no integration required

PCI-DSS compliant payment processing directly from within Salesforce

AppFrontier

• Recurring Payments

Z-Payments makes it easy to receive, reconcile, and manage recurring payments at any frequency - ad hoc, monthly, semi-annually, anually, etc. via payment processing providers such as Authorize.net, Chase Paymentech, and Litle & Co.

• Payment Management and Management platform for businesses that sell goods and services directly to consumers.Transaction Management and consultative merchant services for card-not-present and alternative payments.
• Alternatives reference : http://www.getapp.com/litle-co-application
• Chargent connects directly from Salesforce to a number of different Payment Gateways. You can use any Payment Processor on the back end to process the payments, as long as it works with one of the Gateways that Chargent connects to. You can think of Chargent as a "virtual terminal" that lives 100% within Salesforce, and sends secure credit card and ACH transactions to a gateway, which then sends it to a merchant account and eventually your bank.
• 
• To begin credit card and ACH transactions through Salesforce with Chargent, you need a merchant account from a payment processor as well as a payment gateway. Some companies bundle the two services together but they can also be purchased separately.
• The gateway is a service running on servers that securely connects the purchase platform (eg. Salesforce with Chargent installed, or an eCommerce web site) to the payment processor. When you process a transaction through Chargent, the credit card info is sent through the gateway to the processor.
• The processor hosts the merchant accounts. It is responsible for securely receiving the data sent by the gateway. When it obtains the information needed to process the payment, it begins to handle the transaction and transfer money from the customer to the merchant's bank account.
• Many large payment processors support multiple payment gateways. This is often hard to find on their web site however, since they typically prefer that you use their own gateway or a private labeled gateway, but if you contact them they should provide you with the information.
• As an example, if you use Chase Paymentech for your Payment Processor, you can use Chase's Orbital Payment Gateway, but you can also choose Authorize.net as your Payment Gateway.
• Vantiv (formerly Litle & Co.)

Vantiv is both the payment processor and gateway, using its own proprietary XML gateway to package a complete solution.

Chargent customers wishing to use Vantiv should sign up for the Vantiv Transact service and reference AppFrontier™ / Chargent when enrolling

Vantiv Transact with Chargent's Opportunities package currently supports Tokenization

• Tokenization

Tokenization is a security technology that replaces credit card numbers with "tokens" generated by a payment processor. This means that merchants are not required to store the credit card numbers, and the secure token replaces the credit card number for processing transactions and being stored in your database. Each token is specific to a merchant, so it is useless to anyone else in the event of a security breach.

Chargent currently supports tokenization through our partners Merchant e-Solutions, USAePay, Chase, Vantiv, Stripe, and Realex Payments with the Opportunities package.

Vantiv's tokens are 16 digit numerical codes where the last 4 digits is the same as the credit card's last 4 digits, so you can still show your customers which card they used. Only the card number is tokenized. The expiration date and card verification number are still sent along with the token. This means that the tokens will only expire if the cardholder changes their account number.

Chargent also offers eCheck / ACH tokenization through its partner Vantiv. Because bank account numbers differ greatly in length, eCheck tokens are 17 digit numerical codes which are completely randomly generated. The Vantiv system supplies the last 3 digits of the account number in a separate field.

So consider using tokenization with Salesforce and Chargent. Unlike a credit card or account number, you can store tokens without the possibility of exposing customer information. And Vantiv stores the information in their secure systems, and accesses it only when you submit a transaction using the supplied token.

• You can use any of these payment processing services with Chargent if you choose Authorize.net as your payment gateway:

Barclaycard

Chase Paymentech

Elavon

First Data Merchant Services (FDMS)

Global Payments

Heartland Payment Systems

WorldPay

TSYS Acquiring Solutions (SM)

• You can use any of these payment processing services with Chargent if you choose Payflow Pro as your payment gateway:

Chase Paymentech

First Data Merchant Services (FDMS)

Global Payments

NOVA

Wells Fargo

Vital

                           

* Reference : Content & image from google.

Community Designer : Points to remember

1. Community Designer in conjunction with community templates for self-service lets you create, brand, and publish a custom community site that looks great on any mobile device
2. Choose from four templates to quickly start your site, and then easily style the pages to match your company’s branding.
3. From Setup, click Communities | All Communities. You can access Community Designer by clicking the Community Designer link(Now manage ?), which was previously named Site.com.
4. If you’re setting up a custom community site for the first time, when you click Community Designer, you can choose from one of four templates to create your site before being brought to Community Designer. (If you don’t want to use the templates, you can skip the template selection to access Site.com directly.)
5. When you access a community site that existed before Winter ’15, you’re brought to Community Designer. However, Community Designer doesn’t support branding for sites that weren’t created by using one of the four templates. Instead, you must use Site.com Studio. To open Site.com Studio, click Go to Site.com Studio in the Communities drop-down.
6. After you’re in Community Designer, you can customize the community template to update your community’s branding and fonts.

7. Navigate (1) to the view that you want to style by clicking links and menu items.
8. Brand the community (2) to match your organization’s style and see your changes immediately appear on the page (1).
9. Use the toolbar (3) to see how your community appears on different devices, access views that aren’t easy to navigate to (such as error and login views), and preview and publish the community.
10. Use the Communities menu (4) to go to Site.com Studio to make advanced customizations to your community pages, open Community Management to manage topics, reputation, and for community dashboards and moderation, and access Community Setup to update community membership, login, and other settings.
11. Community Designer doesn’t support branding for sites that weren’t created by using one of the four available templates.
12. With Community Designer, you can brand only the site’s default home page. To try out a different template, you must set the new page as the site’s home page in Site Configuration in Site.com Studio. But don’t worry—you can always switch back to the original home page.
13. Site.com and the Force.com being the other two, to customize a Salesforce Community.
14. Community Designer (coming Winter ’15):If you need to get a self-service Community up and running fast with few choices to make outside of branding, the Community Designer may be the solution for you. You can apply your branding without writing CSS and use the Site.com Studio to move sections around within a predefined page. The templates are targeted for self-service (case deflection, case submission, etc.) and would not work well as they are today for a Community that incorporates anything beyond support. As the product is in Beta, there are some known limitations and we are expecting this to get more robust in the future and cannot wait to see where this tool goes! Important: The new Community Designer is an excellent replacement for the PKB3 package on the AppExchange.
15. Site.com: Site.com is best used in Communities that have a single type of member and need more customization than the Community Designer offers but do not need to support complex processes or complex, targeted messaging. A 100% Site.com approach tends to work better in Customer Communities than Partner Communities which tend to have many different audiences (ISV,SI, etc.).
16. Force.com: If you need a Community that will support complex business processes, packages from the AppExchange (i.e. a Learning Management System), or multiple audiences with different permissions, we would recommend using classic Force.com for customization. This is where most of our customers find themselves landing currently. Using standard configuration tools as well as Visualforce, you have the ability to easily support multiple audiences and complex business processes inside of a Community. Using this approach also means that you can take advantage of Site.com to create custom pages that are heavy in web content and expose them to Community members through a custom link or tab.
17. More than 2,000 active communities of leading global organizations like British Sky Broadcasting, GE Capital, Honeywell, Key Bank, Pearson, State of Colorado, Tata Communications, are based on the Salesforce Community Cloud platform.
18. The Community Designer (Beta) fills the gap by providing a tool to create visually appealing skins for Salesforce Communities.
19. Communities can now be created quicker than ever with Community Designer. You can create, brand, and publish a custom community that works seamlessly on any device. You can start your self-service community by choosing from four modern design templates that are available, and also manage the styling to match your corporate branding.
20. Community Designer is available in Enterprise, Performance, Unlimited, and Developer Editions. Enter the main Setup, click Communities- All Communities. Click the Community Designer link now (formerly named as Site.com) to access Community Designer. You can now choose from one of the four custom templates available. You can even skip the choice of the templates to directly enter the Site.com Studio; however you won’t be able to use Community Designer for your customized branding.
21. You can update your community according to your company’s branding and fonts once you have chosen the template by following these steps:

Click on the links and menu items available to navigate the view that you want to style.

Upload your branding images, and change fonts and colours to match. You can see the changes immediately as they appear on the page.

You can now use the toolbar to see how your community appears on different devices, check the views that are difficult to navigate such as error and login views, and finally preview and publish the community.

Now go to the Site.com Studio to make advanced customizations to your community pages. Access Community Management to manage topics, reputation, community analytics and moderation.

Finally, go to Community Setup to customize community membership, login, and other settings.

22. Apart from Site.com and Force.com, Community Designer is the third tool to customize and brand your Salesforce Community. The key benefits of using it are:

• Community Designer templates provide a proven engagement framework
• You can apply your branding without writing CSS
• Even non-technical community managers can easily customize the community
• Community designer accommodates company branding with a consistent customized appearance (like fonts and colours) across all the corporate marketing properties in the community
• The templates are directed for self-service: case deflection, case submission, knowledgebase, etc.

23.  Vanessa Thompson of IDC said, “Any company can benefit from creating an engaged community.”

Customer engagement through Communities has shifted to altogether a new phase with more diversifications and added ease-of-use features. With Community Designer (currently in Beta) as the latest addition in the Salesforce Community Cloud, you get 4 templates:

• Kokua: For Knowledge articles and case submissions
• Koa: For text-based and categorised, optimized for mobile devices
• Napili: For support communities and posting questions
• Aloha: For App Launcher access using single sign-on authentication

24. You need to ask yourself:

• Does your current community include these objects: Ideas, Cases, Knowledgebase and Answers?
• Is your community responsive and needs to be accessed outside salesforce1?
• Does your community need features like gamification, custom objects, full text search, etc.?
• Is your community search engine optimized and easily found on web?

        Nice and effective answer for these questions is Community designer. Use and enjoy :)

* Reference :  Images and content from google.

FlexiPage

        A Flexible Page is the home page for an app that appears as a menu item in the Salesforce1 navigation menu. FlexiPage represents the metadata associated with a Flexible Page.The FlexiPage component is only supported in Salesforce1. FlexiPage components have the suffix .flexipage and are stored in the flexipages folder.FlexiPage components are available in API version 29.0 and later.

Like Pagelayout, We can add Custom components in Flexipage however Flexipage will be visible only in Salesforce1 application in sidebar. We can use Flexipage to make custom Homepage for some product which will be accessed directly from Salesforce1.Till date Flexipage can be defined in XML file and then deploying it using Eclipse, Ant Migration tool, workbench or any other migration tool. There is no way to define Flexipage directly in Salesforce using point and click functionality.XML file for Flexipage must needs to have “flexipage” extension and should be saved in “flexipages” folder.

Organizing data in Salesforce1 with FlexiPages:-

On a flexipage, you can add a total of 25 components (mix of listview and recent item components).You can mix and match objects from different types here.The fields shown in your listviews are the first 6 columns of your listview.On a flexipage, you can basically add 2 types of components. You have a “listview” component and a “recent items” component.

More control over your navigation:-

This will basically give you the set of “recently-searched objects”. Meaning that your menu will be changing continuously as your users work more with (for example) campaigns or more with opportunities.

You can already choose which items appear on top by “pinning” objects in the search results page. But still, you can’t control which objects show up or not.In the mobile navigation, you then just remove the “Smart Search Items” and add your Flexible Page Tabs. Now you have full control over which objects appear in the menu, in which order, with the list views you want to give to your users!

But there's no Flexipage entry in the menu!

Ok, so it’s true, there is no graphical page-builder, as you would have with the regular page layout editor. However, you don’t need any real developer tools or skills and most of the work you can just copy-paste from the Salesforce documentation.

Just create a folder on your drive with the name you want to give to your flexipage. In that folder, create another folder called “flexipages”. Then, in the flexipages folder, create a file called <your_flexipage_name_here>.flexipage . (make sure the extension of the file is “.flexipage”) In your main folder, now also create a file called “package.xml”.

IMPLEMENTATION (Sample: copied from a code available on internet):-

Step1 : Defining XML file for Flexipage containing detail of components

Filename – “AccountFlexi.flexipage”

   <?xml version="1.0" encoding="UTF-8"?>

   <FlexiPage xmlns="http://soap.sforce.com/2006/04/metadata">

       <flexiPageRegions>

           <componentInstances>

               <componentInstanceProperties>

                   <name>entityName</name>

                   <value>Account</value>

               </componentInstanceProperties>

               <componentInstanceProperties>

                   <name>filterName</name>

                   <value>AllAccounts</value>

               </componentInstanceProperties>

               <componentName>flexipage:filterListCard</componentName>

           </componentInstances>

           <name>main</name>

       </flexiPageRegions>

       <quickActionList>

           <quickActionListItems>

               <quickActionName>NewAccount</quickActionName>

           </quickActionListItems>

       </quickActionList>

       <masterLabel>My new App</masterLabel>

   </FlexiPage>

XML file for Flexipage must needs to have “flexipage” extension and should be saved in “flexipages” folder.

Supported components in Flexipage

1. ListView identified by “flexipage:filterListCard”
2. Recent Items identified by “flexipage:recentItems”
3. Chatter Action identified by “quickActionListItems”

Note :

• For List View Supported objects include standard objects (Account, Campaign, Case, CollaborationGroup, Contact, Contract, Lead, LiveChatTranscript, Opportunity), custom objects.
• Recent Items are available only for Custom Objects.

Step 2 : Create package.xml

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
 <types>
   <members>AccountFlexi</members>
   <name>FlexiPage</name>
 </types>
 <version>29.0</version>
</Package>

Step3 : Deploying Flexipage

Create Zip file containing above both XML files.We need to deploy this zip file into Salesforce and for that, I am going to use Workbench. In Workbench, navigate to deploy, select your zip file and select “Single package”. Once you have successfully deployed above zip file, you will see below page conforming Success message.

Step4 : Creating Tab for Flexipage

Once deployment is done, we can create a new Tab for flexipage. Navigate to create new Tab and at bottom of page you will see option to select new tab for flexipage as shown in below image.

Step 5 : Configuring Navigation menu in Salesforce1

After creating flexipage tab, We have to tell Salesforce1 engine to display this tab in navigation menu of salesforce 1.

Navigate to “Setup | Administration Setup | Mobile Administration | Mobile Navigation” and add Flexipage to navigation.

Step 6 : Testing Flexipage / Flexipage in Action

Now login to Salesforce application from your mobile phone by launching Salesforce1 app or you can also launch it from your browser by navigating to this address “https://YOURINSTANCE.salesforce.com/one/one.app”.

Access Salesforce1 from Browser

Flexipage in Action

Flexipage Components in Salesforce1

Summer 14 changes :-

New FlexiPage Object

Represents a Flexible Page. A Flexible Page is the home page for an app that appears as a menu item in the Salesforce1 navigation menu. Includes access to the associated FlexiPage object in the Salesforce Metadata API.

The following field has been added:

• Description

The optional description text of the Flexible Page.

The following field has been updated:

• ComponentName

This field is now required

Flexible Pages

The flexipage:recentItems component now supports these objects, based on the specified properties.

• All custom objects

• All standard objects for which both of these conditions are true:

◊ A compact layout is defined for the object.

◊ The object is tracked in the most recently used objects list.

If an object is tracked in the most recently used objects list, either one or both of the LastViewedDate or LastReferencedDate fields is present.

The flexipage:filterListCard component now supports all list views that are associated with standard and custom objects except:

• Activity
• ContentVersion
• Task
• User
• UserProfile

                

*Reference : Content &  Images from google.