K2 Vs Nintex workflows for SharePoint

Areas	K2	Nintex
Business	·         Good tool for representing processes visually ·         Support for delivery of data to process approvers and other stakeholders that includes the information they need to perform their role in the process in a friendly format. Ability to show them the data they need to make a decision on a variety of devices, and to record their decisions. ·         Good tools for monitoring and reporting process performance and identify delays.	·         Nintex Workflow is GUI base and easy to use. It is suited for workflows that are not too complex. It would be great to have more in depth training and the user guide has room for improvement as well ·         Nintex is a great tool for a logical, tech-minded individual without official development skills.
Support	·         K2 as has best support and great community base	·         Nintex lags in support
Advantages	·         User friendly ·         Reporting capability ·         Auditing capability ·         Workflow and business process management ·         Line of Business Data integration ·         Good for large data pulling ·         Easy upgrade to new versions	·         Non-technical users can implement somewhat complex solutions. ·         Email notifications easy. ·         Can see workflow task history visually. ·         Administration for Nintex is easy
Disadvantages	·         We found SharePoint's built-in process tools clumsy, hard to re-use, and not very powerful or flexible. ·         Getting setup to where you're actually start using the product can be quiet complex and the instructions are not quite clear	·         Error messages are completely vague, making it extremely difficult to debug. ·         Failures occur for random reasons. ·         Error notifications get sent out too frequently which confuse users. ·         Have performance issue when pulling larger lists ·         Support nightmare for failed workflows.
Cost	·         K2 blackpearl (enterprise) has a fixed cost for unlimited users and servers	·         Nintex has a price per web front-end.  This is key consideration when farming out multiple SharePoint front-ends.
Integration	·         K2 blackpearl provides exclusive activity/event library addressing common systems and scenarios ( AD integration for user management, Exchange integration, SAP, Salesforce,SharePoint integration for actions such as document management, user management, CRM). It also provides excellent framework to connect to LOB systems using Smart Objects. This helps developer’s focus on core process logic than interface details.	·         Nintex also is very tightly integrated with SharePoint and lacks integration ability to external LOB in the enterprise. ·         It also connects to databases and CRM systems, or integrating your SharePoint content with social media platforms
Conclusion	·         K2 is for medium to large budget, scaling to enterprise in IT pro-environment	·         Nintex is best suited for small business solutions which deals with lesser data and business can easily create workflows without any developer

.

Provider hosted app security in SharePoint apps

Check the below link, it was in detail.
https://samlman.wordpress.com/2015/03/02/security-in-sharepoint-apps-part-1/

New Features in SharePoint 2016

1. Role based configuration wizard for configuring a server role

• Front end 
• Application
• Search
• Specialized load
• Distributed cache

1. Zero downtime patching
2. App launcher for on premise has been introduced
3. Office 365 api's coming to On-premise 
4. No Standalone machine any more there should be two servers two install SharePoint now one for SharePoint and other for Sql server
5. No Foundation version any more
6. Build one and deploy into two environments(for one premise and office 365)

BCS in Office 365

We can also call BCS an ORM(object relational map)

Secured store service is used to connect to external sources using different accounts apart from the organizational accounts

The main steps involved in devlopemt using BCS are:

1. Creating external content types using designer or VS
2. Importing external content type to BCS
3. Configure the secured store
4. Creating external lists
5. Creating apps

Creation of App level ECT(external content type)

FileBackedMetadatCatalog loads External content type into it to easy access and also for creation of external lists

Specific finder is a method that is used to find one particular item, it is similar to a view on a list but i only returns one item on a list

We are have all the CRUD operational method for ECT to do

Sample code to connect to a list

Debugging Remote Event Recievers

1. We must create a new azure service bus namespace using azure powershell
2. The command give back a connection sting to connect to Azure environment with EndPoint
3. Use this in visual studio for connecting to azure
4. go to project properties
5. inside that go to SharePoint tab
6. Check the enable debugging via Azure service bus
7. copy past the connection string that we got from command prompt
8. insert a breakpoints and click on F5 for debugging

Remote event receivers in SharePoint 2013

The remote events supports

Site - Create, Move, Delete
List - Create, Delete
List schema - Create, Update, Delete
List Item - Create, Update, Delete, Move, CheckIn, UnCheckIn, CheckOut, AttachmentsAdded, AttachemntsRemoved, FileMoved, FileConverted
App - Install, Update, Uninstall

Some Impotent Points to be noted:

• Remote event receivers call across the networks
• After events use WCF(Windows communication foundation) call on remote web so that they do not block the sharepoint host nor delay the response back to the user
• Remote event recievers will only workf if the concern list is present in App Web
• SharePoint hosted apps doesnt support remote event receievers, its only provider hosted apps
• IRemoteEventService an interface thats get inherited in remote event recievers
• We have only two events called "ProcessEvent" which is a two way event and "ProcessOneWayEvent" for one way
• Properties argument defines the event that has fired on a list item
• We will be having only single entry point for all the events
• Properties.ItemEventProperties is for an item events and Properties.ListEventProperties for list events
• SPRemoteEventResult which is used to sent status back to SharePoint(used for sending information and also for canceling the events)

Before events example

After events example

• App Life Cycle events are two way events
• "ProcessOneWayEvent" never file in App related events

This are just brief points about remote event recievers.

points to be noted on Event receivers in SharePoint 2013

properties.ErrorMessage is used for showing error in event handlers

properties.ListItem.Updateoverwriteversion() is used to overwrite version in list item, rather than adding a new version to the item it overwrites the existing one.

this.EventFiringEnable = false or True to stop or start the events on a list item, when ever you use "Updateoverwriteversion()" method inside a event we should set "this.EventFiringEnable= True" to stop the recursion