Re: [Architecture] [APIM] Extend Subscription Workflow

[Madusanka Premaratne]

[Adding Shani]

On Mon, Sep 14, 2015 at 3:07 PM, Madusanka Premaratne 
wrote:

> Hi Roshan,
> There are two customisations for the subscription workflow ATM. As in the
> same way there can be another workflow with redirection capability. Lets
> say subscriptionCreationRedirectWorkflowExecutor, there we enable the
> redirection capability and user can customise that by giving redirection
> location.
>
> We are not going to provide an API. We are going to provide a workflow
> executor with additional capabilities.
>
> Thanks,
> Madusanka
>
> On Mon, Sep 14, 2015 at 2:52 PM, Roshan Wijesena  wrote:
>
>> Hi Madusanka,
>>
>> On Mon, Sep 14, 2015 at 12:14 PM, Madusanka Premaratne <
>> madusan...@wso2.com> wrote:
>>
>>> No we are not going to deal with payment gateways. It is a customisation
>>> part need to be handled by the user.
>>
>>
>> What kind of customization required by user? do we need to provide an API
>> for that?
>>
>> -Roshan
>> --
>> Roshan Wijesena.
>> Senior Software Engineer-WSO2 Inc.
>> Mobile: *+94719154640 <%2B94719154640>*
>> Email: ros...@wso2.com
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>
>
>
> --
> *Madusanka Premaratne* | Associate Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 835 70 73| Work: +94 112 145 345
> Email: madusan...@wso2.com | Web: www.wso2.com
>
> [image: Facebook]  [image: Twitter]
>  [image: Google Plus]
>  [image:
> Linkedin]  [image: Instagram]
>  [image: Skype]
> 
>
>


-- 
*Madusanka Premaratne* | Associate Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 835 70 73| Work: +94 112 145 345
Email: madusan...@wso2.com | Web: www.wso2.com

[image: Facebook]  [image: Twitter]
 [image: Google Plus]
 [image:
Linkedin]  [image: Instagram]
 [image: Skype]

___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM] Extend Subscription Workflow

[Madusanka Premaratne]

Hi Roshan,
There are two customisations for the subscription workflow ATM. As in the
same way there can be another workflow with redirection capability. Lets
say subscriptionCreationRedirectWorkflowExecutor, there we enable the
redirection capability and user can customise that by giving redirection
location.

We are not going to provide an API. We are going to provide a workflow
executor with additional capabilities.

Thanks,
Madusanka

On Mon, Sep 14, 2015 at 2:52 PM, Roshan Wijesena  wrote:

> Hi Madusanka,
>
> On Mon, Sep 14, 2015 at 12:14 PM, Madusanka Premaratne <
> madusan...@wso2.com> wrote:
>
>> No we are not going to deal with payment gateways. It is a customisation
>> part need to be handled by the user.
>
>
> What kind of customization required by user? do we need to provide an API
> for that?
>
> -Roshan
> --
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: *+94719154640 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>



-- 
*Madusanka Premaratne* | Associate Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 835 70 73| Work: +94 112 145 345
Email: madusan...@wso2.com | Web: www.wso2.com

[image: Facebook]  [image: Twitter]
 [image: Google Plus]
 [image:
Linkedin]  [image: Instagram]
 [image: Skype]

___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM] Extend Subscription Workflow

[Roshan Wijesena]

Hi Madusanka,

On Mon, Sep 14, 2015 at 12:14 PM, Madusanka Premaratne 
wrote:

> No we are not going to deal with payment gateways. It is a customisation
> part need to be handled by the user.


What kind of customization required by user? do we need to provide an API
for that?

-Roshan
-- 
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94719154640*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM] Extend Subscription Workflow

[Joseph Fonseka]

Hi

@Sanjeewa Most payment gateways do not allow to embed in iframes they
restrict it by "X-FRAME-OPTIONS" so it has to be redirects.

IMHO implementation of the payment gateway should be in the 3rd party app
and this particular workflow should facilitate the redirection.

@Madushanka do you have a sequence diagram for this?

Thanks
Jo

On Mon, Sep 14, 2015 at 12:29 PM, Sanjeewa Malalgoda 
wrote:

