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 function which adds the attachments inside the prepare data process I'm not getting any error. Still, they are not visible in the workspace. However, if the initiator manually adds an attachment himself, t...

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 a web service requiring a user id as the input parameter.I seem to be able to populate a list (by calling an LC component returning an ArrayList of objects, even not knowing if this is the correct app...

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 the respective windows etc.It seems like whenever this variable is not empty, the issue occurs. I cannot confirm this 100%, but at least this seems to make some sense.Steffen.

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 app uses to store values in (user abc has just submitted data, dear server - deal with it ). The data is then used to fill all the structures and values that you can use in your server side submit serv...

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 process fields (there's a script that populates the list in the form). For every item, the Workspace app generates a button for the user to click on.Regarding AWS_ASSIGNED_ID, I think this contains the ...