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; } } }

Taskspace importer maturity???

Fred_Fortin

Hi everyone,

Did anyone had any success story with TaskSpaces importers?

I'm only a couple of hours in my experimentation and I can see major flaws in flexibility, documentation and stability.

First it seems that the viewer is mandatory and can't be removed unless you do some WDK.

Second the layout is also fixed, the Document view eForm is displayed as a column on the left side. The width is very small so there's no real benefit into making this a configurable component through eForms... I personally think that the document view layout should be consistent across consulting/creating and importing. Because of the fixed layout of importers, this is not possible.

I'm also having issues with the browser security trying to view documents on the local drive before they are imported...

Am I missing something here or is everyone struggling with importers?

Thanks in advance for sharing your experiences!

Fred

Find more posts tagged with

Comments

Imran_Yusubov

Hi,

For my case, no.I can't even use the standard import functionality due to multiple UCF errors.

Andrei_Paraschiv

UCF problems and security issues can be easily solved by reading Taskspace installation guide and Powerlink sollutions (UAC on windows 7, trused sites, activex enabled, pop-up disabled, java version, group policy and so on).

Imran_Yusubov

Hi Andrei,

Can you please provide a link to Powerlink solutions you have mentioned.

I have read Taskspace installation guide for 55 times every time I get an error.But no luck.

Ela

Hello Andrei,

Can you please provide a link to Powerlink solutions you have mentioned.