> Rather doing redirection shouldn't we load frame within our UI ?
> And we need to evaluate and see how other common platforms direct users to
> payment gateways.
> And then we can come to conclusion.
>
>
>
> On Mon, Sep 14, 2015 at 12:19 PM, Amila De Silva  wrote:
>
>> Does this mean that depending on the outcome of running 'execute' method,
>> Subscription workflow should be able change the HTTP response code (302 if
>> a re-direct) sent back to the invoker?
>>
>>
>>
>> On Mon, Sep 14, 2015 at 12:02 PM, Nuwan Dias  wrote:
>>
>>> IMO, checking the user information, payment information, etc are
>>> implementation details of the workflow. What the WorkflowExecutor lacks
>>> today is the ability to do http redirections when a workflow has been
>>> executed/completed. We shouldn't worry about the implementation details of
>>> the workflow but focus on extending its capability to support those
>>> implementations.
>>>
>>> The 'execute' and 'complete' functions have no return type ATM. We
>>> should probably introduce something like a "WorkflowResponse" abstract
>>> type. This could be HttpResponses or any other form of responses. The
>>> response type implementation should take care of what happens after the
>>> 'execute' and 'complete' actions.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>>
>>>
>>> On Mon, Sep 14, 2015 at 9:48 AM, Madusanka Premaratne <
>>> madusan...@wso2.com> wrote:
>>>
 Hi All,
 I am going to implement the $subject for WSO2 API manager to enable the
 capability of handling paid APIs. The data flow diagram can be seen as
 follows.


 ​
 ​

 As described in the figure above if there are no payment plans set for
 the subscriber the workflow will redirect to third party/inbuilt web page
 to collect those information. If those are already defined it will just
 continue the subscription process.

 To fulfil the above task, I am going to change the existing *execute*
 method of *WorkflowExecutor* to handle the redirection process and to
 receive the feedback. After the operation from the webpage/ the required
 details are already collected the webpage will send a response back to
 workflow executer to complete the execution and complete the subscription.

 Suggestions and feedbacks are welcome.

 Thanks,
 Madusanka

 --
 *Madusanka Premaratne* | Associate Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 835 70 73| Work: +94 112 145 345
 Email: madusan...@wso2.com | Web: www.wso2.com

 [image: Facebook]  [image: Twitter]
  [image: Google Plus]
  [image:
 Linkedin]  [image: Instagram]
  [image: Skype]
 


>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>>
>> --
>> *Amila De Silva*
>>
>> WSO2 Inc.
>> mobile :(+94) 775119302
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>


-- 

-- 
*Joseph Fonseka*
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 772 512 430
skype: jpfonseka

* *
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM] Extend Subscription Workflow

[Sanjeewa Malalgoda]

Rather doing redirection shouldn't we load frame within our UI ?
And we need to evaluate and see how other common platforms direct users to
payment gateways.
And then we can come to conclusion.



On Mon, Sep 14, 2015 at 12:19 PM, Amila De Silva  wrote:

> Does this mean that depending on the outcome of running 'execute' method,
> Subscription workflow should be able change the HTTP response code (302 if
> a re-direct) sent back to the invoker?
>
>
>
> On Mon, Sep 14, 2015 at 12:02 PM, Nuwan Dias  wrote:
>
>> IMO, checking the user information, payment information, etc are
>> implementation details of the workflow. What the WorkflowExecutor lacks
>> today is the ability to do http redirections when a workflow has been
>> executed/completed. We shouldn't worry about the implementation details of
>> the workflow but focus on extending its capability to support those
>> implementations.
>>
>> The 'execute' and 'complete' functions have no return type ATM. We should
>> probably introduce something like a "WorkflowResponse" abstract type. This
>> could be HttpResponses or any other form of responses. The response type
>> implementation should take care of what happens after the 'execute' and
>> 'complete' actions.
>>
>> Thanks,
>> NuwanD.
>>
>>
>>
>> On Mon, Sep 14, 2015 at 9:48 AM, Madusanka Premaratne <
>> madusan...@wso2.com> wrote:
>>
>>> Hi All,
>>> I am going to implement the $subject for WSO2 API manager to enable the
>>> capability of handling paid APIs. The data flow diagram can be seen as
>>> follows.
>>>
>>>
>>> ​
>>> ​
>>>
>>> As described in the figure above if there are no payment plans set for
>>> the subscriber the workflow will redirect to third party/inbuilt web page
>>> to collect those information. If those are already defined it will just
>>> continue the subscription process.
>>>
>>> To fulfil the above task, I am going to change the existing *execute*
>>> method of *WorkflowExecutor* to handle the redirection process and to
>>> receive the feedback. After the operation from the webpage/ the required
>>> details are already collected the webpage will send a response back to
>>> workflow executer to complete the execution and complete the subscription.
>>>
>>> Suggestions and feedbacks are welcome.
>>>
>>> Thanks,
>>> Madusanka
>>>
>>> --
>>> *Madusanka Premaratne* | Associate Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>>> Email: madusan...@wso2.com | Web: www.wso2.com
>>>
>>> [image: Facebook]  [image: Twitter]
>>>  [image: Google Plus]
>>>  [image:
>>> Linkedin]  [image: Instagram]
>>>  [image: Skype]
>>> 
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>


