Infor Worktop 25 Administrator's Guide

InforTechnology Architecture Worktop 2.5

Administrator's Guide Worktop 2.5 for Infor ERP LN 6.1

Copyright © 2007 Infor Global Technology Solutions GmbH and/or its affiliates and subsidiaries

All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor Global Solutions Technology GmbH and/or its affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners.

Important Notices

The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor Global Solutions.

By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor Global Solutions and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor Global Solutions pursuant to a separate agreement (“Purpose”).

In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above.

Although Infor Global Solutions has taken due care to ensure that the material included in this publication is accurate and complete, Infor Global Solutions cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor Global Solutions does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause.

Trademark Acknowledgements

Infor, Infor Global Technologies are trademarks or registered trademarks of Infor Global Technologies, Inc. in the United States and/or other countries.

Baan is a registered trademark of Infor Global Technologies, Inc. in the United States and/or other countries.

All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners.

Publication Information

Document code: U8478G US

Release: Infor Technology Architecture Worktop 2.5

Publication date: November 07

Table of Contents

Chapter 1 Introduction............................................................................................................. 1-1 Definitions, acronyms, and abbreviations................................................................................... 1-1 References................................................................................................................................. 1-2

Chapter 2 Central deployment ................................................................................................ 2-1 Introduction ................................................................................................................................ 2-1 To enable central deployment.................................................................................................... 2-2 To distribute Worktop documents .............................................................................................. 2-5 Central deployment features ...................................................................................................... 2-6

To send shortcuts ................................................................................................................ 2-6 To send messages............................................................................................................... 2-6 Configurations...................................................................................................................... 2-7

System requirements ................................................................................................................. 2-8 Technical details ........................................................................................................................ 2-9

Chapter 3 To use worktop in a terminal server environment ............................................... 3-1

Chapter 4 Worktop and the Workflow integration component............................................. 4-1

Chapter 5 Worktop runtime files and folders......................................................................... 5-2

Appendix A Administration FAQ ............................................................................................... A-1

Appendix B To create application shortcuts............................................................................ B-1

About this Guide

This document is an Administrator’s Guide that describes the Administration part of Worktop 2.5. This document consists of the following chapters:

Chapter 1, “Introduction,” provides an introduction to Worktop 2.5.

Chapter 2, “Central deployment,” provides detailed information about how to set up central deployment in Worktop 2.5.

Chapter 3, “To use worktop in a terminal server environment,” provides information about how to use worktop in a terminal server environment.

Chapter 4, “Worktop and the Workflow integration component,” gives some details about the integration with iFlow.

Appendix A provides answers to frequently asked questions in regard to Worktop administration.

Appendix B provides detailed information about how to create application shortcuts in a central deployment environment.

Send us your comments

We continually review and improve our documentation. Any remarks/requests for information concerning this document or topic are appreciated. Please e-mail your comments to [email protected].

In your e-mail, refer to the document code and title. More specific information will enable us to process feedback efficiently.

mailto:[email protected]?subject=Documentation

iv | Table of Contents

1 Chapter 1 Introduction

Worktop is the user interface for the various Infor ERP products, such as Infor Enterprise Resource Planning and Sales Force Automation (Infor CRM). Worktop provides an easy-to-use and intuitive view on the Infor-integrated products that hides the complexity of the software used.

Definitions, acronyms, and abbreviations

Term Description

DEM Dynamic Enterprise Modeling

ERP Enterprise Resource Planning

%WINDOWSROOT% Location of where Windows is installed, for example, C:\winnt.

% BWROOT% Location of where BW is installed, for example, C:\Program Files\Baan

%WORKTOPROOT% Location of where Worktop is installed, for example, C:\Program Files\Baan\Worktop

UNC Uniform Naming Convention, for example, if C:\Program Files on a machine called cnl05410 is shared under the name Programs, the UNC is \\cnl05410\Programs.

