anchor.diff:  
   === Custom Javascript Buttons
   
  -The main point here will be - change the javascript buttons to lightning quick actions, https://trailhead.salesforce.com/modules/lex_javascript_button_migration[here] it's descirbed in details on how to do this. The reason do ban javascript buttons is simple - it's unsafe, and usually not very user friendly. Below I'll put a simple example on how to change button from Javascript to a Lightning Quick Action.
  +The main point here will be - change the javascript buttons to lightning quick actions, https://trailhead.salesforce.com/modules/lex_javascript_button_migration[here] it's described in details on how to do this. The reason do ban javascript buttons is simple - it's unsafe, and usually not very user-friendly. Below I'll put a simple example on how to change the button from Javascript to a Lightning Quick Action.
   
   ==== 1. Identify The Process Behind Your Button
   
  -There are alot of the use cases for Javascript buttons - from simple record update - to difficult business process of creation of the data model along with triggering the webservice from Apex. Basically, the more complex your javascript button logic is - the worse is system design - and this requires rework of the whole process. But for a simple record update/new records creation, there's a very simple process of transition, which in a result will give *No Changes* for an end user flow.
  +There are a lot of the use cases for Javascript buttons - from simple record update - to difficult business process of creation of the data model along with triggering the webservice from Apex. Basically, the more complex your javascript button logic is - the worse is system design - and this requires rework of the whole process. But for a simple record update/new records creation, there's a very simple process of transition, which as a result will give *No Changes* for an end user flow.
   
   ==== 2. Move the code!
   
  
positive.code: 
  else 
  { 
  	сaseObject.Type = "Social Plus";
  	var result = sforce.connection.update([сaseObject]); 
  
  	if (result[0].success == "true") 
  	{ 
  		location.reload(true); 
  	} 
  
  	else 
  	{ 
  		alert(result[0].errors.message); 
  	} 
  }
  ----
  
  Process is simple as 1-2-3: Check the case type and update it if it's social. It's super easy to move this process to lightning component - no Apex required!
  
  .TransformSocialCaseAction.cmp
  [source,html]
  
negative.code: ** Solutions
  ** Ideas
  ** https://developer.salesforce.com/docs/atlas.en-us.noversion.service_sdk_android.meta/service_sdk_android/android_sos_overview.htm[SOS]
  ** Knowledge (can be used, but lots of functionality is unavailable at this moment)
  
  If your business is OK to switch to Salesforce Classic to continue to use those features - then you'll be fine to proceed with customization changes
  
  