Thanks Anuradha for the clarification. Will try out the suggested approach.

Regards
Asanthi


On Sat, May 17, 2014 at 12:16 PM, Anuradha Karunamuni <[email protected]> wrote:

> Hi Asanthi,
>
> You can test this functionality by dynamically setting the role in the
> humantask instance using a single "logicalPeopleGroup".
>
> E.g.:
>
>        <htd:logicalPeopleGroup name="admin">
>             <htd:documentation xml:lang="en-US">The group of admins
> responsible for the region specified.</htd:documentation>
>             <htd:parameter name="role" type="xsd:string"/>
>         </htd:logicalPeopleGroup>
>
>          <htd:peopleAssignments>
>                  <htd:potentialOwners>
>                     <htd:from logicalPeopleGroup="admin">
>                         <htd:argument name="role">
>
>  htd:getInput("ApplicationApprovalRequest")/test10:authorizedRole
>                         </htd:argument>
>                     </htd:from>
>                 </htd:potentialOwners>
>           </htd:peopleAssignments>
>
> In this case only one "logicalPeopleGroup" is used, but the role is set
> based on the "authorizedRole" value in the request sent by the BPEL
> process. So in order make this work, you need to modify the BPEL process
> request to include the "authorizedRole" during humantask invocation.
>
> You can use the attached samples related to Application Approval process
> to test the scenario. It's implemented to test 3 roles
> namely "1-admin-role", "2-admin-role", "3-admin-role".
>
> Humantask         - ApplicationsApprovalTask-1.0.0
> BPEL Process    - SampleApplicationApprovalWorkFlowProcess_3.0.0
>
> Let me know if you need further details on this.
>
> Regards,
> Anuradha
>
>
>
> On Thu, May 15, 2014 at 11:37 PM, Asanthi Kulasinghe <[email protected]>wrote:
>
>> Hi,
>>
>> This is regarding the configurations of feature 'workflow permission for
>> multiple roles'  implemented under [1]
>>
>> Considering there are 2 roles  as follows how should the .ht file for the
>> relevant work flow be altered?
>>
>>  "allowedRoles":"wfrole1,wfrole2",
>>
>>
>> 1) Should we have one 'logicalPeopleGroup' defined for all allowed roles
>> and have all allowed roles under that 'logicalPeopleGroup' of
>> 'peopleAssignments'
>>
>> eg:
>>
>>  <htd:logicalPeopleGroup name="wfgroup">
>>             <htd:documentation xml:lang="en-US">The group of admins
>> responsible for the region specified.</htd:documentation>
>>             <htd:parameter name="role" type="xsd:string"/>
>>  </htd:logicalPeopleGroup>
>>
>>  <htd:peopleAssignments>
>>                 <htd:potentialOwners>
>>                     <htd:from logicalPeopleGroup="wfgroup">
>>                         <htd:argument name="role">wfrole1</htd:argument>
>>                         <htd:argument name="role">wfrole2</htd:argument>
>>                   </htd:from>
>>                 </htd:potentialOwners>
>> </htd:peopleAssignments>
>>
>> OR
>>
>> 2) Should there be a separate group for each role
>>
>> eg:
>>
>> <htd:logicalPeopleGroup name="wfgroup1">
>>             <htd:documentation xml:lang="en-US"> The group of admins
>> responsible for the region specified.</htd:documentation>
>>             <htd:parameter name="role" type="xsd:string"/>
>>  </htd:logicalPeopleGroup>
>> <htd:logicalPeopleGroup name="wfgroup2">
>>             <htd:documentation xml:lang="en-US">The group of admins
>> responsible for the region specified. </htd:documentation>
>>             <htd:parameter name="role" type="xsd:string"/>
>>  </htd:logicalPeopleGroup>
>>
>>  <htd:peopleAssignments>
>>                 <htd:potentialOwners>
>>                     <htd:from logicalPeopleGroup="wfgroup1">
>>                         <htd:argument name="role">wfrole1</htd:argument>
>>                      </htd:from>
>>                     <htd:from logicalPeopleGroup="wfgroup2">
>>                         <htd:argument name="role">wfrole2</htd:argument>
>>                      </htd:from>
>>                </htd:potentialOwners>
>> </htd:peopleAssignments>
>>
>>
>> I have tried both ways and it's not possible to make tasks available to
>> all 'allowedRoles' at the same time.
>>
>> It would be great if you could attach a sample .ht file with the correct
>> configurations if they differ from what is mentioned above.
>>
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-2044
>>
>> Regards
>> *Asanthi Kulasinghe*
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile: +94777355522
>>
>>
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
*Asanthi Kulasinghe*
WSO2 Inc; http://www.wso2.com/.
Mobile: +94777355522
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to