nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Limit File size

rwinterpacht

We have been running into an issue with some of our users who try to import and eventually deploy many large files at once.

I'm trying to find a good solution to limit how big a file can be that a user imports into the filesystem. This would sorta kill the problem at the source. Some folks have pdf files > 5mb, then push out a bunch of them.

Then, while the workflow is pushing the attached files out to a region, it takes a while and other deployments called from the same workflow in the same branch are reported as failed, since the big deployment is hogging network bandwidth. I thought about putting in an externaltask that will query the files to be pushed out, and send a note to the requestor to reduce the number of files, but that just doesn't seem all that elegant.

Anyone else have any ideas?

Raf Winterpacht
Household Intl/HSBC
TS 5.5.2 sp3

Find more posts tagged with

Comments

nipper

>I'm trying to find a good solution to limit how big a file can be that a user imports into the filesystem. This would sorta kill
>the problem at the source. Some folks have pdf files > 5mb, then push out a bunch of them.

You can put a trigger on the creation of an object that looks to see the sze (via stat) and sets an EA of flag=TOO_BIG on the portly ones. Then in the WF error out if any of the files have that EA set.

>Then, while the workflow is pushing the attached files out to a region, it takes a while and other deployments called
>from the same workflow in the same branch are reported as failed, since the big deployment is hogging network
>bandwidth.

Do you have OD configured to run multiple instances at once ? Does not help bandwidth, but prevents OD from crashing is multiple deployments go at the same time.

iwodstart -inst OD_$$ (roughly on Unix)

HTH

Andy

chart_latest.JPG

rwinterpacht

Great suggestions...thanks for the help!

Raf Winterpacht
Household Intl/HSBC
TS 5.5.2 sp3

whysguy

Raf,

I have run into this problem as well and we handled it via an external task immediately before deployment - it may not be an elegant solution, but it worked for us. Essentially we would check to see if the combined file size, of all files attached to the job, totaled more than 30 Mb (a fairly arbitrary number). If it did, we would send a task back to the user notifying them to reduce the number of files in the job. At first the task was one of the initial tasks in the workflow, but there were other tasks in the job that gave users the ability to add files, so we decided to do it immediately before deployment.

I hope it helps.

- Billy