Topic
  • 3 replies
  • Latest Post - ‏2014-02-19T01:00:35Z by Ashish2
babinag
babinag
91 Posts

Pinned topic Implisit script variables. Need ultimate description.

‏2012-04-18T13:37:46Z |
There is bunch of implicit variables in script api, without documentation. Does anyone use variables, marked by "what for is it?"?

all_itemset_fetch_linked_item, - what for is it?
all_itemset_readonly, - what for is it?
attribute_group, - what for is it?
bypass_approval_workflow, - what for is it?
catalog, - self explanatory
category, - self explanatory
category_tree, - self explanatory
colArea, - self explanatory
collaboration_area, - self explanatory, double?
container, - self explanatory
destination_attribute, - what for is it?
entry, - self explanatory, used everywhere
entrynode, - self explanatory, used everywhere
entrySet, - self explanatory
err, - self explanatory
err_lines, - what for is it?
http_request, - self explanatory
in, - self explanatory
inputs, - used in sample macro script out of box
invoking_user, - what for is it?
item, - self explanatory
job, - self explanatory
lkpTable, - self explanatory
location, - what for is it?
location_tree, - what for is it?
locationRootEntryNode, - what for is it?
logger, - wow, what logger is it?
lookup_table, - self explanatory
message, - what for is it? who ever used it?
msg_attachments, - who ever used it?
multi_request, - what for is it?
node, - self explanatory
organization, - self explanatory, but where to use?
organization_type, - self explanatory, but where to use?
original_doc_folder, - self explanatory, but where to use?
out, - self explanatory
outs, - what for is it?
page, - what for is it?
page_layout, - what for is it?
queueid, - what for is it?
request, - self explanatory
res - self explanatory
run_rule_per_occurence, - self explanatory, but where to use it?
save_event, - self explanatory
sequence, - self explanatory, but what for?
soapFaultCode, - self explanatory, but where to use it?
soapFaultMsg, - self explanatory, but where to use it?
soapIncomingAttachments, - self explanatory, but where to use it?
soapMessage, - self explanatory
SoapOperationName, - self explanatory, but where to use it?
soapOutgoingAttachments, - self explanatory, but where to use it?
soapParams, - self explanatory
spec, - self explanatory
spec_map, - self explanatory
special_outs, - what for is it?
specmap_script_dest_attrib, - what for is it?
step, - self explanatory
stepPath, - self explanatory
this, - self explanatory, where to use?
top, - what for is it?
val, - what for is it?
workflow, - self explanatory
workIndex, - what for is it?
workList, - what for is it?
wrn - what for is it?
Updated on 2012-12-11T06:59:53Z at 2012-12-11T06:59:53Z by babinag
  • KaranBal
    KaranBal
    108 Posts

    Re: Implisit script variables. Need ultimate description.

    ‏2012-06-29T23:15:22Z  
    There are too many to explain. Please search for them in the information center: http://publib.boulder.ibm.com/infocenter/mdm/v10r0m0/index.jsp?
  • babinag
    babinag
    91 Posts

    Re: Implisit script variables. Need ultimate description.

    ‏2012-12-11T06:59:53Z  
    outs - useful variable in, for example, import script context hashmap.
    It holds 3
    
    com.ibm.ccd.common.util.TmpFileWriter
    
    's:
    err_lines - error lines
    err - for errors
    wrn - for warnings.
    Each writer after import results in link to docstore *.csv import report, if number of errors appear at progress($script_stats
    
    com.ibm.ccd.common.interpreter.util.ScriptStats
    
    variable) greater than 0.

    It is possible to add new custom
    
    com.ibm.ccd.common.util.TmpFileWriter
    
    to outs, that will result not to *.csv report but to *.txt report and write useful information to that writer, ant then replace link to errors.csv to errors.txt, for example.
  • Ashish2
    Ashish2
    1 Post

    Re: Implisit script variables. Need ultimate description.

    ‏2014-02-19T01:00:35Z  
    • babinag
    • ‏2012-12-11T06:59:53Z
    outs - useful variable in, for example, import script context hashmap.
    It holds 3 <pre class="jive-pre"> com.ibm.ccd.common.util.TmpFileWriter </pre> 's:
    err_lines - error lines
    err - for errors
    wrn - for warnings.
    Each writer after import results in link to docstore *.csv import report, if number of errors appear at progress($script_stats <pre class="jive-pre"> com.ibm.ccd.common.interpreter.util.ScriptStats </pre> variable) greater than 0.

    It is possible to add new custom <pre class="jive-pre"> com.ibm.ccd.common.util.TmpFileWriter </pre> to outs, that will result not to *.csv report but to *.txt report and write useful information to that writer, ant then replace link to errors.csv to errors.txt, for example.

    Hi,

    Can someone please help me to figure out how to get error lines writer in java?

     I am able to get error writer and warning writer from inArgs argument of import job. How do I get err_lines writer?

    I need to write error records to statistics of the job console.

     

     

    Thanks,