Hi,
Thank you for attending to the meeting and giving your valuable thoughts.
According to the discussion we agreed to continue with our design since it
is a simpler scenario than above mentioned design in IS 5.1.0.
Regards,
Yasima.
On Mon, Jan 30, 2017 at 6:32 PM, Harsha Thirimanna
Hi NuwanD,
C5 workflow implementation for IS not started yet. C4 implementation can be
found in following locations,
- Core implementation:
https://github.com/wso2/carbon-identity-framework/tree/master/components/workflow-mgt
- User-management workflow implementation:
Yes, we will try to see if we can reuse anything. Regarding the points
noted down by Darshana, yes, we have the same objectives and the proposed
design achieves all of them too.
Is the C5 code available somewhere yet?
On Mon, Jan 30, 2017 at 2:53 PM, Yasima Dewmini wrote:
> Hi
Hi Darshana,
Thank you for your input. I will look into above approach and try to figure
out whether we can use same approach.
Regards,
Yasima.
On Mon, Jan 30, 2017 at 3:04 AM, Darshana Gunawardana
wrote:
> Hi Yasima\NuwanD,
>
> With IS 5.1.0 it was implemented generic
Hi Nuwan,
It will be great if you guys can evaluate this and see if anything can be
reused from it. IS 6.0.0 will also be re-using this implementation on top
of C5. Harsha is the one who implemented it for IS 5.1.0. You can talk with
him to get an idea.
Regards,
Johann.
On Mon, Jan 30, 2017 at
Hi Yasima\NuwanD,
With IS 5.1.0 it was implemented generic workflow design[1] that can be
used in any product.
(Quoting Prabath)
It was designed to to achieve,
> 1. Simplicity. Keep simple things simple and have provisions to add more
> complex stuff
> 2. Not coupled into any implementation. No
We should be going with BPMN.
On Thu, Jan 26, 2017 at 2:50 PM, Isuru Haththotuwa wrote:
> Hi,
>
> Have we made a decision whether to use BPEL or BPMN? IMHO better to go
> with BPMN, which is simpler. Also, for the default BP engine, we should
> consider Camunda as well, and
Hi,
Have we made a decision whether to use BPEL or BPMN? IMHO better to go with
BPMN, which is simpler. Also, for the default BP engine, we should consider
Camunda as well, and pick the best one.
[1]. https://camunda.org/
On Thu, Jan 26, 2017 at 2:25 PM, Yasima Dewmini wrote:
On Thu, Jan 26, 2017 at 2:18 PM, Malintha Amarasinghe
wrote:
> Hi Yasima,
>
> Do we consider workflow related RESTful API implementation as well in this
> scope?
>
We have some things to clarify. I will update you with fully detailed
diagram.
>
> Thanks
>
>
> On Thu, Jan 26,
Hi Yasima,
Do we consider workflow related RESTful API implementation as well in this
scope?
Thanks
On Thu, Jan 26, 2017 at 2:09 PM, Yasima Dewmini wrote:
> Hi,
>
> @Shani,
> Thnak you shani for your input. Above diagram shows only the basic idea
> how workflow extension
Though it's available in 2.1.0, it better we keep it open for c5
verification. Hence leaving them open. Sorry for the confusion.
On Thu, Jan 26, 2017 at 2:09 PM, Yasima Dewmini wrote:
> Hi,
>
> @Shani,
> Thnak you shani for your input. Above diagram shows only the basic idea
>
Hi,
@Shani,
Thnak you shani for your input. Above diagram shows only the basic idea how
workflow extension works. I am thinking of adding more detailed diagram of
how the workflow requests are processed with workflow engine and how to
send the status back to APIM.
@Lakshman,
With the discussion
On Thu, Jan 26, 2017 at 2:01 PM, Sewmini Jayaweera wrote:
> Hi,
>
> Since it is the design stage it would be great if we can consider
> improvements suggested when testing previous releases too. Please refer to
> [1] to find the list of improvements.
>
> [1].
Hi,
Since it is the design stage it would be great if we can consider
improvements suggested when testing previous releases too. Please refer to
[1] to find the list of improvements.
[1].
On Thu, Jan 26, 2017 at 12:16 PM, Lakshman Udayakantha
wrote:
> Earlier we used BPS as the default workflow engine. What is the default
> workflow engine we are going to use with C5 implementation? And There
> should be a pluggable point to plug any workflow engine in there.
Hi Yasima,
Don't we need to update database upon workflow completion? Also, Are we
going to write workflow engine from scratch or going to use WSO2 BPS or
Activiti [1]?
Also, this should be extended to other workflows as well?
[1] : https://www.activiti.org/
On Thu, Jan 26, 2017 at 12:08 PM,
Hi,
Earlier we used BPS as the default workflow engine. What is the default
workflow engine we are going to use with C5 implementation? And There
should be a pluggable point to plug any workflow engine in there.
Thanks,
Lakshman
On Thu, Jan 26, 2017 at 12:08 PM, Shani Ranasinghe
Hi Yasima,
Just one thing, IMO we need to incorporate the complete process if the
workflow is enabled also right? in that case the workflow engine will call
APIM with the status.
On Thu, Jan 26, 2017 at 11:29 AM, Yasima Dewmini wrote:
> Hi all,
>
> We are going to implement
Hi all,
We are going to implement workflow extensions for APIM.
Following diagram shows the proposed solution.
Your thoughts and suggestions regarding this are highly appreciated.
Regards,
Yasima.
--
http://wso2.com/signatureYasima Dewmini
Software Engineer, WSO2, Inc.
Email: yas...@wso2.com
19 matches
Mail list logo