Best Of
Re: E-Mail-Folder SMARTVIEW: How to show attachments?
If alternatively, it is sufficient to just have a column indicating the number of attachments (if present) you can use the Module Suite to add a column by configuring it in the content script Volume (CSColumns).
Re: E-Mail-Folder SMARTVIEW: How to show attachments?
Do you have the Module Suite?
With it, I've implemented a custom action that shows a sidebar with the email preview and the list of attachments. It's simple, quick to do, and moreover, you can reuse it for any project by attaching the action to the email subtype.
This way, you can have the preview in the smart UI without having to download it (which the Smart view forces you to do if you click on the email object).
Additionally, you have all the information in the same view without having to load new pages.
See here:
Re: How to hide unused functions in xECM menu and enable Reminders
FYI, All content Server /xECM instances now include ActiveView for free. The method to achieve these changes hasn't changed in in years so you should easily be able to make these changes without any OScript customization.
Here are a couple of blogs on ActiveView. (The second one builds an example)
Re: How do I create folder templates in 22.3? Business Workspaces vs Folder Templates, when to use
I have no experience with folder templates that contain binders/cases/workspaces. I'd first set up a trial for that (with business workspaces) on a test environment.
I can think of one reason to keep the older binder in the folder template after it has been converted to the new type: you may want to keep it if you have specific roles/permissions that you wish to maintain on that level for all subworkspaces (like 'tax returns members').
After conversion, in the existing folders the old binder will remain a workspace, but it will have changed to subtype 848.
As a side note I'd like to advise you to test the conversion of your binders/cases well.
We're also still converting and the main problem is that some binders/cases refuse to be converted while for most it is no problem at all.
We have encountered two specific issues, both of which could be fixed with database updates provided by our implementation partner:
- items in the recycle bin that were deleted before the conversion, cannot be restored
- shortcuts that refer to items within the converted workspaces, stop functioning
Re: How do I create folder templates in 22.3? Business Workspaces vs Folder Templates, when to use
Hi Angela,
I don't see why Tax Returns needs to be a BW. It's not as if you are going to create more Tax Returns folders. The individual years, e.g. Tax Year 2023 can be a BW.
I do however understand that there can be a requirement where a BW needs to be in a BW.
For e.g, we had a client that made a Project BW with a host of folders as a structure, and inside , one of the sub folders needed to be Meetings that had its own structure (Agenda/suppl docs, comms etc) They wanted this to be a BW to make each Meeting conform to the structure.
Re: How can we make a form in appworks responsive as like the layouts. Also other elements in form.
If you use sections inside forms then those sections become responsive in terms of the section will collapse if the controls inside it are hidden for example.
Re: How do I create folder templates in 22.3? Business Workspaces vs Folder Templates, when to use
The simplest implementation is "Connected Workspaces" If you look at its setup documentation you will see that you need
- Classification a.k.a Document Type (real-life examples Invoice,PO, Patient Record). You cannot do a Workspace without that.
- Categories a.k.a User Defined Metadata. It is important in the context of finding things. Think of it as "tagged Information".You can also use this to create objects based on their names (real-life examples Folder for user John Doe (SSN:1234 ). So in a manual use case, you would force the user entering this to part with that information and when CS creates it it refers back to the naming rules and creates this container.
- A place where it can be created like a Folder . This is what you are doing when you create a Workspace Types Object. the Workspace object you make will tie to a category so you can make Dynamic names. This is the Object that you can configure to make "hierarchical" objects as well
- Visual representation of this Object. You interview your business/functional user and you ask them what ll should they see. Typical examples (Photos, Patient Lab Results).Just a collection of high-level folders that people like. This is what you do in the area of Content Server Document Templates
- This is the minimum for "Connected".If you have a leading application like (Maximo, SAP, etc) that can provide the information a manual user is doing then this suddenly becomes an "Extended ECM Implementation"
Extended ECM is a product that OT has continuously revised based on industry best practices/requirements for 20 years. During this process, they have introduced many things that would qualify a product to be compliant. You might need to read up on those specifics
In this
I would concentrate on the Concepts Chapter and leave everything if you are not a CS or leading app developer/technical resource
There may be a better PDF that explains "Connected Workspaces".AFAIK OT has created some utilities that help move things in older code into new code at the end your TW objects have unique representations of DataIDs which can be moved into new "Connected Workspace" implementations using simple tools like WR, OI, and so on.
Re: Error at File.Open() - Could not open file
Run your builder(CSIDE) as Run As Administrator command and try…