Question

Attributes and scanning to a volume

Updated August 21, 2018

asked on August 16, 2018

Hi there :) We migrated 6 TB and have rollovers and everything appears to be working correctly EXCEPT for one thing :(

I migrated Human Resources volume to HRVOL and locked down the old volume. We learned we had a few processes that needed to be modified and there were so many users that needed to change their volume they were scanning to (live and learn). So we unlocked the Human Resources old volume and I have been modifying their volumes through their profiles and sent out instructions to many. It's been several weeks and I have been doing a search on the old Human Resources volume to see who is still using it and changing them one by one. Been seamless EXCEPT I have 3 users that even though I have modified their attributes documents of theirs are still showing up in Human Resources volume.

These are the attributes I modify:

-- <Properties>
   <Attribute>
       <Name>[BasicScanning-ACMOORE]ScanVolume</Name>
       <Data>286</Data>
   </Attribute>
</Properties>

--<Properties>
   <Attribute>
       <Name>[SETTINGS]ImportVolume</Name>
       <Data>286</Data>
   </Attribute>
</Properties>

--<Properties>
   <Attribute>
       <Name>[Scanning-TEKIMBLE]ScanVolume</Name>
       <Data>286</Data>
   </Attribute>
</Properties>

Are there other attributes or setting that I dictate volume? It's not too bad but want to lock the volume down next week.

Thanks and have a lovely morning/day/night

0 0

Answer

SELECTED ANSWER

replied on August 20, 2018

Gotchya!

>>>You can either change the Client settings or set a new volume in Scanning.<<< Do this in the Admin Console correct? Not the end user's client...

0 0

Replies

replied on August 16, 2018

Hi Sue,

One thing to check would be default volumes on folders - is it possible any folders are still pointing to the old volume? If so documents set to use default will get placed in that volume.

0 0

replied on August 17, 2018

Check out the "ScanVolumeSetting" attribute as well for both Scanning and BasicScanning. They're controlled by the "Scanned document" UI settings and they might either be set directly to the old volume or to the "last volume scanned into" which might cause the behavior you're seeing.

0 0

replied on August 20, 2018

Thank you both for your responses :)

Justin: I have checked and double checked this. Also checked workflows to make sure they are not defining a volume and no volumes are being defined in any workflow.

Miruna: I just checked the folks that are the culprits :) and the Data is "ClientImport" for both the BasicScanning and Scanning. What does that mean? That the client has defined which volume to use? If so, OK for me to delete? Or can I hard code the new volume there?

0 0

View 1 previous reply

replied on August 20, 2018

It means Scanning will use the volume defined in the Client under Tools\Options\New Documents\Import Profile. You can either change the Client settings or set a new volume in Scanning.

If you just delete it, Scanning will recreate it next time its own with its default of ...Client Import.

0 0

SELECTED ANSWER

replied on August 20, 2018

Gotchya!

>>>You can either change the Client settings or set a new volume in Scanning.<<< Do this in the Admin Console correct? Not the end user's client...

0 0

replied on August 20, 2018

Either way. The attribute for the import volume is

<Properties>
	<Attribute>
		<Name>[SETTINGS]ImportVolume</Name>
		<Data>VOLUME ID GOES HERE</Data>
	</Attribute>
</Properties>

If you want to keep Scanning in sync with the import settings, I'd change the ImportVolume attribute and leave ScanVolumeSetting be. If not, you can set the scanning attribute to the new volume.

0 0

replied on August 20, 2018

ImportVolume or ClientImport??

0 0

replied on August 21, 2018

All good. Thanks you!!!

0 0

You are not allowed to follow up in this post.

Question

Question

Attributes and scanning to a volume

Answer

Replies

Sign in to reply to this post.