-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM] Extend Subscription Workflow

[Amila De Silva]

Does this mean that depending on the outcome of running 'execute' method,
Subscription workflow should be able change the HTTP response code (302 if
a re-direct) sent back to the invoker?



On Mon, Sep 14, 2015 at 12:02 PM, Nuwan Dias  wrote:

> IMO, checking the user information, payment information, etc are
> implementation details of the workflow. What the WorkflowExecutor lacks
> today is the ability to do http redirections when a workflow has been
> executed/completed. We shouldn't worry about the implementation details of
> the workflow but focus on extending its capability to support those
> implementations.
>
> The 'execute' and 'complete' functions have no return type ATM. We should
> probably introduce something like a "WorkflowResponse" abstract type. This
> could be HttpResponses or any other form of responses. The response type
> implementation should take care of what happens after the 'execute' and
> 'complete' actions.
>
> Thanks,
> NuwanD.
>
>
>
> On Mon, Sep 14, 2015 at 9:48 AM, Madusanka Premaratne  > wrote:
>
>> Hi All,
>> I am going to implement the $subject for WSO2 API manager to enable the
>> capability of handling paid APIs. The data flow diagram can be seen as
>> follows.
>>
>>
>> ​
>> ​
>>
>> As described in the figure above if there are no payment plans set for
>> the subscriber the workflow will redirect to third party/inbuilt web page
>> to collect those information. If those are already defined it will just
>> continue the subscription process.
>>
>> To fulfil the above task, I am going to change the existing *execute*
>> method of *WorkflowExecutor* to handle the redirection process and to
>> receive the feedback. After the operation from the webpage/ the required
>> details are already collected the webpage will send a response back to
>> workflow executer to complete the execution and complete the subscription.
>>
>> Suggestions and feedbacks are welcome.
>>
>> Thanks,
>> Madusanka
>>
>> --
>> *Madusanka Premaratne* | Associate Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>> Email: madusan...@wso2.com | Web: www.wso2.com
>>
>> [image: Facebook]  [image: Twitter]
>>  [image: Google Plus]
>>  [image:
>> Linkedin]  [image: Instagram]
>>  [image: Skype]
>> 
>>
>>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM] Extend Subscription Workflow

[Madusanka Premaratne]

@Sanjeewa,
In the free and paid API concept, we need credit card details, cvc numbers,
expiry dates and billing address etc.. for the paid APIs. Before
subscribing it checks for those information. Actually we do not collect
additional data but the 3rd party webapp does the data collection part and
it redirects back to complete the subscription process.
We are just enabling the capability to extend the workflow process to
handle this.

@Roshan,
There will be three categories for the APIs as *'Free'*, *'Freemium*' and '
*Commercial'*.
If all the tiers are free, it is a 'Free' API
If some of the tiers are free and some are paid then it is 'Freemium'
If all tiers are paid, then it is a 'Commercial' API

No we are not going to deal with payment gateways. It is a customisation
part need to be handled by the user.

Thanks,
Madusanka


On Mon, Sep 14, 2015 at 11:46 AM, Sanjeewa Malalgoda 
wrote:

