Event scripts not appearing.

Hi,I have orphaned a node, created a dummy script, set fEnabled to true..why can i not see my dummy event script?Can someone give me a step by step guide on how to do this?I can never seem to get this to work!

Find more posts tagged with

Comments

Donna Nalls

Hi, I walked through the process as I wrote this message, so this should definitely work for you. Give a shout if it does not!1) Unlock your custom module2) Navigate to WFMain-->WFRoot-->Callback Event Scripts-->GeneralCallbackScripts (but don't unlock it)3) Right click on GeneralCallbackScripts and select "New Orphan"4) Your Ospace should be displayed in the second menu - select it.5) When prompted for the name of the object remove the word "orphan" and add at the beginning. i.e. -- my module is called "MyTest" - so I name that object "MyTestTestingGeneralCallbackScripts"6) Navigate back to your custom ospace and verify that the object has been created.7) set .fEnabled = True for that object8) Highlight your Ospace's Globals object 9) Right Click on the "Build OSpace" method and select "Run Script"10) If desired, verify that your object has been registered.... a) in the Globals Object feature list open double-click on the "f__InitObjs" feature - make note of the last number item in the list..... b) highlight your GeneralCallbackScripts object and look down at the bottom of your Builder window. The object number should be the same as the one in your f__initobjs list - if it is not the last one, it should at least be in the list.12) create your new script13) open the "0Documentation" script and copy the function data out of it - paste it into your new script14) If desired, create a string feature and name it f + plus the name of your script. Add the user display value for the script here.15) Stop and Restart Builder16) Open a browser and log in to LL - open a workflow -- click on a step and check the "Event Scripts" tab. You should see your new script.Regards,Donna

Howard_Pell

Message from Howard Pell <hlpell@opentext.com> via eLink

eLink

I’ve saidthis before and I’ll say it again Donna – you would make a great Livelinktrainer!

<![if !supportEmptyParas]> <![endif]>

Howard

<![if !supportEmptyParas]> <![endif]>

______________________

Howard Pell

Senior Technical Educator

Liaison, Special Projects

Open Text Corporation

www.opentext.com

(1-519) 888-7111 Ext. 2203

<![if !supportEmptyParas]> <![endif]>

-----OriginalMessage-----
From: eLink Discussion: LivelinkBuilder Discussion [mailto:componentbuilder@elinkkc.opentext.com]
Sent: Friday, February 20, 20049:29 AM
To: eLink Recipient
Subject: Hi,

<![if !supportEmptyParas]> <![endif]>

Hi,		Posted by dnalls (Nalls, Donna) on 02/20/2004 09:27 AM
In reply to: Event scripts not appearing.		Posted by DeloitteAdmin on 02/19/2004 08:36 PM

<![if !supportEmptyParas]> <![endif]>

Hi,
I walked through the process as I wrote this message, so this should definitely work for you. Give a shout if it does not!

1) Unlock your custom module
2) Navigate to WFMain-->WFRoot-->Callback Event Scripts-->GeneralCallbackScripts (but don't unlock it)
3) Right click on GeneralCallbackScripts and select "New Orphan"
4) Your Ospace should be displayed in the second menu - select it.
5) When prompted for the name of the object remove the word "orphan" and add <Your Ospace Name > at the beginning. i.e. -- my module is called "MyTest" - so I name that object "MyTestTestingGeneralCallbackScripts"
6) Navigate back to your custom ospace and verify that the object has been created.
7) set .fEnabled = True for that object
8) Highlight your Ospace's Globals object <MyTest Globals>
9) Right Click on the "Build OSpace" method and select "Run Script"
10) If desired, verify that your object has been registered....
a) in the Globals Object feature list open double-click on the "f__InitObjs" feature - make note of the last number item in the list.....
b) highlight your <MyTesting>GeneralCallbackScripts object and look down at the bottom of your Builder window. The object number should be the same as the one in your f__initobjs list - if it is not the last one, it should at least be in the list.
12) create your new script
13) open the "0Documentation" script and copy the function data out of it - paste it into your new script
14) If desired, create a string feature and name it f + plus the name of your script. Add the user display value for the script here.
15) Stop and Restart Builder
16) Open a browser and log in to LL - open a workflow -- click on a step and check the "Event Scripts" tab. You should see your new script.

