03-31-2021 08:54 AM
Hello, OSEG members!
Your Board of Directors has been hard at work in the past month to work on putting together content and exploring subjects with our Hyland representatives that are relevant to our group. A subject which came up in our recent meetings with Hyland leadership was documentation. We're about to dive in to some deeper conversations about what the community would like to see (in terms of improvement) and I'd love the opportunity to pass on stories from our membership to help drive those improvements.
OnBase Documentation - Two Levels
When I think about documentation, I see two different, distinct types of documentation which can be important to us as OnBase administrators, developers, and users:
I think there is opportunity for discussion on both of these topics, and I'd be really interested in seeing what our members have to offer!
Do you have any success stories or areas where you see opportunity for improvement with Official Documentation from Hyland? What practices (if any) do you employ in your own organization to help document and track processes, procedures, and comments on your applications?
Join the conversation and post your responses below! We look forward to hearing from you.
05-21-2021 04:21 AM
I agree with
I appreciate that this discussion is being had internally.
06-01-2021 10:22 AM
We use configuration templates in our Confluence Wiki to document details of our projects such as new Document Types, WorkView applications, Unity Forms, etc. We use the Wiki to document configurations and processes specific to our environment as well. The Wiki is great for collecting the details and comparing changes between versions of the page to note modifications over time. It is also completely searchable. We have only have documented items created or modified by my team over the past 10 years, so plenty has not been documented yet. The Wiki is also handy for creating focused instructions for end users.
06-01-2021 02:59 PM
We use Jira for internal service requests. For this reason our user facing documentation is created in Confluence. This allows it to be surfaced in Jira Service Desk. Most of our internal documentation is done with Google Docs. Mostly for the superior editor and ease of sharing.
The most often used Google Docs are the 50+ page installation/upgrade checklist and 70+ page refresh checklist. We also generate dev notes for major solutions. I've found we frequently receive requests for similar solutions and the dev notes serve as a wonderful checklist, making it easier to not overlook complicated configuration requirements.
06-04-2021 09:08 AM
06-08-2021 09:45 AM
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.