IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
For logging/tracing purposes I'd like to be able to get actual information about the mapping/card/function/field I'm currently at.
So I can write into a logging about that particular point in the execution.
A bit like LASTERRORCODE() or GETRESOURCENAME().
I'm thinking about these :
GETMAPDIR() : the directory where the mapping currently runs
GETMAPSOURCE() : the name of the source (.mms) of the currently running mapping
GETMAPNAME() : gets the name of the mapping that's currently running.
GETCARDNAME() : the name of the outputcard that's currently being build
GETCARDNUMBER() : the number of the outputcard that's currently being build
GETFUNCMAPNAME() : the name of the functional map you're currently in
GETFIELDNAME() : the name of the field you're currently in, optionally also if it's in a typetree
(like groupname::fieldname or maingroup::subgroup::fieldname)
GETCARDINDEX() : the index of the occurence the functional map is currently in
GETFIELDINDEX() : the index of the occurence a (group-)field is currently in.
How will this idea be used?
I'm using a lot of standardized functions in remote maps.
If I could get this information using these functions I wouldn't have to explicitly enter and maintain them if something changes, it would always be accurate.
These remote functions write a so-called 'EventLog' if something goes wrong.
It helps me find the exact spot where the error originated (which is always somewhere in a calling map).
I think that others could also benefit even for debugging purposes so one doesn't have to comb to massive trace-files.
A couple of these functions writing in a log would simplify that a lot.
|What is your industry?||Automotive|
|What is the idea priority?||Medium|
|Link to original RFE|