This post is article 21 from the 30 Articles App series for SharePoint

One of the common question I get from many readers is that what possibly they can do with SharePoint App? So here in this article I will discuss about what possible SharePoint artifacts and components you can include in an App.

One explicit limitation of the SharePoint App Model is that no server-side code can reside on the SharePoint farm as part of an App, and so if your app need to use any server-side code then it must be hosted outside of SharePoint either in the cloud or on-premises. So and when applicable any use of server-side code need cloud App Model. And the main benefit is that you can always scale your application without affecting the current SharePoint environment.

So here it begins, You can create/include all sort of SharePoint components mentioned below in your SharePoint App :

Fields (of field types that are built into SharePoint)

Custom content types

Custom List templates

List and library instances

Custom list views

Custom list forms

Remote event receivers -> check Article -17, 18 for more details

Custom actions (including shortcut menu items and ribbon customizations) -> Check Article -12

Modules, Pages, CSS, JavaScript files used by SharePoint pages,

SharePoint WebParts (built-in) and app parts -> Check Article -8

You can also include Features (Web-scoped only), Web templates (but not site definitions), BCS Models (web-scoped only), external Content types and external lists referencing to that BCS Model, Property bags; and Workflows (SP2013 workflows now use Azure hosted workflow runtime. Coded workflows that use the SharePoint-hosted workflow runtime cannot be included in an app for SharePoint.Only declarative workflows or workflows that use the newer runtime are allowed. to see what’s new in SP2013 workflow check this)

This post is article 20 from the 30 Articles App series for SharePoint

I assume you have read article -19 to understand basic about cross-domain calls in SP Apps.

In this article I will discuss about implementing cross-domain communication from an SharePoint app.

• Let’s get started with placing SP.RequestExecuter.js library ( you can find this in LAYOUTS folder ) into you app project. you can put this file in scripts folder in your app project.
• Register the trusted domain(s) in your app manifest like below.
  Lets say for example I want to put otherdomain.com as a trusted domain so I am registering that as following.

   <AppPrincipal> 
     <Internal AllowedRemoteHostUrl="https://otherdomain.com/" /> 
   </AppPrincipal>
  

• With this library you can use REST or JSOM to communicate with SharePoint
• For REST option you will need to create a new SP.RequestExecutor as following.

  var executor = new SP.RequestExecutor(appweburl);
  executor.executeAsync(
  {
  url:
  appweburl +
  "/_api/SP.AppContextSite(@target)/web/lists/getbytitle('aanuslist')?@target='" + targeturl+ "'" ,
  method: "GET",
  headers: { "Accept": "application/json; odata=verbose" },
  success: successHandler,
  error: errorHandler
  }
  );

• If you choose JSOM then get client context as below.

  var context = new SP.ClientContext(appweburl);    
  // context: The ClientContext object provides access to the web and lists objects. 
  var factory =  new SP.ProxyWebRequestExecutorFactory(appweburl); 
  // factory: Initialize the factory object with the app web URL. 
  context.set_webRequestExecutorFactory(factory); 
  var contextt = new SP.AppContextSite(context, targeturl);
  
  //Get the web and list objects and prepare the query 
  var web = contextt.get_web(); 
  var list = web.get_lists().getByTitle("aanuslist"); 
  var camlString = "<View> <ViewFields>" +
                   "<FieldRef Name='Title' />" +           
                   "</ViewFields> </View>";
  var camlQuery = new SP.CamlQuery(); 
  camlQuery.set_viewXml(camlString); 
  allItems= list.getItems(camlQuery); 
  context.load(allItems, "Include(Title)"); 
  //Execute the query with all the set options and parameters 
  context.executeQueryAsync(successHandler, errorHandler);
  
  

• Make sure in both scenarios your page includes reference to the cross-domain js library

Happy reading… and see you guys for the next article 🙂