> @Madusanka,
> What does it meant by collect user data. When subscribers signup or
> register by admin they are suppose to provide information.
> And we may have user data in our side. What do we additionally collect
> here?
>
> Are we calling external billing system to create account there? I think we
> can use user provisioning concept here rather collecting information from
> user.
> We can provision user available in our side to 3rd party using
> provisioning APIs available(like JIT).
> WDYT?
>
> Thanks,
> sanjeewa
>
> On Mon, Sep 14, 2015 at 9:48 AM, Madusanka Premaratne  > wrote:
>
>> Hi All,
>> I am going to implement the $subject for WSO2 API manager to enable the
>> capability of handling paid APIs. The data flow diagram can be seen as
>> follows.
>>
>>
>> ​
>> ​
>>
>> As described in the figure above if there are no payment plans set for
>> the subscriber the workflow will redirect to third party/inbuilt web page
>> to collect those information. If those are already defined it will just
>> continue the subscription process.
>>
>> To fulfil the above task, I am going to change the existing *execute*
>> method of *WorkflowExecutor* to handle the redirection process and to
>> receive the feedback. After the operation from the webpage/ the required
>> details are already collected the webpage will send a response back to
>> workflow executer to complete the execution and complete the subscription.
>>
>> Suggestions and feedbacks are welcome.
>>
>> Thanks,
>> Madusanka
>>
>> --
>> *Madusanka Premaratne* | Associate Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>> Email: madusan...@wso2.com | Web: www.wso2.com
>>
>> [image: Facebook]  [image: Twitter]
>>  [image: Google Plus]
>>  [image:
>> Linkedin]  [image: Instagram]
>>  [image: Skype]
>> 
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>


-- 
*Madusanka Premaratne* | Associate Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 835 70 73| Work: +94 112 145 345
Email: madusan...@wso2.com | Web: www.wso2.com

[image: Facebook]  [image: Twitter]
 [image: Google Plus]
 [image:
Linkedin]  [image: Instagram]
 [image: Skype]

___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM] Extend Subscription Workflow

[Nuwan Dias]

IMO, checking the user information, payment information, etc are
implementation details of the workflow. What the WorkflowExecutor lacks
today is the ability to do http redirections when a workflow has been
executed/completed. We shouldn't worry about the implementation details of
the workflow but focus on extending its capability to support those
implementations.

The 'execute' and 'complete' functions have no return type ATM. We should
probably introduce something like a "WorkflowResponse" abstract type. This
could be HttpResponses or any other form of responses. The response type
implementation should take care of what happens after the 'execute' and
'complete' actions.

Thanks,
NuwanD.



On Mon, Sep 14, 2015 at 9:48 AM, Madusanka Premaratne 
wrote:

> Hi All,
> I am going to implement the $subject for WSO2 API manager to enable the
> capability of handling paid APIs. The data flow diagram can be seen as
> follows.
>
>
> ​
> ​
>
> As described in the figure above if there are no payment plans set for the
> subscriber the workflow will redirect to third party/inbuilt web page to
> collect those information. If those are already defined it will just
> continue the subscription process.
>
> To fulfil the above task, I am going to change the existing *execute*
> method of *WorkflowExecutor* to handle the redirection process and to
> receive the feedback. After the operation from the webpage/ the required
> details are already collected the webpage will send a response back to
> workflow executer to complete the execution and complete the subscription.
>
> Suggestions and feedbacks are welcome.
>
> Thanks,
> Madusanka
>
> --
> *Madusanka Premaratne* | Associate Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 835 70 73| Work: +94 112 145 345
> Email: madusan...@wso2.com | Web: www.wso2.com
>
> [image: Facebook]  [image: Twitter]
>  [image: Google Plus]
>  [image:
> Linkedin]  [image: Instagram]
>  [image: Skype]
> 
>
>


-- 
Nuwan Dias

Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM] Extend Subscription Workflow

[Roshan Wijesena]

Hi Madusanka,

What's all about the "payment plans" ? Are we going to expose a payment
gateway ?

Regards
Roshan.

On Mon, Sep 14, 2015 at 11:46 AM, Sanjeewa Malalgoda 
wrote:

