variables in Workflow

Following code is taken from manual

my @bundle = $localizer->load( $dir, $propfile ); 

my $submit_image = $localizer->format('submit_image');
my $submit_image_label = $localizer->format('submit_image_label');

CGI_info(
   title               => $localizer->format('page_title'),
   locale              => __VALUE__('iw_locale'),
   error_label_bgcolor => "#EEEEEE" ,
   cancel_label        => $localizer->format('cancel_button_label')  ,
   submit_label        => $localizer->format('submit_button_label')  ,
);

    TAG_info(

       # The value of the tag "iw_submit_comment" (obtained from the user)
       # will appear as a user variable on the submit task.
       # It will also be used as the job's description.

       iw_submit_comment  =>  
           [ html        => "",
             error_msg   => $localizer->format('submit_comment_error_msg'),
             label       => $localizer->format('submit_comment_label'),
           ],

#      iw_output_file => "\n",
#      iw_debug_mode  => "\n",
    );

    # make sure the file list is defined 
    my @submit_file = ();                      # files sorted in unencoded
    if (__ELEM__('iw_file'))                   # form, then html-encoded 
    {                                          # by hand via CGI_lite 
@submit_file = map { TeamSite::CGI_lite::escape_html_data($_);
                           } sort  __VALUE__('iw_file');
    }  ...............

are iw_file and iw_locale variables defined by Autonomy for a workflow ? Where can I find this list of default workflow variables ?

I can see iw_raeaowner, iw_branch, iw_user and some more. Where is exhaustive list ? Or is there a way to figure out such variables ?

Thanks

Find more posts tagged with

Comments

ISCBorisB

...are iw_file and iw_locale variables defined by Autonomy for a workflow ? Where can I find this list of default workflow variables ?

I can see iw_raeaowner, iw_branch, iw_user and some more. Where is exhaustive list ? Or is there a way to figure out such variables ?Thanks

You may want to take a look at the "*.wft" Collection here: /iw-home/local/config/wft/solutions.
Read Synopsis at the beginning of these WF templates, you'll find lists of exposed HTTP request
keys there.

That said, you probably do not need any of it. All this Jazz is related to older "WFT" Workfow
instantiation mechanism. Although still in use, modern Vendor-supported approach is to use WF Models
or "WFM".

Unless your deliberate choice is for whatever reason WFT (support for existing WFs, etc...), find
"Workflow Modeler User's Guide" and start reading.

peculiar

Thanks, I did get some details in here.

Is there a way to ask beginner questions ? Which will be of the level of using TeamSite ? I am new to TS and not very familiar. I had some training from one of TS developers in our organization. But, that was not up to the mark.

who is iw_areaowner ? Is he the owner of work area ? There are many users in a work area, I have not seen anyone as an owner of a work area. I have seen author, editor, reviewer, admin and master, but not owner. So who is areaowner ? Is he owner of workflow ? Who is owner of workflow ? When here it says owner of workflow, does it mean the one who is mentioned as owner of workflow(I have not seen anyone as an owner of a workflow) or the one who started a workflow job ?So, one who started a job (workflow instance) automatically becomes workflow owner (for that job) ? So any user who initiates this workflow becomes owner of the workflow for that job, right ? So if different instances of same workflow are initiated by different users then there are different owners for that particular workflow, is that right ? And workflow owner (job owner) is specified in TeamSite as iw_areaowner, is that right ?
All other users of workflow are simply users specified by iw_user in TeamSIte for that job.

Regards.

ISCBorisB

Q. who is iw_areaowner?
A. Navigate to the Branch level, Click "Workareas" and check properties of any WA. You will see that it has an owner.
Check properties of Staging/Editions, they also have owners. In short, every "Area" of the Branch has an owner.

Q. Who is [the]owner of workflow?
A. Workflow developer decides who will be the owner of instantiated workflow Object (The "Job" in TS vernacular).
This decision is implemented through WFT Template or WFM Model.

iw_user is a job instantiator. In the simple WF you'd indicate that iw_user will be the job owner as well.
There are however sound use cases where you would like somebody else to own a job. For example, you may want
to deny the job instantiator an ability to arbitrarily terminate WF or perform other privileged actions. To accomplish that
you'd indicate Job owner that differs from iw_user. It can be iw_areaowner or it can be anyone else that your use
case requires. With code, you can make instantiation time ownership assignment as dynamic as you want.

Q. So, one who started a job (workflow instance) automatically becomes workflow owner (for that job)?
A. I hope it is clear from above explanation that the answer is "It depends on how Template/Model sets Job Owner".
In some WFs that will indeed be the case. In others it won't.

Q. So if different instances of same workflow are initiated by different users then there are different
owners for that particular workflow, is that right?
A. Same as above

peculiar

Thanks.

I checked wft file for one of the workflows. A section of it is as follows.[php]
owner="__TAG__('iw_areaowner');"
creator="__TAG__('iw_areaowner');"
description="__TAG__('iw_submit_comment');">

owner="__TAG__('iw_areaowner');"
description="Author Content Approval"
start="t"
readonly="t">

......[/php]In here, it does specify owner = _TAG_(iw_areaowner)
Does it mean that owner of the workarea from where this workflow is instantiated is the owner of this workflow ? With that said, if this workflow is configured to be available in different workareas and all workareas have different owners. In that case owner of the workflow will change according to the workarea its instantiated from ?
Can a workflow be configured for branch level ? That is a workflow is available to some branch and not to others ? Or can it be configured at workarea level only ? and different branches need to have their own copy of workflow ?
available_templates.cfg has nothing to do with assigning ownership of workflow, right ?

Regards

ISCBorisB

Does it mean that owner of the workarea from where this workflow is instantiated is the owner of this workflow ? With that said, if this workflow is configured to be available in different workareas and all workareas have different owners. In that case owner of the workflow will change according to the workarea its instantiated from ?
Can a workflow be configured for branch level ? That is a workflow is available to some branch and not to others ? Or can it be configured at workarea level only ? and different branches need to have their own copy of workflow ?
available_templates.cfg has nothing to do with assigning ownership of workflow, right ?

Regards

Hmmm... That's 7 more questions. IMO it's time for you to start playing with WF Templates, instantiate jobs and try to answer these questions yourself.

Adam Stoller

Hmmm... That's 7 more questions. IMO it's time for you to start playing with WF Templates, instantiate jobs and try to answer these questions yourself.

... and read the manuals and, most likely, see about getting formal workflow development training from HP-Autonomy-Interwoven.

The forums aren't really the right place to get training....