I created a new flow and updated an exisiting one and they both disappeared! They are not in the app folder "ctg_crm_load".

09/23/2008 18:51:04  EDASERVE   (ICM18164) Request ctg_crm_load/flow02 was created/updated successfully for User: SYSTEM.
09/23/2008 18:51:04  EDASERVE   (ICM18164) Request ctg_crm_load/flow02 was created/updated successfully for
09/23/2008 18:51:04  EDASERVE   User: SYSTEM.
09/23/2008 18:52:15  EDASERVE   (ICM18164) Request ctg_crm_load/flow02 was created/updated successfully for User: SYSTEM.
09/23/2008 18:52:16  EDASERVE   (ICM18164) Request ctg_crm_load/flow02 was created/updated successfully for
09/23/2008 18:52:16  EDASERVE   User: SYSTEM.
09/23/2008 18:52:28  EDASERVE   (ICM18164) Request ctg_crm_load/flow02 was created/updated successfully for User: SYSTEM.
09/23/2008 18:52:28  EDASERVE   (ICM18164) Request ctg_crm_load/flow02 was created/updated successfully for
09/23/2008 18:52:28  EDASERVE   User: SYSTEM.
09/23/2008 18:56:10  EDASERVE   (ICM18164) Request ctg_crm_load/bmoorg1 was created/updated successfully for User: SYSTEM.
09/23/2008 18:56:10  EDASERVE   (ICM18164) Request ctg_crm_load/bmoorg1 was created/updated successfully for
09/23/2008 18:56:10  EDASERVE   User: SYSTEM.
09/23/2008 18:57:32  EDASERVE   (ICM18164) Request ctg_crm_load/bmoorg1 was created/updated successfully for User: SYSTEM.
09/23/2008 18:57:32  EDASERVE   (ICM18164) Request ctg_crm_load/bmoorg1 was created/updated successfully for
09/23/2008 18:57:32  EDASERVE   User: SYSTEM.
09/23/2008 18:58:01  EDASERVE   (ICM18164) Request ctg_crm_load/bmoorg1 - BMO Organization Table Update was created/updated successfully for User: SYSTEM.
09/23/2008 18:58:02  EDASERVE   (ICM18164) Request ctg_crm_load/bmoorg1 - BMO Organization Table Update was
09/23/2008 18:58:02  EDASERVE   created/updated successfully for User: SYSTEM.
09/23/2008 18:58:21  EDASERVE   (ICM18164) Request ctg_crm_load/actsumru1 BMO Activity Rollup for mWholesaler was created/updated successfully for User: SYSTEM.
09/23/2008 18:58:21  EDASERVE   (ICM18164) Request ctg_crm_load/actsumru1 BMO Activity Rollup for mWholesaler
09/23/2008 18:58:21  EDASERVE   was created/updated successfully for User: SYSTEM.

When you say they are not in the apps folder called ctg_crm_load, do you mean you cannot see them via the DM Console or did you also look via Windows Explorer (or your OS equivalent)? If you cannot see them either way, I would definitely open a case with IBI. If you can see them via the OS, then it sounds like something may have happened to the profile associated with the login you use. If there is no profile associated with the login you're using, it would default to the EDASPROF. Check to see if the .PRF hasn't been corrupted somehow.

The flows are nowhere to be seen - they're not in the DM client screen and they're not in the app folders on the server.

I don't think it's worth it for me to open a case because I'm running v5.3.4 and that's running out of gas...

It looks like you have spaces in the flow names, that may be the cause of the problem. In current releases that's prevented when you try to save the flow.

I did not have spaces in the flow names when I created the flows: flow2, bmoorg1, bmoorg2. WHen I select the name in the Data Management Console to add a description after the flow name, "bmoorg1 - BMO Organization Table Update" the log says "Request ctg_crm_load/bmoorg1 - BMO Organization Table Update was created/updated successfully for User: SYSTEM" but the flow disappears. How does one add a description to a flow if not by selecting the name and changing it?

Francis, let me see if I got this straight. You created a flow called 'bmoorg1', then you renamed it to 'bmoorg1 - BMO Organization Table Update'? Is that right or is there some way in version 5.3 that allows you to add descriptions? If you didn't rename your flow, you can stop reading here. I'm sorry to say I've never put descriptions on my flows and don't have a copy of 5.3 to look back on at the moment. I tried in 7.1 to rename one of my flows similar to what you did. It gave me an error and would not let me rename it. I can tell you that what we've always done is just had descriptive names, which can sometimes be long. Like in your case, we'd have named it BMO_Organization_Table_Update1, or something like that. As far as length of name, I looked through all my 7.1 stuff and I have one flow where the name is 32 characters long and a stored procedure where the name is 37 characters long. Version 5.3 could be different but I don't recall having issues with name lengths in 5.3.

A flow name cannot contains spaces, and you can't add a description by renaming a flow. To add or change a description, open the flow, click on the first toolbar button, flow properties, and enter a new description. Then resave the flow.