REST - Integration - Part 3

In Pega, One good part is, most of the services and connectors, they had used in pega implementation itself. So we no need to search outside or in other sites to identify how to implement it in Pega.

Same in the case of Rest Connector also.

Every one of us had seen the pega developer studio, in right hand side we have seen list of updates from pega, which is provided from PDN site and its consumed through REST Connection and displayed to us.

URL Used:http://pdn.pega.com/rss/designerstudio

Connect REST:pyRSSConnectService

DataPage : D_PDNFeed

Clipboard structure of Data which we are getting after parsing from the REST and then its mapped to the Data Page are below.

Once data is mapped correctly into the Data page, In UI the data will be displayed as below:

Some Other PRPC - Pega URLs

Some other Blogs and URLs which are giving more details about Pega PRPC are given below:

Blogspot:
http://prpcpega.blogspot.in/

http://malathigujju.blogspot.in/

http://prpcdeveloper.blogspot.in/ -- This have most Details and informations

http://usnarayana-siva.blogspot.in/

http://pegacommander.blogspot.in/

http://pisupativenkatasesha.blogspot.in/2008_12_01_archive.html

http://balakrishnathati.blogspot.in/

http://mypega.blogspot.in/

http://codepega.blogspot.in/p/pega-csa-questions.html

http://pegaguide.blogspot.in/

http://singhvikash.blogspot.in/2013/08/pega-tutorial-what-is-dco-in-pega-prpc.html

http://kbolyand.blogspot.in/2015/03/format-date-datetime-in-pega-prpc.html?view=mosaic

http://prpcgroup.blogspot.in/

https://krishnapega.blogspot.in/ - Implementation Examples had been given in this URL, Creating ZIP file, Direct Web access and so on.

http://pegaiq.blogspot.in/2014/06/how-to-call-activity-from-java-java.html - Pega simple examples and sample Interview Questions

Word Press:
https://pegalive.wordpress.com/category/pega-topics/page/2/

https://techbpm.wordpress.com/2013/12/24/pega-technical-architecture/

http://www.wordpresswiki.org/introduction-to-pega/

http://www.wptutes.org/introduction-to-pega/

http://www.slideshare.net/DeclanChellar/bpmn-in-pegasystemsprpc-flow-rules

http://pega.iexpertify.com/

https://pegaworld.wordpress.com/ - similar to above sites this also has lot of examples


Other sites:
https://www.pegaxchange.com/

http://mindmajix.com/pega-interview-questions - Pega Interview Questions with answers had been given here.

Inbound Email Configuration - Part 1

In this Post we will see how to configure the inbound email i.e. Service Email in Pega PRPC.

For Configuring that we need to create Email Listener, Service Email and Service Package.

Service Package is needed for mention Access group, to know which applivctions need to pick for rulesets and version. And Pooling and then authentication.

Service Email - that is needed to parse the Email which we got. To get informations like To, From, Subject and Message and need to process based on the data we received.

Email Listener to watch the Folder, say for example - INBOX. and other configurations like What is the email sizre it can process and how much interval it should be there.

Email Account: This it to read the email for which folder need to watch, this will be mentioned in the Email Listener.

After configuring email Listener, we need to Start the Email Listener from SMA.

Screen Shot are given below:

For Starting the Email Listener from SMA:

For Testing Simple Mail.

when mail is sent received in that Email ID, email listener will read tht email so in clipboard we can see below

After getting the values we can do modifications or updations in our applications.

REST Wizard - Part 2

Continuation of REST wizard:

For example :

Keep our url as:

http://apilayer.net/api/historical?access_key=e30045a7f29409200bxxxxxx&date=yyyy-mm-dd

and in the same domain, other services also we need to access. Their URLs like

http://apilayer.net/api/convert?access_key=wwewewewee

http://apilayer.net/api/live?access_key=weweewe

In that case,

While running wizard, in the Define Parameters Screen

U will get option to mark it as parameter as below.

If we want to make that as parameter and it can be passed from the activity/some other place from where we are calling this REST connector.

So that single REST connector Rule can be used for multiple purpose.