April 28th, 2009 by Brian Cors
We’ve added several new user types and deployment options to SalesDoc Architect release 5.0, making SalesDoc Architect more flexible, easy to use and easy to update than ever before. Now you have several user type options to choose from…
- Stand-alone users who are always disconnected from the network.
- Stand-alone users who have occasional network access to a shared drive so that SalesDoc Architect can check for data and application updates.
- Network users who are always connected to a shared drive on the LAN and access data from that shared drive.
- Combo users who are sometimes connected to a shared drive on the LAN and sometimes need to be able to work “offline” (disconnected) from the shared drive.
You can change your user type by clicking the SalesDoc Architect button, then Setup, then “Network setup”.
Stand-alone users are not connected to a shared network drive. For these users, SalesDoc Architect data and application updates are manually emailed to these users, who then double-click on the update files to install the updates.
Stand-alone users who have occasional network access to a shared drive gain the benefit of automatically being informed of SalesDoc Architect data and application updates. On occasion, SalesDoc Architect will attempt to access the shared drive and determine if updates are available. If they are, the user will be prompted to download and install them.
Read the rest of this entry »
April 15th, 2009 by Brian Cors
SalesDoc Architect is now compatible with Office 2007 and Microsoft’s Vista operating system.
SalesDoc Architect end users with Office 2007 will see only one variation from previous versions of Office: the SalesDoc Architect toolbar must be accessed by clicking the “Add-Ins” tab within Excel. Other than that, SalesDoc Architect works exactly the same.
For SalesDoc Architect Managers, we’ve made the conscious decision to save all Word documents within SalesDoc Architect’s document library in the legacy Word “doc” format rather than in the new “docx” format that Microsoft has just released. We can’t see any features or functionality lost by sticking with the “doc” format, and our clients gain the advantage of not having to deal with compatibility issues between users who have different versions of Microsoft Office.
As far as Vista is concerned, we recommend installing SalesDoc Architect into a folder different than “Program Files” (we’d suggest you install it to a top-level “CorsPro” folder by simply deleting the “Program Files” part of the folder path during the setup process). The user installing SalesDoc Architect should have full admin rights to the machine, or at least full admin rights to the installation folder.
April 2nd, 2009 by Brian Cors
For all of the new SalesDoc Architect user types that are “network-connected” in some fashion (see “New SalesDoc Architect User Types and Deployment Options” for further information), SalesDoc Architect automates the process of checking for and installing application and data updates.
On occasion, SalesDoc Architect will reach out to the shared network drive to determine if updates are available and, if so, will prompt the user to download and install them. End users no longer need to close SalesDoc Architect to install the updates; they can install them while SalesDoc Architect is still running (although SalesDoc Architect Manager, which the SalesDoc Architect admin uses, must be closed).
The most accurate update checking process occurs for network and combo users who are accessing data from the network drive (whereas stand-alone users with network access only access the update files, not the actual data files). When they check for updates, network and combo users actually compare the data files themselves, rather than just the update files.
Users can also manually check for updates by clicking the SalesDoc Architect button, then Setup, then “Install SalesDoc Architect updates.”
Read the rest of this entry »
