In Metastorm e-Work 6.6.x

When adding a timed action to an existing map which have folders on that stage, the folders do not get assigned that Timed Action and no entry is made in eWait.

Solution :

I’ve written the attached Store Procedure which runs through all the folders on the selected stage and adds the action where needed to eWait. You can also define what the deadline should be set to.

Variables that needs to be provided:

• @map varchar(100), - the map name
• @stage varchar(100), - stage to which the action was added
• @timedActionName varchar(100) - the name of the timed action that was added

Then the following line should be edited in the Stored procedure to set what the deadline should be. Set the correct map table and field(will maybe update the SP to dynamically to this later):

• SELECT ef.eFolderID,mr.dteDeadline FROM EFOLDER ef,MapTable mr WHERE mr.efolderid=ef.efolderid AND eMapName=@map AND eStageName=@stage

Hope this post will help someone out abit.

Check Stage Timed Actions

written by Arné

Yesterday, I was onsite at a client where they had some database problems, and had to revert back to one of their backups. For some strange reason they merged two backups(as I can derive from them) together. This caused havoc on the ework database though. I don’t know what the DBA did but for some strange reason you could open up To-Do list items, but not Blank Form items. NO error was logged to the Event Log or could be found in the Services Manager.

First I tried a few test and then it struck me - the FolderID’s was out of sync, as the guy who “merged” the database did not take this into consideration. I tested, and saw it was only the FOLDERID table which’ next ID was too low, and lower as the actual latest entry in the EFOLDER table.

To fix the problem, I just set the next ID(Identity Seed) in SQL Server management Studio for the table FOLDERID to be higher than the last folderid in the EFOLDER table.

This seem to have fixed the problem, though we are still testing to make sure that they did not break any other tables or e-Work core functionality in the data structure.

written by Arné