Hi Udara,

I think that will depend on how the lifecycle is defined and what states
are declared as 'delete states'.  i.e. Does the lifecycle contain a
possible transition as 'Published' ---> 'Deleted'. If such a state
transition is available we will face the issue you mentioned regarding
subscriptions.

The deletion will be more meaningful if transitions to a delete state are
restricted to start from states such as 'deprecated', 'retired' or
'rejected'.

WDYT?

Thank you,
Sameera


On Wed, Aug 13, 2014 at 10:10 AM, Udara Rathnayake <uda...@wso2.com> wrote:

> Hi Sameera,
>
> Is there a way to activate this delete state? Let's take an asset in
> published life-cycle state, so are we going to allow user to click on
> delete state and then remove the asset?
> If yes, how we going to manage current subscribers for that particular
> asset?
>
> Regards,
> UdaraR
>
>
> On Wed, Aug 13, 2014 at 9:11 AM, Sameera Jayaratna <samee...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I am currently working on [1], to facilitate deleting an asset through
>> the UI in Publisher. We plan to provide this based on the lifecycle state
>> of the asset. Therefore a set of states/a single state has to be defined as
>> 'delete' state(s).
>>
>> As per a discussion with SameeraM, there are two ways in which we can
>> present this to the user.
>>
>> 1. When a user clicks on the delete state,
>>
>>
>>    - A message prompt will appear to confirm the deletion
>>    - If user confirms, the asset will be permanently deleted and the
>>    state transition will occur showing the current state as the given 
>> 'delete'
>>    state.
>>    - Else, the state will remain as it is.
>>    - In this approach its meaningful to define only a single delete
>>    state, as entering the state means deletion of the asset.
>>
>> 2. When a user clicks on one of the delete states,
>>
>>
>>    - A 'delete asset' button will appear on a side of the current view
>>    - The user can choose to delete the asset or not.
>>    - In this approach we can have a set of states defined as delete
>>    states, in which the user *may *delete an asset if needed.
>>
>> What is the best way to provide this functionality?
>>
>> [1] https://wso2.org/jira/browse/STORE-120?filter=11919
>>
>> Thank you,
>> Sameera
>>
>> --
>>
>>
>>
>> *Thanks & Regards, Sameera Jayaratna Software Engineer; **WSO2 Inc. *
>>
>> *lean . enterprise . middleware |  http://wso2.com <http://wso2.com> *
>>
>> _______________________________________________
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Udara Rathnayake*
> Software Engineer
> WSO2 Inc. : http://wso2.com
>
> Mobile : +94 772207239
> Twitter : http://twitter.com/udarakr
> Blog    : http://udarakr.blogspot.com
>
>
> _______________________________________________
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 



*Thanks & Regards,Sameera Jayaratna Software Engineer; **WSO2 Inc. *

*lean . enterprise . middleware |  http://wso2.com <http://wso2.com> *
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to