we are refactoring some of our scripts and we want the code in an after-submit should only run after a map-reduce task finishes , is this possible?

The after-submit function of a record will always run immediately after the record is saved to database. It will not be tied to the completion of the map-reduce job. What is the use-case for wanting that?

correct, I have an after-submit on Transfer Order that creates item fulfillment however we have assembly that need tob e build before the item fulfillment

have the map-reduce script check a box on the record and then run the afterSubmit only if that box is checked?

You can do this via configuration at the Script Deployment level by adjusting the Context Filtering on the Deployment record or in code via the

N/runtime

module's executionContext property

(or a specific M/R)

You could use

N/runtime.Script

to detect a specific M/R

the map-reduce is building the assembly not tied to the transfer order record

can you not check in the after submit if the assembly has been built or not before fulfilling it? (I don't know much about assemblies)

so the transfer order is created via external api ---> Also a task for map reduce is created via reslet to trigger map reduce task

Sounds like this would be a use case for

.addInboundDependency()

option when triggering the Map/Reduce, but unfortunately, that's only available to search-type tasks. I wonder if you add multiple dependencies do they run in series or parallel. If the former, you could hack this by creating a dummy search task, and set your M/R and then the second script to create the IF as dependencies

i personally say use the logic from the after submit in the map/reduce script instead so you can make it run after the creation of the assembly record

can i just move the logic from the after submit to summarize of the map/reduce ?

unlikely unless you are misusing the map/reduce script