Change the Instance Web Page Title

To change 3e's web page title, change the value of the PageTitle key in the WebUI config file <func directory>\Inetpub\WebUI\Web.config.

Text and variables can be used, including:

• [User] (displays current user name)
• [Version] (3e instance version)
• [WebServer] (name of the that served up the current page)
• [Title] (name of the 3e object being displayed; Dashboard, Report, Process, etc.)
• [DBServer] (name of the SQL server hosting the current database)
• [DBCatalog] (name of the current database)

Examples:
<add key="PageTitle" value="3E TRIAL [Version]" />

<add key="PageTitle" value="[WebServer] [User] [Title] [DBServer] [DBCatalog] [Version]" />

Dashboard Edits Not Saving

When editing a dashboard, for changes to save correctly the WebUI site must have a config WorkingMode value set to "Production" (rather than "AppDevelopment").

Otherwise after saving a dashboard the page refreshes to its previous state and any edits are lost.

To change the setting, open the config file: [INSTANCE_DIRECTORY]\Inetpub\WebUI\Web.config and change
<add key="WorkingMode" value="AppDevelopment" />
to
<add key="WorkingMode" value="Production" />.

Exception Raising

The standard method of raising exceptions in 3e is to display them in the top Exception panel - the panel shared with other item lists such as the Worklist.

Exception raised in Proforma Generation Process

To raise an exception in this way, the Exception property of the Process's underlying Object must be set to an instance of the NxApplicationException class. For example, from within the Object:
Me.Exception = New NxApplicationException(New Guid("430e4f35-2834-46ea-b031-b718054c7f62"))

Or from a Process:
Me.ProfMaster.ProformaCollection(0).Exception = New NxApplicationException(New Guid("430e4f35-2834-46ea-b031-b718054c7f62"))

The GUID value is set to the Id of a Message that describes the error.
To remove the Exception, set the Exception property to null:
Me.Exception = Nothing

BillSum Table Rebuild

The BillSum table is a snapshot of all billing information per Timekeeper and Matter. It is effectively a non-live amalgamation of the Timecard, Costcard and Chargecard tables. It is updated periodically but can become out of date and inaccurate due to various errors in the system.

To rebuild the BillSum table take the following steps, courtesy of Weronika Kozlowska, Application Support Consultant at Elite Thomson Reuters UK:

1. Go to Notification task Manager > select the BillsumMsgQueue task > tick the 'Disable' option and release

2. Go to the Build Billsum Tables process > tick all 4 month / period options > Background > Release

3. After a while, go to Notification Task and Log viewer and click the 'View Background Tasks' button you will see your process initally with a 'Running' status > periodically check whether the status changes to 'Complete' (It might take a few hours)

4. Once the task is complete, go back to Notification task Manager > select the BillsumMsgQueue task un-tick the 'Disable' option and release.

If you have a period of the day/week when no billing information (time, costs, charges) is ever captured, late at night or early morning for example, the Build Billsum Tables can be scheduled to run automatically via the Notification Task Manager process. The BillsumMsgQueue task need not be disabled first if you are confident no billing information will be captured during the run time. Note that the Build Billsum Tables task can take several hours to run.

Right-Click Cancel on Processes

Right-clicking on a Process in My Action List shows a handy Cancel pop up menu. Using this short cut can be much quicker than opening the Process and then cancelling from within a new page.

Cancel a Process from the Action List

For a right-click cancel to work, the Process must contain a path that leads to an end point without intervening steps.

Right-click cancel possible - A Process with a route to an end point with no steps (the bottom "Cancel" route)

Right-click cancel not possible - A process without a "no-step" route to a end point 

When a Process does not contain a route without intermediate steps, an error is show when attempting to cancel from the Action List.

Error message from a failed right-click Process cancel

However, intermediate steps are sometimes required when cancelling a Processes to perform certain tasks or return to a previous state. Unlocking records or freeing up resources for example. Rather than adding a step and preventing a right-click Action List cancel, the code that would be in the step can be written in the Else rule before the end point.

The Else rule (selected in blue) before the end step

This way, clean-up functionality can still run when the user cancels from the Action List.

Adding New Bank Accounts

If a new Bank Account is needed, other dependencies may need to be created first. The order in which to add these dependencies is as follows:

• Bank Group
• Unit (if a new unit is requried)
• GL Unit (if a new unit is requried)
• GL Natural
• GL Account
• Bank Account (Either Bank Account Client Account or Bank Account AP (Office))