Regards,
Donna

DeloitteAdmin_(Delete)_2707331

Hi Donna,I've followed your instructions, my new node is registered with f_initobjs and i have copied the funciton code from the ODocumentation script.I've set fEnabled to TRUE.I still can not see an Events SCript tab in my user step when I restart Builder?This is the code i have in my AssignManagers script:Function Dynamic AssignManagers( \ Object prgCtx, \ WAPIWORK work, \ Integer workID, \ Integer subWorkID, \ Integer taskID, \ Integer returnSubWorkID, \ Integer returnTaskID, \ Dynamic extraData = Undefined ) Dynamic retVal return( retVal )endAlso, I have edited the webuilder.lxe file and modified change of state to incldeu my new ospace so that it is always unlocked when i start Builder, this does not work either..my ospace is always locked when i start builder..

Donna Nalls

Hello,I think there is something not right with your installation/environment. Did your module install correctly? When you look at the Install Module page, is your module showing up in the list of installed modules???Do you have anything else in your module at this time?Did you use the "Make a New Module" (by the great Martin Scott) to create your module???This is definitely a configuration issue.I understand from Howard Pell that there is an Incident Support program provided by Open Text and they might be able to walk you through your initial set up and configuration. Info is at the following link: https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=2672347&objAction=browseDonnaps--also, you might try removing your changes to the webuilder.lxe file - one modification at a time until you determine what your issue is - it is definitely setup/configuration, etc.

DeloitteAdmin_(Delete)_2707331

OK,I seemed to remember last time when I was playing with Builder we had a module installed called WFDOCPUBLISH.This module had been downloaded from KNowledge Centre and had a Publish_Doc script in it..I just reinstalled that module and the Events Tab now appears and there are now 2 scripts that I can choose from, the PublishDOc script that comes with the WFDOCPUBLISH module AND the other script is the script I have been trying to view all along... i.e the one from my own moduleDOes that make any sense?? :-)If the problem had been a set up/config/enviornment problem then would the WFDOCPUBLISH script have worked?Also with regard to the incident support, I think you can only use that if you are part of the SDK GOld SUpport Program... we only have the standard support..I have zipped up and attached my module, if any one has time I would appreciate if they could take a look at the ini files or something....

DeloitteAdmin_(Delete)_2707331

OK...So now I have uninstalled the WFDOCPUBLISH module and the Events Tab is still present with only my script in there,,Which is great!But i still dont get why installing the WFDOCPUBLISH module "triggered" the EVent SCript Tab to appear..Hope someone can clear that up..I'm now going to try and get my sript to do stuff! :-)

James_Maure_(americ02admin_-_(deleted))

Hi Donna,This is Dave Barker. It's been a long time since we've talked. It's good to see that you are still prowling around the KC. Here is a link to the history of the Make a New Module script, just in case you were curious.https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=3353588&objAction=view&show=2I am starting to work on a new custom module that takes this idea a step or two further to allow you to create custom modules from a web interface. How far it will go yet, I'm not sure. But I plan on making it more configurable than the existing script and will probably add some new preconfigured stub items like agents, etc.I've also created a new Workflow Deletion Utility that can delete approximately 4-5 workflows from Livelink per second. So, it helps to greatly reduce the clutter and wasted space that can occur within the Workflow system.A feature of this module is a new Request Handler type that provides a Streaming response instead of the slow and cumbersome two-step method. This is very useful for performing large data manipulation jobs, like bulk loading, large deletions, etc.The Workflow Deletion Utility Ciao,David Barkerdbarker38@yahoo.com