.wtd file Worktop document

.gct file GUI Configuration Template

.sct file Server Configuration Template

CDEP Central Deployment

1-2 | Introduction

COM Common Object Model

SP Service Pack

BW Baan Windows

BWC Baan Windows Configuration

Worktop Server Machine with Worktop installed

Worktop Client Machine without Worktop installation. Worktop runs from the server

Worktop Document Owner

An administrator who created the document on a specific machine

Administrator User logged on to a machine on which Worktop is installed locally

References

Document Abbreviation

Infor ERP Baan 5.0c central deployment for DEM and Baan Windows

[CD_DEM_BW]

Infor Baan ERP Windows Client Installation Guide [WCIG]

Worktop 2.5 Administration Guide [WT_ADM]

Worktop 2.5 Configuration Guide [WT_CFG]

2 Chapter 2 Central deployment

Introduction

There are different ways to setup centrally deployed access to the backend system:

Webtop The preferred solution for central deployment and remote access is Webtop. Webtop is the User Interface going forward, and offers the smallest network load.

Worktop centrally deployed Since Webtop does not support all application sessions (on older Baan versions), Worktop centrally deployed can be an alternative for Webtop. How to setup Worktop central deployment is described in this chapter.

Note: Be aware that Worktop causes a higher network load than Webtop.

Windows 2000/2003 Terminal Server / Citrix. For more information refer to Chapter 3 “To use worktop in a terminal server environment”.

Worktop 2.5 completely supports central deployment on Infor ERP LN. On Infor Baan IV, central deployment is only partially supported. In this case, BW still must be locally installed.

The combination of Windows Vista clients and usage of a Central Deployed worktop is not supported.

Using Worktop in a central deployment environment offers numerous advantages, mainly for system administrators who now only have to install, configure, and maintain one system instead of all users separately. Generally, the advantages are:

2-2 | Central deployment

No client-side installation or automatic installation and update.

Global access, but only if you use Windows XP with roaming profiles.

The administrator can create Worktop document templates, with which the end user can work, with no configuration activity required.

Although personalization is supported, end users cannot change configurations reserved by the administrator.

Enabling central deployment is significantly simplified in the 2.3 and later versions of Worktop. To enable central deployment in Worktop 2.5, you must simply click a button and distribute a shortcut to a Worktop document. The following two sections discuss this procedure in greater detail.

For best results, read these two sections carefully to work with central deployment in Worktop.

The following section provides information about the additional central deployment functionality that Worktop supports. The final section in this chapter describes the technical details of central deployment. Note that no detailed knowledge of the technical details of central deployment in Worktop is required. This information is only included for additional support.

To enable central deployment

In a central deployment environment, Worktop is installed on only one computer. To work with this installation, any other client can launch the Worktop client executable located on that machine. The machine on which Worktop is installed is referred to as the Worktop server. Any other machine from which Worktop is run, but on which Worktop is not installed, is referred to as a Worktop client.

The menu options that are available for a user in Worktop depend on whether the Worktop server or the Worktop client runs. The Worktop server has additional, so-called administrative options.

The following options are available only on the Worktop server:

The New command on the File menu.

The Save command on the File menu.

Enabled “Workflow Server” entry from the Workflow tab in the Tools\Options dialog box.

Enabled host name and port number entry from the Drag-and-Relate tab in the Tools\Options dialog box.

The complete Administrator menu.

Central deployment | 2-3

However, these options only apply to administrators who are also owners of the Worktop document. Therefore, in Worktop, the following two types of authorization are actually available:

Administrator: A user has Worktop installed locally. Note that all users logged in onto a machine with Worktop installed are, therefore, administrators.

Owners: Owners of a Worktop document are administrators logged in to the machine where the Worktop document was created originally. Therefore, if an administrator runs Worktop and subsequently opens a Worktop document created on a different Worktop server, this administrator is not an owner of the document.

