Last week at CreatorCon San Diego myself and a few colleagues from the Inspire Program had the pleasure of presenting during the Enterprise Architecture Track a few of the presentations from Knowledge.  We focused on the topics that we felt most applied to the Enterprise Architecture Community.  This included Integration Platform as a Service, Rationalizing your technology landscape and Application Inheritance to provide flexibility and scale to your environment.

 

Below are the links to the original presentations from knowledge:

  

https://community.servicenow.com/docs/DOC-7051

 

https://community.servicenow.com/docs/DOC-7038

 

https://community.servicenow.com/docs/DOC-6816

 

During the Integration as a Platform presentation we shared the definition and key components of integration platform as a service (iPaaS) along with an example of leveraging the ServiceNow platform as a iPaaS layer.  Below are the key components of a iPaaS solution as defined by the industry.

blog1.png

Our definition included why ServiceNow was uniquely positioned as a iPaaS layer and also some of the flexibility that the platform provided when leveraging it as a iPaaS solution.  Below are the key components of an iPaaS solution on top of the capabilities of the ServiceNow Platform.

blog2.png

Finally, we concluded with a real world example of applying iPaaS on ServiceNow for a real world customer solution.  In our example we solve for the managers and requestors that have a daily battery of requests and use multiple tools on their desktop to manage this type of work.  They are frustrated by the lack of standardization for each request they get from their employees.  The amount of time lost everyday in doing these types of tasks take a toll on other more important, impactful work and management knows it.  To solve the problem we leverage ServiceNow as a iPaaS to consolidate the different types of request into a single, mobile first application where requests provide context and accountability for approvals with the ability to delegate if necessary in a easy to use way.  Creating this type of solution allows for management and requestors alike to focus on impactful projects while giving them back precious hours they would have lost tracking approvals across a multitude of systems.

 

blog3.png

 

After the demonstration at CreatorCon of this example there was a lot of questions about if this example was reusable and if folks could experience this in a live environment.  The quick answer was "Yes" and it lead into a discussion about snexperiences.com.

 

In snexperiences when you launch the universal approval experience you can even go to the design library to see how it was built.

 

blog4.png

 

Attached to the blog post is the final deck from CreatorCon San Diego.  Let me know if you have success or failure as you take the Journey with ServiceNow and iPaaS.