Perfect! Thanks Chamila!
Dmitry
On Wed, Oct 1, 2014 at 8:33 PM, Chamila Adhikarinayake
wrote:
> Hi Dmitry,
> This feature is already done and we ship this with APIM 1.8. Sorry for not
> updating this thread.
>
> Regarding the scenarios, We have provided facility to add custom workflow
> extensi
Hi Dmitry,
This feature is already done and we ship this with APIM 1.8. Sorry for not
updating this thread.
Regarding the scenarios, We have provided facility to add custom workflow
extension. Currently we ship UserSignUpWSWorkflowExecutor which also has a
user approval process [1]. We can also cr
Any update on that?
What is the ETA for the feature?
Is there something we can review yet?
Were you able to satisfy all the end-user experience requirements?
Dmitry
On Fri, Sep 5, 2014 at 10:09 AM, Dmitry Sotnikov wrote:
> Thanks Chamila!
>
> Here is the workflow that I would like to see in
Thanks Chamila!
Here is the workflow that I would like to see in the API Cloud:
Scenario A: User Self Sign-Up:
1. Plato is an app developer and wants to develop an app for the
population of the Atlantis island to track the water level and notify when
the island goes under the sea. He finds that
looping Dmitry to the thread
On Fri, Sep 5, 2014 at 10:26 AM, Chamila Adhikarinayake
wrote:
> Hi all,
>
> The current user signup method (jsFunction_addUser() [1]) in API manager
> uses addUser method in UserRegistrationService[2] (through
> UserRegistrationAdminService from APIM) to register
Hi all,
The current user signup method (jsFunction_addUser() [1]) in API manager
uses addUser method in UserRegistrationService[2] (through
UserRegistrationAdminService from APIM) to register the user and suggested
to use that same method for tenant user signup as well (Shariq has modified
this so
Hi Chamila,
I think you have to start the TenantFlow and set the ID for the tenant
correctly before fetching the configuration. In the method
jsFunction_resumeWorkflow, this is done by calling
PrivilegedCarbonContext.startTenantFlow();
PrivilegedCarbonContext.getThreadLoca
Actually the tasks are created with that executor for other tenants as
well. but not inside the correct tenant domain in the BPS. They are created
in carbon.super tenant domain and the related task can be viewed in
workflow-admin ui only by login as super user.
following is the reason I think that
On Wed, Sep 3, 2014 at 9:02 PM, Chamila Adhikarinayake
wrote:
> Hi all,
> I'm creating user self signup feature for tenant store in API Manager.
> Current api manager provides only self signup facility for carbon.super
> store. To add tenant users, tenant admin has to manually add it through the