Administrators who are not owners of the currently opened Worktop document will not have access to the additional options as described previously, except for the New command on the File menu.

The Administrator menu enables you to enable central deployment for a Worktop document. The menu contains the following menu items related to Central Deployment:

Enable or disable Central Deployment.

Send shortcuts.

Send a message.

Initially, your Worktop document will not have the central deployment option enabled. In this case, the Send Shortcut(s) menu option is unavailable, because this option is only applicable in a central deployment environment.

To enable central deployment for this document, and note that you must repeat this procedure for any document you want to enable, select the Enable or Disable Central Deployment option.

The following dialog box appears:


To enable central deployment for this document, simply click Enable. After several seconds, Worktop finishes. Worktop shares your Worktop and BW directory, prepares your BW environment, and prepares your Worktop document for Central Deployment. During this process, error messages can appear. In this case, Worktop notifies you that the enabling failed and refers to the log file. The log file is called wtError.log and is located in the \log subdirectory of the Worktop directory.

The following two issues can cause this type of error:

Directory could not be shared: Worktop shares both the BW and Worktop directory for read access. This sharing can fail; in this case, you must share the directories manually. Worktop presents a dialog box that lists precisely which directories you must share. Always check the access rights to the directories. Make sure they are shared read-only.

Use of spaces in names: If you apply Central Deployment, neither the used BWC file name nor the Worktop document name must contain spaces. If spaces were detected in either of the two names, Worktop notifies you of this fact, and you must first change the name.

In addition, some warning messages can appear. The following two issues can cause these types of warnings:

Use of Infor ERP Baan IV: Central deployment is not fully supported on Infor Baan IV. Worktop


notifies you about this fact if you enable a Worktop document using an Infor ERP Baan IV environment. To use central deployment on Infor ERP Baan IV, you must install the BW client on all clients. The version of this BW client must be of the exact same version used by the Worktop server. Note that Worktop only provides a warning, and continues with the enabling. As long as the BW client of the same version is installed on the clients, central deployment will function fully.

Worktop document not yet saved: To enable Central Deployment, the document must be saved first. If the document was not saved previously, Worktop warns you that you must first save the document and automatically open the Save As dialog box. If the document was saved previously, Worktop automatically saves the document before you enable the document.

After you successfully enable Central Deployment, the Create Shortcut button at the bottom of the dialog box becomes enabled, and the Send Shortcut(s) option on the Administrator menu becomes available. Click Create Shortcut to create a shortcut to this Worktop server that you can subsequently sent to any user who must work with this document. After you receive the shortcut via mail you only need to drag it to your desktop, or to wherever you want the shortcut, and open the shortcut. Worktop starts and opens the document automatically. This option will be discussed in more detail later.

After you enable central deployment for this document, you might want to change policies with respect to password saving and configuring BWC files. Information on how to change these policies is discussed in more detail in the Infor ERP Baan 5.0c Central Deployment for DEM and Baan Windows and Infor ERP Baan Windows Client Installation Guide.

To distribute Worktop documents

If you enabled central deployment for a Worktop document, the Create Shortcut option in the Enable or disable Central Deployment dialog box becomes available. This option enables you to create a shortcut to this Worktop document and save the shortcut to disk. From there, you can distribute the shortcut to users, for example, by e-mail.

If you click Create Shortcut, a save dialog box appears and you can save the shortcut to a desired location. The shortcut that will be created contains a shortcut to the Worktop client executable on the Worktop server and opens the Worktop document automatically when you activate the shortcut.

You can create multiple shortcuts, each of which contains a reference to a different Worktop document. Users can work with multiple shortcuts


simultaneously that are opened in the same Worktop instance. Only one instance of Worktop can run at a time.

Central deployment features

To send shortcuts

