Sage 100

There is a Sage KB article on recommended AV exclusions that I tend to attach with "go Live" emails.

Paperless Office fixes, by version.

Version conflicts (like when the CR print engine is updated, breaking printing from older versions... and when the Amyuni driver is updated, breaking Paperless in older versions...).

@Kevin Moyes (or any other members) would you be able to lend a hand on this? We have these in Google Docs and could use as many creators/editors to build up our knowledge as possible. 

My concern is that as members leave the business and Sage personnel leave that suddenly we are left with gaps in knowledge. 

I'd like to see the group start documenting as much as possible  - here's an example of what's been started. A lot of the work is just scraping relevant items from Higher Logic and documenting it in a Google Doc.

There is a Sage KB article on recommended AV exclusions that I tend to attach with "go Live" emails.

Paperless Office fixes, by version.

Version conflicts (like when the CR print engine is updated, breaking printing from older versions... and when the Amyuni driver is updated, breaking Paperless in older versions...).

Hi Wayne,

Going back two decades, I started saving KBAs from the Sage website. I have over 1,000 documents that I am happy to share. However, the value is likely in the organization of the documents, yes? I don't have a lot of time, but I have a little bit of time each month to contribute. Let me know how I can help.

Karen

@Kevin Moyes (or any other members) would you be able to lend a hand on this? We have these in Google Docs and could use as many creators/editors to build up our knowledge as possible. 

My concern is that as members leave the business and Sage personnel leave that suddenly we are left with gaps in knowledge. 

I'd like to see the group start documenting as much as possible  - here's an example of what's been started. A lot of the work is just scraping relevant items from Higher Logic and documenting it in a Google Doc.

There is a Sage KB article on recommended AV exclusions that I tend to attach with "go Live" emails.

Paperless Office fixes, by version.

Version conflicts (like when the CR print engine is updated, breaking printing from older versions... and when the Amyuni driver is updated, breaking Paperless in older versions...).

Karen,

Are these PDF files? Google Workspace is pretty good at searching content inside PDF so there may not be much work aside from uploading them into a Google Drive folder. 

Hi Wayne,

Going back two decades, I started saving KBAs from the Sage website. I have over 1,000 documents that I am happy to share. However, the value is likely in the organization of the documents, yes? I don't have a lot of time, but I have a little bit of time each month to contribute. Let me know how I can help.

Karen

@Kevin Moyes (or any other members) would you be able to lend a hand on this? We have these in Google Docs and could use as many creators/editors to build up our knowledge as possible. 

My concern is that as members leave the business and Sage personnel leave that suddenly we are left with gaps in knowledge. 

I'd like to see the group start documenting as much as possible  - here's an example of what's been started. A lot of the work is just scraping relevant items from Higher Logic and documenting it in a Google Doc.

There is a Sage KB article on recommended AV exclusions that I tend to attach with "go Live" emails.

Paperless Office fixes, by version.

Version conflicts (like when the CR print engine is updated, breaking printing from older versions... and when the Amyuni driver is updated, breaking Paperless in older versions...).

Karen,

Are these PDF files? Google Workspace is pretty good at searching content inside PDF so there may not be much work aside from uploading them into a Google Drive folder. 

Hi Wayne,

Going back two decades, I started saving KBAs from the Sage website. I have over 1,000 documents that I am happy to share. However, the value is likely in the organization of the documents, yes? I don't have a lot of time, but I have a little bit of time each month to contribute. Let me know how I can help.

Karen

@Kevin Moyes (or any other members) would you be able to lend a hand on this? We have these in Google Docs and could use as many creators/editors to build up our knowledge as possible. 

My concern is that as members leave the business and Sage personnel leave that suddenly we are left with gaps in knowledge. 

I'd like to see the group start documenting as much as possible  - here's an example of what's been started. A lot of the work is just scraping relevant items from Higher Logic and documenting it in a Google Doc.

There is a Sage KB article on recommended AV exclusions that I tend to attach with "go Live" emails.

Paperless Office fixes, by version.

Version conflicts (like when the CR print engine is updated, breaking printing from older versions... and when the Amyuni driver is updated, breaking Paperless in older versions...).

One of my biggest questions is, how will the information be organized.   We have a diverse community with some extremely technical people, some more functional implementers and some who just do basic support.  In addition, we have a treasure trove of knowledge on third party products, reporting tools, project management software, etc. which fall outside the umbrella of technical articles.  

I know this is a HUGE undertaking and we need to start one bite at a time, and the technical knowledgebase is top priority.  Within that we may want to segregate it into categories of Upgrades, Integrations (VI), Scripting, SQL Server, Windows, etc. depending on the content categories and tags you have in the initial dump of data.  

Also know that however you organize it, entropy and misunderstanding can creep in and frustrate people.  Just remember that the work you do will improve the efficiency of many and appreciated by those who use it most, and those who know the least!

Right now it's Google Workspace

I think Google can be a good solution (as could Microsoft)  since it will allow for searching inside of PDF files, easy collaboration and entirely web-based.

Years ago with Evernote and to some extent Dropbox we did undergo an effort to create tags and more granular folder structures. I don't think it materially improved the ability to locate things. I found myself 99% of the time doing a regular search. 

Right now I've been collecting into these folders

Which includes a folder - Sage Announcements and Notes -  to capture as many Sage and Sage-related emails as possible. Much of this is already posted in Sage Partner Hub however documents occasionally go missing from the hub so it seems like a good idea to begin our own collection. 

My thought is that the overall tool(s) used is less important than we start and maintain a good collection of knowledge. As people leave Sage (or get moved to other product lines) this knowledge is going to get harder to find.

One of my biggest questions is, how will the information be organized.   We have a diverse community with some extremely technical people, some more functional implementers and some who just do basic support.  In addition, we have a treasure trove of knowledge on third party products, reporting tools, project management software, etc. which fall outside the umbrella of technical articles.  

I know this is a HUGE undertaking and we need to start one bite at a time, and the technical knowledgebase is top priority.  Within that we may want to segregate it into categories of Upgrades, Integrations (VI), Scripting, SQL Server, Windows, etc. depending on the content categories and tags you have in the initial dump of data.  

Also know that however you organize it, entropy and misunderstanding can creep in and frustrate people.  Just remember that the work you do will improve the efficiency of many and appreciated by those who use it most, and those who know the least!