D2 - Importing docs

jose.machado.pereira

Hi,

I've one simple doubt about configuration in D2.

I've a Auto Naming functionality configurated in D2-Config.

When I use D2 to import a doc, object name is changed to the pattern configured.

But what happens if I import a doc with, for example, Captiva?? Is object name changed? Or I need to do 'the old way', use a TBO??

Thanks,

Find more posts tagged with

Comments

Lakshminarayanan

Hello -

You do not have to write a TBO.

Even for documents from IA, D2 Applies naming according to the config whn rteated by D2Coremethod.

ideally you would export (from IA) the scanned docuemnts into a specific folder/cabinet. Then you would schedule a job which treats these documents with D2CoreMethod so that all D2 Configurations (Autonaming, AutoLinking, Permissions) are applied on these documents.

Best Regards and Good Luck

YacineYounes

Hello,

In addition to the solution of this is a DQL example to execute D2CoreMethod :

EXECUTE do_method WITH method = 'D2CoreMethod', arguments = '-docbase_name "@DocBaseName" -dql_filter "select r_object_id from dm_sysobject (all) where @Condition;" -naming "true" -autolink "false" -security "false"';

you are free to change autolink and security flags,

Best regards

Julien.Fontaine

Another way is also to ask IA to execute the D2CoreMethod directly via embedded script.

jose.machado.pereira

I understant what you said...I tried it...and it works. Nice.

But if I want to also start a WFor attach a lifecycle?

In D2-config, I created a Creation Matrix with Lifecycle and Workflow configuration. Then I went to DA and configured the D2JobCore to read from an Cabinet and with all flags=true.

If I create a doc with DFC, the Auto Naming and Auto Link works, but the Lifecycle isn´t attached and the WF is not started....

The only away that all things work is if I attach the lifecycle and start WF by code (just like a TBO's).

Julien.Fontaine

Hello,

You have an other alternative with 100 % configuration :

- Add another autonamming to update the a_status of your document to a defined value ('Wait') for example.

- Define a docset in your configuration matrix to catch all 'Wait' document

- Add your lifecycle to this docset

- Add a lifecycle batch in order to promote Wait document to the first step of your lifecycle

- Throw the workflow in your lifecycle !

Good luck !

Julien.Fontaine

Does it works ?

jose.machado.pereira

I already had thought in something like that but I still not tried