Hi all,
+1. This is about failure of first action of app creation, if it is failed,
just show error message and continue. No need to update database.
thank you.
On Mon, Jul 18, 2016 at 9:18 AM, Mahesh Chinthaka wrote:
> Yes adding a failure pop up message would be enough
Yes adding a failure pop up message would be enough IMO. I forgot to
mention that in my previous reply. Thanks Danushka
On Mon, Jul 18, 2016 at 9:13 AM, Danushka Fernando
wrote:
> To be specific, AFAIK even we name these as events, This is not for data
> publishing kind of a
To be specific, AFAIK even we name these as events, This is not for data
publishing kind of a thing. This is only to render the ui. Then there is an
issue of UI when its broken in earlier stages it don't show the msg box
with msg of application creation failed. So before showing that it should
Hi All,
Isnt it better to avoid adding an event at this point ?
Since nothing has been created related to application , no need of adding
an event right ?
WDYT ?
On Sat, Jul 9, 2016 at 8:19 AM, Amalka Subasinghe wrote:
> Hi,
>
> In our app creation logic, we have number of
Hi,
In our app creation logic, we have number of steps and when each step
failed/succeeded, we add a event to a event table.
We found a situation, where the createAppInDataBase step failed, then the
addAppCreationEvent also getting failed.
That's because, in createAppInDataBase we add