If a Worktop document is centrally deployed, a shortcut is sent to the users, who then automatically have access to all shortcuts created in the document by the administrator. However, immediately after you open the document for the very first time, the document is copied to the user’s profile. The next time you open the document, this personal copy is used. Therefore, any changes made to the original document by the administrator afterwards will have no effect on the user’s personal document.

In most cases, this will not be an issue because any user can modify the user interface of Worktop in the way they choose. However, the administrator might have new important information to share among the users. To share this information, the administrator can send a selection of the shortcuts present in the shortcut bar to the users.

If the administrator selects the Send Shortcut(s) option from the Administrator menu, a dialog box appears which contains all shortcuts present in the current Worktop document. From this list, the administrator can make a selection and click Send to send these shortcuts to all users.

The users receive a message that informs them that “New shortcuts have been made available by your administrator.” The user can choose to ignore this message, or import these shortcuts into the current document.

To send messages

You can send messages to all users currently using your Worktop server. These users are those who are currently running the Worktop client executable on your Worktop server. To send a message, on the Worktop server, on the Administrator menu, click Send Message. The Send Message dialog box appears, as shown in the following figure:


Type the message you want to send into the text field and click Send to send the message to all users. The message appears on all users’ desktops with a maximum delay of 10 seconds. To view additional help, click the question mark icon in the lower-left corner of the dialog box.

Configurations

Specially designed for Central Deployment, you can select or clear the following options in the Worktop.ini file, which is located in the root directory of the Worktop directory on the Worktop server:

Automatic creation of a desktop shortcut: If you select this option, a shortcut to the Worktop application will be created automatically on the user’s desktop. Note that this is a shortcut only to the application and not to a document. Upon activation, only the application will be launched. The shortcut will be created only once. By default, this option is not enabled because, for best results, you must use the Create Shortcut options provided in Setup Central Deployment dialog box instead.

Message pulling. If you select this option, Worktop clients ping the Worktop server for new messages every 10 seconds. Only if this option is enabled administrators can send messages and shortcuts. If this option is not selected, administrators cannot send messages or shortcuts, and the menu items will be disabled. For best results, clear this option if the additional network traffic caused, which is usually negligible, is unacceptable.

Automatic removal of non-accessible shortcuts: The administrator may have created or sent shortcuts to a user that are not accessible to that user at all. For example, the administrator sends a share shortcut to all users, while only a number of these users have permission for this share.


In this case, you can use this option to automatically remove these shortcuts. By default, this option is selected and, as a result, all inaccessible shortcuts are filtered out for the user automatically.

Storage of passwords in configuration files. In some organizations, security rules do not allow storing passwords in any form on local machines. Therefore, you can use this option to disable local password storage. By default, this option is enabled, which means that Worktop users can store the Workflow server password locally. If this parameter is set to 0, Worktop users cannot store the Workflow password on their local machine. Consequently, the Save Password check box and the related edit field are unavailable in the Worktop Options | Workflow dialog box.

The default values for these options are contained in the Worktop.ini file:

AutoShortcut=0

AutoMessage=1

AutoRemoveShortcuts=1

PasswordStorage=1

These entries correspond to the options in the same order as described in the previous list. To select the option, the value of the entry must equal to 1. To clear the option, the value of the entry must equal to 0.

System requirements

The system requirements for a Worktop server are identical to the requirements for a Worktop client, as described in the Installation Guide. The only difference in system requirements for a Worktop client is that on the client, neither Worktop nor BW must be installed. However, if you use Infor ERP Baan IV, BW must be installed locally. The reason for this is because Infor ERP Baan is registry-independent and Infor ERP Baan IV is registry-dependent.

The combination of Windows Vista clients and usage of a Central Deployed worktop is not supported.


Technical details

Error logging

Worktop places any error or warning messages in a file called wtError.log. This file is located in the Application Data\Baan\Worktop\log directory of the users profile for users and in the \log subdirectory on the Worktop server for administrators. The log file often contains useful information to determine the cause of the problem. Each log contains the date and time on which the error was generated and a description of the problem. Optionally, arguments are added that provide more-detailed information. The error codes in front of each error are useful for support, because these error codes provide information about where these errors were generated in the source code.

