Hi Vetrikam, have you been able to solve this in the meantime? I'm currently running into the same issue and haven't got any idea how to solve this ... KR Steffen.

Yes Nith, you are correct - we want the initiator to see the attachments, and because of that, this would probably need to be done either in the prepare data or the render process. Since it's a Flex based form, PDF attachments are not an alternative, either.If I try to invoke a component based funct...

Hello everybody,I'm having a problem with an advanced workflow application and I guess I'm stuck What I want to achieve is to have a set of initial task attachments that get automatically attached to an initial task. This means that I want to have one or two documents attached to the endpoint task w...

Hi everybody,we're having a problem with a customer scenario that we can't seem to sort out: We are implementing a complex user-centric workflow (products: Forms, Reader Extensions, Output, Process Management). For reporting purposes, the customer needs a flat PDF copy of every PDF form that any use...

Hi Steve,1st of all, thank you for your reply.In my scenario, I'd like to populate a grid with user names, id's and some additional information. When a user clicks on an entry (or row), I'd like to use data from the respective record (let's say the user's id) for subsequent operations, like calling ...

Hello all,I'd like to ask a question about form guides: What I would like to do is to populate a collection of items on the server side and to display those items in a grid control (or similar) in a form guide. After displaying, the user should be able to select one of the items by clicking on the r...

It's LCES v8.2 with no additional fixes.

Yes I do, but I have an "educated guess" what might be causing this.The LC server is running on Solaris. From time to time, there's the need to run some program which is using a GUI (like configManager for example). To be able to do this, the DISPLAY env variable needs to be set if one wants to see ...

Since you mentioned AWS_ACTION etc. in your post I thought I should provide some info ... but maybe that was a misunderstanding.For the other two, I can only suspect that those are not at all relevant for the *form* itself. I guess they are just meant to be containers for values that the Workspace a...

Hi Nith,as far as AWS_ACTION is concerned - I think this is a dropdown list which contains a list of all the options the respective user should have when it comes to submitting the form. The list is populated at runtime from a comma-separated list which is stored on the server in one of the other pr...