Asynchronous flag for the "Synchronizer(s) Execution" SAT

Follow

Soren Staun

• February 05, 2018 10:19

As a MooD solution designer

I want the ability to set a "Synchronizer(s) Execution" SAT to be asynchronous 

So That I am be able to first do actions that sends feedback back to the user (so he waits), but then kick off a background job to update caches or other things 

Benefits : Better response times since user doesn't have to wait for caching to complete and he doesn't need to monitor everything in a SAT group.

Acceptance Criteria 

1. …… I can configure the SAT 
2. …… Tick off Asynchronous 
3. Execute and watch first part be sync and last part be async.

Customer / Originator SEB

Priority Medium

 

1

• Official comment

  

  Iva Sharp

  • February 05, 2018 10:25
  • Edited

  Hi Soren, 

  Thank you, the request has been logged with the product owner,                                                                     We'll get back to you in due course.

  Best regards from the MooD team,                                                                                                                          Iva 

  Comment actions Permalink
• 

  Hugh Emery

  • April 06, 2018 11:48

  Hello Soren,

   

  Do you mind elaborating further on the use case here? We are looking for some further explanation to ensure we understand the story correctly.

   

  Kind Regards,
  Hugh

  0

  Comment actions Permalink
• 

  Soren Staun

  • April 12, 2018 11:10

  Hey,

   

  Yes, absolutely. I’ve been in some situations where I would like to:

  • Execute a SAT I would like the user to see if it fails or not (synchronous)
  • Execute further SATs doing back-end clean up which the users does not have wait for (asynchronous)
  • (In that order!)

   

  So:

  SAT group is:

  1. Export Data
  2. Import Data
  3. Refresh cache 1
  4. Refresh cache 2
  5. Refresh cache 3
  6. Refresh cache 4
  7. Refresh cache 5
  8. Refresh cache 6

   

  A concrete use-case:

  SEB wants to run a synchronizer that publishes initiatives from a draft state to a published state. This is handled by the first 2 SATs that first export the needed data (Excel merge out), and then Excel In to read the data into Measures (could be anything, but we used measures this time). Once the data is written into measures successfully, the users I happy and can go away.

   

  Problem is, we’re not done since we need to refresh a lot of caches doing all kinds of calculations, so further 10 SATs need to run after this (asynchronously).

   

  Problem for user: I’m waiting 6 minutes for caches to refresh, and 10 seconds would be enough.

   

  If I could turn the scenario into:

  SAT group is:

  1. Sync run: Export Data
  2. Sync run: Import Data
  3. Async run: SAT execution

   

  Where 3 would run another SAT group:

  1. Refresh cache 1
  2. Refresh cache 2
  3. Refresh cache 3
  4. Refresh cache 4
  5. Refresh cache 5
  6. Refresh cache 6

   

  And then set a [X] flag on SAT Execution window that could hold the logic 

  That would effectively fix issue and allow me to combine waiting for user and not waiting.

   

  Best regards,

   

  Søren

  0

  Comment actions Permalink

Please sign in to leave a comment.