Table of Contents

Known Bugs and Limitations

Known limitations of AwareIM, with the workaround for each where one exists.

Applicability Rules & IS UNDEFINED

Problem/Limitation Description

Using IS UNDEFINED in an applicability rule will not have the expected results when the attribute is a reference attribute. 

Event.Organiser IS UNDEFINED

Work Around

Refer to an attribute on the reference attribute instead 

Event.Organiser.ID IS UNDEFINED

 

Arithmetic In Find

Problem/Limitation Description

Arithmetic operations with dates are not supported in FIND action, for example using the following will not work: 

FIND Account WHERE Account.Date=CURRENT_DATE-1

Work Around

Use functions with dates (such as DATE_ADD) instead of arithmetic operations, for example: 

FIND Account WHERE Account.Date= DATE_ADD(CURRENT_DATE,-1)

 

Functions Exclusive To Cloudbase Derby

Problem/Limitation Description

The following functions are supported only in Cloudscape/Derby database:
WORD_NUMBER
WORDS_FROM_LEFT
WORDS_FROM_RIGHT

Work Around

None

 

Function Limitations In Subqueries

Problem/Limitation Description

MIN, MAX and AVG expressions are not supported if used in subqueries on groups. For example the following query is not supported if Transaction is a group: 

FIND Account WHERE  (COUNT Transaction WHERE (MAX.Transaction.Amount = 1000))

Work Around

Avoid using these expressions in subqueries

 

Loss Of LAN Connection

Problem/Limitation Description

If the AwareIM Server is started when either LAN or Internet connection is up and then either LAN goes down or Internet is disconnected, the server goes down too

Work Around

Start the AwareIM Server within the configuration that you intend to work with. For example, if you only use dial-up Internet connection occasionally make sure that you start the AwareIM Server first and then connect to the Internet. This way when you disconnect from the Internet AwareIM will continue to work properly.

 

Printing HTML Documents From Rules

Problem/Limitation Description

Printing of documents of HTML type from rules is not supported

Work Around

None

 

Report Summary Pane Resizing In Mac

Problem/Limitation Description

If you drag the bottom line of the Summary pane in the Report Designer the height of the Summary band is not changed even though it appears visually that it is.

Work Around

Change height of the Summary band using Band Properties – see Setting Band Properties

 

Report Band Resizing In Mac

Problem/Limitation Description

Dragging bands in Report Designer to change their height is not supported on Mac OS X

Work Around

Hold down Apple key and click on the band’s header to bring up the bands property dialog. Specify the height of the band in the dialog

 

Required With Owned By References

Problem/Limitation Description

If two business objects are related through a parent/child relationship (see Reference Attributes) and the reference attribute to a child is defined as “Required” it is impossible to add a new child instance from a form of the parent instance using Add New button (see working_with_references_in_the_operation_mode)

Work Around

Do not force “Required” flag for reference attributes or create child instance first and then add it to a parent using Add button.

 

Sorting References In Business Object Group Queries

Problem/Limitation Description

Sorting on reference attributes in a query will not work if query searches business object group. For example, sorting in the following query will not work if Account is business object group: 

FIND Account ORDER BY Account.Owner.Name

Work Around

Define a shortcut attribute and sort by it, for example: 

FIND Account ORDER BY Account.OwnerName

Where OwnerName is the shortcut to Account.Owner.Name

 

Undefined With Multiple References

Problem/Limitation Description

Checking for UNDEFINED value of a multiple reference attribute (see Reference Attributes) in queries does not work correctly. For example, the following will not work: 

FIND Account WHERE Account.Transactions IS UNDEFINED

Work Around

Use EXISTS or COUNT expressions, for example 

FIND Account WHERE COUNT Transaction WHERE (Transaction IN Account.Transactions) = 0

 

Unsupported Functions In Queries

Problem/Limitation Description

The following functions and expressions are not supported if used in queries:
WAS CHANGED
WAS CHANGED TO
TYPE
OLD_VALUE

Work Around

None

 

Use Of IN With Complex Identifiers

Problem/Limitation Description

IN expressions using complex identifier of the reference list are not supported if used in subqueries. For example, the following query is not supported: 

FIND Client WHERE  (COUNT Account WHERE (Account IN Client.Carrier.Accounts) > 3)

Note that the following query is supported: 

FIND Client WHERE (COUNT Account WHERE (Account IN Client.Accounts)>3)

Work Around

Avoid using such constructs in queries