Question Previous step name

Hi,

The sessions executes with ExecuteDelivery cannot know the parent session name.

You need to pass the information as a process parameter with the expression ${~/CORE_NAME}$, for example like this :



Does this help in what you were trying to do ?

OK, I did not see this process in your previous Export, but anyway I think I understand better what you need to do.

You need to setup an "Error handling" process which would be triggered when any of the mappings / steps have an error.
Is this correct ?

Here is a quick example, based on a Scripting action as documented in the Reference Documentation "Developer's Guide > Working with Scripting > Using the Scripting Context > getVariableTreeByName Method" :



Notes :
- I have put all the mappings and steps that I want to monitor in the same subprocess => no need to design multiple red links, only one will detect any error occurred in the subprocess
- the scripting action will produce an output like this on the Runtime console, showing the exact step where the error occured :

14/01/2020 12:00:29,492 - default (c0a83801016fa3b643beceeb09979b15) is started
-- ACTION --> default/Mappings/Load DIM_PAYMENT_TYPE/L1-DIM_PAYMENT_TYPE-Load/Creation of load table
java.sql.SQLException: SQL Exception
at com.indy.engine.main.connections.b.b(SourceFile:253)
at com.indy.engine.main.connections.b.a(SourceFile:320)
at com.indy.engine.main.connections.JDBCConnectionContainerI.<init>(SourceFile:43)
at com.indy.engine.action.common.ActionCodeTypeI.setConnection(SourceFile:379)
at com.indy.engine.actionCodes.JdbcActionCodeI.executeDDL_DML(SourceFile:769)
at com.indy.engine.actionCodes.JdbcActionCodeI.executeSimpleCode(SourceFile:1271)
at com.indy.engine.action.common.ActionCodeTypeI.executeCode(SourceFile:1509)
at com.indy.engine.action.common.ActionCodeTypeI.run(SourceFile:1653)
at java.lang.Thread.run(Thread.java:748)
[...]
14/01/2020 12:00:49,053 - default (c0a83801016fa3b643beceeb09979b15) is ended

This example prints the step name and the error on the Console. But you can imagine to store this information in a variable, send an email, or write it in a database... as you wish.
Does this help for what you were trying to do ?

Please send and export of the TEST_GCE_p_GCE_ISF_PPH_Child process, not the TEST_GCE_p_GCE_ISF_PPH.

I don't know what "retrieve all informations about datastore" means, can you provide more details ?

It is not currently possible to extract Source and Target table names from a mapping at execution time.
This idea sounds quite obscure to me, because a mapping may have multiple Sources, Targets, and the same datastore can be both a Source and a Target in the same mapping.
So it cannot be as simple as "what is the mapping source and target names" ?
If you have a real business use case behind this, I suggest you post your detailed need in the Feedback section of this website.
=> stambia.org/feedback