Worktop documents

Worktop 2.5 documents are separated into the following three parts:

Worktop document (.wtd file).

Server configuration template (.sct file).

GUI configuration template (.gct file).

You save the two templates in the %WORKTOPROOT%\templates directory immediately after you create a Worktop document. A Worktop document is only a pointer to two of these templates, and the only information a Worktop document contains is which .sct and .gct file must be used.

Now, if a user opens a Worktop document for the very first time, the corresponding .gct file is copied from the server into the users profile in the \Application Data\Baan\Worktop\documents directory.

The next time the user opens the Worktop document, Worktop finds this .gct file in the user’s profile and uses that file instead of the file located on the server. The user has write access to the local .gct file, but not to the .gct and .sct files on the server. The .sct file is not copied to the client, but is always read from the server.

Note: Because the .gct and .sct file separate GUI settings and server settings, you can reuse these files. For example, if you created a document and want to create a second document using the same GUI settings, but different server settings, you can either modify the reference in the Worktop document to the other .gct file, or overwrite the .gct file.


Transparency of documents

You can copy and open Worktop documents anywhere, although not the templates, because Worktop contains pointers to the UNC name of the corresponding templates. Therefore, you can, for example, create a Worktop document on the Worktop server with the name test.wtd and copy this document to your local machine and open the document from that location. From the Test.wtd file that Worktop points to, Worktop reads the templates on the Worktop server and loads these templates. You can load Central Deployment-enabled Worktop documents from within any Worktop: either a Worktop client or Worktop server.

To optimize performance: Worktop mirrors

The Worktop server is not much more than a distributor of all Worktop files. Worktop only shares the files that the Worktop clients require. Therefore, the hardware specifications of the Worktop server will not be the bottleneck, but rather the speed of the network. For example, if you connect to a Worktop server located in the Netherlands from your office in Japan, approximately 8 megabytes (MB) of data is transferred from that server to your client. This transfer usually only occurs the first time if you run Worktop_client.exe, or every time when you run Worktop.exe. In both cases, this amount of data is usually quite large.

To minimize the amount of data transferred over long distances, you can install extra Worktop servers or mirrors.

Users can use this local Worktop server to launch Worktop, either Worktop.exe or Worktop_client.exe, while still using the Worktop documents located on the central Worktop server. For more information, refer to “Transparency of documents.”

In this case, only the Worktop document is sent over the long distance, which is only a small amount of kilobytes. As few as 50 KB would already be a large document.

To use multiple Worktop servers

You can run a Worktop client and work with Worktop documents located on multiple Worktop servers simultaneously.

Global access

Worktop 2.5 supports global access; however, this only applies when roaming Profiles are used, which is supported on Windows XP. Because


Worktop writes the personalized documents into the user’s profile, global access is supported when Worktop is roaming.

Worktop.exe versus Worktop_client.exe

After installation, two Worktop related executable files are located in the %WORKTOPROOT%\bin directory on the Worktop server, Worktop.exe, and Worktop_client.exe. To run the Worktop server, you must run Worktop.exe on the Worktop server. Usually, you can launch Worktop from the Start menu. Note that you do not have to run Worktop to enable Worktop clients to connect to this Worktop server. No services are required.

To run a Worktop client, browse to the \bin subdirectory of the Worktop share on the client machine. For example, if a Worktop server called cnl05259 has shared the Worktop directory with the name Worktop, open Explorer on the client machine and browse to \\cnl05259\Worktop\bin.

Two executables are located here: Worktop.exe and Worktop_client.exe. To run the Worktop client, you can use either of the following methods:

Run Worktop.exe: In this case, no Worktop-related files will be stored on the local machine, but these files will be loaded into memory. After you close Worktop, the memory is released. The advantage of this method is that no Worktop files, except for the personal documents, are stored on the client. The disadvantage of this method is that each time you start Worktop, you must transfer the Worktop-related files from the Worktop server into the client’s memory, which causes significant network load.

Run Worktop_client.exe. If a user runs Worktop_client.exe, initially only a very small executable is transferred from the Worktop server to the client. The first time this executable runs, this file will copy the Worktop-related files into the %USERPROFILE%\Local Settings\Temp\ Application Data\Baan\Worktop directory. Subsequently, Worktop_client.exe runs Worktop.exe from that directory.

Any other time, this file checks whether files are missing and whether the Worktop server contains a version of Worktop that differs from the client’s version. In both cases, the client will be updated.

We recommend this method because the network load is significantly less, and Worktop will have a faster startup time on the client. Therefore, the Create Shortcut option in the Setup Central Deployment dialog box points to this executable.


Manual distribution of Worktop documents

After you install and configure Worktop, you probably want to distribute the Worktop documents to users. The easiest manual method to distribute these documents is to send a shortcut to Worktop_client.exe with the document as the start-up parameter. To send a shortcut, take the following steps:

1 Create a shortcut to Worktop_client.exe: Right-click on Worktop_client.exe in Explorer and, on the shortcut menu that appears, click Create Shortcut.

2 Right-click on the shortcut you created in the previous step and, on the shortcut menu, click Properties. Select the second tab, which is the Shortcut tab.

3 In the Target field, add the UNC name of the document to be opened behind the path to the Worktop_client executable. For information on UNC, refer to Chapter 1, “Introduction.” As a result, the syntax will be: <Worktop_client path> <Worktop document UNC path>.

4 Attach the shortcut to an e-mail message and send the message to all users.

3 Chapter 3 To use worktop in a terminal server environment

As of version 2.3, the Worktop supports the Microsoft Terminal Server service. Although, Worktop has been tested for Windows 2000 Terminal Server, other terminal servers, such as Windows NT TS and Citrix, are also supported.

Terminal Services is a service that adds terminal support to Windows 2000 Server. Terminal Services is a multisession environment that provides remote access to Windows-based programs running on the server. Essentially, Terminal Services is an alternative to central deployment, which is described in Chapter 2, “Central deployment.”

To enable terminal server users to use the Worktop, the administrator must configure the Worktop in the Terminal Services configuration to start up with the argument /ts.

3-2 | To use worktop in a terminal server environment

In the following example, the administrator configured the terminal server so that, when a user connects, the Worktop starts automatically:

Several methods are available to deploy the Worktop on terminal server. The most typical approach is to enable users to connect to terminal server with their system account. Subsequently, a user can open a Worktop document that is created by an administrator and connect to the Baan backend with their personal Baan account. Specific changes made to the document, such as GUI modifications, are stored in the terminal server user profile.

A second approach is for all users to connect to terminal server with their system account and connect to the Baan backend with a common account. This can be useful if all users rely on one specific DEM business process.

To use worktop in a terminal server environment | 3-3

Note that some restrictive issues, such as the following, apply to the use of terminal server:

Administrators control the deployment of Worktop documents, as described in Chapter 2, “Central Deployment.”

Older versions of terminal server only support up to 256 colors.

Some screen update problems exist. In many cases, minimizing and maximizing, or resizing the Worktop window can resolve this issue.

4 Chapter 4 Worktop and the Workflow integration component

Infor Worktop uses a Workflow integration component (iFlow.jar) to connect to Infor Workflow. With Worktop two versions, iFlow6.2build87 and iFlow6.2build110, are shipped. When Worktop tries to connect, first iFlow6.2build110 is used. If this version does not match the one that the Infor Workflow server uses Worktop will notify the user to save the current Worktop document and restart the Worktop with the saved document. Worktop again tries to connect with Infor Workflow but now via iFlow6.2build87. If this version does not match the one of the Workflow server, Worktop will download the correct Workflow integration component from the wfupdate web application. The wfupdate web application is part of Infor Workflow. The wfupdate web application needs to be deployed on the same server as Infor Workflow cause the workflow server and port are used to call the wfupdate web application.

