Great work Ram :) I always share your playlist to anyone asking me about RAP. I have few statements I need you to answer if they are right or wrong - 1. Changes to UI before clicking save button is only possible when determination 'on modify' is wrapper in a side effect. 2. If there is no side effect, then 'on modify' and 'on save' both trigger on click of save button, just that the sequence is that first 'on modify' triggers and then 'on save'. 3. The logic of point 1 and 2 stands same in case of draft enabled RAP app.
1. Changes on UI before clicking save are not automatically possible. 2. on modify' and 'on save' both trigger on click of the save button always irrespective of side effect As soon as you click on save first it will trigger on modify then on save.The on;y advantage of on modify if something goes wrong user can edit fix and save again. But in on Save something goes wrong you can't come back to interaction phase and you have to start again In next video you will see live (❁´◡`❁)
Thank you for your response@@SAPTECHNOMANIAC :) As per my understanding, determination 'on modify' can work like 'onchange' event of JavaScript if wrapper in a side effect. We do not need to click save button for it to trigger with side effects.
@@Sachinartani Your statement is not true in case of non=-draft application .May be true for non-draft I need to check. My statements are true with respect to non-draft application. For draft application I need to check once again you will see in upcoming video where I will convert this application to draft application ☺☺
Great work Ram. 👍
Thank you! Cheers!
Great work Ram :)
I always share your playlist to anyone asking me about RAP.
I have few statements I need you to answer if they are right or wrong -
1. Changes to UI before clicking save button is only possible when determination 'on modify' is wrapper in a side effect.
2. If there is no side effect, then 'on modify' and 'on save' both trigger on click of save button, just that the sequence is that first 'on modify' triggers and then 'on save'.
3. The logic of point 1 and 2 stands same in case of draft enabled RAP app.
1. Changes on UI before clicking save are not automatically possible.
2. on modify' and 'on save' both trigger on click of the save button always irrespective of side effect
As soon as you click on save first it will trigger on modify then on save.The on;y advantage of on modify if something goes wrong user can edit fix and save again. But in on Save something goes wrong you can't come back to interaction phase and you have to start again
In next video you will see live (❁´◡`❁)
Thank you for your response@@SAPTECHNOMANIAC :)
As per my understanding, determination 'on modify' can work like 'onchange' event of JavaScript if wrapper in a side effect. We do not need to click save button for it to trigger with side effects.
@@Sachinartani Your statement is not true in case of non=-draft application .May be true for non-draft I need to check. My statements are true with respect to non-draft application. For draft application I need to check once again you will see in upcoming video where I will convert this application to draft application ☺☺
@@SAPTECHNOMANIAC Yes, I think you are right. I will wait for the next video. Thanks 🙂
Nice playlist with clear understandiing thanks a lot.....do you provide training as well
No, I just upload videos on UA-cam 🙂