Service call handling invoked before loaded

Andrzej Michalec

January 24, 2017 at 5:53 am #3558

Hi,
In SPARK 4.4.7 there is new “on invoked” handler added to Service Call component. To my surprise when Service Call is configured as “auto run” it gives me following sequence of handlers: invoked-load-result, instead of: load-invoked-result. I expect load event to handled before any other activities so that concept of load-handling is consistent across the system. Can you confirm and change event sequence in next release?

regards,
andy.

SPARK Support

January 27, 2017 at 11:25 am #3600

Hello,

Thank you for bringing this to our attention.  We are currently investigating this issue and will respond with further information in a timely fashion.

Regards,

SPARK Support

SPARK Support

January 31, 2017 at 11:08 am #3611

Hi Andy,

I was able to replicated the issue that you are seeing.  After a discussion with the Development Team, here are our observations.

Due to the fact that the On Load event is triggered by the bpmext.js as part of the loadView method, individual SPARK controls do not “trigger” the On Load event.  It appears that this is only an issue for Service Calls that use auto-run.  If the scenario calls for both an On Load and an On Invoked event to be triggered, and the On Load code must run first, use this work-around:

1. Leave auto-run deselected
2. Place the code required in the On Load event
3. Add a me.execute() statement to the end of On Load

Regards,

Stephen P.

Andrzej Michalec

February 8, 2017 at 5:44 am #3638

Stephen, thank you for explanation and workaround. I assume however that in next release(es) you will make “on load” running before “on invoked” to fulfil the contract imposed by coach framework saying that load happens first 🙂

regards,
-andy.

SPARK Support

February 17, 2017 at 11:35 am #3750

Hi Andy,

Let me review this with the Development Team again.

I will advise you if we decide to put this as a Known Issue with the work-around provided.

Regards,

Stephen p.