Hi Johann and all,
As per the offline chat with Pulasthi, the executor serialize the workflow
info and save in the database before calling the bpel service. (see the
diagram below)
So in our case if we are to use this component, we will have to do a
network call with all the information for
+1 to change the form tag into transitionInputs. Please see the diff of
scxml.xsd to enable this.
--- wso2greg-5.0.0-SNAPSHOT/repository/resources/scxml.xsd 2015-03-10
21:13:38.0 +0530
+++ ../wso2greg-5.0.0-SNAPSHOT/repository/resources/scxml.xsd 2015-04-02
17:38:54.547890501 +0530
@@
Hi all,
This is regarding using a single JIRA instance for all apps in all tenants.
1. Using the role based access control, we can restrict users seeing other
tenant applications.
ex: foo tenant users are assigned to foo_role in jira.
@Dilhasha, Please have a look at jira role mapping to jira
Hi Manjula,
Thanks for the feedback.
Regarding 1. I agree with you that we can use role based mapping to
restrict accessibility to each project.
But we will be using the admin user to create apps in the JIRA instance.
Given that, I can't still find a way to solve the problem of having similar
Hi,
I have specified a flow chart and my suggestions regarding the scenarios in
[1].
https://docs.google.com/document/d/1qDRObBh4CLnO755TgyINWAey9c1X3W1BFI-hgkh9rlQ/edit?usp=sharing
Please comment and point out any mistakes and suggest any other options we
can consider.
[1]
Hi Pulasthi, hi Tanja,
can you provide a consolidated architecture figure, please? Can you also
position in your architecture BPS? I assume the requirements you address
by your architecture is the ability to create an on-ramp workflow for ES,
AM,... in a fast way, correct?
Thanks!
Best
