Comparison between Workflow, Process Flow, Visual flow

Feature	Workflow	Process Flow	Visual Flow / Visual Workflow
Description	Workflow allow users to set up criteria and actions	Process Flow automates your business processes by providing a powerful and user-friendly graphical representation of your process as you build it.	Visual Workflow enables you to create flows, which are triggered by users rather than events
UI	Runs in Background and take the action for ex field update	Runs in Background take the action for ex. Post chatter feed	Allows user to interact from UI and take input from user.
Initiated By	Triggered by events. For ex. Record save	Triggered by events. For ex. Record save	Triggered by users rather than events. For ex. Survey button click on lead object.
Supported Actions	·   Create a task ·   Create an email alert ·   Field Update New ·   Outbound Message ·   New Flow Trigger	·   Create a record ·   Update fields on any related record—not just the record or its parent. ·   Launch a flow—as an immediate or a scheduled action. ·   Send an email ·   Post to Chatter ·   Submit for approval ·   Call apex methods ·   The process builder doesn’t support outbound message	·   Lookup any object ·   Create Flow variables ·   Do CURD on any object
Scope	Limited to object in context and its master	Process Flow is not tied to any object	Visual Flow is not tied to any object
Interface	Point and click, multi-screen	Drag drop, Single Screen, easy to change & visualize	Drag drop, Single Screen, easy to change & visualize
Scheduling	Immediate and scheduled actions	Immediate and scheduled actions	Only Immediate actions
Use case	Send a web service callout to Inventory management system to update stock when  opportunity close successfully	Send a chatter feed to group of users when high value opportunity stage is changes	Wizard for self-help portal if it does not resolve issue then log a case with all the details.

Using NTLM authentication from Salesforce apex

We had requirement of integrating web-services that used NTML authentication from Salesforce.

The whole process of this integration was very interesting and so I thought of writing article which may help someone on how to tackle this type of integration.

Here are points we will cover:

1) What is NTML authentication and how it works

2) How we can use NTML authentication from Apex?

3) If you face any issues how to resolve them?

Ok, Lets start with point #1



1) What is NTML authentication and how it works: 

In a Windows network, NT LAN Manager (NTLM) is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. There are various versions of it  NTLMv1, NTLMv2 & NTLM session.  Full details of NTLM is out of scope of this article. you can find more details at https://en.wikipedia.org/wiki/NT_LAN_Manager

How it works: 

A) The client sends an initial message to the server, advertising certain options or capabilities such as cryptographic algorithm support .

B) The server creates a challenge, c, and returns the challenge and the options or capabilities that it can support to the client .

C) The client computes a function on the challenge, resp = f(c, password), and sends the results to the server, along with the user's textual name and domain .

D)The server looks up the user (by the name passed) and computes the same function, f(c, user's password). If the result matches resp (that is, what the client sent in step C), the passwords are presumed to match, and the user is authenticated.

More Details: https://msdn.microsoft.com/en-us/library/cc239684.aspx




2) How we can use NTML authentication from Apex?

Well its dead simple. Nate Wallace have wrote apex classes that takes care of all over heads and you just need to deploy these classes to your org and use them.

Here is sample code on how to use these classes and give a call to NTLM SOAP service.


String body = 'XML_REQUEST_BODY_XXXXXXXXXXXXXXXXXXXX';
String ep = 'END_POINT_URL_XXXXXXXXXXXXXX';

HttpClient httpObj = new HttpClient('DOMIN_XXXX\\USERNAME_XXXXXX','PASSWORD_XXXXXXXX',True);  /* Note two forward slashes between domain and username \\  */
HttpRequest req = new HttpRequest();
req.setBody(body);
req.setMethod('POST');
req.setEndpoint(ep);

req.setHeader('Content-Type','text/xml;charset=UTF-8');

HttpResponse res = httpObj.send(req);
System.debug('Response**:' + res);
System.debug('Response**:' + res.getBody());

This should give you a XML response. Well but what if you did not get valid response... this bring us to next topic


3) If you face any issues how to resolve them?

When working on integration there are generally (at least) two components. First is Server and second is client. In our case our endpoint is server and client is in apex. When we face issue it becomes difficult to identify the issue. To resolve issue we should first decide where the issue is? in client or in server?

To find that out we can use tool like SoapUi to replace our client. SoapUi is tested and trusted tool so when we use it properly we eliminate the possibility of client side issue for ex. incorrect  XML.

To use SoapUI with NTLM authentication you need do following:

a) Import WSDL into SoapUI

b) Click on any service and open Request1

c) On left hand bottom side of Request1 there is authorization tab, click on it.

d)  Select add new authorization and select type As NTLM and provide the credentials

e) Now you can replace the ? in your Request1 with actual values and click submit request button.


If you get positive response when you use SoapUi then it means that there is something wrong in your client:
Examples of client side issues:
1) Invalid XML
2) Incorrect parameter in XML
3) Invalid Header
4) 401 error : authentication failed due to user name/ password / domain
5) 500 Internal server error due to wrong data

If you get negative response when you use SoapUi then it means that there is something wrong in your Server:

1) 500 Internal server error due long processing time
2) 401 error:  network restriction like IP restriction  

Conclusion:While working on integration you need to isolation the issue whether its in client or server and then proceed further.