> @Madusanka,
> What does it meant by collect user data. When subscribers signup or
> register by admin they are suppose to provide information.
> And we may have user data in our side. What do we additionally collect
> here?
>
> Are we calling external billing system to create account there? I think we
> can use user provisioning concept here rather collecting information from
> user.
> We can provision user available in our side to 3rd party using
> provisioning APIs available(like JIT).
> WDYT?
>
> Thanks,
> sanjeewa
>
> On Mon, Sep 14, 2015 at 9:48 AM, Madusanka Premaratne  > wrote:
>
>> Hi All,
>> I am going to implement the $subject for WSO2 API manager to enable the
>> capability of handling paid APIs. The data flow diagram can be seen as
>> follows.
>>
>>
>> ​
>> ​
>>
>> As described in the figure above if there are no payment plans set for
>> the subscriber the workflow will redirect to third party/inbuilt web page
>> to collect those information. If those are already defined it will just
>> continue the subscription process.
>>
>> To fulfil the above task, I am going to change the existing *execute*
>> method of *WorkflowExecutor* to handle the redirection process and to
>> receive the feedback. After the operation from the webpage/ the required
>> details are already collected the webpage will send a response back to
>> workflow executer to complete the execution and complete the subscription.
>>
>> Suggestions and feedbacks are welcome.
>>
>> Thanks,
>> Madusanka
>>
>> --
>> *Madusanka Premaratne* | Associate Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>> Email: madusan...@wso2.com | Web: www.wso2.com
>>
>> [image: Facebook]  [image: Twitter]
>>  [image: Google Plus]
>>  [image:
>> Linkedin]  [image: Instagram]
>>  [image: Skype]
>> 
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94719154640*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM] Extend Subscription Workflow

[Sanjeewa Malalgoda]

@Madusanka,
What does it meant by collect user data. When subscribers signup or
register by admin they are suppose to provide information.
And we may have user data in our side. What do we additionally collect
here?

Are we calling external billing system to create account there? I think we
can use user provisioning concept here rather collecting information from
user.
We can provision user available in our side to 3rd party using provisioning
APIs available(like JIT).
WDYT?

Thanks,
sanjeewa

On Mon, Sep 14, 2015 at 9:48 AM, Madusanka Premaratne 
wrote:

> Hi All,
> I am going to implement the $subject for WSO2 API manager to enable the
> capability of handling paid APIs. The data flow diagram can be seen as
> follows.
>
>
> ​
> ​
>
> As described in the figure above if there are no payment plans set for the
> subscriber the workflow will redirect to third party/inbuilt web page to
> collect those information. If those are already defined it will just
> continue the subscription process.
>
> To fulfil the above task, I am going to change the existing *execute*
> method of *WorkflowExecutor* to handle the redirection process and to
> receive the feedback. After the operation from the webpage/ the required
> details are already collected the webpage will send a response back to
> workflow executer to complete the execution and complete the subscription.
>
> Suggestions and feedbacks are welcome.
>
> Thanks,
> Madusanka
>
> --
> *Madusanka Premaratne* | Associate Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 835 70 73| Work: +94 112 145 345
> Email: madusan...@wso2.com | Web: www.wso2.com
>
> [image: Facebook]  [image: Twitter]
>  [image: Google Plus]
>  [image:
> Linkedin]  [image: Instagram]
>  [image: Skype]
> 
>
>


-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] [APIM] Extend Subscription Workflow

[Madusanka Premaratne]

Hi All,
I am going to implement the $subject for WSO2 API manager to enable the
capability of handling paid APIs. The data flow diagram can be seen as
follows.


​
​

As described in the figure above if there are no payment plans set for the
subscriber the workflow will redirect to third party/inbuilt web page to
collect those information. If those are already defined it will just
continue the subscription process.

To fulfil the above task, I am going to change the existing *execute*
method of *WorkflowExecutor* to handle the redirection process and to
receive the feedback. After the operation from the webpage/ the required
details are already collected the webpage will send a response back to
workflow executer to complete the execution and complete the subscription.

Suggestions and feedbacks are welcome.

Thanks,
Madusanka

-- 
*Madusanka Premaratne* | Associate Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 835 70 73| Work: +94 112 145 345
Email: madusan...@wso2.com | Web: www.wso2.com

[image: Facebook]  [image: Twitter]
 [image: Google Plus]
 [image:
Linkedin]  [image: Instagram]
 [image: Skype]

___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture