How to Update the Workflow Title using Event Scripts

Can anyone tell me how to update the workflow title using event scripts once the workflow is initiated. I am using the following Update statement to update the title, but for some reason i get 0 rows updated in the OT SQL Logs.

update wsubwork set subwork_title = 'My Title' where subwork_subworkid = 502182

But if i run the same SQL from the back-end, the tables get updated appropriately. Any Clues.

Thanks in advance.

Find more posts tagged with

Comments

Appu_Nair

See this thread where my good friend Donna Nalls talks about doing this

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=16660648&objAction=view&show=2

My USD0.02,you should not use table updates/inserts directly in livelink.It is not equipped to do all the other related table updates so you are running the risk of either

Completely making a lot of orphanned entries
You are starting out and you have adopted a wrong path to follow.

If you were really curious and learning builder you should by now have been able to use CAPI to do what you were doing ALTHOUGH I REALLY ADVICE AGAINST IT.

In any case if my supervisor told me to do this I would trace the RH work.statusdone and code the title using this snippet which I just looked up using builder.You only need the WAPI.UpdateSubWorkAttribute

if ( IsFeature( r, 'Title' ) && Length( r.TITLE ) )
                        name = Str.Trim( r.TITLE )

                        if ( Length( name ) )
                            .CheckError( WAPI.UpdateSubWorkAttribute( \
                                                        work, \
                                                        r.WorkID, \
                                                        r.SubWorkID, \
                                                        WAPI.SUBWORK_TITLE, \
                                                        name ) )
                        end

Your event script has most of that info the call is expecting.

Good luck in your endeavours

VIJHAY DEVARAJAN

Appu

Thanks a ton for psting the snippet.

On your snippet you have used a variable 'r', can you elaborate how the variable 'r' was initialized. \

In order to fetch the Workflow title can i use the LoadWorkData() function to do so, as shown below.

$WFMain.WAPIPkg.LoadWorkData(prgCtx, work)

Also, can you tell me the exact OSpace which you referred in builder to get hold of the snippet, Thanks.

Appu_Nair

oscript has search ,search for work.statusdone RH and you will find the RH.Just initiate a workflow with two or three steps.Initiate the first step and manage the map as if you want to change the title.If you have put a break in that RH you can see what "r' contains.Usually in oscript request handlers use 'r' which is the Request record for passing all the stuff from the posting form

The ospace is webwork I do not have builder access now

VIJHAY DEVARAJAN

Following is the code snippet i am using to rename the workflow title during initiation:

myWork = prgCtx.WSession().AllocWork()
status = WAPI.AccessWork(myWork, workID, subWorkID)
if(status == 0)
result = WAPI.UpdateSubWorkAttribute(myWork, workID, subWorkID, WAPI.SUBWORK_TITLE, formWFName)
end
WAPI.FreeWork(myWork)

The variable myWork is a local variable declared within the event script, which is of type WAPIWORK.

The workflow gets initiated without issues, but i get an error message "Could not locate specified work". I am also able to Echo the values for the variables workID and subWorkID. Any Clues.

Appu_Nair

I beleive you are doing everything correct.So is the title not getting updated or are you saying that you are not expecting to see the error in builder.

If the title is not getting updated it is just a small timing issue.

Eventscripts are written in C++ so it almosts becomes like a "chicken & egg" situation if eventscripts are called too soon.(like I want my Eventscript to run on initaition)

For eg.My aim is to update the title which behind the scenes has to update a table.

So the right sequence is

User sees workflow

User fills form

Let workflow be initiated

Let there be a dummy step like a FYI right after initiate maybe create a IH step and let it be assigned to an agent

The title is committed in the db

Put your event script on the exit condition of this second step(when this step is completed)

I do not know further to comment on your FreeWork error

Take a look at postings form Jeff Lang where he comments on writing/debugging event scripts correctly.

use search on old postings in Development,builder and workflows there should be plenty of eye openers form Jeff ::)

Appu_Nair

After I posted this I suddenly realized that you may just be looking for a way to get a meaningful title.do you know that wokflow attributes and form attributes can be used to conjure up a title.It does not need any eventscripting et al.If that is your only requirement you can take a look at this example I put hastily together(before somebody else points out that how manty oscript programmers does it take to change a title at initiation

See this word document link

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=17487218&objAction=download

This approach does not work on subworkflows so you do have to do that in oscript

VIJHAY DEVARAJAN

Appu

I have resolved the issue, i put an additional user step and called the event script in the 'Step Becomes Ready' event. Technically this user step will not be visible to the user.

As you suggested using the IH step, i observed that for some reason the event scripts were never called by the IH step.