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

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

RM for Explorer

mlarkinmn

Are there any plans for the RM features to be exposed via the Explorer view. Share still seems to not include alot of the advanced features available in Explorer and in many cases is not sufficient for alot of our work which would be records.

Find more posts tagged with

Comments

mrogers

Nope. The plan is to add the missing features to Share.

mikeh

Are there any plans for the RM features to be exposed via the Explorer view. Share still seems to not include alot of the advanced features available in Explorer and in many cases is not sufficient for alot of our work which would be records.

Which specific features are you missing?

Note that we're working on: Advanced Search, Rules, improved Workflow support, amongst others.

Thanks,
Mike

mlarkinmn

We use CIFS integration a great deal and need advanced workflow capabilities. We also have significant use of custom content models.

mlarkinmn

We also make use of the import feature as we often upload zipped collections of materials where we need to maintain the file and folder hierarchy. Only other way to do this would be with CIFS. I see no way to do this with Share.

mikeh

Thanks for the feedback. Taking each point…

1 - CIFS. Yes, we've been talking about this. It should just be a matter of getting some config down to Share and presenting a link - low impact.
2 - Advanced workflow. Coming once the new Workflow API is in-place.
3 - Custom content models. Already available in 3.2 via the new Forms Service.
4 - Import zip. Again, we've been talking about this, as it's fairly low-hanging fruit.

I don't see why most, if not all, of those features shouldn't be in v3.3.

Thanks,
Mike

carlos_miguens

Relating to this:

We also make use of the import feature as we often upload zipped collections of materials where we need to maintain the file and folder hierarchy. Only other way to do this would be with CIFS. I see no way to do this with Share.

Irrespective of Share or Explorer, you would be prevented from doing this in any records management system, as you cannot create arbritrary hierarchies of folders and records. If you need to preserve such a structure it should be imported as a zip file. Note however this is different to importing a complete or part of a fileplan, which the current RM system does by allowing import of an ACP file.

and relating to this

We also have significant use of custom content models.

In the RM module you can define "user defined" metadata on records which is then exposed through the forms interface, the control is not as extensive as in Explorer, but it is there.

Carlos

mlarkinmn

I understand that you can't create folders and hiearchies at will in a records space whoever, we will need to make a record of courses within a training department. A course and it's source materials can be made up of hundreds of files in a space with subspaces. The space (or course) needs to be a single record. I can manage this in Explorer not in Share. Can a space be moved to a record space and be a single record in RM?

carlos_miguens

That actually sounds like a nifty feature to have. We don't have a way of doing that right now, the best way would be for a combined zip -> file operation into the RM system. You can of course do it manually which will work if you only have a small number fo courses but not if you have many.

Carlos

mlarkinmn

Thanks for the feedback. Taking each point…

1 - CIFS. Yes, we've been talking about this. It should just be a matter of getting some config down to Share and presenting a link - low impact.
2 - Advanced workflow. Coming once the new Workflow API is in-place.
3 - Custom content models. Already available in 3.2 via the new Forms Service.
4 - Import zip. Again, we've been talking about this, as it's fairly low-hanging fruit.

I don't see why most, if not all, of those features shouldn't be in v3.3.

Thanks,
Mike

Any timetable for when this may be available in Community or Enterprise??
Thanks!

mikeh

V3.3 is still in planning, so no dates yet.

Mike