Re: [Architecture] [IAM] UX design for Retryable Outbound Provisioning Feature.

[Malithi Edirisinghe]

Hi Menaka,

I have few suggestions.

1. This is with related to outbound provisioning. So I think the name
should indicate that aspect. Moreover, this feature is more related with
monitoring aspect and triggering some actions based on that. Maybe
something like 'Outbound Provisioning Monitor' would be more suitable.
Also, I think this should move under some menu item like 'Monitor' or
'Manage'.

2. I think it's better to have an option to select all entries and perform
some action (retry/delete). Yet, below should be considered.

   - Should we allows retry for success operations. I think when success
   operations only 'delete' operations should be allowed
   - Is there a filter option as 'All' which will list both failed and
   success operations. If someone select all entries from that and perform a
   retry what would be the expected behavior. IMO, in such a case, the message
   to the end user should indicate only failed operations are retried.
   - There's a difference between deleting a success entry and a failed
   entry. If a failed entry is deleted it cannot be retried again and there's
   no need of a retry operation for a success entry. So, IMO, when deleting a
   failed entry the impact should be highlighted to the end user and upon
   confirmation entry should be deleted.

Thanks,
Malithi.

On Fri, Feb 2, 2018 at 9:47 AM, Menaka Jayawardena  wrote:

> Hi Imesh,
>
> Thank you very much for the suggestions. Please find my comments inline.
>
> Hi Menaka,

 Please find the bellow suggestions.

 IMHO, the filtration controls should resemble a visual connection to
 the listing.

>>>  I have followed the default UX design in Management Console for this
> otherwise it would break the consistancy.
>
>>
 Retry and delete actions should get a more prominence since they are
 the primary actions of this page

>>> +1 for this.
>
> If we could filter the data on the selection of each filtration criteria,
 IMO it's better to remove the "filter" button. For and example if we could
 update the listing according to the selected criteria, the action is not
 needed.

>>>  Yes. This could be done.
>
> When Deleting / Retrying without selecting a record, IMO it's better to
 disable the buttons until the user select at-least one record. WDYT?

>>>  +1.
>
>> --
 *Thanks and Best Regards,*
 Imesh Ashandimal Chandrasiri
 *Software Engineer*
 WSO2, Inc.
 lean . enterprise . middleware
 *E:* ime...@wso2.com | *P:* 0716519187 <071%20651%209187>

 --
>> *Menaka Jayawardena*
>> *Software Engineer - WSO2 Inc*
>> *Tel : 071 350 5470*
>> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
>> *
>> *Blog: https://menakamadushanka.wordpress.com/
>> *
>>
>>
>
>
> --
> *Menaka Jayawardena*
> *Software Engineer - WSO2 Inc*
> *Tel : 071 350 5470*
> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
> *
> *Blog: https://menakamadushanka.wordpress.com/
> *
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Malithi Edirisinghe*
Associate Technical Lead
WSO2 Inc.

Mobile : +94 (0) 718176807
malit...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [IAM] UX design for Retryable Outbound Provisioning Feature.

[Menaka Jayawardena]

Hi Imesh,

Thank you very much for the suggestions. Please find my comments inline.

Hi Menaka,
>>>
>>> Please find the bellow suggestions.
>>>
>>> IMHO, the filtration controls should resemble a visual connection to the
>>> listing.
>>>
>>  I have followed the default UX design in Management Console for this
otherwise it would break the consistancy.

>
>>> Retry and delete actions should get a more prominence since they are the
>>> primary actions of this page
>>>
>> +1 for this.

If we could filter the data on the selection of each filtration criteria,
>>> IMO it's better to remove the "filter" button. For and example if we could
>>> update the listing according to the selected criteria, the action is not
>>> needed.
>>>
>>  Yes. This could be done.

When Deleting / Retrying without selecting a record, IMO it's better to
>>> disable the buttons until the user select at-least one record. WDYT?
>>>
>>  +1.

> --
>>> *Thanks and Best Regards,*
>>> Imesh Ashandimal Chandrasiri
>>> *Software Engineer*
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> *E:* ime...@wso2.com | *P:* 0716519187 <071%20651%209187>
>>>
>>> --
> *Menaka Jayawardena*
> *Software Engineer - WSO2 Inc*
> *Tel : 071 350 5470*
> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
> *
> *Blog: https://menakamadushanka.wordpress.com/
> *
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
*
*Blog: https://menakamadushanka.wordpress.com/
*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture