AgilePoint Knowledge Base » Knowledgebase » AgilePoint BPMS Suite

Known Issues for AgilePoint v5.0

DouglasD — Tue, 17 Aug 2010 16:20:48 GMT

Periodically AgilePoint releases temporary or intermediate bug fixes for individual issues before hotfixes or service packs become available. See the README files in the Zip file for each fix for deployment instructions.

Issue 1

Description

After upgrading to AgilePoint v5.0, old process models (created in previous AP versions) that use the Dynamic Group shape are not working at design time (in Envision), or at run time.

Download

Ascentn.AgileWork.Premier.zip

Issue 2

Description

Upgrading from AgilePoint v4.5 to any higher version fails to update the Oracle database schema. (This issue only applies to Oracle database users.)

Download

ServerConfigurationUI.zip

Issue 3 (AgileForms Only)

Description

Before this fix if we have any Yes/No field in Subform then while Submiting the first Activity following error was encountered.

An error has occurred:
StoreDataCommon: RetrieveData: Object reference not set to an instance of an object. at AgilePoint.AgileFormEngine.FormRenderControl.NameValueXMLToDFC(XmlNodeList NameValueNodes, Boolean IsSubForm) at....

Download

AgilePoint.AgileForms.AgileWork.zip

Issue 4

Description

The Download File AgilePart in the SharePoint Stencil caused an application pool recycle within AgilePoint Server. In order to fix this issue, this AgilePart now uses the Windows Temp folder to download a copy, rather than a folder within AgilePoint Server.

NOTE: This is for AgilePoint Integration for SharePoint v2 only.

Download

Ascentn.SharePoint.AgileConnector.zip

Issue 5 (AgileReports Only)

Description

Login failures occur for AgileReports because user profiles for first-time users are not being automatically synchronized with Active Directory.

Download

AgileReports.ActiveDirectorySync.zip

Issue 6

Description

SharePoint Form Server is creating unnecessarylog entries, causing bloat in the log.

Download

Ascentn.SharePoint.FormServer.v2.zip

Issue 7

Description
After upgrading to 5.0, on the Add Template screen in Enterprise Manager, an error message says that a property is mising from the Date Picker control. The reason is, one of the previous upgrades put Ascentn.Workflow.Webcontrol.dll into the GAC of the AgilePoint Server. This Dll needs to be uninstalled from the GAC.

Fix

Log on to the AgilePoint Server using an account that has write permissions on the GAC. The Administrators account on the local computer has this permission.
Navigate to the GAC at %systemdrive%\Windows\Assembly.
Right-click the Ascentn.Workflow.WebControls assembly file, click Uninstall, and then click Yes to confirm.
Repeat step 3 for all resources file which start with Ascentn.Workflow.WebControls.resource.

Issue 8

Description

The WCF AgilePart does not support custom attributes in the Endpoint URL field.

Note: There was a bug in the original download. As of 8/13/2010, this has been fixed. If you downloaded the previous fix, please replace it with the current attachment.

Download

Ascentn.AgilePart.WCFService.zip

Issue 9 (AgileForms Only)

Description

Labels typed in any language other than English appear as ???? in AgileForms at runtime.

Download

AgileForms_Language_Fix.zip

AgilePoint Floating License FAQ

DouglasD — Thu, 12 Aug 2010 11:01:23 GMT

What is an AgilePoint Floating User License?

For newAgilePoint customers purchasing AgilePoint BPMS v5.0 or higher, the AgilePoint Floating User License is available. In a floating license model, only the active AgilePoint BPMS system users are counted against the number of purchased license seats. The number of active users is defined as the number of user sessions on the AgilePoint Server at a given time.

A user session lasts from initial login from any application to the time the session times out. (The timeout period is configurable.) If the user logs in before the current session times out, the session and the timeout period are renewed. Applications that can initiate a user session include AgilePoint Envision, AgilePoint Enterprise Manager, SharePoint, customized web applications, or web service calls from Microsoft Internet Explorer.

How can I estimate my number of users for an AgilePoint Floating User License?

Use the following calculation to estimate the number of users you will require under the AgilePoint Floating User License. Note that this is a basic estimate to be used as a general guideline intended as astarting point. You can use your own estimating scheme if desired.

[totalnumber of AgilePoint users] * [average number of hours per day each user will be actively using AgilePoint] / [number of hours per work day] = [number of required floating license seats]

Example: 200 total AgilePoint users * 2 hours average usage per user per day / 8 hours per work day = 50 floating user license seats

What happens if my total number of concurrent users exceeds my maximum number of active user license seats?

If your total number of concurrent users exceeds the maximum number of active users allowed by your License Agreement, the AgilePoint Server will generate an email warning to the system administrator. At this point, system performance may slow somewhat.

If you receive a warning regarding your maximum users, AgilePoint recommends that you 1) monitor your licenseusage, 2) try tuning your session timeout settings to accommodate your current user load, and 3) purchase additional license seats if required.

How can I monitor my actual number of active users once the system is up and running?

To monitor your actual number of users, query the AgilePoint database to analyze your maximum number of users in a day, and the frequency with which that maximum is reached. The AgilePoint system refreshes the user session count every 10 minutes. A record is generated each timethe maximum number of license seats is reached.

To monitor your license usage, run the following query against the AgilePoint Database:

select DATE_OCCURRED, OBJECT_INFO, DESCRIPTION as WARNING from WF_AUDIT_TRAILS where CATEGORY=7 order by DATE_OCCURRED desc

The results look like the following. L=n represents the maximum number of floating license seats. A=n represents the number of active user sessions.

DATE_OCCURRED	OBJECT_INFO	WARNING
2010-05-10 17:34:40.027	L=2,A=3	The maximum number of concurrent users allowed by your AgilePoint License Agreement is 2, but your actual n ….
2010-05-10 17:29:04.400	L=2,A=2	NULL

In addition, you can run the query in Microsoft Excel to create graphs that will enableyou to track your usage over time. For Excel, create the following view:

CREATE VIEW WFV_FLOATING_SESSIONS as select DATE_OCCURRED as [TIME],CONVERT(INT, RIGHT(OBJECT_INFO, LEN(OBJECT_INFO) - CHARINDEX('A=',OBJECT_INFO) - 1)) as ACTIVATED_SESSIONS, DESCRIPTION as WARNING from WF_AUDIT_TRAILS where CATEGORY=7

Then create the following query:

select * from WFV_FLOATING_SESSIONS

TIME	ACTIVATED_SESSIONS	WARNING
2010-05-10 17:34:40.027	3	The maximum number of concurrent users allowed by your AgilePoint License Agreement is 2, but your actual n ….
2010-05-10 17:29:04.400	2	NULL

How can I tune my server settings to better accommodate my current number of user licenses?

If your number of concurrent, active user sessions are exceeding the number of seats in your Floating User License Agreement, you can change the session timeout interval to better accommodate your usage.

There is a tradeoff between greater numbers of available license seats and system performance. If you have shorter session timeouts, you tend to have a higher number of available license seats, but frequent user session renewals can negatively impact system performance. On the other hand, if you have a longer user session timeoutperiod, performance is better because the system is not renewing user sessions as often. However, longer timeouts can yield fewer available license seats and active sessions for users who are not actively using the AgilePoint system.

To modify the session timeout, in the AgilePoint neflow.cfg file in the <server> node, modify thevalue of the UALExpirationPeriod attribute (<server UALExpirationPeriod="n" ...>). The unit for this value is minutes. The minimum value is 15.

How can I purchase additional license seats?

Toincrease your floating license capacity, contact AgilePoint.

Keywords

license, agreement, user, report

How do I update the logon credentials for the AgilePoint Impersonator account?

DouglasD — Thu, 15 Jul 2010 08:52:39 GMT

Summary

This article describes how to update the logon credentials for the AgilePoint Impersonator account.

Applies To

AgilePoint users.

Details

To change the AgilePoint Impersonator account credentials:

Update the AgilePoint Configuration

On the AgilePoint Server machine, click Start > All Programs > AgilePoint > AgilePoint Server Configuration to open the AgilePoint Configuration Console.
On the System tab, update the System User and Password fields as required.

Update IIS

On the AgilePoint Server machine, open the IIS Manager.
Navigate to the AgilePoint application pool, right-click the AgilePoint application pool name, and click Properties.
On the Properties dialog box, click the Identity tab.
On the Identity tab, enter the desired logon credentials in the User name and Password fields.
Reset IIS.

Update AgilePoint Data Services

On the AgilePoint Server machine, open the Windows Services list.
Right-click AgilePointDataServices, and click Properties.
On the Properties dialog box, click the Log On tab.
On the Log On tab, enter the desired password in the Password and Confirm password fields.

Update SharePoint Integration

Complete the following only if: a) you are a SharePoint Integration user, and b) your Impersonator credentials are the same for your AgilePoint Server and SharePoint Integration:

On the SharePoint Server machine, open the AgilePoint Configuration list.
On the AgilePoint Configuration list, click Edit Item to update the values for the ImpernatorUser and ImpersonatorPass.

Why does an error occur when many AgilePoint workflows are started simultaneously from a SharePoint library?

DouglasD — Fri, 09 Jul 2010 13:00:46 GMT

Summary

When many AgilePoint workflows are started simultaneously from a SharePoint library, sometimes the process fails to start and/or memory errors occur on the SharePoint server. This most often occurs during stress testing.

Applies To

AgilePoint SharePoint Integration users.

Details

This issue occurs because of the SharePoint Workflow Throttle setting, which limits the number of workflows that can be processed at any one time (the default value is 15). If the limit is exceeded, the workflows over the limit will be held, and then run later by the SharePoint Timer Service. By default, the SharePoint Timer Service does not recognize AgilePoint.

You can fix this issue in one of the following ways.

Increasethe SharePoint Workflow Throttle setting

You can increase the SharePoint Workflow Throttle setting to handle a larger number of simultaneous workflows. For instructions, see the following article: http://msdn.microsoft.com/en-us/library/dd441390(office.12).aspx.

Add a Configuration File

You can add a configuration file to the SharePoint Sever, so that AgilePoint is recognized by the SharePoint Timer Service:

In a text editor, create a file named owstimer.exe.config.
Paste the following information in the text file:

<?xml version="1.0" encoding="utf-8" ?>
  <configuration>
    <appSettings>
      <add key="APSettingsListName" value="AgilePoint Configuration" />
      <add key="APSettingsSiteUrl" value="http://[AgilePoint Server host]" />
      <add key="APSettingsWebName" value="" />
    </appSettings>
  </configuration>
Save the file to the following location on your SharePoint machine: c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN.

AgilePoint Documentation Updates and Corrections

DouglasD — Fri, 09 Jul 2010 12:28:13 GMT

About this List

In most cases, AgilePoint does not update and re-publish documentation for past AgilePoint software releases. This article provides updates and corrections to the AgilePoint documentation for past releases. Items are organized by AgilePoint BPMS release number, and then by document title.

Note that many corrections are also made to the AgilePoint documentation from one release to the next, but those corrections may not be listed here.

v5.0

Installation Guide

Correction: In the instructions for Configuring AgileReports, the following step is incorrect:

In the web.config file in the virtual folder for the Enterprise Manager web application, add the following element as a child of <appSettings> with the correct AgileReports URL:

In the value, replace Gateway.aspx with Default.aspx.

Pre-Installation Guide

Correction: Before installing AgilePoint Server, Cluster Server Manager, or any AgilePoint client software component (Envision or Developer, for example), you must turn off Windows User Account Control (UAC).

Envision Online Help

Correction: For the Common Dialog AgileWork, you cannot use Approve, Publish, or Submit as values for the Work to Perform property.

v4.7 SP2

All Documents

Update: Windows XP is no longer supported for AgilePoint BPMS, including within development environments.

Update: Microsoft SQL Server 2000 is no longer supported for AgilePoint BPMS.

Pre-Installation Guide

Keywords

documentation, errata, error, correction, update, bulletin, note

Installing AgileReports for Oracle

DouglasD — Mon, 28 Jun 2010 14:44:38 GMT

Summary

This article provides attached files and instructions for installing AgileReports for Oracle.

Applies To

AgileReports customers using an Oracle database.

Details

To install AgileReports in an Oracle environment:

Download and extract the attached file, AgileReports_Oracle.zip.
Open the file <your path>/AgileReports For Oracle/AgileReportsInstallationInstructionsForOracle.pdf. This document, Installing AgileReports for Oracle, provides instructions for completing the AgileReports installation in an Oracle environment.
Follow the instructions in Installing AgileReports for Oracle to complete the installation. This document explains what to do with the other files in the download package.

Using Xpath to retrieve inner XML string from custom attributes

DouglasD — Fri, 26 Feb 2010 09:04:40 GMT

Description

The user has a need to refer to an XML string within AgilePoint custom attributes. However, when using Xpath as a reference, the XML structure is ignored and is returned as plain text.

Applies To

AgilePoint users with processes that refer to strings of XML code in the custom attributes.

Resolution

To refer to a literal XML string from an Xpath, add a tilde (~) at the end of the path. Adding the tilde returns the inner XML for the element the Xpath refers to. The following example shows an Xpath with the tilde:

$XMLREPEATING2HTML(${/exp:expenseReport/exp:items~})

Keywords

Xpath, inner XML, string, literal, retrieve, call, display

Accessing log files to troubleshoot AgilePoint installation issues

Brian A — Fri, 11 Sep 2009 10:07:29 GMT

Summary

This article provides information about accessing the system generated log files when encountering error messages during installation.

Applies To

AgilePoint installation
AgilePoint Envision
AgilePoint Enterprise Manager
AgilePoint Server
AgilePoint SharePoint Integration

Symptoms

Error messages are encountered during the installation of AgilePoint. Most common errors are due to insufficient privileges to access and copy files to certain directories, using the gacutil/i, or installing the apsvrmon.exe.

More Information

If you encounter an error message during the installation of an AgilePoint component, log files are generated and can be found at the following locations:

AgilePoint Envision - C:\Program Files\Common Files\Ascentn\1\Installer.log
AgilePoint Developer - C:\Program Files\Common Files\Ascentn\2\Installer.log
AgilePoint Server - C:\Program Files\Common Files\Ascentn\3\Installer.log
AgilePoint Enterprise Manager - C:\Program Files\Common Files\Ascentn\4\Installer.log
AgilePoint SharePoint Integration - C:\Program Files\Common Files\Ascentn\279\Installer.log

Keywords

Installation error message

When will the next version of AgilePoint be available?

Brian A — Tue, 30 Jun 2009 18:50:46 GMT

The information in this article applies to:

AgilePoint Suite

QUESTION(S)
	When will the next version of AgilePoint be available?

SHORT ANSWER
	See below.

ANSWER
	AgilePoint v4.0 is the most recent major release available. The following minor releases, patches, and hotfixes are available: Contact us at support@ascentn.com for more information about this release and for download instructions.

Last Reviewed:
Keywords:

AgilePoint 4.7 Service Pack 1 is now available

Brian A — Wed, 15 Apr 2009 10:45:02 GMT

Summary

AgilePoint 4.7 Service Pack 1
===========================================
Release Date: April 14, 2009

Applies To

The AgilePoint0407ServicePack1.exe Service Pack works only with AgilePoint v4.7. The Service Pack cannot be uninstalled using Add/Remove Programs. However, when installing this Service Pack, all of the files and GAC assemblies that are updated by this Service Pack will be archived under: "C:\Program Files\Ascentn Corp\upgrade\". If for any reason the Service Pack needs to be rolled back, these files can be used to manually restore the system to the state it was in before the Service Pack was applied.

Apply this Service Pack to all machines where any of the AgilePoint v4.7 components are installed.

Enhancements and Fixes

*** AgilePoint Server:
• ReassignWorkItem and CompleteWorkItem with ClientData=null was not working. The application of this Service Pack ensures that if the ClientData parameter is null, then ReassignWorkItem and CompleteWorkItem will work.

• The QueryDatabase and QueryDatabaseEx Web methods have been restricted to have ReadOnly access for enhanced security.

• A workflow stops sometimes if more than two loop routines are executed in parallel. The application of this Service Pack allows for running two loops in parallel.

• AgileWork events were being fired multiple times if the AgileWork had more than one Event handler associated with the same event. The application of this Service Pack ensures that the number of events raised corresponds to the number of Event Handlers.

• AgilePart/AgileWork DLL assembly on a faster server was being loaded in the memory twice. The application of this Service Pack ensures that each DLL only gets loaded once.

• AgilePoint Server does not get the correct HomeDirectory if the Web Service.asmx is in a sub folder. The application of this Service Pack allows for the Web Service.asmx to be embedded in a sub folder.

*** AgilePoint Envision:
• In the Premier stencil, for AgileWorks like WebForm, Workload balancing, etc. there is a "SharePointServer" configuration property that creates tasks on the SharePoint task list. This was not working for AgilePoint SharePoint Integration v2. The application of this Service Pack ensures that the SharePoint configuration property can be used for the AgilePoint SharePoint Integration v2.

• The Vote AgileWork was not working for AgilePoint SharePoint Integration v2. The application of this Service Pack ensures that the Vote AgileWork can be used for the AgilePoint SharePoint Integration v2.

• Process Adaptation’s voting feature was not working for the AgilePoint SharePoint Integration v2. The application of this Service Pack ensures that the Process Adaptation AgileWork can be used for the AgilePoint SharePoint Integration v2.

• The Multiple Condition shape throws an exception when deleting a particular condition. The application of this Service Pack allows for the deletion of a condition in the Multiple Condition activity.

• The UpdateMetadata shape shows a warning message "Metadata name already exists" in Envision when the source and destination lists have the same fields for the item you try to update. The application of this Service Pack handles this condition.

*** AgilePoint SharePoint Integration:
• If you move a list item via process flow, the process flow gets cancelled and a new process flow is starting on the element at the new location. The application of this Service Pack ensures that the existing process is not cancelled and a new process will not be initiated in the target list, also the list item will carry over the information to the target list.

• The Task List now supports multiple Web applications. If you create two different tasks on two different Web applications in SharePoint, and then try to access the task of the other Web application using the Task List Web Part from the current Web application, the task is now accessible.

• If you move a document via process flow, the process flow gets cancelled and a new process flow is starting on the element at the new location. The application of this Service Pack ensures that the existing process is not cancelled and a new process will not be initiated in the target list, also the document will carry over the information to the document library.

• The Process Adaptation link was missing in the Process Viewer for SharePoint Integration v2. The application of this Service Pack ensures that the Process Adaptation link is now visible in the Process Viewer.

• After a process completes, the automatic task created by Windows Workflow Foundation (WF) in the SharePoint Task List should be deleted to improve maintenance. The application of this service Pack ensures that the WF created task is deleted in the SharePoint Task List.

• If a user has "Contribute" privileges and tries to associate an AgilePoint workflow, then the system should allow it, even if the user does not have "Write" access to the configuration list. The application of this Service Pack allows users with "Contribute" privileges to associate an AgilePoint workflow.

• Functionality for allowing OEM partners to add their own custom actions to the SharePoint Task List was missing in the SharePoint Integration v2. This functionality has now been added with this Service Pack.

• The SharePoint Metadata Synchronizer is using the SharePoint root site collection to create an object of Lists.asmx. The application of this Service Pack ensures the system will use the current site collection to create the object.

• The Create List Item and Update List Item shapes have been enhanced to support multiple lines in a field.

• The SharePoint List AgileParts were only working when using a US Date/Time format for date fields. The application of this Service Pack ensures that other Date/Time formats can be used. This has been fixed for both SharePoint Integration v1 and v2.

• An enhancement has been made to support the regular Manual activity shape for ASP.NET based process models and allows tasks to be accessed from within the SharePoint Task List Web Part. This removes the limitation of using only the WebForm shapes for ASP.Net based process models to access Web application tasks through the SharePoint Web Part.

*** AgilePoint Event Services:
• An enhancement has been made to the Event Services to support the option of moving a file to another folder after initiating a process.

• Date/Time format for Event Services for global languages was not supported. There were a few issues with Japanese. The application of this Service Pack ensures that the Date/Time format for Event Services for global languages is supported.

*** AgilePoint Enterprise Manager:
• An enhancement that hides the Process Detail link if a user does not have permission to see this section. A new permission has been added.

• An enhancement that hides the Event Services link if a user does not have permission to see this section. This is based on the Modify/View System Configuration permission.

• License usage for Process Models in Enterprise Manager was calculated incorrectly. The application of this Service Pack fixes the calculation to work properly.

*** AgilePoint InfoPath Integration:
• An enhancement to prevent users from accessing a page through an email link to the InfoPath based task if the task has already been completed. This is specific to InfoPath Forms Services.

*** Miscellaneous Changes:
• Dutch and Japanese localization fixes.

More Information

Send a request to support@ascentn to obtain the AgilePoint v4.7 Service Pack 1.

Keywords

AgilePoint v4.7 Service Pack 1

How to complete a work item in asynchronous web service call with the NeedCallBack property set to true?

Brian A — Mon, 16 Jun 2008 14:00:00 GMT

The information in this article applies to:

AgilePoint Suite
AgilePoint Enterprise Manager
AgilePoint Envision
AgilePoint Developer
AgilePoint Server

GOAL(S)
	Trying to get the asynchronous web service call to work for an activity with NeedCallBack property set to true. Does it require coding and what API should be used?

SUMMARY
	When NeedCallBack is set to true, the activity can only be completed by explicit API call CompleteProcedure(wID).

SOLUTION
	For asynchronous web service calls to work with the NeedCallBack property set to true, the work item will wait for an explicit call back in order to complete. This call back could be from a 3^rd party component which completes the work item explicitly through custom code. In this sceanrio, you will be completing an automatic work item, the API to use is CompleteProcedure(wID) in which work item ID (wID) must be passed in as the argument. NOTE: In order to send the wID, pelase use the $WorkItemID (case sensitive) as one of the Input Parameters.

Last Reviewed:
Keywords:

Tusca Sample Application fails if date format is not MMDDYYYY (En-US)

Brian A — Tue, 19 Feb 2008 11:46:00 GMT

The information in this article applies to:

AgilePoint Tusca Sample Application

SYMPTOMS
	The AgilePoint Tusca Sample Application throws the following error: Server Error in '/TuscaSampleApplication' Application.

CAUSE
	There is custom date parsing code within the AgilePoint Tusca Sample Application that uses the MMDDYYYY (En-US) format. If your machine uses a different date format (e.g. other than En-US) it may cause the AgilePoint Tusca Sample Application to fail.

RESOLUTION
	The Tusca Sample Application is being phased out of the AgilePoint product install.

Last Reviewed:
Keywords:

Retrieve performance tracing data from AgilePoint Server for custom components

Brian A — Thu, 14 Feb 2008 10:56:00 GMT

The information in this article applies to:

AgilePoint Server v4.0 or later

GOAL(S)
	This article provides instructions for reporting on performance tracing data for custom AgilePoint components.

SUMMARY
	AgilePoint Server provides a Performance Tracing utility, allowing you to report on performance of custom components such as custom AgileParts, AgileWorks, AgileConnectors, AgileStubs, or Web Services. The performance citieria is based on milliseconds, for example you can write a query to return the most time consuming AgileParts. This utility requires a new database table as well as the insertion of a configuration file as detailed below.

SOLUTION
	To use this utility, you will need a database that includes a table called WF_PERF_TRACES (it is not recommended to add this table to the AgilePoint database). You will also need to add a PerfTrace.config XML file to the root level folder where AgilePoint Server is installed (e.g. c:\inetpub\wwwroot\AgilePointServer\). The location of AgiePoint Server can be determined from the registry. To use the utility to perform performance tracing: Create a new table called WF_PERF_TRACES in a database as below. It is not recommended to use the AgilePoint database for this table. This SQL can be copied from the attached file. SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [WF_PERF_TRACES]( [SOURCE] [varchar](1024) NULL, [CATEGORY] [int] NULL, [OBJECT_ID] [varchar](256) NULL, [TIME_STARTED] [datetime] NULL, [TIME_SPAN] [int] NULL ) ON [PRIMARY] GO SET ANSI_PADDING OFF A sample query may return results as shown below: Add the PerfTrace.config file to the root level folder where AgilePoint Server is installed (e.g. c:\inetpub\wwwroot\AgilePointServer\). The location of AgiePoint Server can be determined from the registry. You can download the PerfTrace.config file as an attachment to this article. The PerfTrace.config file looks like this: Configure the PerfTrace.config file as follows: a. Within the Database section, enter the database vendor and connection string. b. The Filter section allows you to add the categories for which you want to report on. The categories that are available include: • AgilePart – Reports on all AgilePart data. • ProcessEventHandler – Reports on AgileWork and AgileStub data. • TrackingEvent – Reports on AgileConnector data. • WebService – Reports on Web Service data. When doing the reporting, a few of the filtering options that are available include: • Exclude Categories - To exclude one or more of the categories, remove the category from the PerfTrace.config file. For example, remove the <Category>WebService</Category> to tell AgilePoint Server to exclude Web Service tracing data from being recorded to the database. • When writing your SQL, each category has been assigned a numerical identifier for filtering. This allows you to report only on a certain category. Each category is identified as follows: AgilePart – 0. ProcessEventHandler – 1. TrackingEvent – 2. WebService – 3. A couple of sample query statements are shown below: select * from WF_PERF_TRACES where source like '%Sample%' order by time_span desc select * from WF_PERF_TRACES where category = 0 and source like '%Move%' order by time_span desc A sample query may return results similiar to below: NOTE: It is not necessary to restart IIS upon making changes to the configuration file. AgilePoint Server will begin recording this tracing data to the database within 10-30 seconds. You can delete this file or rename it to stop this service.

Last Reviewed:
Keywords:

Use Active Directory as the source of AgilePoint user information

Brian A — Thu, 13 Sep 2007 10:17:00 GMT

The information in this article applies to:

AgilePoint Suite
AgilePoint Enterprise Manager
AgilePoint Envision
AgilePoint Developer
AgilePoint Server

GOAL(S)
	Describe several ways in which Active Directory (AD) can be integrated with AgilePoint.

SUMMARY
	AgilePoint supports enterprise level user/role/group management that can easily integrate with and link to Active Directory, domain user database, LDAP, etc. Three different methods for integrating AgilePoint with Active Directory are described below.

SOLUTIONS
	Two different methods for integrating AgilePoint with Active Directory are described below: A) In AgilePoint Enterprise Manager, you can connect to your AD remotely and selectively reuse the user credential info from your AD by associated username and email address to AgilePoint. Only the users that are associated with AgilePoint will have access to AgilePoint. B) AgilePoint can run a daemon module to monitor the 'subset' of AD users that will be granted access to AgilePoint and dynamically update the association when changes are made to the AD.

Last Reviewed:
Keywords:

Process instance becomes automatically suspended during loop

Brian A — Mon, 27 Aug 2007 18:58:00 GMT

The information in this article applies to:

AgilePoint Suite

SYMPTOMS
	A process instance becomes automatically suspended during a loop.

CAUSE
	If you are encountering a process instance becomming automatically suspended it may be due to a configuration where the maximum number of loops has been exceeded. The Max Loop is the number of times a process instance can loop back to the previous activity. The maximum number of sessions for an activity is set to 50 by default. Once a process instances loops back the 51st time, the process instance will become suspended.

RESOLUTION
	In some cases, you may have a special need to have more than 50 sessions, in this case, open the netflow.cfg file (in the root folder where AgilePoint Server is installed) in Notepad, and change the value for maxLoop to a higher value, and then save the file. NOTE: Reset IIS upon making changes to the netflow.cfg file. NOTE: This has to be done manually because currently there is not a user interface to change this setting.

Last Reviewed:
Keywords:

Upgrade Instructions for 3.2.x to 4.0

Brian A — Thu, 23 Aug 2007 10:25:00 GMT

The information in this article applies to:

AgilePoint Suite Upgrade

TOPIC(S)
	The attached document provides the information necessary for upgrading your existing v3.2.x installation of AgilePoint to v4.0. AgilePoint v4.0 requires the .NET 2.0 or 3.0 Framework. This upgrade procedure upgrades any existing AgilePoint 3.2.x version (.NET 1.1) assets to v4.0 (.NET 2.0).

SUMMARY
	This document specifically focuses on two main upgrade scenarios: Upgrading the .NET 1.1 based edition of AgilePoint v3.2.x to the .NET 2.0 based edition of AgilePoint v4.0. Upgrading the AgilePoint SharePoint 2003 Integration to the AgilePoint v4.0 (MOSS 2007) Integration.

DETAILS
	See attachment.

Last Reviewed:
Keywords:

View InfoPath XML Data on Data tab in Enterprise Manager

Brian A — Tue, 07 Aug 2007 11:41:00 GMT

The information in this article applies to:

AgilePoint Enterprise Manager

GOAL(S)
	To provide instructions for making available the Click to view XML data link on the Data tab in Enterprise Manager.

SUMMARY
	For MS InfoPath based processes, you can view additional XML data from the InfoPath form via the Data tab in Enterprise Manager.

SOLUTION
	In order to access this information, you must add a line to the Enterprise Manager Web.config file located at C:\AgilePoint\EnterpriseManager. <add key="ShowXml" value="true" /> After adding this line, you will now see the Click to view xml data link. On the Data tab, click the Click to view xml data link. The XML of the MS InfoPath form is displayed in a browser window.

Last Reviewed:
Keywords:

Error message: Column Document_NavUrl does not belong to table

Brian A — Mon, 14 May 2007 11:59:00 GMT

The information in this article applies to:

AgilePoint SharePoint Integration
AgilePoint InfioPath Integration

ERROR
	"Column Document_NavUrl does not belong to table.”

STEPS TO REPRODUCE
	In the AgilePoint - Document Control Task List Web Part for SharePoint, click the down-arrow and select Modify Shared Web Part. Uncheck the Document list item. Run an InfoPath Form based process and notice error message "Column Document_NavUrl does not belong to table.” appears when trying to pop-up the form.

DETAILS
	The “Document” column in the task list is required (visible) in order to pop-up the InfoPath Form for an InfoPath based process. If the Document column is hidden, (check box is unchecked), the Document and Document_NavUrl columns is not created when generating columns for the datagrid and the error message “Column Document_NavUrl does not belong to table.” is displayed.

Last Reviewed:
Keywords:

My evaluation key is expiring, can I get an extension?

Brian A — Mon, 14 May 2007 10:10:00 GMT

The information in this article applies to:

AgilePoint Envision
AgilePoint Developer
AgilePoint Server

QUESTION(S)
	My evaluation key is expiring, can I get an extension? My evaluation key is expiring, can I extend the key? Can I extend the duration of my product evaluation period?

SHORT ANSWER
	If you want to continue your evaluation, please contact Ascentn support (support@Ascentn.com) for an evaluation extension. If you want to convert your evaluation keys into actual product license keys, please contact sales@ascentn.com.

ANSWER
	Before your keys are expiring you will receive warning messages in pop-up dialogs. If you want to continue your evaluation, please contact Ascentn support (support@Ascentn.com) for an evaluation extension. You will receive new evaluation license keys. When a product is expired, just type in the corresponding new license key and activate the product again. You will not need to un-install and re-install the product. If you want to convert your evaluation keys into actual product license keys, please contact sales@ascentn.com.

Last Reviewed:
Keywords:

How long can I use an evaluation key?

Brian A — Mon, 14 May 2007 10:08:00 GMT

The information in this article applies to:

AgilePoint Envision

AgilePoint Developer

AgilePoint Server

QUESTION(S)
	How long can I use an evaluation key? When do evaluation keys expire?

SHORT ANSWER
	Evaluation keys expire after 30 days.

ANSWER
	Currently our evaluation keys allow you to use the products for: • AgilePoint Server: 30 days • AgilePoint Envision: 90 times • AgilePoint Developer: 90 times

Last Reviewed:
Keywords:

What are all of the shapes in Envision diagrams?

Brian A — Wed, 14 Mar 2007 14:04:00 GMT

The information in this article applies to:

AgilePoint Envision

QUESTION(S)
	What are all of the different shapes in Envision diagrams? What are the different activities that can be used in AgilePoint Envision process templates/diagrams?

SHORT ANSWER
	Each shape in an AgilePoint Envision process template represents an activity or workflow state. The collective name for all of these shapes is AgileShape. See below for more information about the standard AgileShapes that are built into AgilePoint Envision.

ANSWER
	Below is a list of the standard Envision shapes/activities. Generic BPM shapes: Start - Represents the starting point of a process. This AgileShape is activated when a process instance is initiated, and can never be re-entered. A process template must contain exactly one Start AgileShape. Procedure - An activity that is tied to a system task and performed on the server side. In general, an automated activity is for performing a task between two or more systems such as application integration. Examples of automated activities include generating a report at the end of a process, updating database when a request is approved, etc. AgilePoint provides various ways to integrate with, synchronously or asynchronously, through C#, VB.NET, managed C++, COM, XML Web Service, Messaging queue, etc. IMPORTANT NOTE: This AgileShape should only be used within process templates that are (or will be) associated with an AgileStub (created using AgilePoint Developer). NOTE: The AgilePart and WebService AgileShapes do not require the creation of an AgileStub, and can often be used instead of this AgileShape. Procedure with Timeout - This AgileShape is identical to the Procedure AgileShape, except that it has one additional design-time property, and one additional Output connection. These two differences allow the process modeler to model the portion of the process that should occur should the activity become overdue (i.e. is not completed within the specified TimeSpan). This AgileShape is typically used to represent a procedure activity that requires a time-based escalation process. Manual - An activity that is associated with a user interface (such as Web Form, Win Form) to perform human task. A manual activity requires set up of task type, participant, and schedule to generate task at runtime and prompt for human intervention. For instance, a manual activity may be to prompt a user interface at run time for placing an order, approving a request, submitting or reviewing a document, etc. Manual with Timeout - This AgileShape is identical to the Manual AgileShape, except that it has one additional design-time property, and one additional Output connection. These two differences allow the process modeler to model the portion of the process that should occur should the activity become overdue (i.e. is not completed within the specified TimeSpan). This AgileShape is typically used to represent a manual activity that requires a time-based escalation process. SingleCondition - A conditional logic activity that branches into two routines determined by a Boolean value. For example, the approval status of a request. MultipleCondition - A condition activity that can branch into more than two routines determined by a primitive data type such as: integer, number, date, and string. Various operators such as Equals, Greater Than, contains, etc., are supported to enable the most sophisticated process dynamics. You can use the Multiple Condition AgileShape to determine whether a String value is null by using the operator "Equals" and entering the value as "<NULL>" (without the quotes). SubProcess - When entered, this AgileShape will initiate another process instance as a subprocess. Email - An activity that specifies an email notification. Or - An activity that associates multiple activities with the Or condition. Successful completion of one or more of the associated activities will result the start of the exit activity of the Or condition activity. And - An activity that associates multiple activites with the And condition. All associated activities must be completed successfully before the start of the exit activity of the And condition activity. AgilePart - This is a generic AgileShape that can be associated with any AgilePart that is registered in AgilePoint Envision. The user will be prompted to select a specific AgilePart when this AgileShape is added to a process template. NOTE: Custom AgilePart components must be registered in AgilePoint Envision before they can be used in a process template. See the AgilePoint Envision section for additional information about registering an AgilePart. AgileWork - This is a generic AgileShape that can be associated with any AgileWork that is registered in AgilePoint Envision. The user will be prompted to select a specific AgileWork when this AgileShape is added to a process template. NOTE: Custom AgileWork components must be registered in AgilePoint Envision before they can be used in a process template. See the AgilePoint Envision section for additional information about registering an AgileWork. Stop - Represents the ending point of a process. A process template must contain exactly one Stop activity. Premier Extension shapes: Web Service - An AgilePart activity that accesses a Web Service and its methods which are registered in AgilePoint Envision. User can select the appropriate Web Service and its specific method using the Web Service shape. BRE - An activity that accesses BizTalk Rules Engine and its policies which are registered in the AgilePoint Envision. User can select the appropriate BizTalk Rules Engine and its specific policies using the BRE shape. Delay - This AgileShape can be used to force the process to pause (for a specified length of time, or until a specified date) before allow the process to continue to the next AgileShape. Insert Database - This AgileShape can be used to insert a new database record into a database table. Batch Insert - This AgileShape can be used to insert multiple new database records into a database table. It can also be configured to delete certain records before the new records are inserted. Update Database - This AgileShape can be used to update multiple existing database records in a database table. Delete Records - This AgileShape can be used to delete multiple existing database records in a database table. Stored Procedure - This AgileShape can be used to execute dynamic query statements and/or call database stored procedures. NOTE: This AgileShape does not support capturing return values or output parameters. Refer to the Query Database AgileShape for retrieving data from the database. Query Database - This AgileShape can be used to execute dynamic query statements and/or call database stored procedures in order to retrieve data from the database. Cancel Tasks - This AgileShape can be used to cancel all Assigned and Overdue tasks. Update Parent Process - This AgileShape can be used to update the values of one or more custom process attributes in a separate process instance. WebForm - This AgileShape can be used to represent a manual (i.e. human input required) activity that uses a web page as the user interface for the activity. NOTE: This AgileShape may only be used when working with a Generic process template. Dynamic Sequential Approval - This AgileShape can be used to represent a Manual (i.e. human input required) activity that must be completed sequentially by 1 or more participants. It is designed to be used as part of a “loop” in a process, so that the process flow will keep returning to this AgileShape until a sufficient number of participants have completed the activity (or until some other condition exits the loop). The UI associated with the Task determines where the value(s) associated with the UI are stored (e.g. an Approval value). Dynamic Parallel Approval - This AgileShape can be used to represent multiple manual (i.e. human input required) activities that must be completed simultaneously (or in parallel). Vote - This AgileShape can be used when a group of approvers is involved at an activity step, you can configure the AgileWork to require mandatory approvals from certain participants and to move forward based on a certain percentage of approves that have approved. Workload Balance - This AgileShape can be used when a work group defined in AgilePoint Server is responsible to complete a particular Manual Activity. Assume only one participant is needed to complete the task each time. This WorkLoad Balance AgileWork assigns the work item to the participant with the least amount of work items in the work group. The selection criteria is based on the least amount of work which is the sum of assigneded and overdue tasks. If all the participants in the group have the same work load, then the WorkLoad Balance AgileWork will pick a participant at random. Update Custom Attributes - This AgileShape can be used to update the runtime value(s) of one or more custom process attributes. When using this shape, you specify the name(s) of one or more custom process attributes, and associate a snippet/fragment of C# code with each attribute name. At runtime, each snippet will be executed/evaluated to determine the value that will be assigned to the associated custom process attribute. This AgileShape essentially allows you to create and embed a simple “custom AgilePart” in your process, without actually having to create, name, compile, deploy, or register the AgilePart. NOTE: In developer terminology, each “snippet” must be a valid C# expression that will return a value that can be stored in a custom process attribute. Advanced Extension shapes: External Command - Used to define environment variables and run a command prompt. Java - Used to execute Java components. Sequential Workflow - This AgileShape can be used to expose your Microsoft Windows Workflow Foundation assets at the AgilePoint process layer. CSharp - This AgileShape can be used to add managed custom code using the C# coding language. VB - This AgileShape can be used to add managed custom code using the Visual Basic coding language. Microsoft SPS shapes: New Site - Used to create a new site by specifying site title, site url as well as the site template such as STSAP for AgilePoint Team Site template. New Form Library - Used to create a new form library. New Library - Used to create a new document library New Folder - Used to create a new folder using an absolute URL. Download Files - Used to download files from a SharePoint library to a local file system. Upload Files - Used to upload file from local file system to SharePoint library. Copy Files - Used to copy files from a folder/library to another folder/library. Move Files - Used to move a file from a folder/library to another folder/library. InfoPath Sub Process - This AgileShape is used to provide the flexibility to associate different InfoPath forms for each Sub Process in a particular process. Submit - A manual activity with the Work To Perform property set to Submit. Approve - A manual activity with the Work To Perform property set to Approve. Publish - A manual activity with the Work To Perform property set to Publish. Approved - A single condition activity used to check the custom attribute of Approved. Portal Listing - Used to create a portal listing for a document. Update InfoPath - Used to update an InfoPath Form with XML data. InfoPath View - This AgileShape can be used to represent a manual (i.e. human input required) activity that uses a view of a Microsoft InfoPath form as the user interface for the activity. NOTE: This AgileShape may only be used when working with a Microsoft InfoPath process template. NOTE: This AgileShape may only be used with a Microsoft InfoPath form based on managed code (i.e. not JScript).

Last Reviewed:
Keywords:

Can't access SharePoint site after installation

Brian A — Tue, 21 Nov 2006 11:16:00 GMT

The information in this article applies to:

Microsoft SharePoint

SYMPTOMS
	Receive Internet Explorer Security dialog when trying to launch SharePoint. NOTE: The following steps are only recommended when setting up the Ascentn Financial Site application in an AgilePoint evaluation environment. Consult your SharePoint Administrator when installing for other purposes (e.g. production environment installations).

CAUSE
	The SharePoint site is not yet part of the Trusted sites in Internet Explorer.

RESOLUTION
	Launch the SharePoint main page (http://Machine_Name:Share_Point_Port_Numer/default.aspx) in Internet Explorer. The Internet Explorer Security dialog appears as shown above. Click Add. The Trusted Sites dialog appears. In the Add this web site to the zone field, type in http://Machine_Name (the machine name that hosts the SharePoint Portal Server). Make sure Required server verification (https://) for all sites in this zone is unchecked and click Add, then Close. If your company policy prevents you from adding the SharePoint site to the Trusted Sites, you should first find out if you are accessing SharePoint using Internet or Local Intranet. (You can find out by accessing the SharePoint site and looking at the status bar at the bottom of the IE window, which will indicate if you are running SharePoint using Internet, Local Intranet, or Trusted. Depending on which mode you use to access SharePoint, change the Internet Security Settings for that mode by following these steps: Click Tools > Internet Options > Security > and click on the Custom Level button. Under Reset to, choose Low. Click Reset and then Yes. Under Settings, make sure the settings below are enabled: Under ActiveX controls and plug-ins: Download unsigned ActiveX control Initialize and script ActiveX controls not marked as safe Under Miscellaneous Allow scripting of Internet Explorer Web browser control Submit nonencrypted form data Under Scripting Active scripting Under User Authentication > Logon Automatic login with current username and password Click OK then Yes.

Last Reviewed:
Keywords:

What databases are supported by AgilePoint?

Brian A — Tue, 26 Sep 2006 16:06:00 GMT

The information in this article applies to:

AgilePoint Suite

QUESTION(S)
	What databases are supported by AgilePoint?

SHORT ANSWER
	See below.

ANSWER
	AgilePoint Server maintains all process-related data in a relational database. The databases currently supported are: SQL Server 2000 SQL Server 2005 Oracle 8i Oracle 9i Oracle 10g (Support comming in 2007) DB2 (Support comming in late 2006) AgilePoint Envision includes out-of-the-box AgileParts for querying, inserting, updating, and deleting data to/from relational databases. The databases currently supported by these AgileParts are: SQL Server 2000 SQL Server 2005 Oracle 8i Oracle 9i Oracle 10g (Support comming in 2007) DB2 (Support comming in late 2006)

Last Reviewed:
Keywords:

How to find out what version of an AgilePoint component is installed?

Brian A — Tue, 26 Sep 2006 14:49:00 GMT

The information in this article applies to:

AgilePoint Suite
AgilePoint Enterprise Manager
AgilePoint Envision
AgilePoint Developer
AgilePoint Server

GOAL(S)
	Find out the version of the installed AgilePoint product.

SUMMARY
	The installed version can be found from Control Panel > Add or Remove Programs.

SOLUTION
	The best way to find the version of your installed AgilePoint products is to go to the Control Panel > Add or Remove Programs. First, look for any items with a name like "AgilePoint ... Upgrade". These represent version upgrades. E.g. In the image below, the original version of AgilePoint was upgraded to "AgilePoint 3.2.0 Build(1006)". Next, select the specific AgilePoint component that you want to determine the version for, then click on the ‘Click here for support information’ link and the original version number will be shown in the Support Info dialog. For example, in the following screen shot 3.1.6.4 is the originally installed version of the AgilePoint Developer component.

Last Reviewed:
Keywords:

The Process Viewer is not correctly mapping workflow activities with the associated status indicators

Brian A — Fri, 15 Sep 2006 15:16:00 GMT

The information in this article applies to:

AgilePoint Process Viewer

SYMPTOMS
	There is an issue with the Process Viewer not correctly mapping workflow activities with the associated status indicators.

CAUSE
	1. In Envision, check to see if any portion of the process model (shapes, lines, text, graphics, etc.) extends beyond the "page" borders? 2. Check to see if the process model contains any specific "non-AgilePoint" or custom Visio shapes (such as text bubble graphics)?

RESOLUTION
	Ensure that no portions of the process model extend beyond the page borders by moving all portions of the model into the page area. You can use the "Shape > Actions > Page Size" menu command to increase the page size. If the page size/boundaries aren't an issue, then try removing any text bubbles or any other similar shapes/graphics, and see if that resolves the issue. The Process Viewer's graphics rely on the coordinates within the VSD file, and it is possible that some custom shapes or graphics could modify or corrupt the coordinates in the VSD file. Also, if the process modeler did anything else to the model that might potentially affect shape coordinates (e.g. rotating or flipping shapes, or resizing shapes) and that hasn't been done in other models not affected by this issue, then you might need to try removing and then replacing any shapes that were modified in such a way to see if such actions are the cause.

Last Reviewed:
Keywords: