<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV>Hi All,</DIV>
<DIV> I have a really dumb question(rather, a clarification) about the usage of 'Organizational Objects'(Organizational unit,position,job,workcenter etc.) in the responsible agents field in the STEP definition of a workflow.</DIV>
<DIV> I undestand that all the organizational objects form part of application data which is client/system dependent.This means,when the workflow is transported to other systems,the workflow may not work correctly because these org objects may not exist in the target system.So what's the point of specifying this application data in the workflow definition ?! . I feel it's best to leave the values for organization object as blank in DEV system, and then use 'Workflow customizing' to assign the organization objects in the traget system.</DIV>
<DIV> </DIV>
<DIV>Pls advice if you agree with me or excuse this ignorant fellow workflower......... </DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Kiran.</DIV></div><br>
<hr size=1>Check out <a href="http://us.rd.yahoo.com/evt=43257/*http://advision.webevents.yahoo.com/mailbeta">the all-new Yahoo! Mail</a> - Fire up a more powerful email and get things done faster.</body></html>