Modify eFolderID Sequence

Hi,

 

We are migrating from an old 7.6 process to a newer 9 process and I would like to know if there is a way to change the eFolderID sequence so that it begins at a number that is proceeding the existing number used in the 7.6 process?

 

To give a bit of background, part of the FolderID is used in a seperate system and we have recently been running into an issue where the number has been previously used in the 7.6 process and the old entry is being returned from the seperate system and not the newer entry.

 

At present the v9 process is at eFolderID 2200, where the 7.6 process (which is still in production and awaiting the final testing of this new v9 replacement) is using ID 23,000.

 

Could I insert a new record into the eFolderID table with the number before the one that I want to start from?  Will this work and will there be any side effects from doing something like this?

 

Thanks,

 

 

Matt

Tagged:

Comments

  • Hi Trevor,

     

    That's fine.  We have used this technique on many occassions.  The sequence gives the last folderID used by the engine. When we migrate systems we often set the next folderID to a new value to give a clear indication of which environment the folder was created on.

     

     Bear in mind though that folderID prefixes have been re-introduced in v9 so if you are testing for paricular ranges of folderID you will need to bear this in mind.

     

    Hope this helps.

  • Thanks Paul, this worked a treat and was the cause of the problem :)

     

    Matt

  • Hi Paul,

     

    Is there any way where we can set the Folder name depending upon the process variable values, without modifying the folderID as genereated by Metastorm?

     

    Desired Folder name example : "Testprocess_TA1"  instead of Testprocess0001 (as created by Metastorm by default)

    Where Testprocess is the prefix for the process.

    and "TA1" is the value from the process variables defined while creating the case.

     

     

    Thanks

    Sundeep

  • You can create any folder name you desire.  The default may be Testprocess0001, but you can change ProcessContext.FolderName to anything you wish via an assignment action.

     

    We do something similar with sub-folders so that its number is related to its parent ... e.g. Parent folder name is NM012345 and we rename the child folder to NM012345R or NM012345B in child folders so users can easily see what the child relates to.

  • Hi BMellert,

     

    Thanks for your input. It worked. :)