To test the wfupdate web application you can use:

http://<workflow-server>:<port>/wfupdate/DownloadJarServlet?method=getjar A file save dialog will appear so you can provide a location to save the workflow integration component.

Note: The user needs to restart Worktop to free the java virtual machine and to load a new classpath with another version of the workflow integration component.

5-2 | Worktop runtime files and folders

5 Chapter 5 Worktop runtime files and folders

The worktop uses a number of files and folders in which runtime data is saved during Worktop execution, such as the following:

Worktop documents (.wtd files).

Server configuration template (.sct files).

GUI configuration template (.gct files).

A cache folder for caching the ERP menu tree items and DEM processes.

A folder where the history files are saved.

The default location of these folders differs between Windows XP and Windows Vista. On Windows XP, the default location for these folders is immediately below the Worktop installation folder (%WORKTOPROOT%). For example: c:\Program Files\Baan\Worktop\documents.

On Windows Vista, a normal user program is not allowed to write in the program files folder or any of its sub-folders. Therefore, the default location of the Worktop runtime files on Windows Vista is in a sub folder of the Local Application Data folder (CSIDL_LOCAL_APPDATA). For example: C:\Users\<username>\AppData\Local\Infor\Worktop\documents. The Local Application Data folder is a per-user folder which does not get copied if the user profile roams.

This difference implies that when different Windows users use the same system, on Windows XP these users can share each others Worktop documents. However, on Windows Vista the Worktop documents cannot be shared by different Windows users.

A Appendix A Administration FAQ

Q: Can I use the same .bwc file from multiple Worktop documents simultaneously by using several Baan logins?

A.: No. If you use the same BWC file from two Worktop documents and you open both documents, no login or password is requested when you open the second document. Worktop assumes that you want to use the same Baan login as for the first document. No workaround is currently available to address this known issue. This problem is a Baan Automation, or, more precisely, a COM restriction.

Q: What is the wfupdate web application?

A: The wfupdate web application comes with the Infor Workflow extension. The wfupdate application can be deployed along side the Workflow server. The wfupdate web application provides download access to the correct Workflow integration component. With Worktop two versions of the Workflow integration component are shipped. However when these are not correct Worktop will automatically try to download the correct version from the wfupdate web application

B Appendix B To create application shortcuts

In Worktop, to create application shortcuts, you can simply drag the executable or shortcut to the executable from Explorer to the Shortcut Bar in Worktop. As long as you do not centrally deploy Worktop, this method is adequate. However, a problem arises as soon as you run the Worktop client and try to run the shortcut.

In this case, you will encounter two problems. The first problem is that the executable that you created the shortcut to is probably not shared, nor do you want to share this executable. You do not want to share any application to which you created a shortcut. The second problem is that, even if you did share an executable, most applications do not support central deployment, therefore, the application will not run that way anyway. For example, if you create a shortcut to the Microsoft Word application, word.exe, you must share the directory where the word.exe file is located, but the share still will not work because Microsoft Word does not support central deployment.

A solution for this is to create a shortcut to a local shell command. To do that, take the following steps:

1 In the Run Application field, type the name of the application you want to start and precede it with a “#”. Don not specify a path. To create a shortcut to notepad, type “#notepad”.

2 Press Create Shortcut behind the field to create a shortcut.

3 Now the shortcuts can be distributed with the “Send Shortcut(s)…” menu option.

B-2 | To create application shortcuts

In the following picture the Run Application field and the Create Shortcut button are highlighted.

To create application shortcuts | B-3

Infor Worktop 25 Administrator's Guide

Documents

Transcript of Infor Worktop 25 Administrator's Guide