using eRaiseFlag to raise a Flag from outside of metastorm

[Rosemary Fromm]

I have gone through all the notes I can find on settings this up, but whatever I do, it does not work!

I have setup the Flag, put it into the correct Map, set it as a Loopback Flag. Set all the values of the data i want to pass, giving names that relate to the Fields. Set the value in the 'Do This' Function. But nothing happens.

Oh and created a batch file to send the data - per the instructions - before I put it into my application.

Help please

[BMellert]

Without knowing more, here are a few things to star with:

• Are you getting an error, trying to execute eRaiseFlag.exe perhaps, or is it just the action is not running?
• Might this be a new flag added to an existing folder?  To check, is there an appropriate flag in eWait for the folder(s) in question?
• Is the "Folder which must raise the flag..." setting on the Flag action Flag tab set correctly?  (e.g. its not set to "This folder's parent" when you are trying to raise for "This folder")

[Mark Beverley]

Also might be worth checking to see what users are associated with the flag raiser role in the  metastorm process engine in component services.

[Rosemary Fromm]

OK basic info

this is in 7.5

I am getting no error message when I execute the Batch file - I was but have managed to stop it by changing my rights on the server.

I have added a new flag into an existing map - as I want to add in new folders that way (should have mentioned that earlier).

the questions raised about existing folder therefore do not apply I suspect....

My plan is to eraise a flag externally, with data attached from outside of Metastorm, the Map's Flag was then to pick up the Flag, pull in the data, create a new folder and pass it on to the next stage. I have setup the Flag to pull in the data - but could not see anywhere to Create a new folder.

Maybe I need to tell the Flag that it has to create a new Folder in some way ??

[Rosemary Fromm]

I have set myself as a member of the flag raiser role, then when that did not work I added in my entire department to the Windows User Group in the flag raiser role on the server. Then restarted the Engine. That was one of the suggestions I found on the Metastorm Forum somewhere when I did a search on raising the flag externally.

I also found something about the data being passed using tabs in between the data in the command line, that stated the Registry needed checking, but when I checked it was not set to 0.

[Mark Beverley]

I'd suggest

1 coment out all the variable settings in the when action started of the flag.

i.e. remove all the %variable1:=%flagdata[1]

then publish and try to raise the flag using the command line.

i.e.  eraiseflag /flagname:"[flagname]" /flagfolder:"[Folderid]"

obviously only have the flag folder argument if you have a folder already and you are trying to raise that instance of a flag only. if you are creating a folder or want all flags to fire then dont have the flagfolder argument.

get that working first and they you can look at passing data.

[Rosemary Fromm]

I can see that might be a good idea, as it is simpler - but I cannot see how I would know it had worked - no data will appear in the table, so how would I know ??

RR

[Mark Beverley]

if you check the eevent table that should tell you if the flagged action has fired.

[Rosemary Fromm]

Aah, I had forgotten about E-Event - too long since I did any reporting on this system.

No nothing in there, so it is not getting that far then.....

I have tried removing the Data from the Batch file I wrote, better go and check my syntax again I suppose...

RR

[BMellert]

Must making sure I understand ... this new flag is coming off the starting clapboard, correct?  (That's what I'm guessing by your intent to create new folders, but making sure.)  I've used this approach without issue.

If its off the start clapboard, there should be an entry for the flag name in eWait with an empty eFolderID.  As mentioned above, I've used this many times without issue -- mostly for data conversion but also to start new child folders.

If its off another stage, check the eWait table for the folder(s) in question to make sure the flag is defined there for the folder(s).  If there is no entry in eWait, raising the flag will never do anything against a target folder.