That information is not recorded anywhere.

If this is a File Utility issue, then you logged it in the wrong area and it won't likely get read by the people that could help. Instead of Workspace, try API or Foundation.If it is somehow related to Workspace, the please provide more context. Thanks.

I don't think you can just set properties in the xml data that will be directly applied to a button in the form, or add the button in the xml data. I think you will have to put the UI controlling info in the xml data which will be merged into the PDF in your render step, and have some code in the form load event that uses the UI info to manage your buttons. The buttons should likely all be configured invisible in the form so you don't get screen flashing on startup. Maybe others with more Form s...

there was a bug for a similar type of problem when the form (not an attachment) was loaded from a document variable that came from disk and contained backslashes in the filename attribute of the doc. the url generated for this document was invalid causing a 404. Contact support and get the Process Management patch for your version.

I'm unaware of any way to get the code other than applying the SP (1 or 2) and then applying the latest Process Management QuickFix for the SP you choose. My opinion is that keeping as current as safely possible is best if you want to benefit from all fixes so I would go with SP2. SP2 has been out for quite a while so I consider it a safe choice. The SP2 workbench introduced some new features but fully supports any existing applications so this shouldn't be a problem. Whatever you choose, testin...

I'm pretty sure there is a way to find the process to db tablename mapping but I don't recall what it is. Maybe someone else reading this can chime in. FI don't usually have that many processes defined so I just get the table schema for each one at a time until I see the columns that match and then use a processinstanceid from the table to confirm it is the correct process by looking it up in the tb_processinstance table. Not elegant but it works for a small number of tables. Also, I have a corr...

i'm not ready to give up on those process variable strings yet. what are the max lengths and were they ever changed. also check the database table for that process (name will be tb_pt_) and see how the columns are defined - do they match your defs.

Just double checking, the stack says the error is occurring with a different process than you mentioned in the bug.==> An error occurred while retrieving the list of process instances for process "dbCreditCounter/Processes/CC01_CreditWorkflow".Are you looking at the right process?Also, which version of Oracle are you using ( I found some hits says oracle 11g throws this in some cases where 10g didn't).Jon