<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>File Upload on RIA Docs</title>
    <link>https://docs.riaproducts.com/dih/3.0.0/docs/executable-classes-for-task-execution/fileuploadworkentryexecutor/</link>
    <description>Recent content in File Upload on RIA Docs</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://docs.riaproducts.com/dih/3.0.0/docs/executable-classes-for-task-execution/fileuploadworkentryexecutor/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Upload Groovy Integration</title>
      <link>https://docs.riaproducts.com/dih/3.0.0/docs/executable-classes-for-task-execution/fileuploadworkentryexecutor/upload-groovy-integration/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.riaproducts.com/dih/3.0.0/docs/executable-classes-for-task-execution/fileuploadworkentryexecutor/upload-groovy-integration/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#overview&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;When dealing with complex file uploads, you can use a Groovy class or code snippets. Groovy runs within the JVM and is controlled by the DIH framework, so it can access the same classes, objects, and environmental components as DIH. This allows you to manipulate the file upload data while it is being uploaded, reducing the need for temporary or staging areas.&lt;/p&gt;&#xA;&lt;p&gt;There is no parameter for Groovy. It should be coded in any of the following:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
