via Adding Metadata to tickets created by the Mobile SDK – Zengineering Blog – Zendesk Developer Portal.
Zendesk provides a number of ways to add additional information to tickets. This helps provide context for agents or can even be used to trigger business logic. The iOS and Android mobile SDKs provide four ways to append additional information to created tickets. This information is stored globally so it can be set at any time before a ticket is created and will be added to every ticket submitted over the lifetime of the app. Below is a brief summary followed by examples of how to use each type in the mobile SDKs. All of the examples below add metadata to tickets created by the Zendesk Mobile SDK. They have no effect on the UI provided with the SDK.
- Ticket Fields: Ticket fields contain data about a ticket, such as subject, requester, status, and description. For more information please see About Ticket Fields.
- Tags: Tags are strings you can use to add more context to tickets. For more information please see Using Tags.
- Additional Text: The iOS and Android mobile SDKs allow you to appended additional text directly to each ticket created.
- Ticket Forms (Enterprise only): A ticket form is a set of predefined ticket fields for a specific support request. For more information please see Creating Ticket Forms.
via Amazon Web Services Mobile SDKs for Xamarin Now Available | Xamarin Blog.
Today, we’re excited to share the launch of the Amazon Web Services (AWS) Mobile SDKs for Xamarin. With these new SDKs, developers can easily connect their high-performance, native Xamarin apps to Amazon’s powerful array of AWS cloud services.
AWS platform services provide several powerful solutions, including: identity management through Amazon Cognito Identity, Amazon Cognito Sync, Amazon Simple Storage Service cloud storage, Amazon DynamoDB’s fully managed database, Amazon Mobile Analytics, and Amazon Simple Notification Service for mobile push notifications.
The AWS Mobile SDKs for Xamarin allow you to use a shared C# codebase to connect your native Xamarin iOS and Android apps to any of these AWS services. For example, you can use Amazon Cognito Cloud Sync to synchronize app states between devices for a seamless, cross-device experience and use Amazon S3’s cloud storage for easy access to critical documents and content.
Integrating the AWS Mobile SDKs for Xamarin into your mobile apps is simple.
Source code of the sample at : https://github.com/ajaychebbi/mobilef…
Detailed how to on creating a Xamarin Forms based app and adding MobileFirst SDK to it to connect and invoke procedure.
Step by step guide to people new to Xamarin as well as IBM Mobile First. This video will guide you to
Create a Xamarin app
Add a simple button and display a alert
Add the IBM MobileFirst component
Write code to connect to the MobileFirst server
Add a MasterDetail layout
Invoke a procedure and display the feed in a list View
In this article we are going to explore building a simple native Android application that utilizes the Chatter REST API within the Salesforce Platform. To accomplish this, we will use the Salesforce Mobile SDK 2.1, which acts as a wrapper for low-level HTTP functions, allowing us to easily handle OAuth and subsequent REST API calls. The TemplateApp provided in the SDK as a base is really going to be your cleanest starting point. My tutorial essentially uses the structure of the TemplateApp and build upon it by borrowing and modifying from the REST Explorer sample application; this helps to ensure things are as straightforward as possible. We aren’t going to touch on every aspect of building this application, but instead cover the salient points, giving the reader a good starting point and trying to expand on the salesforce.com documentation. This tutorial attempts to serve as a bit of a shim for developers are not overly familiar with the platform to use the API in a way that is presumably more familiar. A lot of what we’ll cover will complement the Salesforce Mobile SDK Developer Guide; throughout this tutorial I will reference the relevant page numbers from that document instead of reproducing that information here in its entirety.